Memos and transaction status
Understand public notes, signing safeguards, expiry and validated results.
Browse all 38 guides
Optional public notes
Escrow and check Create, Finish/Cash and Cancel forms accept an optional memo. Each memo belongs to that transaction; finishing an escrow does not edit its creation memo. A memo is not an encrypted message, escrow condition or destination tag.
This interface limits the note to 256 UTF-8 bytes. Accented letters and emoji may take more than one byte. Whitespace-only input is omitted. The ledger stores the text as hexadecimal data; explorers may decode it. Read it in the transaction review before approving.
Review, sign, submit, validate
Reviewing prepares transaction fields. Your wallet then signs. XRPFrontend checks the response and submits it. A transaction hash can be displayed before settlement; it alone is not success.
The interface reports success only after a validated tesSUCCESS result. A validated failure can still consume a network fee. After a timeout or lost connection, look up the hash on the correct explorer before retrying. Mainnet links use livenet.xrpl.org and Testnet links use testnet.xrpl.org.
Xaman expiry adjustment
Xaman can extend LastLedgerSequence, the short transaction submission deadline, by up to ten ledgers beyond the reviewed value. The current comparison permits this bounded adjustment and signature fields; other reviewed fields must match.
LastLedgerSequence is not an escrow release date or invoice due date. A larger or unexpected change is blocked. This protection is not a substitute for comparing all meaningful details inside your wallet.