Run an Arbitrum Orbit Node
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 Arbitrum 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.
Access settings
Navigate to your deployment dashboard. Click on Settings, then select General from the sidebar.
Enable external nodes
Activate the Enable external nodes setting. Note: If you wish to disable this setting later, please contact our Support.
Gather required information from the deployment dashboard
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.
Access configuration files
You will find the Websocket URL for the Sequencer Feed Relay and HTTP URL for the AnyTrust DA (Fallback) and other required parameters in the same popup.
Next steps
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.
