Typed network messages
Block announcements, transaction announcements, votes, and synchronization requests have distinct message forms. Each serves a specific part of network operation.
Move the messages that matter
Connect peers. Deliver the next decision.
Sigil’s network architecture defines peer admission, message propagation, synchronization, and rate controls around the consensus protocol.
P2P NetworkingIllustrated study
Shared rules. Separate actors.
Illustrated coordination. No live network activity.
01 / Built for a purpose
Agreement depends on communication.
Validators need blocks, transactions, and votes at the right time. Sigil defines the message and peer-management rules around that traffic, while keeping transport behavior separate from deterministic consensus decisions.
Peer admission and diversity
Peer state, admission checks, and diversity controls give operators a way to reason about who is connected and how concentrated those connections are.
Controlled propagation
Propagation planning can distribute block payload shards and recover data from the required pieces. Fanout and payload limits constrain the work.
Ingress and gossip budgets
Rate limits, scoring, and quota models help control incoming demand. The network can distinguish accepting a message from accepting its transaction into a block.
Synchronization with context
Block and state sync messages help peers catch up. Operators still need to verify current height, lag, and transport reachability in the actual deployment.
The details matterGood questions.
Good questions.
Clear answers.
Does a reachable RPC endpoint prove the P2P network is healthy?
No. RPC reachability, peer connectivity, synchronization, and consensus participation are separate observations.
How does this relate to Weave?
Weave provides a wider peer-to-peer data layer in the ecosystem. Sigil’s network messages and consensus traffic have their own responsibilities, while artifact availability remains outside ordinary block execution.
Keep exploringOne capability.