Chain profile
Blockchain-native
Avalanche.
Facts
Chain identity at a glance.
- Type
L1
- Native settlement
- AVAX · USDC · USDT · EURC
- Account model
- EVM-standard EOA + ERC-4337 on C-Chain; UTXO on X-Chain; subnet-specific account models on Evergreen Subnets (P-Chain accounts are protocol-internal validator/subnet-coordination accounts, not a user-facing model)
Vendor stack · L5 → L1
The 5-layer Stable Stack.
Each row is one named vendor slot from the chain's vendorStack. Solid markers are code-enforced
(the chain blocks or signs); dashed markers are
policy-enforced (the chain flags, humans or systems act on
the signal).
L5 → L1 — application down to network
L5 · Application
dapp-ecosystem
C-Chain dApp ecosystem (Trader Joe, Aave V3, Benqi, others — VERIFY current dominant dApps)
C13C14 ◇ policy-enforced
subnet-ecosystem
Subnet ecosystem framework (Evergreen Subnets, institutional subnet operators — VERIFY current subnet-operator roster and production status; institutional subnets out-of-scope here)
C13C14 ◇ policy-enforced
L4 · Account
account-cchain
EOA + ERC-4337 on C-Chain (EVM-standard)
C1 ◆ code-enforced
account-xchain
UTXO on X-Chain (Bitcoin-style UTXO model — native asset transfers)
C1 ◆ code-enforced
custody
Institutional custody (Anchorage Digital, Fireblocks, Coinbase Custody, BitGo — VERIFY which integrate with Avalanche C-Chain at cutoff)
C1 ◇ policy-enforced
L3 · Execution
evm
EVM smart contracts on C-Chain (EVM-compatible execution layer)
C13C16 ◆ code-enforced
subnet-creation
Subnet creation primitives (P-Chain manages validator-to-subnet assignment, subnet creation, and validator-set coordination — VERIFY exact module identifiers)
C16 ◆ code-enforced
cross-subnet-messaging
Avalanche Warp Messaging / AWM (cross-subnet messaging primitive — VERIFY current production status and subnet adoption)
C7C16 ◆ code-enforced
ethereum-bridge
Avalanche Bridge (canonical bridge to Ethereum — VERIFY current operator entity, architecture post-SGX migration if any, supported assets, and capacity)
C7 ◆ code-enforced
sanctions-oracle
Chainalysis OFAC Oracle on C-Chain (VERIFY integration — high-leverage compliance primitive; confirm or remove)
C2 ◆ code-enforced
L2 · Consensus
consensus
Avalanche consensus protocol — Snowman for linear chains (C-Chain, P-Chain), Avalanche DAG for X-Chain; permissionless validator entry via AVAX staking (Primary Network minimum stake ~2,000 AVAX — VERIFY current parameter)
C10 ◆ code-enforced
L1 · Network
network
Avalanche P2P transport + DA (AvalancheGo node software — github.com/ava-labs/avalanchego)
◆ code-enforced
Fig. 1 —
Vendor slot per layer; solid border = code-enforced, dashed
border = policy-enforced.
Bridges supported
Cross-chain transport surface.
- Avalanche Bridge
- Wormhole
- LayerZero
- CCTP
- Axelar (VERIFY)
Related paths
Paths that route through Avalanche.
Compliance paths whose settlementChains
include avalanche or whose steps execute
on this chain.
Source
Where the truth lives.
compliance/registries/chains/avalanche.ts —
full discipline header, sources, and per-field VERIFY
inventory live in the chain-profile source file. See the path resolver to see
this chain in a resolved compliance journey.
Explore the architecture
Pick a thread.