Chains
Aptos
The Move format: all 32 bytes of hex written out, or the single digit AIP-40 short form for the special addresses. Nothing in between.
Chain / Move
Aptos
"aptos""apt""Aptos"
- Symbol
- APT · 8 decimals
- Coin type
- 637
- CAIP-2
- aptos:1
- Checks
- address · txid
fields set 5 / 9
Network
- CAIP-2
aptos:1 - Magic
none - PoW
none - RPC
none - Explorerexplorer.aptoslabs.com
Access
- Create
create("aptos") - Resolve
getChain("apt") - CLI
chains info apt - Tryplayground with a sample address
Address format
The Move family format, shared with Sui. Either all 32 bytes written out, 0x and 64 hex digits, or the single digit short form AIP-40 defines for the special addresses 0x0 through 0xf, which is how the framework address 0x1 is actually written. Anything in between is rejected. Accepting dropped leading zeros would make every EVM address a valid Move address too, and identify would report a family nobody asked about.
An Aptos address and a Sui address can't be told apart by looking, so identify names both.
import { getChain } from "@agntn/chains";
const chain = getChain("apt");
chain.assertAddress("0x1"); // returned unchanged
chain.type; // "move"
chain.caip2; // "aptos:1"
The Aptos CAIP-2 profile uses the numeric chain_id from the fullnode API. Mainnet is aptos:1, not aptos:mainnet.
Spellings
aptos, apt, Aptos. The key is aptos, the rest resolve through getChain.