XRPL open-offer cleanup · non-custodial

Open Order Cleanup

Validated XRPL reads · Xaman-reviewed OfferCancel Mainnet Data network

Find open trades you forgot about. Clear the ones you no longer want.

This tool reads the wallet’s currently open XRPL offers directly from a validated ledger. It is useful after testing, after using an exchange or trading interface you no longer use, or simply as a final check that no old limit order is still active. Canceling an offer removes that open commitment; when the ledger object is removed, its owner-reserve requirement can also be released back to the account’s available XRP.

Find every current offeraccount_offers reads the selected XRPL account at a validated ledger.

One cleanup controlClear visible offers in a bounded sequence; every cancellation still requires Xaman approval.

Verify, don’t assumeEach OfferCancel must reach validated tesSUCCESS and match the saved intent.

Show what came backAfter cleanup, compare OwnerCount and XRP balance and report the estimated owner reserve released.

Important: the XRPL account_offers response does not reliably tell this page how “old” an offer is. This tool therefore lists every offer that is still open and lets you clear the ones you no longer want. It does not guess that an offer is stale.

Access boundary

Public inspection → Xaman approval → validated cleanup

1

Public

Review the workflow, exact XRBC identifiers, safety rules, and method without connecting a wallet.

2

Xaman

Desktop uses Xaman’s official QR authorization and transaction QR. Mobile uses the same supported browser flow as a same-device deeplink. No seed or private key is entered on this page.

3

Intent-bound + validated

Every write receives a fresh six-digit challenge and SHA-256 intent digest, then the validated transaction is compared with the prepared critical fields.

No token gate and no desktop extension signer. Public-address inspection remains read-only. When you deliberately connect Xaman on desktop, Xaman presents its official phone QR; transaction approval stays in Xaman. GemWallet, Crossmark, MetaMask and other injected desktop wallets are not used by this page. The Render endpoint remains bounded/read-only and is never a signer.

Xaman authorization · public-address inspection

Load the account, then clear its open offers.

Checking device posture…

Read without a walletPaste any XRPL classic address to inspect its currently open offers. That creates no signing authority.

Desktop Xaman = official QRPress Connect Xaman. Xaman’s browser SDK creates the authorization QR; this page no longer uses a permanently embedded handoff QR as if it were a wallet request.

Every cancel is boundAPP, six-digit CHALLENGE, DOMAIN and INTENT_SHA256 memos bind each OfferCancel to a short-lived request and its validated result.

XRPL · Xaman

Connect Xaman

Desktop: Xaman shows its official authorization QR for the phone that holds Xaman. Mobile: the same action opens Xaman directly. The browser never receives your seed or private key.

Status: Not connected

Six-digit challenge—

Intent SHA-256—

No wallet required

Inspect a public XRPL address

Paste an r… address to read its validated open offers. Use this first if you only want to check whether an old or forgotten limit order is still active.

Security policy: wallet authorization is allowed only on the canonical top-level HTTPS page. Writes are Mainnet-only, Xaman account identity is rechecked before signing, every OfferCancel receives a new challenge and intent hash, and completion is reported only after validated tesSUCCESS plus critical-field matching.

Live cleanup route Waiting for an account

1 · AccountNot loaded

2 · account_offersWaiting

3 · Xaman OfferCancelWaiting

4 · Validated resultWaiting

“Clear Open Offers” is one cleanup workflow, but XRPL still requires a separate OfferCancel transaction for each offer. This page prepares them sequentially and stops immediately on rejection, failure, mismatch, or validation timeout.

Validated ledger function

Currently open XRPL offers

Waiting for account

Load a public XRPL address or connect Xaman to check for open offers.

Every row is an offer that is still open on the validated XRP Ledger. Cancel individually, or use Clear Open Offers to process the visible set sequentially. The queue stops if any Xaman approval is rejected or a validated result cannot be confirmed.

Execution result

Results

No cancellation submitted

Validated OfferCancel results, OwnerCount changes, observed XRP balance changes, and estimated owner-reserve release will appear here.

Activity log

Important

Verify the account, Mainnet network, transaction type OfferCancel, OfferSequence, fee, challenge, and intent digest in Xaman before approving. XRPL transactions are irreversible after validation. Never approve a transaction that differs from the page summary.

Read-only Render proxy contract

The page needs bounded POST access to server_info, server_state, account_info, account_offers, account_lines, ripple_path_find, and tx. The final method checks a submitted hash for validated: true and tesSUCCESS. The proxy should allowlist methods, validate parameters, rate-limit clients, impose response/time limits, and never receive seed phrases or sign transactions.

Xaman Developer Dashboard requirement

This release uses the shared XRBC browser application key and canonicalizes wallet authorization to https://xrbitcoincash.com/limit-extraction.html. Register that exact URL in the application’s Origin/Redirect URIs. The www host is deliberately not used for wallet authorization; mobile wallet actions redirect to the canonical non-www origin first.

Wallet capability separation

Xaman is the only signing lane enabled by this release. On desktop the official browser authorization uses Xaman’s QR flow; on mobile the same SDK flow can deeplink into Xaman. GemWallet and Crossmark remain browser-extension integrations in their current official documentation, so this page deliberately does not connect them. MetaMask and other injected/EVM providers are not loaded or queried.