Goal
Replicate durable engine state over TCP from a serving node to an externally paced follower.
Why
Followers need to resume from an exact retained ledger cursor, catch up without duplicate application, and recover from a snapshot when their cursor is no longer retained.
Scope
- add a versioned handshake and bounded control-message framing
- serve retained blockstore bytes or the newest complete accountsdb snapshot
- reconnect followers from a flushed durable cursor
- apply transactions, blocks, resets, and seals through ordered engine paths
- stage snapshots for installation on follower restart
- integrate client and dispatcher termination with the shutdown manager
Notes
Block boundaries flow through the external pacer so state, seals, resets, and durable cursors remain ordered.
Goal
Replicate durable engine state over TCP from a serving node to an externally paced follower.
Why
Followers need to resume from an exact retained ledger cursor, catch up without duplicate application, and recover from a snapshot when their cursor is no longer retained.
Scope
Notes
Block boundaries flow through the external pacer so state, seals, resets, and durable cursors remain ordered.