Aptos
Details for 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'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
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 wormhole address format.
Aptos
Ecosystem
Wormhole Details
Name:
aptosChain ID:
22Contract Source: aptos/wormhole/sources/wormhole.move
Consistency Levels
The options for consistencyLevel (i.e finality) are:
| Level | Value |
|---|---|
Finalized | 0 |
This field is may be ignored since the chain provides instant finality.
For more information see https://aptos.dev/reference/glossary/#byzantine-fault-tolerance-bft
Mainnet Contracts (1)
1)| Type | Contract |
|---|---|
Core |
|
Token Bridge |
|
NFT Bridge |
|
Testnet Contracts (2)
2)| Type | Contract |
|---|---|
Core |
|
Token Bridge |
|
NFT Bridge |
|
Local Network Contract
| Type | Contract |
|---|---|
Core |
|
Token Bridge |
|
NFT Bridge |
|
Last updated