Invalid transaction submitted as valid, or vice-versa. Since Alonzo, the ledger may allow invalid transactions to be submitted and included on-chain, provided that they leave a collateral value as compensation. This prevent certain class of attacks. As a consequence, transactions now have a validity tag with them. Your transaction did not match what that validity tag is stating. The field 'data.declaredSpending' indicates what the transaction is supposed to consume (collaterals or inputs) and the field 'data.mismatchReason' provides more information about the mismatch.

Hierarchy

  • SubmitTransactionFailureSpendsMismatch

Index

Properties

Properties

code

code: "3136"

data

data: object

Type declaration

  • declaredSpending: "inputs" | "collaterals"
  • mismatchReason: string

message

message: string