Paxeer XDocs
How does a transaction reach finality?

From submission to a committed block

A transaction is final once the block covering its execution receipt is committed. Before that it passes through two earlier stages, and pax_sequencerReceipt reports which one it has reached.

Transaction progress on one network

kernel executesvalidators commit
SubmittedThe node holds the transaction
ReceiptedSigned execution receipt
CommittedCovered by a committed block
  1. Submitted to Receipted: kernel executes
  2. Receipted to Committed: validators commit
What each rung lets you decide
RungRequired evidenceApplication decision
submittedTransaction hash and nonce without a receiptTrack the existing submission.
receiptedSigned execution receipt and consistent decoded fieldsInspect success or failure and the recorded effects.
committedReceipt covered by a committed blockTreat the verified outcome as final.

Recovery

When you do not know the outcome

Track the transaction you already sent and obtain its evidence before taking another economic action. A new transaction can repeat the intended payment.

  1. Keep what you signed

    Retain the signed transaction, its hash and its nonce.

  2. Read the receipt

    Call pax_sequencerReceipt with that transaction hash.

  3. Verify the signature

    Check the signed receipt against the governed receipt keys from px_getReceiptKeys.

  4. Check the covering block

    Treat the outcome as final only once a committed block covers the receipt.

A submission acknowledgement is not finality

Release a paid resource only after checking the receipt against the expected payer, recipient, asset, amount and execution result, together with the block commitment your application requires. See payment release policies.

Ask next

2 blocks are shown verbatim from the documentation, and every identifier in the text was found there.

Reviewed answer
From submission to a committed block · Paxeer X Docs