Aperture

Supported production mainnet

BNB Smart Chain in Aperture.

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

BNB Smart Chain is not just a ticker.

BNB Smart Chain is an EVM-compatible network with its own validator set, state, and transaction history. Ethereum tooling conventions apply, but BNB Smart Chain is not Ethereum mainnet.

Address format. A 20-byte EVM account displayed as a 0x-prefixed hexadecimal address.

A 0x address may look identical across BNB Smart Chain and Ethereum. Confirm the sending platform explicitly says BNB Smart Chain or BSC.

Account identity

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

Native asset and tokens

BNB pays gas. BEP-20 assets are identified by BNB Smart Chain and their exact contract address.

Fees and transaction state

The network’s native asset pays gas. A transaction hash, receipt, block inclusion, and any rollup settlement stage describe different parts of its lifecycle.

Mainnet boundary

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

The network is part of the address.

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