XRBitcoinCash logo

XRPL offers · Wallet-reviewed actions

Order Manager
v3.0.0 · Mobile-only Xaman signing · Desktop read-only Mainnet

Review open offers. Cancel deliberately. Verify validation.

Inspect a connected account’s validated XRPL offers, approve each cancellation in your wallet, and treat it as complete only after the transaction is found in a validated ledger. XRBC trust-line and purchase actions are Mainnet-only.

Validated readsAccount offers and balances use the validated ledger.
Bounded batchesSequential cancellation stops on rejection, failure, or timeout.
Fresh path quoteXRBC purchase paths are calculated immediately before review.
Mobile-only signingDesktop browsers never receive wallet-session authority; use the local QR handoff.

Access boundary

Public desktop → mobile wallet → independently validated

1

Public

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

2

Mobile Xaman

Wallet authorization is available only on the canonical HTTPS page from a likely mobile/touch device. Desktop users scan the local QR instead.

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 hidden holding gate and no desktop wallet session. Desktop can inspect a public XRPL classic address and scan a locally generated handoff QR. It cannot authorize Xaman, GemWallet, Crossmark, MetaMask, injected providers, or transaction signing. The Render endpoint remains bounded/read-only and is never a signer.

Mobile-only signing policy

Wallet access without a desktop wallet session

Checking device posture…
Desktop = public/read-onlyNo Xaman OAuth, injected extension, MetaMask, GemWallet or Crossmark connection is initiated on desktop by this release.
Mobile = Xaman onlyThe Xaman SDK is loaded from the official Xaman host only after a deliberate mobile user action. No wallet seed or private key is requested.
Every write = new intentAPP, six-digit CHALLENGE, DOMAIN and INTENT_SHA256 memos bind the browser summary to a short-lived transaction request.
XRPL · mobile authorization

Xaman

On a phone or tablet, this button uses Xaman’s browser/Web3 authorization flow and deeplinks into Xaman. On desktop, the same button only reveals the mobile handoff QR.

Status: Not connected

Six-digit challenge—
Intent SHA-256—
No wallet required

Inspect a public XRPL address

Desktop users can review open offers using only a public r… address. This creates no wallet session and cannot enable transaction buttons.

GemWalletOfficial integration is browser-extension based. Disabled here because this release does not grant desktop wallet-session authority.
CrossmarkOfficial integration is browser-extension based. Disabled here rather than inventing an unsupported mobile deeplink.
Security policy: native XRPL writes are Mainnet-only and require the canonical HTTPS origin, a top-level page, a likely mobile/touch device, an active Xaman account that still matches the selected account, explicit transaction review, a fresh intent challenge, and post-validation field matching.

Open Orders

No data yet.

Mobile-only security mode disables bulk cancellation. Cancel one visible offer at a time; each cancellation receives a fresh Xaman request, challenge, intent digest, and post-validation comparison. The queue stops if an approval is rejected, a transaction fails, or validation cannot be confirmed.

Results

Cancellation submissions, observed balance changes, and reserve-release estimates will appear here.
Activity log

      

    


    

      
Quick Buy · XRBitcoinCash (XRBC)

      
Mainnet only. Requires the exact XRBC trust line. Each purchase requests a fresh XRPL path and may route through AMM pools or order books. The signing request uses the displayed maximum XRP spend, including 2% path-movement headroom.

      

        
        Issuer: rEjwniYhYR5QDZzK1a1x2359j8j8N43Ypw
        Trust limit: 20,999,999.999999996 XRBC
      

      

        
        
        
        
      

      
No purchase quote requested.

      

    


    

      
Important

      

        Verify the account, network, transaction type, issuer, currency, amount, fee, and maximum spend in your wallet before approving. XRPL transactions are irreversible after validation. Never approve a transaction that differs from the page summary.
      

      

        Disclaimer: This is non-custodial software, not a broker, exchange, or guarantee. You sign in your wallet. A validated offer cancellation can reduce OwnerCount and release the corresponding owner-reserve requirement, but the observed XRP balance change also includes fees and other ledger activity. Verify every result independently.
      

      

        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 and only on the canonical mobile experience. 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.