Canonical account derivation
Supported accounts are derived through Wallet Core coin APIs or the chain’s signer and address rules, then verified before they are stored or used for signing.
Supported networks
25 mainnets. Each treated as itself.
Aperture’s production catalog is mainnet-only. Every supported network retains its own account rules, addresses, native fee asset, tokens, signing behavior, and transaction identity.
25supported production mainnets
13EVM mainnets
4Bitcoin-family networks
8other network account models
Current network catalog
Names identify the mainnet integration. Symbols alone never establish token or network identity.
EVM mainnets
Bitcoin-family UTXO networks
Independent account models
How network support is defined
A logo in a list is not enough. Aperture treats support as a set of concrete, network-specific responsibilities.
Mainnet-only identity
The production catalog does not add or retain testnet networks, endpoints, balances, assets, or transaction flows.
Lossless quantities
Blockchain quantities, balances, gas values, prices, rates, and fiat values are persisted as lossless base-10 text rather than binary floating-point values.
Contract-aware tokens
Known tokens are resolved by network plus normalized on-chain identity. Custom and uncatalogued tokens can use permitted network data, but a ticker never becomes the identity key.
Network-aware send and receive
The selected network controls address validation, fee asset, QR payload behavior, transaction construction, signing, broadcast, and finality display.
Public infrastructure boundary
Balances, history, fees, prices, and broadcast can require external RPC or data providers. Those requests use public account and transaction information, not a private signing key.
Before receiving or sending
Use the network label as part of the destination—not as a cosmetic detail.
- Select the asset and exact mainnet in Aperture.
- Use the address or QR code shown for that selection.
- Confirm the sender, exchange, or bridge is using the same mainnet.
- For tokens, verify the complete contract, mint, type, or issued-asset identity.
- Review the native network fee and recipient before authorizing a send.
A compatible address format is not proof that a transfer is appropriate. Some EVM networks share address syntax, while the assets and transaction histories remain on different chains.
Continue with first-party detail
Go deeper with the product pages, Journal explainers, and machine-readable sources that support this page.
Self-custody is clearest when the rules are visible.
Download Aperture from the official App Store listing, verify the product identity, and understand your recovery method before moving funds.