Aptos
Last updated
Was this helpful?
Last updated
Was this helpful?
Details for working with Aptos based chains.
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're already 32 bytes.
e.g. 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31 => 0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31
However, emitter addresses are recorded as a uint64 (8 bytes), so they're left padded with 0s to 32 bytes.
e.g. 0x0000000000000001 => 0000000000000000000000000000000000000000000000000000000000000001
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 wormhole address format.
|
|
Name: aptos
Chain ID: 22
Finalized
0
This field is may be ignored since the chain provides instant finality.
1)Core
0x5bc11445584a763c1fa7ed39081f1b920954da14e04b32440cba863d03e19625
Token Bridge
0x576410486a2da45eee6c949c995670112ddf2fbeedab20350d506328eefc9d4f
NFT Bridge
0x1bdffae984043833ed7fe223f7af7a3f8902d04129b14f801823e64827da7130
2)Core
0x5bc11445584a763c1fa7ed39081f1b920954da14e04b32440cba863d03e19625
Token Bridge
0x576410486a2da45eee6c949c995670112ddf2fbeedab20350d506328eefc9d4f
NFT Bridge
0x1bdffae984043833ed7fe223f7af7a3f8902d04129b14f801823e64827da7130
Core
0xde0036a9600559e295d5f6802ef6f3f802f510366e0c23912b0655d972166017
Token Bridge
0x84a5f374d29fc77e370014dce4fd6a55b58ad608de8074b0be5571701724da31
NFT Bridge
0x46da3d4c569388af61f951bdd1153f4c875f90c2991f6b2d0a38e2161a40852c
Contract Source:
The options for (i.e finality) are:
For more information see