Skip to content

docs: clarify network mode, tx gossip and NAT #20247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mattsse merged 1 commit into from
Dec 10, 2025
Merged

docs: clarify network mode, tx gossip and NAT #20247

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions docs/vocs/docs/pages/sdk/node-components/network.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,15 +41,28 @@ The network uses multiple discovery mechanisms to find and connect to peers:

### Protocol Support
- **ETH Protocol**: Core Ethereum wire protocol for blocks and transactions


### Network Mode
- **PoS networks**: Block broadcasting is disabled and considered a protocol violation. New blocks are obtained from the consensus layer and requested over devp2p.
- **PoW networks**: Block announcements are enabled to help propagate new blocks quickly.

### Message Broadcasting
The network efficiently propagates new blocks and transactions to peers using:
- Transaction pooling and deduplication
- Block announcement strategies
- Bandwidth management

Note: In PoS networks, block broadcasting is disabled and considered a protocol violation. New blocks are obtained via the consensus layer (CL) and requested over devp2p. In PoW mode, block announcements are enabled.

### Transaction Gossip Control
- A `tx_gossip_disabled` flag can be used to disable transaction gossip end-to-end.
- This is useful for private nodes, bandwidth-constrained deployments, or setups that rely on out-of-band transaction ingestion.

### NAT and External IP Resolution
- Optional NAT resolver support helps determine and advertise the correct external IP and port for discovery and inbound connectivity.

## Next Steps

- Learn about the [Transaction Pool](/sdk/node-components/pool)
- Understand [Consensus](/sdk/node-components/consensus) integration
- Explore [RPC](/sdk/node-components/rpc) server setup
- Explore [RPC](/sdk/node-components/rpc) server setup
Loading