Aperture

Supported production mainnet

Telos EVM in Aperture.

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

Telos EVM is not just a ticker.

Telos EVM is an EVM-compatible execution environment on the Telos network with its own chain identity and transaction history.

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

Use Telos EVM destinations and explorers for this Aperture integration; do not substitute another Telos account format or network context.

Account identity

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

Native asset and tokens

TLOS pays gas on Telos EVM. Token contracts are identified on Telos EVM, not by a symbol borrowed from another chain.

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 Telos EVM mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.

The network is part of the address.

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