Aperture

Supported production mainnet

Aptos in Aperture.

A network-aware home for APT—with Aptos addresses, fees, asset identity, transaction state, and safety boundaries kept visible.

Aptos is not just a ticker.

Aptos is a Move-based proof-of-stake network. Accounts hold resources and publish or interact with Move modules; transactions use an account sequence number and are executed by the Aptos virtual machine.

Address format. A 32-byte account address, conventionally displayed as a 0x-prefixed hexadecimal value.

Aptos addresses can be shortened for display by removing leading zeroes, but verification should compare the normalized full account identity.

Account identity

Aperture derives and validates the public account under Aptos rules. It does not assign a generic address from another network family.

Native asset and tokens

APT is the native fee asset. Fungible assets and other on-chain objects must be identified by their exact Aptos type or object identity, not by a ticker alone.

Fees and transaction state

APT pays gas. A submitted transaction progresses through execution and ledger commitment; a wallet should distinguish a successful committed transaction from submission alone.

Mainnet boundary

This catalog entry is Aptos mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.

The network is part of the address.

In Aperture, choose Aptos 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.

  1. Confirm the receive screen says Aptos.
  2. Copy or scan the complete address; do not retype it.
  3. Check whether the sending service requires an additional memo, tag, or network-specific field.
  4. For a new route or meaningful amount, consider a small test transfer first.
  5. Keep the receive screen available until the sender has verified the same network.

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 Aptos, review the full recipient, the APT 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.

Use the right source for the right question.

External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.

One interface. 25 mainnets. No blurred boundaries.

Use Aptos alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.