vipnode-client flow

[shazow]

Console version:

$ vipnode-client --rpc="http://localhost:8545/" --pool="https://pool.vipnode.org/api"
Connecting to RPC: http://localhost:8545/
Checking RPC API compatibility: go-ethereum detected.
Connecting to vipnode pool: https://pool.vipnode.org/api
Registering node: enode://6f8a80d143…b39763a4c0/
ACCOUNT BALANCE IS EMPTY. Please register here: https://pool.vipnode.org/register?node=6f8a80d143
...
Balance detected: 0.4 ETH
Connected to peer: enode://...
Ready.

Web version:

EnodeID:     [enode://...] <Check Status>
Add Balance: [0.4] ETH (Optional)
<Register>

• EnodeID will be associated with the wallet's address.
• needs to check both, the enodeID and the current wallet for any other enodeIDs that have been registered. Maybe a different form layout would make more sense?
• with no added balance will replace the any existing enodeID associated with the address.

To recap, the same enodeID can be registered to multiple wallets. Maybe the same wallet can have multiple enodeIDs? Either way, the balance is owned by the wallet.

<Check Balance> <Withdraw Balance>

At any point, the wallet can withdraw the remaining balance.

Some thoughts:

• Would be cool if the client could hand over a signed transaction (using web3) to the vipnode pool before connecting to the network to add to the account balance.
• Would be cool to use state channels or something here, but probably too much work for v2. Maybe v3.