Account identity
Aperture derives and validates the public account under Avalanche C-Chain rules. It does not assign a generic address from another network family.
Supported production mainnet
Avalanche C-Chain in Aperture.
A network-aware home for AVAX—with Avalanche C-Chain addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
Avalanche C-Chain is not just a ticker.
Avalanche C-Chain is Avalanche’s EVM-compatible contract chain. It has its own consensus, blocks, state, and chain identity.
Address format. A 20-byte EVM account displayed as a 0x-prefixed hexadecimal address.
Avalanche also has other chain contexts and address formats. Aperture’s listed integration is specifically Avalanche C-Chain.
Native asset and tokens
AVAX pays C-Chain gas. Contract assets are identified by the Avalanche C-Chain and exact contract address.
Fees and transaction state
The network’s native asset pays gas. A transaction hash, receipt, block inclusion, and any rollup settlement stage describe different parts of its lifecycle.
Mainnet boundary
This catalog entry is Avalanche C-Chain mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose Avalanche C-Chain and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says Avalanche C-Chain.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on Avalanche C-Chain, review the full recipient, the AVAX amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand Avalanche C-Chain protocol rules
Public block explorerInspect Avalanche C-Chain public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use Avalanche C-Chain alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.