Simulate transaction
POST /transactions/simulate
curl https://api.mainnet.aptoslabs.com/v1/transactions/simulate \ --request POSTThe output of the transaction will have the exact transaction outputs and events that running an actual signed transaction would have. However, it will not have the associated state hashes, as they are not updated in storage. This can be used to estimate the maximum gas units for a submitted transaction.
To use this, you must:
- Create a SignedTransaction with a zero-padded signature.
- Submit a SubmitTransactionRequest containing a UserTransactionRequest containing that signature.
To use this endpoint with BCS, you must submit a SignedTransaction encoded as BCS. See SignedTransaction in types/src/transaction/mod.rs.
Parameters
Query Parameters
If set to true, the max gas value in the transaction will be ignored and the maximum possible gas will be used
If set to true, the gas unit price in the transaction will be ignored and the estimated value will be used
If set to true, the transaction will use a higher price than the original estimate.
Request Body required
A request to submit a transaction
This requires a transaction and a signature of it
object
A hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034An enum of the possible transaction payloads
object
entry_function_payloadEntry function id is string representation of a entry function defined on-chain.
Format: {address}::{module name}::{function name}
Both module name and function name are case-sensitive.
0x1::aptos_coin::transferType arguments of the function
Arguments of the function
An enum of the possible transaction payloads
object
script_payloadMove script bytecode
object
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Move function
object
Move function visibility
Whether the function can be called as an entry function directly in a transaction
Whether the function is a view function or not
Generic type params associated with the Move function
Move function generic type param
object
Move abilities tied to the generic type param and associated with the function that uses it
Parameters associated with the move function
Return type of the function
Type arguments of the function
Arguments of the function
An enum of the possible transaction payloads
object
module_bundle_payloadAn enum of the possible transaction payloads
object
multisig_payloadA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
entry_function_payloadEntry function id is string representation of a entry function defined on-chain.
Format: {address}::{module name}::{function name}
Both module name and function name are case-sensitive.
0x1::aptos_coin::transferType arguments of the function
Arguments of the function
An enum representing the different transaction signatures available
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
multi_agent_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1The other involved parties’ addresses
The associated signatures, in the same order as the secondary addresses
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
fee_payer_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1The other involved parties’ addresses
The associated signatures, in the same order as the secondary addresses
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
single_senderAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
no_account_signatureResponses
200
A transaction submitted by a user to change the state of the blockchain
object
A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034Whether the transaction was successful
The VM status of the transaction, can tell useful information in a failure
Final state of resources changed by the transaction
A final state change of a transaction on a resource or module
object
delete_moduleA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1State key hash
Move module id is a string representation of Move module.
Format: {address}::{module name}
address should be hex-encoded 32 byte account address that is prefixed with 0x.
Module name is case-sensitive.
0x1::aptos_coinA final state change of a transaction on a resource or module
object
delete_resourceA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1State key hash
String representation of a MoveStructTag (on-chain Move struct type). This exists so you can specify MoveStructTags as path / query parameters, e.g. for get_events_by_event_handle.
It is a combination of:
move_module_address,module_nameandstruct_name, all joined by::struct generic type parametersjoined by,
Examples:
0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::Account
Note:
- Empty chars should be ignored when comparing 2 struct tag ids.
- When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).
See doc for more details.
0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>A final state change of a transaction on a resource or module
object
delete_table_itemAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Deleted table data
object
Deleted key
Deleted key type
A final state change of a transaction on a resource or module
object
write_moduleA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1State key hash
Move module bytecode along with it’s ABI
object
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1A Move module
object
A hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Friends of the module
Public functions of the module
Move function
object
Move function visibility
Whether the function can be called as an entry function directly in a transaction
Whether the function is a view function or not
Generic type params associated with the Move function
Move function generic type param
object
Move abilities tied to the generic type param and associated with the function that uses it
Parameters associated with the move function
Return type of the function
Structs of the module
A move struct
object
Whether the struct is a native struct of Move
Whether the struct is marked with the #[event] annotation
Abilities associated with the struct
Generic types associated with the struct
Move generic type param
object
Move abilities tied to the generic type param and associated with the type that uses it
Fields associated with the struct
Move struct field
object
String representation of an on-chain Move type tag that is exposed in transaction payload.
Values:
- bool
- u8
- u16
- u32
- u64
- u128
- u256
- address
- signer
- vector: vector<{non-reference MoveTypeId}>
- struct: {address}::{module_name}::{struct_name}::<{generic types}>
Vector type value examples:
- `vector<u8>`
- `vector<vector<u64>>`
- `vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>`
Struct type value examples:
- `0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>
- `0x1::account::Account`
Note:
1. Empty chars should be ignored when comparing 2 struct tag ids.
2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).A final state change of a transaction on a resource or module
object
write_resourceA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1State key hash
A parsed Move resource
object
String representation of a MoveStructTag (on-chain Move struct type). This exists so you can specify MoveStructTags as path / query parameters, e.g. for get_events_by_event_handle.
It is a combination of:
move_module_address,module_nameandstruct_name, all joined by::struct generic type parametersjoined by,
Examples:
0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>0x1::account::Account
Note:
- Empty chars should be ignored when comparing 2 struct tag ids.
- When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).
See doc for more details.
0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>This is a JSON representation of some data within an account resource. More specifically, it is a map of strings to arbitrary JSON values / objects, where the keys are top level fields within the given resource.
To clarify, you might query for 0x1::account::Account and see the example data.
Move bool type value is serialized into boolean.
Move u8, u16 and u32 type value is serialized into integer.
Move u64, u128 and u256 type value is serialized into string.
Move address type value (32 byte Aptos account address) is serialized into a HexEncodedBytes string.
For example:
0x10x1668f6be25668c1a17cd8caf6b8d2f25
Move vector type value is serialized into array, except vector<u8> which is serialized into a
HexEncodedBytes string with 0x prefix.
For example:
vector<u64>{255, 255}=>["255", "255"]vector<u8>{255, 255}=>0xffff
Move struct type value is serialized into object that looks like this (except some Move stdlib types, see the following section):
{
field1_name: field1_value,
field2_name: field2_value,
......
}For example:
{ "created": "0xa550c18", "role_id": "0" }
Special serialization for Move stdlib types:
- 0x1::string::String
is serialized into
string. For example, struct value0x1::string::String{bytes: b"Hello World!"}is serialized as"Hello World!"in JSON.
object
{ "authentication_key": "0x0000000000000000000000000000000000000000000000000000000000000001", "coin_register_events": { "counter": "0", "guid": { "id": { "addr": "0x1", "creation_num": "0" } } }, "self_address": "0x1", "sequence_number": "0"}A final state change of a transaction on a resource or module
object
write_table_itemAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Decoded table data
object
Key of table in JSON
Type of key
Value of table in JSON
Type of value
A hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034An enum of the possible transaction payloads
object
entry_function_payloadEntry function id is string representation of a entry function defined on-chain.
Format: {address}::{module name}::{function name}
Both module name and function name are case-sensitive.
0x1::aptos_coin::transferType arguments of the function
Arguments of the function
An enum of the possible transaction payloads
object
script_payloadMove script bytecode
object
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Move function
object
Move function visibility
Whether the function can be called as an entry function directly in a transaction
Whether the function is a view function or not
Generic type params associated with the Move function
Move function generic type param
object
Move abilities tied to the generic type param and associated with the function that uses it
Parameters associated with the move function
Return type of the function
Type arguments of the function
Arguments of the function
An enum of the possible transaction payloads
object
module_bundle_payloadAn enum of the possible transaction payloads
object
multisig_payloadA hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
entry_function_payloadEntry function id is string representation of a entry function defined on-chain.
Format: {address}::{module name}::{function name}
Both module name and function name are case-sensitive.
0x1::aptos_coin::transferType arguments of the function
Arguments of the function
An enum representing the different transaction signatures available
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
multi_agent_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1The other involved parties’ addresses
The associated signatures, in the same order as the secondary addresses
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
fee_payer_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1The other involved parties’ addresses
The associated signatures, in the same order as the secondary addresses
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
single_senderAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
ed25519_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_ed25519_signatureThe public keys for the Ed25519 signature
Signature associated with the public keys in the same order
The number of signatures required for a successful transaction
All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
single_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
multi_key_signatureobject
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256r1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
federated_keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
object
ed25519All bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
secp256k1_ecdsaAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
web_authnAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1object
keylessAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1Account signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
no_account_signatureAccount signature scheme
The account signature scheme allows you to have two types of accounts:
- A single Ed25519 key account, one private key
- A k-of-n multi-Ed25519 key account, multiple private keys, such that k-of-n must sign a transaction.
- A single Secp256k1Ecdsa key account, one private key
object
abstraction_signatureAll bytes (Vec0x and fulfilled with
two hex digits per byte.
Unlike the Address type, HexEncodedBytes will not trim any zeros.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1An enum representing the different transaction signatures available
object
no_account_signatureEvents generated by the transaction
An event from a transaction
object
object
A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034A hex encoded 32 byte Aptos account address.
This is represented in a string as a 64 character hex string, sometimes shortened by stripping leading 0s, and adding a 0x.
For example, address 0x0000000000000000000000000000000000000000000000000000000000000001 is represented as 0x1.
0x88fbd33f54e1126269769780feb24480428179f552e2313fbe571b72e62a1ca1A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034String representation of an on-chain Move type tag that is exposed in transaction payload.
Values:
- bool
- u8
- u16
- u32
- u64
- u128
- u256
- address
- signer
- vector: vector<{non-reference MoveTypeId}>
- struct: {address}::{module_name}::{struct_name}::<{generic types}>
Vector type value examples:
- `vector<u8>`
- `vector<vector<u64>>`
- `vector<0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>>`
Struct type value examples:
- `0x1::coin::CoinStore<0x1::aptos_coin::AptosCoin>
- `0x1::account::Account`
Note:
1. Empty chars should be ignored when comparing 2 struct tag ids.
2. When used in an URL path, should be encoded by url-encoding (AKA percent-encoding).The JSON representation of the event
A string containing a 64-bit unsigned integer.
We represent u64 values as a string to ensure compatibility with languages such as JavaScript that do not parse u64s in JSON natively.
32425224034Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
Cursor to be used for endpoints that support cursor-based
pagination. Pass this to the start field of the endpoint
on the next call to get the next page of results.
400
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
403
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
404
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
413
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
500
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
503
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas
507
This is the generic struct we use for all API errors, it contains a string message and an Aptos API specific error code.
object
A message describing the error
These codes provide more granular error information beyond just the HTTP status code of the response.
A code providing VM error details when submitting transactions to the VM
Headers
Chain ID of the current chain
Current ledger version of the chain
Oldest non-pruned ledger version of the chain
Current timestamp of the chain
Current epoch of the chain
Current block height of the chain
Oldest non-pruned block height of the chain
The cost of the call in terms of gas