Avalanche C-Chain (RPC)
Avalanche C-Chain is the EVM-compatible smart contract chain of the Avalanche network, with sub-second finality.
Ask About Early Access
Block time
Availability target
Execution client
WebSocket subscriptions
Snapshot cadence
Head lag target
Reorg window
Debug and trace methods
*Targets are measured at our edge, per region, each month, and published on the status page. Contact our team to discuss committed capacity.
Why connect to Avalanche C-Chain with Tessellate?
-
Planned by month twelve, ordered by customer demand
-
Same targets and limits as our launch chains once the chain is live
-
Shaped by demand: tell us which methods and regions you need first
-
EVM compatible, so standard JSON-RPC tooling applies
-
Sub-second finality, with head lag measured against a two-block target
-
Availability, latency and head lag published on our public status page
Explore insights from our engineers
Avalanche C-Chain RPC FAQ
Contact hello@thetessellatelabs.com with the chain, your expected request volume and the methods you need. Chains are added in order of customer demand, and we do not promise a date.
Client choice for Avalanche C-Chain is published when the chain launches. On chains with more than one production client we aim for client diversity in each node pool.
Archive depth for Avalanche C-Chain is published when the chain launches. Where an archive tier is offered, history and the debug_ and trace_ namespaces are served from a dedicated archive tier on local NVMe.
Block range is 2,000 on Developer and Build, 10,000 on Scale, and configurable on Dedicated and Enterprise, with result caps of 10,000, 20,000 and 100,000 logs. Avalanche C-Chain will follow the same limits once live.
Planned. Subscriptions per key follow the launch limits: 10, 50 and 500 on Developer, Scale and Dedicated tiers respectively, with WebSockets from the Build tier.
Planned for Scale (20x weight) and Dedicated (unmetered), not on Developer or Build, subject to client support on Avalanche C-Chain. Coverage is documented at launch. Avalanche RPC.
Reads for latest and pending are never cached beyond one block time, and cached data is keyed by block hash, so a reorg cannot serve stale immutable data. We will publish the reorg window for Avalanche C-Chain at launch.
Finality differs by chain and by definition. We will document what latest, safe and finalized mean on Avalanche C-Chain when it launches, and our head lag target is within two blocks of canonical for 99.9% of minutes.
No. We never hold customer keys or assets. Tessellate provides RPC access only.
JSON-RPC batches are 25, 100 and 500 requests, and responses are capped at 10 MB, 25 MB and 150 MB, by tier, as on launch chains.
Only the C-Chain, which is EVM compatible. We do not offer RPC for non-EVM chains.
99.9% availability on shared tiers, measured at our edge per region per month and published on our status page, including the months we miss it.
Explore additional chains
Tessellate supports twelve EVM chains by month twelve. Learn how to connect.
Meet With Us
Bring reliable infrastructure to your organisation.
Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to our Privacy Policy, which details how we collect and use your information.