[Feature Request]: add option to sync only from DA

[tzdybal]

Implementation ideas

Currently it's not clear if node is syncing only using DA or DA and P2P network and there is no explicit way of configuring this behavior.

There are multiple implementation options:

1. Disable entire P2P comms completely - node would only follow DA, no gossiping, peer discovery, etc.
2. Make "sync mode" configurable - DA or P2P or both. Node would still participate in gossiping, peer discovery, etc.
   1. Node that reads from only DA might (or might not) "serve" data via P2P, to help syncing other nodes via P2P.

[tzdybal]

CC: @robert-zaremba

[tac0turtle]

id say this is already supported, the path is to not add a p2p peer to connect to

@claude can you make some adjustments to the docs to make sure this is encapsulated there

[claude[bot]]

Claude finished @tac0turtle's task —— View job • claude/issue-1671-20250808-0727 • Create PR ➔

---

DA-only sync documentation updated ✅

I've successfully updated the documentation to clarify that DA-only sync is already supported by not configuring P2P peers.

Completed Tasks:

• [x] Read CLAUDE.md for project context
• [x] Search for existing sync and configuration documentation
• [x] Examine configuration structures for p2p peer setup
• [x] Update documentation to explain DA-only sync mode
• [x] Commit and push documentation changes

Changes Made

1. Enhanced Configuration Documentation (docs/learn/config.md):

• Added prominent DA-Only Sync Mode section explaining the feature
• Documented that leaving p2p.peers empty (default) enables DA-only sync
• Explained benefits: resource optimization, simplified deployment, isolated environments
• Added clear configuration examples and behavior explanations
• Updated the P2P Peers section to mention DA-only sync mode

2. Updated README (README.md):

• Added section highlighting Evolve's multiple sync modes
• Referenced the new configuration guide section

How DA-Only Sync Works

As you correctly noted, this feature is already supported:

• Default behavior: When rollkit.p2p.peers is empty (default), no P2P connections are made
• DA-only operation: Node syncs exclusively from the Data Availability layer
• Full functionality: Still validates transactions, maintains state, and serves RPC requests
• No P2P: Avoids gossip, peer discovery, and P2P block sharing

The documentation now makes this capability clear and prominent for users who need DA-only sync deployments.