Account identity
Aperture derives and validates the public account under NEAR Protocol rules. It does not assign a generic address from another network family.
Supported production mainnet
NEAR Protocol in Aperture.
A network-aware home for NEAR—with NEAR Protocol addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
NEAR Protocol is not just a ticker.
NEAR Protocol is an account-based proof-of-stake network. Accounts can have multiple access keys with different permissions, and cross-contract execution can continue through asynchronous receipts.
Address format. A human-readable named account such as name.near or a 64-character implicit hexadecimal account.
Named accounts are convenient but remain network-specific identities. Check every character and suffix rather than relying on visual familiarity.
Native asset and tokens
NEAR is the native fee and storage asset. Fungible tokens are contracts, so the contract account—not a copied name or symbol—anchors token identity.
Fees and transaction state
NEAR pays for gas and storage. A transaction can create receipts, so final execution status is more meaningful than merely accepting the original transaction.
Mainnet boundary
This catalog entry is NEAR Protocol 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 NEAR Protocol 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 NEAR Protocol.
- 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 NEAR Protocol, review the full recipient, the NEAR 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 NEAR Protocol protocol rules
Public block explorerInspect NEAR Protocol 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 NEAR Protocol alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.