Shares the node's knowledge of any payloads associated with the given intent hash. Generally there will be a single payload for a given intent, but it's theoretically possible there may be multiple. This knowledge is summarised into a status for the intent. This summarised status in the response is likely sufficient for most clients.
The logical name of the network
"{{network}}"
The intent hash for a user transaction, also known as the transaction id. This hash identifies the core content "intent" of the transaction. Each intent can only be committed once. This hash gets signed by any signatories on the transaction, to create the signed intent. Either hex or Bech32m-encoded strings are supported.
Transaction status response
The status of the transaction intent, as determined by the node. FateUncertain or FateUncertainButLikelyRejection mean that it's still possible that a payload containing the transaction
An explanation as to why the intent status is resolved as it is.
An integer between 0
and 10^10
, marking the epoch from which the transaction will no longer be valid, and be permanently rejected.
Only present if the intent status is InMempool or Unknown and we know about a payload.