Block Node #1081
Block Node #1081
Conversation
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
…nd service definitions Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
✅ Deploy Preview for hedera-hips ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
| - [ ] Q: Does the block node require or rely on a transmission of full state from a CN? If so what’s the contract between | ||
| nodes here? Previously the CN output state every 15 mins |
There was a problem hiding this comment.
Block Nodes that manage live state or produce state snapshots require a state snapshot to start up if not active since genesis for that network. That snapshot should, however, be transferred manually (either from cloud storage or another block node).
The consensus node, in a block stream mode, should not ever transmit a state snapshot to another system. State snapshots in this realm are local backup only and should be short-lived ephemeral data (if stored at all).
One of the major benefits of block nodes is that we remove the bandwidth, processing, and complexity of managing state snapshot transfers from consensus nodes entirely.
If a running block node ever needs a state snapshot for some reason, the best place to get one is another block node.
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
Signed-off-by: Nana Essilfie-Conduah <nana@swirldslabs.com>
Description:
Abstract
This HIP introduces and proposes the adoption of a new node type that is designed to parse the block stream, store
latest state and serve up additional network APIs such as state proofs and block retrieval that support decentralized
querying and verification of state.
A block node will primarily sit in between a consensus node and a mirror node to serve as a decentralized source of
verifiable network state and transaction information. As an emergent feature a block node will introduce a new node
economy through independent community operations. Anyone will be able to independently run a block node or block
stream parsing product that provides value added services to users e.g. aggregated data insights, data availability.
Block Nodes will have a rich API, allowing consumers to receive a subset of the stream, or the full stream. Block Nodes
can innovate on payment -- they can be commercial and have connectivity rules / rate limits / SLAs for customers.
They can require payment for serving blocks, or they can serve blocks for free.
Related issue(s):
Expands on #1055
Notes for reviewer:
Checklist