Formally Outline Current Application Flow

[ansermino]

We need a more formal and detailed outline of the full stack flow in its current state. There are some drawings and text in the existing README.md. Some aspects may still be undefined. We should aim to be as detailed as possible. Here is an existing description for some guidance: https://gist.github.com/ansermino/20c6eb65a9bbb73d1a5e2e6b3aeb5fc1

Some points to focus on:

• [ ] Registration/connecting a new node
• [ ] Establishing which nodes are up and providing valid data (#11 )
• [ ] Dealing with bad nodes
• [ ] Registering new users
• [ ] Establishing a connection to the network
• [ ] Paying out nodes

[ChainSafeSystems]

@noot has started implementing a registration contract https://github.com/ChainSafeSystems/denode/tree/elizabeth/contracts

[ChainSafeSystems]

potential architecture for paying out nodes utilizing state channels. The main problems this solves is twofold.

• 1. micropayments for an amount of calls depending on the type of subscription.
• 2. dispute mechanism for settling discrepancies between nodes and users.

@noot and I have done some preliminary research and have begun playing around with connext.network

@ansermino please review this and let us know your thoughts.