You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bridge Node
A bridge node is a full node that is connected to a Celestia Core node via RPC. It receives either a remote address from a running Core node or it can run a Core node as an embedded process, but the critical difference is that instead of constructing blocks via sampling the network for shares, it receives headers and blocks directly from its trusted Core node, validating blocks and producing ExtendedHeaders to broadcast to the Celestia DA network.
Full Node
A full node is the same thing as a light node, but instead of performing LightAvailability (the process of DASing to verify a header is legitimate), it performs FullAvailability which samples the network for shares in order to fully reconstruct the block and store it, serving shares to the rest of the network.
Light Node
A light node listens for ExtendedHeaders from the DA network and performs DAS on the received headers.
The current full node implementation should be renamed to bridge and a new standalone full node implementation should be added.
The CLI should include detailed descriptions of what it means to run each node type.
Summary
After devnet, we need to do hygiene work in our node types
Gain
This is beneficial for our upcoming tool that will be creating in-memory network and deploy nodes to test against
Evidence
Code-base node part
Implementation ideas
No response
Urgency
Medium
The text was updated successfully, but these errors were encountered: