The block number this transaction was included in. For transactions that have not been included in a block yet, this will be zero.
The fee paid to the root node to include this transaction.
The first input to this transaction. For deposits, the input will have
a blockNumber
, txIdx
, and outIdx
of zero and a depositNonce
set
to the nonce of the deposit being spent.
A transaction must always define input0
.
The confirm signature belonging to the transaction whose outputs are
referenced by input0
.
The second input to this transaction. This may be set to a 'zero' input if there are no coins being spent via this input.
The confirm signature belonging to the transaction whose outputs are
referenced by input1
.
The index of this transaction within the block it was included in. For transactions that have not been included in a block yet, this will be zero.
Generated using TypeDoc
The body of a Plasma transaction. We draw a distinction between the body of a transaction and its signatures to match the transaction encoding expected by the Plasma smart contract. The contract expects transactions to be RLP-encoded as follows:
The TransactionBody, in this case, is the first element of the above array.
The
inputXConfirmSig
fields represent the confirm signatures belonging to the transaction referenced by theblockNum
,txIdx
, andoutIdx
fields of the referenced input - in other words, the 'previous' transaction in the UTXO DAG. By committing to confirm signatures in this manner, anyone can use them to challenge an invalid exit once an output is spent.