Account identity
Aperture derives and validates the public account under Solana rules. It does not assign a generic address from another network family.
Supported production mainnet
Solana in Aperture.
A network-aware home for SOL—with Solana addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
Solana is not just a ticker.
Solana transactions invoke on-chain programs through instructions. Accounts store state, a recent blockhash participates in transaction validity, and the runtime can execute independent work in parallel.
Address format. A base58-encoded 32-byte public key. Token balances often live in token accounts controlled by the wallet owner.
A token mint and a recipient wallet address are both base58 strings. Their role and the selected Solana flow must stay explicit.
Native asset and tokens
SOL is the native fee asset. SPL-compatible tokens are identified by their mint address; the wallet owner address, token account address, and token mint are different identities.
Fees and transaction state
SOL pays transaction fees, with optional prioritization depending on the transaction. Solana reports commitment stages, so processed, confirmed, and finalized should not be collapsed into one label.
Mainnet boundary
This catalog entry is Solana 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 Solana 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 Solana.
- 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 Solana, review the full recipient, the SOL 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 Solana protocol rules
Public block explorerInspect Solana 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 Solana alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.