Account identity
Aperture derives and validates the public account under Bitcoin rules. It does not assign a generic address from another network family.
Supported production mainnet
Bitcoin in Aperture.
A network-aware home for BTC—with Bitcoin addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
Bitcoin is not just a ticker.
Bitcoin uses unspent transaction outputs rather than an account balance. A send selects spendable outputs, creates new outputs, and commonly returns change to the wallet.
Address format. Bitcoin mainnet addresses can include modern bech32 or bech32m forms beginning with bc1, plus supported legacy-compatible formats.
Every valid derived receive address remains part of the deterministic wallet. Fresh addresses reduce obvious reuse; they do not make the public ledger anonymous.
Native asset and tokens
BTC is the native asset and fee unit. Aperture also supports fresh Bitcoin receive addresses and compatible Silent Payments as distinct privacy-aware receiving options.
Fees and transaction state
Fees are determined by transaction virtual size and the chosen fee rate, not by the BTC amount alone. Confirmations accumulate as blocks build on the transaction’s block.
Mainnet boundary
This catalog entry is Bitcoin 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 Bitcoin 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 Bitcoin.
- 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 Bitcoin, review the full recipient, the BTC 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 Bitcoin protocol rules
Public block explorerInspect Bitcoin 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 Bitcoin alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.