Ideas, design and planning bucket

[dmugtasimov]

This is a supertask that is used for holding ideas, design architecture and planning other tasks

Ideas / mind map

• Communication between nodes
  • Block confirmation (temporary implementation: just send confirmations without actual validation of the block) #434
  • Create POST /api/v1/blocks/ API end-point for CVs to accept new blocks from PV #110
  • Add create /api/v1/signed-change-requests/ end-point #106 - partially implemented, we need to implement coin transfer part
  • Validate blocks arrived from PV to CV #431
  • Permanent implementation POST /api/v1/block-confirmations/ #433
  • After adding a new block to its blockchain PV must notify each CV about the new block #113
• Blockchain synchronization
  • Even when a node is online there may be network issues which lead to missed blocks. It can be detected if a notification with block number higher that expected is arrived. In that case the node must sync missing blocks. But we need to tell apart this situation from where a higher number block arrives just because the previous block has not been fully confirmed yet (move that a half of CVs have not sent notifications about the previous block).
• Bounty tasks
• The only proof of acting on behalf of particular account (node) is possessing its private (signing) key. Responding from particular IP-address is not enough. Therefore not only all node requests, but all responses must be signed
• Create task about return nodes from API in stable order. We need this for correct implementation of APIBlockchain.yield_nodes()
• How to validated that pv schedule signed change request is authorized?
• Deploy and configure Sentry
• POST /api/v1/blocks/ should work for CV only
• Validate that signer is authorized for signed change request