DApp and bot for Status.im

Hackathon GitHub Issue: status-im/hackathon#13

{"whisper-identity": "13-registereth-bot",
  "name":             "#13 RegisterEth Bot",
  "bot-url":          "https://adamdossa.github.io/RegisterEthBot/public/bot/bot.js"}

NB - this bot needs @rasom latest fixes from:
https://github.com/rasom/status-react/tree/jail-improvements
I have added the relevant .apk that @rasom provided to my submission.

Video Demo:
https://youtu.be/ebUiV_DWTNE

RegisterEthBot (Status Hackathon)

This bot facilitates communication with a collection of Smart Contracts (deployed on the Ropsten Ethereum blockchain).

This collection of Smart Contracts allows users to associate their Ethereum addresses with a number of different social network handles.

Currently implemented are Registrar contracts for Reddit, Github & Twitter - the framework provides straightforward interfaces to allow other new Registrar contracts to be implemented for additional social networks.

Registration

Registration is a two step process.

Step one generates your proof-of-handle by posting your Ethereum address from your social media network.

Step two is sending a blockchain transaction with that proof-of-handle. The Registry smart contract delegates validation of your proof-of-handle to a Registrar specific to the social media network. Generally this will use oraclize.it to validate your proof-of-handle off-chain.

The proof-of-handle varies depending on the social media network - currently we have implementations for Twitter, Github and Reddit. It is easy to add new registrars for additional social media networks!

Post your Ethereum address using your social media handle. For the currently implemented registrars this involves:

Twitter: tweet out your Ethereum address from your twitter handle.
Your twitter handle is then your proof-of-handle.
Reddit: post to /r/ethereumproofs a message containing your Ethereum address.
The little hash in the URL linked to your post is your proof-of-handle.
e.g. for:
https://www.reddit.com/r/ethereumproofs/comments/6gkk1w/0xdaf383e889e15e3615db17d1f86422f2bda539f2/
your proof-of-handle would be 6gkk1w
Githib: create a public gist with your Ethereum address in the description.
The generated gist ID of your gist is your proof-of-handle.
e.g. for:
https://gist.github.com/adamdossa/cbcc239a915800bfc96d60f1f8ceeb45
your proof-of-handle would be cbcc239a915800bfc96d60f1f8ceeb45

Send a transaction from your Ethereum address to the Registry contract, along with your proof-of-handle which is used by the relevant Registrar contract to validate your proof.

Architecture of Smart Contracts

There is a single Registry contract (implementing the RegistryI interface). This contract is responsible for holding mappings between Ethereum addresses and social media handles (partitioned by social media network, e.g. Reddit, Twitter).

The Registry contract allows Registrar contracts (implementing the RegistrarI interface) to register with it. A Registrar contract is specific to a given social media network, and is responsible for implementing behaviour necessary to prove that a given social media handle owns an Ethereum address. Usually this is done via an Oracle service (using Oraclize) to check the evidence provided in 1. above.

When a user wishes to register a new social media handle, they would call the Registry contract specifying their proof (used by the Registrar contract to check 1. above).

The Registry contract can then be used to query your handles, and the handles / Ethereum addresses of other users.

Status Bot

It is possible to issue the following commands:

/details - shows the details of how to generate the proof from 1. above for each of the Registrars (currently Reddit, Github & Twitter).

/whoAmI - shows your social media handle (if registered previously).

/status - shows the most recent event issued by the Registry contract that relates to your address. Can be used to track the status of your registration request(s).

/register - allows you to register your Ethereum address with any of the provided registrars.

/nameToAddress - shows the Ethereum address associated with a provided social media handle.

/addressToName - shows the social media handle associated with a provided Ethereum address.

Deployment - Smart Contracts

We need to deploy our smart contracts - this is done via the truffle framework:

truffle compile - this will check our smart contracts compile and generate associated .json files.
truffle migrate - this will deploy our contracts onto whichever Ethereum network is configured in truffle.js
truffle test - this will execute tests against the contracts. Note - this needs to be run on testrpc.

NB - for the purpose of the Status Hackathon, we need to deploy our contracts to the Ropsten network as bots can only communicate with contracts on this network (i.e. they can't use testrpc).

Deployment - RegisterEthBot

This assumes you are using an Genymotion as your Android emulator:

Start Genymotion and Android emulator (following instructions as per Status documentation).
Open the Status app (if you've downloaded the latest nightly build .apk file, this can be dragged onto the Android emulator within Genymotion).
Log in / create a new user within Status, and in the Console app (in Status) execute /debug On.
In a terminal run status-dev-cli scan. You should see a couple of IP addresses - ignore the one which has "56" in it, and use the other below in place of .
In a terminal run status-dev-cli add --ip <IPADDRESS> to add your bot to your Status app running in the Genymotion emulator.

Contract Addresses

Registry: 0x195647cca7be636e03eee0af20b21745d06d7d12

RedditRegistrarComputation: 0x4237b97cf9a566d67b6ac254e2fc9cd645109e75

GithubRegistrarComputation: 0x86fb059a34fc326130a2a4ac274447559837dfa0

TwitterRegistrarComputation: 0x147cdec28faa359fcea7b83cae75e13d7996e93f

adamdossa/RegisterEthBot