Dedicated node
What is a dedicated node?
A dedicated node is a node that exclusively deployed for and belongs to a particular customer, with its compute resources are not being shared with anybody else. Such nodes are highly customizable and can offer more additional services than elastic nodes. This means that each dedicated node can be configured to perfectly match the case and needs of a particular customer.
Dedicated node plans
Subscription level — a Business or Enterprise subscription is required.
See Pricing Page.
Node clients
For most of the protocols, the popular mode clients are available for dedicated nodes:
- Reth
- Geth
- Erigon
For example, for Web3 data backfills, Reth might be the fastest option.
Modes
For dedicated nodes deployed on the most of public chains, Chainstack supports the following modes:
- Full — a node that stores full blockchain data. However, it has limitations to how many blocks are available for querying.
- Archive — a node that stores full blockchain data and an archive of historical states, which makes it possible to query any block since the chain genesis.
The following modes are available per each protocol:
| Protocol | Full | Archive | Full mode querying limits |
|---|---|---|---|
| Ethereum | ✅ | ✅ | Latest 128 blocks |
| Polygon | ✅ | ✅ | Latest 128 blocks |
| BNB Smart Chain | ✅ | ✅ | Latest 128 blocks |
| Base | ✅ | ✅ | |
| Avalanche | ✅ | ✅ | Latest 32 blocks of C-Chain |
| Arbitrum | ✅ | ✅ | Latest 128 blocks |
| zkSync Era | ✅ | ❌ | A full node currently stores the full blockchain data and an archive of historical states starting from the chain genesis. |
| Polygon zkEVM | ✅ | ❌ | A full node currently stores the full blockchain data and an archive of historical states starting from the chain genesis. |
| Optimism | ✅ | ✅ | Latest 128 blocks |
| Aurora | ✅ | ✅ | Latest 5 epochs |
| Solana | ✅ | ❌ | Up to the first block available on the node. ~1.5 days worth. |
| Scroll | ✅ | ✅ | |
| Ronin | ✅ | ❌ | |
| Aptos | ✅ | ✅ | Latest 100,000,000 transactions |
| Gnosis Chain | ✅ | ✅ | 1,024 MB of historical states. ~10 hours worth of immediately previous blocks. |
| Fantom | ✅ | ✅ | As Go Opera, the Fantom client, does not have automatic state pruning implemented, there is currently no difference between a full node and an archive node. |
| Starknet | ✅ | ❌ | |
| Tezos | ✅ | ✅ | With a full node, you can query any block information or operation but you cannot query the balances or staking rights before the current checkpoint. A checkpoint is automatically done every 4,096 blocks. This means that with a full node, you can only query the balances and staking rights from when the last checkpoint happened until the latest block within the current 4,096 block cycle. |
Debug and trace API
Regardless of mode, all dedicated nodes will have debug and trace API enabled for protocols which support this feature. See the full list of protocols with debug and trace API.
Hosting regions
Dedicated nodes offer unparalleled flexibility, allowing them to be deployed in various combinations of networks and modes across any hosting regions currently available. With this flexibility, you can seamlessly leverage dedicated nodes in a desired hosting region, ensuring optimal performance and adaptability for your Web3 projects.
Updated about 2 months ago