Submit transaction
POST/transaction
Submit a signed transaction to the network containing a command to be executed such that if the submission is successful then it will be included in the chain's mempool. The network will then attempt to execute the transaction in the next available block, where the results of its execution can be seen on the EventBus.
Request
- application/json
Body
required
tx object
Transaction containing a command to execute on the network, and a signature to provide authentication.
Hex-encoded address of the sender. Not supported yet.
Protobuf message of type InputData
marshalled into bytes. If the transaction version is V3 or higher then this bytes
string must be prepended with chain_id_as_byes + \0
.
pow object
Proof-of-work containing the random transaction ID used by the client and the nonce.
Number which, combined with the transaction identifier, will produce a hash with the required number of leading zeros to be accepted by the network.
Unique transaction identifier used to seed the proof-of-work hash.
Hex-encoded public key of the sender.
signature object
Signature of the input data field, signed by the sender of this transaction.
Algorithm used to create the signature.
Hex encoded bytes of the signature.
Version of the algorithm used to create the signature.
Possible values: [TX_VERSION_UNSPECIFIED
, TX_VERSION_V2
, TX_VERSION_V3
]
Default value: TX_VERSION_UNSPECIFIED
Version of the transaction.
Possible values: [TYPE_UNSPECIFIED
, TYPE_ASYNC
, TYPE_SYNC
, TYPE_COMMIT
]
Default value: TYPE_UNSPECIFIED
Method of submission.
Responses
- 200
- default
A successful response.
- application/json
- Schema
- Example (from schema)
Schema
Error code to indicate the category of failure if the transaction was not successfully submitted.
Further details for why the transaction was not successfully submitted.
Unused.
Further details for the underlying consensus layer of the result of the transaction.
Whether or not the transaction was validated and submitted to the chain's mempool.
Hash of the transaction, which can be used to identify the transaction in a node's event stream.
{
"code": 0,
"data": "string",
"height": "string",
"log": "string",
"success": true,
"txHash": "string"
}
An unexpected error response.
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- ]
details object[]
{
"code": 0,
"details": [
{
"@type": "string"
}
],
"message": "string"
}