Definition and scope
Building a Reliable Transaction-Submission System addresses a distinct part of developer guides. Persist signed transactions and reconcile them against validated ledgers until success or expiry is proven.
Reliable XRPL applications do more than submit JSON. They choose appropriate server connections, manage pagination and subscriptions, construct and sign transactions safely, interpret tentative and validated results, and recover cleanly from interruption. Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
How it works
Reliable submission persists the signed blob and hash, assigns LastLedgerSequence, submits to a trusted server, and keeps querying validated ledgers until success, final failure, or provable expiry.
- LastLedgerSequence: verify this field, object, or component against the cited protocol documentation.
- tx_blob: verify this field, object, or component against the cited protocol documentation.
- hash: verify this field, object, or component against the cited protocol documentation.
- validated: verify this field, object, or component against the cited protocol documentation.
- expiry: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A worker records Sequence, hash, and expiry before broadcast, resubmits the identical blob when safe, then reconciles tx results and account sequence after the last ledger passes.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
A preliminary tesSUCCESS only means the server accepted the transaction for processing. Re-signing a changed transaction during uncertainty can create duplicate intent.
Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
Current network status
Network-independent guidance. This guide explains an operational or representational concept. Confirm live server values and service-specific behavior before relying on it in production.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.