A dedicated Avalanche C-Chain endpoint for sub-second finality workloads: DeFi, gaming and enterprise apps that cannot wait on shared pools.
Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.
https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/avaxwss://endpoints.boltrpc.io/ws/YOUR_API_KEY/avaxReplace YOUR_API_KEY with your API key. Get a free key →
Copy-paste examples for the libraries you already use. Swap the API key, hit run.
import { ethers } from "ethers";
const provider = new ethers.JsonRpcProvider(
"https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/avax"
);
const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);Connect your dApp, bot, or protocol to Avalanche C-Chain with BoltRPC. ISO 27001:2022 certified infrastructure for enterprise and institutional Avalanche deployments, with predictable request-unit pricing that scales alongside your workload.
| Chain ID | 43114 |
| Protocol | Avalanche Consensus (C-Chain) |
| Block time | ~2 s |
| Native token | AVAX |
| Finality | ~1 s (Snowman consensus) |
| EVM compatible | Yes |
Avalanche’s C-Chain is the EVM-compatible contract chain within the Avalanche network, used for institutional DeFi, gaming subnets and enterprise blockchain deployments. Aave, Curve and other major DeFi protocols operate on Avalanche. The Avalanche Foundation actively funds ecosystem growth through grants and developer programs. Avalanche’s subnet architecture allows enterprises to launch their own blockchains with custom validator sets, while the C-Chain serves as the primary DeFi and developer-facing chain. The combination of sub-second finality and EVM compatibility makes Avalanche attractive for financial applications that need both speed and security guarantees.
Avalanche is not a single chain. The network has three native chains: the C-Chain (Contract Chain) for EVM smart contracts, the X-Chain (Exchange Chain) for asset transfers using Avalanche’s UTXO model, the P-Chain (Platform Chain) for staking and subnet management. When developers say “Avalanche RPC”, they mean the C-Chain only. The X-Chain and P-Chain use distinct Avalanche-native APIs that are not JSON-RPC compatible. BoltRPC’s Avalanche endpoint connects to the C-Chain at chain ID 43114.
Avalanche Subnets are independent blockchains with their own validator sets, launched on the Avalanche network. Many Subnets are EVM-compatible, meaning they support the same JSON-RPC interface as the C-Chain but use a different chain ID. If you are building on a specific Subnet rather than the main C-Chain, verify the Subnet’s chain ID and endpoint separately. Subnet RPC access is not the same as C-Chain access.
The Snowman consensus protocol gives the C-Chain sub-second transaction finality under normal conditions. This is materially different from Ethereum, where transactions take 12 to 13 minutes to reach cryptographic finality. For applications that rely on finality guarantees, Avalanche’s speed means shorter confirmation windows, but you should confirm finality via the chain state, not just by block inclusion.
Institutional DeFi on the C-Chain Lending and stablecoin protocols poll price feeds, collateral ratios and positions continuously. Sub-second finality only helps if the RPC layer answers at the same speed.
Gaming subnets and their C-Chain bridges Game studios on Avalanche subnets settle assets and payouts through the C-Chain. Bridge watchers and payout services confirm transactions in real time, a workload that turns into support tickets when reads lag.
Enterprise and tokenization deployments Tokenized asset issuers and enterprise pilots reconcile balances and transfer history on a schedule. Predictable request-unit pricing puts a fixed number on a reporting job before it runs.
Wallets and portfolio trackers
Balance displays and transaction history call eth_getBalance, eth_call and eth_getLogs for every user session. Choosing a provider that sustains that read volume is the difference between a balance that updates and one that spins.
Avalanche attracts institutional DeFi protocols and enterprise blockchain projects that require certified infrastructure. BoltRPC runs on Matrixed.Link's ISO/IEC 27001:2022 certified node infrastructure, providing the security baseline that enterprise teams need for due diligence and compliance. No other comparable RPC provider at this price point carries this certification.
Avalanche finalizes transactions in under a second using the Snowman consensus protocol. When the chain itself is this fast, your RPC provider becomes a more meaningful factor in your application's overall response time. Slow or congested endpoints negate the chain's speed advantage.
Avalanche's DeFi ecosystem generates high RPC volume. BoltRPC handles production load without degradation during peak periods.
BoltRPC offers fixed monthly plans priced in request units, starting at $49. Visit boltrpc.io/pricing for full plan details.
Any Ethereum code works on Avalanche C-Chain with a single endpoint change.
Dedicated infrastructure for production Avalanche applications. Contact us for volume requirements above the Business plan.
Every standard Avalanche method you would expect. Archive-only methods are available on request for qualifying plans.
eth_blockNumbereth_calleth_getBalanceeth_sendRawTransactioneth_getLogsCommon questions about connecting to Avalanche over BoltRPC.
An API key in under 60 seconds, Avalanche plus 35+ other chains, and a team that answers when you write.