Signature, receipt and durability

Signature, receipt and durability A sequence diagram generated by Archify. build / simulate sign + submit verified envelope ingest ack: signature proposed payload finalized height execute + stage publish result post-apply drain durability result receipt event notification hint get transaction read receipt execution status reconciled result Client · sign + reconcile · Sequence participant Client sign + reconcile RPC · validate envelope · Sequence participant RPC validate envelope Ingest · mempool · Sequence participant Ingest mempool Consensus · finalized payload · Sequence participant Consensus finalized payload Reporter · ordered execution · Sequence participant Reporter ordered execution Journal · program writes · Sequence participant Journal program writes Live state · receipt + state · Sequence participant Live state receipt + state Writer · WAL / QMDB · Sequence participant Writer WAL / QMDB WebSocket · notification hint · Sequence participant WebSocket notification hint Legend request return async trace default message

Three separate observations

  • • A signature means ingest acceptance, not successful execution.
  • • Execution publishes a live receipt; the writer completes durability separately.

Read the result before acting

  • • Finalized status alone does not prove power-loss durability.
  • • Reconcile lost notifications with the saved signature; do not resend.

Failure accounting

  • • Failed execution discards staged program writes.
  • • Documented fee and EVM nonce accounting can survive that failure.