At this time, the setup and maintenance of self-hosted nodes are not included in Conduit’s standard scope of support. The guide below provides a high-level overview for setting up an external node. Please note that, due to frequent updates to the underlying software, additional configuration steps or variables may be required.
If you’re onboarding a partner or tool, we recommend using Conduit Nodes — the managed, production-ready version of nodes for your RPC needs. Conduit RPC nodes are actively maintained, monitored, and optimized to scale with your network’s performance requirements.
If you’d like to maintain a backup RPC provider, we suggest Tenderly, an approved Conduit vendor.
To run a self-hosted node for an OP Stack rollup deployed on Conduit, please follow the steps below to configure the necessary settings and gather all required information. Afterwards, you can proceed with Conduit’s Github Repository on how to run a node.
Navigate to your deployment dashboard. Click on Settings, then select General from the sidebar.
Activate the Enable external nodes setting. Note: If you wish to disable this setting later, please contact our Support.
Navigate to the Deployment Dashboard. Go to the Overview section and click the Run a Node button on the right side.
OR
Visit the Conduit Hub if the network is public, select the network and click on Run a Node.
The popup will provide the rollup.json, genesis.json files and other required parameters.
You should now have all the information about your Rollup that is needed to run your own self-hosted node. Follow Conduit’s Repository for the next Steps.
You will find the value for OP_NODE_P2P_STATIC in the same popup. We also recommend setting OP_NODE_P2P_SYNC_ONLYREQTOSTATIC to true. This setting ensures more consistent and stable synchronization by forcing the node to request sync data only from OP_NODE_P2P_STATIC.
If you plan to submit transactions to your node, set the public RPC URL of your network as the OP_GETH_SEQUENCER_HTTP. For production usage, you can generate an API Key via Conduit Nodes. You can find the public RPC URL in the dashboard or on the hub.
Run optimism_syncStatus to check the current sync status of your node. From the output, note the block number associated with the sync status. Search for this block number on your block explorer to determine when it was processed on our end. By comparing the block’s processing time, you can estimate how far behind your node is in the synchronization process.