Content: Operating a DuskEVM Validator

[HDauven]

Summary

We need to create a dedicated documentation section for running a DuskEVM validator node, for node operators, infrastructure partners, and explorers. This should cover everything from base configuration to RPC rate limits.

It should complement the existing Dusk L1 node guides and be placed under the operator section. Where applicable, it makes sense to reference back to the Geth CLI reference and documentation.

Requested Details

Document how configurations similar to the following can be found:

• File Directory: How to configure the directory where node data is saved, and any other directory
• Ports: How to configure ports and host
• RPC Settings: Enable/disable RPC (JSON-RPC server), host, port, and modules.
• CORS Configuration: Specify allowed origins for cross-origin requests.
• HTTP Modules: Define which "modules" are exposed via RPC.

Document how validators can use feature flags or modify the default configuration to:

• Reduce storage requirements (e.g. pruning)
• Limit incremental storage growth without compromising log lookback capabilities (e.g. searching for archived events)
• Limit the number of events obtained via batch calls
• Fetch all the events emitted from genesis

Document all the available parameters for nodes, including:

• A parameter that caps the transaction fee that can be sent via the RPC (similarly to rpc.txfeecap in geth)
• A parameter that limits the maximum size (in bytes) a result of an rpc request could have (similarly to rpc.batch-response-max-size in geth)
• A parameter that limits the number of queries in a batch RPC request (similarly to rpc.batch-request-limit in geth)
• Document the maximum number of logs or data size that the batch version of the getLogs method (or equivalent) can handle in a single request.
• Document if there is any rate limits in a method such as _getLogs?
• Document if and how retrieval of contract events is supported, and how that differs from log lookback in EVM