POSTEncode submission
This API accepts unsigned transaction information in JSON format and converts it to BCS (Binary Canonical Serialization) format. You can use the converted result to sign the transaction and then submit it via the Submit Transaction API.
That is, this endpoint enables you to submit transaction requests to the API even in languages that do not have BCS-supporting libraries. You do not need to use this endpoint when using an SDK that supports BCS, such as the official Rust, TypeScript, or Python SDK.
To sign a transaction using this endpoint's response:
- Decode the hex-encoded string from the response into bytes.
- Sign the decoded bytes.
- Convert the signed bytes to Ed25519 signature format and use it to create the final transaction signature.
A field representing the address of the account that sent the transaction. When expressed as a string, it is displayed as a 64-character hexadecimal string, and may be abbreviated by omitting leading zeros and adding 0x.
A field representing the transaction occurrence order. Represents a 64-bit unsigned integer as a string.
A field representing the maximum amount of gas to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
A field representing the gas price to use when the transaction occurs. Represents a 64-bit unsigned integer as a string.
A field representing the transaction expiration time. Represents a 64-bit unsigned integer as a string.
A field representing the payload to use when the transaction occurs.
The type of the payload
String representation of the Entry Function identifier defined on-chain.
Field representing the generic type arguments of the Entry function.
Field representing the arguments of the Entry function.
A field representing the nonce used to prevent transaction replay attacks. Represents a 64-bit unsigned integer as a string.
A field representing the transaction signature. One of Ed25519, MultiEd25519, MultiAgent, FeePayer, Account, or NoAccount can be selected.
The type of the signature
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
All byte (Vec) data is expressed as a hex-encoded string starting with 0x, with two hex digits per byte. Unlike the Address type, HexEncodedBytes does not omit any zeros.
Current block height of the chain
예: 0
Chain ID of the current chain
예: 0
Current epoch of the chain
예: 0
Oldest unpruned ledger version of the chain
예: 0
Current timestamp of the chain
예: 0
Current ledger version of the chain
예: 0
Oldest unpruned block height of the chain
예: 0
Cursor for the next page
예: string
Amount of gas actually used for transaction execution
예: 0