Aptos
This page includes details on working with Aptos-based chains.
Addresses
Because Wormhole works with many environments, the Wormhole address format is normalized. For Aptos-based chains, no normalization is needed for standard addresses since they already have 32 bytes. E.g. 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31 becomes 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31.
However, emitter addresses are recorded as a uint64 (8 bytes), so they're left padded with 0s to 32 bytes. E.g. 0x0000000000000001 becomes 0000000000000000000000000000000000000000000000000000000000000001.
Emitter
On Aptos, an emitter capability is taken from the core bridge. The core bridge generates capabilities in a sequence and the capability object ID is its index in the sequence. The capability object ID (uint64) is used as the emitter address after normalizing to the Wormhole address format.
Aptos
Ecosystem
Wormhole Details
- Name:
aptos - Chain ID:
22 - Contract Source: aptos/wormhole/sources/wormhole.move
Consistency Levels
The options for consistencyLevel (i.e., finality) are:
| Level | Value |
|---|---|
| Finalized | 0 |
This field may be ignored since the chain provides instant finality. For more information, see the Aptos Docs.
MainNet Contracts 1
TestNet Contracts 2
Local Network Contract
| Type | Contract |
|---|---|
| Core | 0xde0036a9600559e295d5f6802ef6f3f802f510366e0c23912b0655d972166017 |
| Token Bridge | 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31 |
| NFT Bridge | 0x46da3d4c569388af61f951bdd1153f4c875f90c2991f6b2d0a38e2161a40852c |