Skip to content

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

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

Type Contract
Core 0x5bc11445584a763c1fa7ed39081f1b920954da14e04b32440cba863d03e19625
Token Bridge 0x576410486a2da45eee6c949c995670112ddf2fbeedab20350d506328eefc9d4f

Testnet Contracts 2

Type Contract
Core 0x5bc11445584a763c1fa7ed39081f1b920954da14e04b32440cba863d03e19625
Token Bridge 0x576410486a2da45eee6c949c995670112ddf2fbeedab20350d506328eefc9d4f

Local Network Contract

Type Contract
Core 0xde0036a9600559e295d5f6802ef6f3f802f510366e0c23912b0655d972166017
Token Bridge 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31

Got any questions?

Find out more