Account identity
Aperture derives and validates the public account under X Layer rules. It does not assign a generic address from another network family.
Supported production mainnet
X Layer in Aperture.
A network-aware home for OKB—with X Layer addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
X Layer is not just a ticker.
X Layer is an EVM-compatible layer-two network with its own chain state and Ethereum settlement relationship. Its current architecture uses the OP Stack after migrating from its earlier Polygon CDK design.
Address format. A 20-byte EVM account displayed as a 0x-prefixed hexadecimal address.
An exchange may offer several withdrawal networks for the same ticker. Select X Layer explicitly when using an X Layer address in Aperture.
Native asset and tokens
OKB pays gas on X Layer. Tokens are identified by their X Layer contract addresses.
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 X Layer 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 X Layer 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 X Layer.
- 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 X Layer, review the full recipient, the OKB 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 X Layer protocol rules
Public block explorerInspect X Layer 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 X Layer alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.