Summary\n\nCreate a dedicated operator section for the current DuskEVM stack. DuskEVM is not a separate validator network: operators run an OP Stack deployment backed by Dusk L1, a Rusk archive node, the DuskEVM adapter, and op-reth.\n\nThe guide should serve node operators, infrastructure partners, RPC providers, and explorers. It should complement the existing Dusk L1 documentation and link to the pinned OP component documentation where appropriate.\n\n## Architecture to document\n\n- Rusk archive node and the archive/history requirements used by the adapter.\n- Writable and read-only adapter roles, including relayer ownership and nonce isolation.\n- op-reth sequencer and verifier roles.\n- op-node, batcher, proposer, and challenger.\n- Blockscout and public RPC placement.\n- The immutable address book, L1/L2 genesis, rollup configuration, and contract deployment bundle.\n\n## Required operational topics\n\n- Data directories, persistence, listeners, ports, CORS, and public/private RPC boundaries.\n- Rusk archive retention and complete hash-bound event availability.\n- Adapter database lifecycle, schema compatibility, clean rebuild, resynchronization, and finalized-divergence handling.\n- Router epoch schedules and the writable-adapter restart requirement at an activation boundary.\n- op-reth proof/history retention required by proposer and challenger workflows.\n- RPC request, batch, log-range, response-size, and rate limits.\n- Relayer key configuration, funding, isolation, and rotation.\n- Startup ordering and readiness for Rusk, adapter, op-reth, op-node, writers, challenger, explorer, and ingress.\n- Metrics and alerts for adapter sync/completion, Rusk archive availability, OP heads, writer progress, and challenger health.\n- Backup, restore, rollback, clean reset, and recovery procedures.\n- Version and checksum pinning for Rusk, Piecrust, contracts, adapter, op-reth, and OP components.\n\n## Acceptance criteria\n\n- Documentation describes the current adapter/op-reth architecture and contains no legacy op-geth or legacy DuskEVM proxy instructions.\n- Separate runbooks exist for a writable sequencer-side deployment and a read-only verifier/explorer deployment.\n- Configuration examples match the released binaries and deployment bundle.\n- Public exposure and rate-limit guidance cover the adapter, op-reth, and Blockscout independently.\n- Recovery procedures cover an adapter rebuild from canonical Rusk history and an op-reth resync.\n- The guide states the minimum supported component revisions and required protocol activation features.
Summary\n\nCreate a dedicated operator section for the current DuskEVM stack. DuskEVM is not a separate validator network: operators run an OP Stack deployment backed by Dusk L1, a Rusk archive node, the DuskEVM adapter, and op-reth.\n\nThe guide should serve node operators, infrastructure partners, RPC providers, and explorers. It should complement the existing Dusk L1 documentation and link to the pinned OP component documentation where appropriate.\n\n## Architecture to document\n\n- Rusk archive node and the archive/history requirements used by the adapter.\n- Writable and read-only adapter roles, including relayer ownership and nonce isolation.\n- op-reth sequencer and verifier roles.\n- op-node, batcher, proposer, and challenger.\n- Blockscout and public RPC placement.\n- The immutable address book, L1/L2 genesis, rollup configuration, and contract deployment bundle.\n\n## Required operational topics\n\n- Data directories, persistence, listeners, ports, CORS, and public/private RPC boundaries.\n- Rusk archive retention and complete hash-bound event availability.\n- Adapter database lifecycle, schema compatibility, clean rebuild, resynchronization, and finalized-divergence handling.\n- Router epoch schedules and the writable-adapter restart requirement at an activation boundary.\n- op-reth proof/history retention required by proposer and challenger workflows.\n- RPC request, batch, log-range, response-size, and rate limits.\n- Relayer key configuration, funding, isolation, and rotation.\n- Startup ordering and readiness for Rusk, adapter, op-reth, op-node, writers, challenger, explorer, and ingress.\n- Metrics and alerts for adapter sync/completion, Rusk archive availability, OP heads, writer progress, and challenger health.\n- Backup, restore, rollback, clean reset, and recovery procedures.\n- Version and checksum pinning for Rusk, Piecrust, contracts, adapter, op-reth, and OP components.\n\n## Acceptance criteria\n\n- Documentation describes the current adapter/op-reth architecture and contains no legacy op-geth or legacy DuskEVM proxy instructions.\n- Separate runbooks exist for a writable sequencer-side deployment and a read-only verifier/explorer deployment.\n- Configuration examples match the released binaries and deployment bundle.\n- Public exposure and rate-limit guidance cover the adapter, op-reth, and Blockscout independently.\n- Recovery procedures cover an adapter rebuild from canonical Rusk history and an op-reth resync.\n- The guide states the minimum supported component revisions and required protocol activation features.