Avalanche (C-Chain)
L1 · Ava Labs / Avalanche Foundation
No assets on record here yet, so there is nothing to measure.
Assets
No tokenized-asset contract is on record for Avalanche (C-Chain). That is an absence in our register, not a finding that none exist.
What is being used
No activity sample has been read for this chain. That is an absence, not a zero.
How it works
How it works nothing stated — the evidence layer refused
The citation audit has no green verdict for today. Nothing about Avalanche (C-Chain)'s mechanics is rendered until the internal primitives evidence audit passes for the current evidence file. An absence here is a statement about our reading, not about the chain.
What changed, in full
AVAX-1 endpoint probes 2026-11-14 2026-11-18 07:30:00 · primary · from the chain row (no dated diff for this chain yet)
Raw record
In one line: AVAX-1 endpoint probes 2026-11-14 2026-11-18 07:30:00 · primary · from the chain row (no dated diff for this chain yet)
Snapshot note: P1a live rowset (contracts+usage); P0 baseline hash in as_of='2026-11-11' row
Last updated: snapshot 2026-11-18 07:30:00 · usage — (none recorded) · KB as_of 2026-11-18 07:30:00
The full timeline for this chain — contract changes and watch events merged, dated, and linked.
Coming and watched0
What’s coming — measured on the test cluster not looked at
Nothing on the test cluster has been LOOKED AT for this chain. 0 issuer-owned mainnet addresses would be scanned, and the scanner refused the chain because no endpoint here is proven from the operator’s own documentation. That is a gap in our coverage — not a statement about what the issuer is doing.
An endpoint is proven only after a live response is recorded from this host, dated. A remembered URL is not a proven one, and a scan that guessed one would produce confident nonsense.
Readings0
Per-contract charts
No usage rows recorded for this chain (absent, not zero) — no chart is drawn, because there is nothing measured to draw.
Assets & activity
No contracts on this chain, so no asset rows can join — the absence is inherited from the contracts table (absent, not zero).
Usage history 0 rows
No usage rows recorded for this chain (absent, not zero). Usage metrics are recorded per snapshot; an empty table means none have been recorded yet, not that activity is zero.
How this chain is measuredidentity, capabilities, gaps
Capability set
No capability rows recorded for this chain (absent, not zero). Capabilities are an explicit set per contract — an empty table means none have been recorded, not that capabilities are off.
Standards on this chain
No standards recorded for avalanche. Absence here is a state, not a gap to fill: some chains publish no proposal process, and the registry notes below say which. Nothing is invented to fill this table.
Identity
- Type
- L1
- Operator
- Ava Labs / Avalanche Foundation
- Token standards
- ERC-20
- Gas model
- AVAX; ~0.9 s/block measured 2026-11-14; eth_getLogs window capped at 99 blocks
- Privacy model
- none native — fully transparent public chain
- Agent surfaces
- json-rpc api.avax.network (chainId 0xa86a proven); llms.txt + llms-full.txt published; no MCP proven
- Last proven endpoint
- https://api.avax.network/ext/bc/C/rpc
source: (source: avalanche contracts work) endpoint probes 2026-11-14 · as_of 2026-11-18 07:30:00 · primary
Honest gaps
- 0 contracts: no contracts recorded for this chain in knowledge.db (kb_as_of 2026-11-18 08:37:10)