Aperture

Supported production mainnet

Stellar in Aperture.

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

Stellar is not just a ticker.

Stellar is a public payments network organized around accounts, operations, assets, and ledgers. One transaction can contain several operations, and issued assets are represented through a code together with an issuer account.

Address format. A StrKey-encoded public account beginning with G; muxed accounts and transaction memos can carry additional destination information.

Exchanges may require a memo even when the Stellar address is correct. Omitting a required memo can make a deposit difficult to credit.

Account identity

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

Native asset and tokens

XLM is the native asset and pays fees. An issued Stellar asset is not identified by its code alone: the issuing account is part of the identity, and receiving it may require a trustline.

Fees and transaction state

Fees are expressed in stroops of XLM per operation. A transaction becomes final when it is included in a closed, validated ledger.

Mainnet boundary

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

The network is part of the address.

In Aperture, choose Stellar 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 Stellar.
  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 Stellar, review the full recipient, the XLM 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 Stellar alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.