A dockerized deployment of all the uport dependencies
CapGemini has published a writeup on how to deploy a private Ethereum network using Docker compose. https://github.com/ethereum/go-ethereum/wiki/Running-in-Docker
To run an Ethereum Docker cluster run the following:
docker-compose up -d
By default this will create:
- 1 Ethereum Bootstrapped container
- 1 Ethereum container (which connects to the bootstrapped container on launch)
- 1 Netstats container (with a Web UI to view activity in the cluster)
To access the Netstats Web UI:
open http://$(docker-machine ip default):3000
docker-compose scale eth=3
Will scale the number of Ethereum nodes upwards (replace 3 with however many nodes you prefer). These nodes will connect to the P2P network (via the bootstrap node) by default.
We can use the official go implementation
https://github.com/ipfs/go-ipfs
The fueling server, Sensui, helps new users of Ethereum overcome the initial hurdle of needing to purchase Ether to pay the fees needed to use the network. Sensui works to alleviate this problem by paying the gas fees for the user, permitting the user to create a new uPort and get up and running immediately. The Sensui server works by utilizing the account based infrastructure of the Ethereum network. Suppose a user wants to send a transaction but they have no Ether in their sending account. The user signs the transaction as they normally would, then sends the signed transaction to the Sensui server. The server verifies that the sending account does not have enough Ether to pay for the gas, sends enough Ether to the account to pay the fees, and finally sends the user-signed transaction to the network.
There is no public reference implementation of this server.
The messaging server, Chasqui, is in charge of communication from a desktop-based decentralized application frontend to and from the mobile app. A uPort user will initially connect to a dapp by scanning the "connect with uPort" QR code. This code contains a session ID that is shared between the mobile app and the dapp frontend. When connecting with uPort the dapp frontend shows the QR code and will then poll the Chasqui server for a uPort identifier posted to the session ID. The mobile app will post the identifier and this is then immediately picked up by the dapp frontend. Similarly when sending a transaction via the mobile app the dapp will poll the Chasqui server for a transaction hash. Once the transaction hash has been posted the dapp can immediately show that a transaction has been sent and update the UI accordingly. Note that the Chasqui server is not used when the decentralized application is run in a mobile browser.
There is no public reference implementation of this server.