Nikolay Volf

- along with block count - it is actually much more informant indicator of the being job done - `Processed 814 blocks (_12334 transactions_) in 60.00660687100026 seconds. Chain information: [sch:5184...

- [x] decoderawtransaction - [ ] stop

There should possible to query peer-wise: 1) best block 2) best common block 3) score (any subjective number) 4) currently requested headers/blocks (which are "inflight")

`getpeerinfo` RPC method requires collecting information by sync/p2p about specific peers (not persisted, session-wise) such as: - average ping time - number of synced headers & blocks - total bytes...

- [ ] createrawtransaction

- [x] addnode - [x] getaddednodeinfo - [x] getconnectioncount - [ ] getpeerinfo

- [ ] getwork - [ ] submitblock - [ ] getgenerate - [ ] setgenerate - [ ] settxfee

- [ ] getinfo - partially

part of #247 - [x] getbestblockhash - [x] getblockhash - [x] getdifficulty - [x] getblock - [x] gettxout - [ ] gettxoutsetinfo

Potential attack vector

1

As this todo says: ```rust // reorganization is performed only if length of side chain is at least the same as main chain // todo: shorter chain may actualy become...