Regional elastic node
What is a regional elastic node?
Regional elastic node is a service providing a regional-based endpoints which are tightly bound to particular location and provider.
Networks
Regional elastic nodes can be deployed in the following networks:
| Protocol | Mainnet | Testnet | Testnet faucet |
|---|---|---|---|
| Ethereum | Mainnet | Sepolia Testnet ā a proof-of-stake public permissioned Ethereum testnet. HoleÅ”ky Testnet ā a proof-of-stake public permissioned Ethereum testnet. | Chainstack Faucet |
| Polygon | Mainnet | Amoy Testnet Mumbai Testnet | Testnet Polygon faucet |
| BNB Smart Chain | Mainnet | Testnet | Chainstack Faucet |
| Base | Mainnet | Sepolia Testnet | Chainstack Faucet |
| Avalanche | Mainnet | Fuji Testnet | Testnet AVAX faucet |
| Arbitrum | Arbitrum One Mainnet | Sepolia Testnet | Chainstack Faucet |
| zkSync Era | Mainnet | Sepolia Testnet | Chainstack Faucet |
| Polygon zkEVM | Mainnet | Testnet | |
| Optimism | Mainnet | Sepolia Testnet | Chainstack Faucet |
| Aurora | Mainnet | Testnet ā public NEAR testnet | Testnet NEAR faucet |
| Solana | Mainnet | Devnet ā public Solana sandbox network | Solana faucet |
| Aptos | Mainnet | Testnet | Aptos faucet |
| Oasis Sapphire | Mainnet | Testnet | |
| Gnosis Chain | Mainnet | Chiado Testnet | Gnosis Chain faucet |
| Cronos | Mainnet | Testnet | Cronos faucet |
| Fantom | Mainnet | Testnet | Fantom faucet |
| Starknet | Mainnet ā public Starknet mainnet. L2 to the Ethereum Mainnet. | Sepolia Testnet | Starknet faucet |
| Harmony | Mainnet | Testnet | Harmony faucet |
| Tezos | Mainnet | Jakartanet | |
| Bitcoin | Mainnet | Testnet | One of the Bitcoin faucets |
Modes
For regional elastic node 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. |
| Aptos | ā | ā | Latest 100,000,000 transactions |
| Oasis Sapphire | ā | ā | A full node currently stores the full blockchain data and an archive of historical states starting from the chain genesis. |
| Gnosis Chain | ā | ā | 1,024 MB of historical states. ~10 hours worth of immediately previous blocks. |
| Cronos | ā | ā | Latest 100 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. |
| Harmony | ā | ā | Latest 128 blocks |
| 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. |
Dedicated gateways
A dedicated gateway is one of the elastic node customization features that is available on the Enterprise plan.
Dedicated gateways process connections and traffic exclusively for a specific customer, avoiding potential issues from handling multiple customers' workload. This ensures a stable and reliable connection while reducing the likelihood of connection errors.
Updated 24 days ago