Performance.Interoperability.Privacy.Compliance.
A high-performance EVM, configured for regulated finance.
Interoperability
Every chain speaks natively.
Native messaging between Avalanche chains, public or private, verified against validator sets on the P-Chain.
- Authenticated messaging
- Messages carry aggregate BLS signatures from the source validator set, verified at the destination against the validator registry on the P-Chain.
- Native token transfer
- Interchain Token Transfer (ICTT) moves tokens between L1s over ICM, with contracts you deploy and control.
- Permissionless relay
- Messages are carried by relayers anyone can run. The destination chain verifies the source validators' signatures, never the messenger.
Performance
Finality in milliseconds.
Sub-second finality on the shared C-Chain, and under 100 milliseconds on an L1 all your own.
- High-performance EVM
- The C-Chain and every L1 run the EVM by default: Solidity, Foundry, and the wallets your users already have work unchanged.
- Irreversible settlement
- Snowman consensus accepts each block exactly once. No confirmation counting, no reorg window, no clawback of settled value.
- Dedicated blockspace
- Each L1 has its own validators, gas token, and fee market. Someone else's busy application never touches your latency.
- Horizontal scale
- Capacity grows by adding L1s: each new chain brings its own validators and fee market instead of bidding for shared blockspace.
Privacy
Visible to participants. Invisible to everyone else.
Whatever your privacy requirement, the architecture meets it: close the network, place the data, extend the VM with the cryptography you choose.
- Validator-only networks
- One configuration flag closes the chain. Only validators and the nodes they admit can connect, sync, or serve its data.
- Data residency
- Validators are machines you place: keep every copy of the ledger in a jurisdiction, a data center, or your own racks.
- Encrypted transport
- Traffic between nodes runs over TLS. Even on the network path between your data centers, the chain's data is never readable in transit.
Compliance
Policy enforced by the protocol.
Decide who can validate, deploy, and transact on your L1. The rules are built into the chain's virtual machine, not written in policy documents.
- Approved deployers
- Only addresses you approve can deploy contracts. The EVM enforces it at execution, not by convention.
- Transaction gating
- Only approved wallets can transact at all. The chain rejects anyone else's transaction before it executes.
- Permissioned validator set
- You decide which operators validate, your machines or named partners, and admit or remove them through the validator manager contract.
Start on the C-Chain.Graduate to your own L1.
The shared C-Chain gives an application immediate reach. A dedicated L1 keeps native messaging and irreversible finality, and makes the rest configurable: blockspace, gas token, who validates, who can see the chain, and who can use it.
| DECISION | C-ChainShared, public, EVM | Your own L1Dedicated, configurable, any VM |
|---|---|---|
| INTEROPERABILITY → | ||
| Interchain Messaging | Native | Native |
| Token transfer (ICTT) | Native | Native |
| PERFORMANCE → | ||
| Virtual machine | High-performance EVM | The same EVM, a customized EVM, or any VM you build |
| Chain-level features | Fixed by the network | Extend the EVM with your own |
| Finality | Under a second | Under 100 milliseconds |
| Reorgs | None | None |
| Blockspace | Shared with every application | Dedicated, with its own fee market |
| Gas token | AVAX | A token you choose |
| PRIVACY → | ||
| Network access | Public | Public, or validator-only |
| Data residency | Primary Network validators | Wherever you place validators |
| COMPLIANCE → | ||
| Validators | Primary Network validators | Operators you admit |
| Contract deployment | Anyone | Approved deployers only |
| Transactions | Anyone | Approved wallets only |
| Build on the C-Chain | Create an L1 | |