Skip to main content
Version: mainnet (v0.72)

Submit transaction​

Submit a signed transaction

Request Body required
    tx object

    Represents a transaction to be sent to Vega.

    address string

    Hex-encoded address of the sender. Not supported yet.

    inputData byte

    One of the set of Vega commands. These bytes are should be built as follows: chain_id_as_bytes + \0 character as delimiter + proto_marshalled_command.

    pow object

    Proof of work contains the random transaction id used by the client and the nonce.

    nonce uint64

    Number which, combined with the transaction identifier, will produce a hash with the required number of leading zeros to be accepted by the network.

    tid string

    Unique transaction identifier used to seed the proof-of-work hash.

    pubKey string

    Hex-encoded public key of the sender.

    signature object

    Signature of the input data.

    algo string

    Algorithm used to create the signature.

    value string

    Hex encoded bytes of the signature.

    version int64

    Version of the signature used to create the signature.

    version v1TxVersion

    Possible values: [TX_VERSION_UNSPECIFIED, TX_VERSION_V2, TX_VERSION_V3]

    Default value: TX_VERSION_UNSPECIFIED

    Version of the transaction, to be used in the future in case changes are implemented to the transaction format.

    type Type of transaction request, for example ASYNC, meaning the transaction will be submitted and not block on a response

    Possible values: [TYPE_UNSPECIFIED, TYPE_ASYNC, TYPE_SYNC, TYPE_COMMIT]

    Default value: TYPE_UNSPECIFIED

    • TYPE_ASYNC: Transaction will be submitted without waiting for response
    • TYPE_SYNC: Transaction will be submitted, and blocking until the tendermint mempool returns a response
    • TYPE_COMMIT: Transaction will be submitted, and blocking until the tendermint network has committed it into a block. Used only for debugging, not for submitting transactions
Responses

A successful response.

Schema
    code int64
    data Data for details
    height int64
    log string
    success Success will be true if the transaction was accepted by the node, **Important** - success does not mean that the event is confirmed by consensus
    txHash Hash of the transaction, if accepted
Loading...