EPIC: Consensus-to-Block node integration

[jsync-swirlds]

This epic consists of designing, testing, and verifying the integration between consensus node and block node when a consensus node is publishing a block stream to a block node.

Tech Notes:

1. Use Local Node for integration testing.
2. Slow down consensus traffic in local node else we will get blocks every ms, or less, because CN sends blocks for every round.
   • Round time depends on latency, and is ~1s in Mainnet, but is <10ms on testnet (local network), and may be sub μs on local node (same physical machine).
3. Local node can generate different types of transactions using Mirror Node, Simulator Client, and SDK(s).
   • Prefer Mirror Node over Simulator over SDK(s) based on client priority and timelines.

Block Node Tasks

Preview Give feedback

1. Design handshake between CN and BN to determine what Block to start streaming from. #120
   +0
   
2. Implement Connection from CN to BN. (TBD Details on how to select a BN) #418
   +0
3. Establish an integration environment (single server?) for testing
4. Add support to Block Node for a "missed block" response (CN sends block later than next)
5. Add support to Block Node for an "old block" response (CN sends block already present)
6. Add support to Block Node for error responses (BN encounters an unrecoverable internal error).
7. Add support to Block Node for "behind" response (BN is behind CN and needs to catch up).
8. Longevity test for Consuming Block Stream #417
   1 of 6
   +0
   

Block Stream Simulator Tasks

Preview Give feedback

1. Add support to the Block Stream Simulator to send out-of-order blocks
2. Add support to the Block Stream Simulator to fail sending mid-block
3. Add support to the Block Stream Simulator to handle BN error response(s).
4. Add support to the Block Stream Simulator to test Block Node "behind".

Consensus Node services team will track associated work on consensus node in a mirror epic.