Deploying nodes

Step-by-step guide to deploying blockchain nodes using Chainstack Self-Hosted, including protocol selection, client configuration, and network options.

This guide explains how to deploy blockchain nodes using Chainstack Self-Hosted.

Supported deployments

Protocol	Network	Client	Node type
Ethereum	Mainnet	Reth + Prysm	Full node
Ethereum	Sepolia	Reth + Prysm	Full node
Ethereum	Hoodi	Reth + Prysm	Full node

Additional protocols and networks are on the roadmap. See the FAQ for details.

Resource requirements

Before deploying a node, ensure your infrastructure has sufficient resources available. See System requirements for detailed specifications.

The Control Panel itself consumes system resources. When planning your infrastructure, account for both the Control Panel overhead and the resources required by the nodes you intend to deploy.

Deployment wizard

1. Access the deployment wizard

   1. Log in to the Control Panel
   2. Navigate to Nodes
   3. Click Create node or click the + button next to a preset
2. Select protocol and network

   1. Select a protocol
   2. Select a network
3. Configure node settings

   Each Ethereum network ships with two preset tiers — a standard preset for production and a Light preset for evaluation. The Light preset uses half the CPU and RAM of the standard preset but the same storage, so you can move between tiers without resizing disks.

   Network	Preset name in the UI	CPU (total)	RAM (total)	Storage
   Ethereum Mainnet	Ethereum Mainnet Reth Prysm	8 vCPU	32 GiB	~2 TiB
   Ethereum Mainnet	Ethereum Mainnet Reth Prysm (Light)	4 vCPU	16 GiB	~2 TiB
   Ethereum Sepolia	Ethereum Sepolia Reth Prysm	8 vCPU	32 GiB	~1.3 TiB
   Ethereum Sepolia	Ethereum Sepolia Reth Prysm (Light)	4 vCPU	16 GiB	~1.3 TiB
   Ethereum Hoodi	Ethereum Hoodi Reth Prysm	8 vCPU	32 GiB	250 GiB
   Ethereum Hoodi	Ethereum Hoodi Reth Prysm (Light)	4 vCPU	16 GiB	250 GiB

   CPU and RAM are split evenly between the Reth (execution) and Prysm (consensus) clients. Both presets currently ship Reth v1.11.3 and Prysm v7.1.3, with snapshot bootstrap pre-configured — the node downloads a pre-built chain snapshot rather than syncing from genesis. See Initial sync times below for what to expect.

   For production, pick the standard preset and size your host per System requirements. For evaluation on a smaller server, pick the Light preset.

   Snapshot bootstrap temporarily requires 2× the final storage. The node first downloads the snapshot archive, then extracts it into the chain data directory, so both copies coexist on disk until extraction completes. Provision the node’s persistent volume at 2× the storage figure in the table above; the volume can be reclaimed or stay sized for headroom once the snapshot archive is removed.

4. Review and deploy

   1. Review your configuration
   2. Click Create node to start the deployment

   

Deployment process

After initiating deployment, the node goes through several phases:

Phase	Description	Duration
Bootstrapping	Resources are allocated, client software is configured	2–5 minutes
Running	Node is deployed and synchronizing with the network	Continuous

The node shows Running status once deployed. Initial bootstrap from the snapshot completes in minutes to hours; the node then catches up to the chain head in the background.

Initial sync times

Sync times depend on your hardware and network conditions:

Phase	Approximate time
Snapshot bootstrap	Minutes to hours (network dependent)
Catch-up to chain head	Continuous

See System requirements for specifications and a community-maintained list of hardware recommendations.

After deployment

Once your node reaches Running status:

1. Access the node details to view connection information
2. Start using the node for your applications

Next steps

• Managing nodes — Learn about node operations
• Troubleshooting — Resolve deployment issues