Skip to main content
Snap sync significantly improves the experience of syncing an OP Stack node. On the consensus layer, op-node enables it with the --syncmode=execution-layer flag. Rather than re-executing every block from genesis, the execution client downloads chain and state data from other nodes on the network over P2P and begins executing from the completed state. This means that performing a snap sync is significantly faster than performing a full sync.
  • Snap sync enables node operators on your network to sync faster.
  • Snap sync removes the need for nodes on your post Ecotone network to run a blob archiver.

​
Enable snap sync for chains

To enable snap sync, chain operators need to spin up a node which is exposed to the network and has transaction gossip disabled. This node will serve snap sync requests on the execution layer from other nodes on the network.
For snap sync, all nodes should expose port 30303 TCP and 30303 UDP to easily find other nodes to sync from. These are op-reth’s defaults for --port (TCP) and --discovery.port (UDP).
  • If you set the port with --discovery.port, then you must open the port specified for UDP.
  • If you set --port, then you must open the port specified for TCP.
  • The only exception is for sequencers and transaction ingress nodes.
1

Setup a snap sync node

  • Expose port 30303 (op-reth’s default listening and discovery port) to the internet on TCP and UDP.
  • Disable transaction gossip with the --rollup.disable-tx-pool-gossip flag
2

Enable snap sync on your network

  • See the sync modes reference for how node operators enable snap sync (execution-layer sync) on your chain network.