Skip to readiness evaluator
Continuous evidence monitor Public · Read-only · No wallet

XRPL Readiness Evaluator

Observe the XRP Ledger as a living financial rail: validated-ledger events, XRBC and RLUSD liquidity, protocol capabilities, tokenized assets, regulated access, interoperability and institutional workflows—while keeping announcements, pilots, private ledgers, Ripple products and global-finance context explicitly separated.

Ledger events WebSocket stream15 seconds independent polling6 hours source fingerprint monitoring0 automatic claim promotions
Network boundaryPublic XRPL, private XRPL-derived platforms, sidechains and Ripple products remain separately labeled.
Evidence boundaryA changed webpage or keyword match creates a candidate—not a verified integration claim.
Score boundaryScores summarize observed evidence and operating conditions; they are not forecasts, endorsements or investment ratings.
Two independent measurements

Integration Evidence and Settlement Readiness

Institutional evidence changes when reviewed sources change. XRBC settlement readiness changes with the live validated ledger, AMM and order book.

Snapshot loading
XRBC Settlement Readiness

Live operational score from validated-ledger freshness, XRBC AMM reserves, fee and two-sided order-book conditions.

Verified evidenceReviewed

Loading public-ledger and separately classified evidence.

Primary sources monitored

Waiting for source monitor snapshot.

Validated-ledger telemetry

Live XRPL and XRBC Settlement Layer

Validated ledgers stream directly from public XRPL WebSocket infrastructure when available. A separate 15-second Render-proxy poll cross-checks server state, amendments, AMMs and funded order books. No wallet or transaction is involved.

Connecting to validated-ledger data…
Next refresh:
Ledger streamConnectingTrying approved public endpoints
Stream ledgerNo ledger event yet
Transactions / ledgerLedger hash unavailable
Cross-checkPendingStream vs 15-second validated-ledger poll
Validated ledgerAwaiting ledger close time
Server stateBase fee unavailable
XRBC AMM XRP reserveTrading fee unavailable
XRBC AMM token reserveSpot price unavailable
Best DEX bidFunded depth unavailable
Best DEX askFunded depth unavailable
Bid / ask spreadTwo-sided status unavailable
Live-data confidenceNo successful refresh yet

Live score construction

The settlement score remains unavailable until independently parsed ledger, AMM and order-book responses are received.

XRBC-specific boundary: XRBC liquidity is one issued-asset operating sample. It does not measure total XRPL throughput, the value of XRP, or global institutional adoption.

Read-only request set

server_info, validated ledger, feature, XRP/XRBC AMM and both funded order-book sides, plus the same AMM/book checks for the XRP/RLUSD reference rail. Failed components stay unavailable.

Inspect raw live responses
No live response has been recorded.
Observable settlement rails

XRBC and RLUSD Market-Rail Observatory

Two issued assets are observed separately against XRP. XRBC shows this ecosystem's market-operating conditions; RLUSD provides an institutional stable-value reference rail. Neither is treated as total XRPL activity.

Validated ledger · read-only
XRBC / XRP

XRBitcoinCash rail

Awaiting data
AMM XRP
AMM XRBC
Spot
Spread
Best bid
Best ask
RLUSD / XRP

Ripple USD reference rail

Awaiting data
AMM XRP
AMM RLUSD
Spot
Spread
Best bid
Best ask

RLUSD issuer: rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De. Liquidity here is an observed XRP/RLUSD market slice, not circulating supply, reserve proof or total payment volume.

Validated-ledger close ageRolling session only · up to 60 polls
XRBC bid/ask spreadRolling session only · percent
RLUSD bid/ask spreadRolling session only · percent
Protocol capability surface

Running Server, Amendments and Reference Release

The server build and feature response are observed live. Release notes describe software capability; only the live amendment response can indicate whether a known amendment is enabled on the queried network/server.

Known Amendments
Observed server buildAwaiting server_info
Reference releasexrpld 3.3.0Published Aug 6, 2026 · software availability only
Known amendments returnedAwaiting feature response
Enabled amendments returnedAmendment-blocked state unknown
Protocol features are loading.
Activation boundary: a feature appearing in xrpld release notes means the software contains code for it. XRPL amendments activate separately through network governance; the page never converts release availability into an “enabled on Mainnet” claim.
Financial-system construction

From Core Ledger to Mainstream Financial Workflows

This map shows where reviewed evidence exists across the integration chain. It does not imply that every institution or system uses every layer.

Public XRPL Private XRPL-derived XRPL-adjacent sidechain Announcement / pilot Context only
Reviewed primary-source register

Verified Integration Evidence

Every item states what the source supports and what it does not support. Automated source changes never enter this register on their own.

0items shown
Automated source health

Primary-source Monitor

The scheduled updater records status, final URL, MIME type, HTTP metadata, content fingerprint, signal terms and changes. A blocked source is marked unavailable—not treated as disproving the underlying claim.

Automatic review boundary: HTTP success proves only that a source was reachable. A changed hash proves only that its retrieved representation changed. Neither event verifies institutional adoption.
Change-detection queue

Candidates Requiring Human Review

Changed monitored sources appear here until reviewed, dismissed or deliberately converted into a new versioned claim in the source registry.

0 pending
Transparent classification

Methodology and Non-Overclaiming Controls

The evaluator is designed to reveal evidence progression without presenting corporate announcements, private pilots or adjacent systems as equivalent to validated public-XRPL use.

1 · Identity separation

Ripple, XRP, public XRPL, private XRPL-derived systems, Ripple corporate products, sidechains, SWIFT and BIS architectures remain distinct.

2 · Maturity separation

Awareness, software release, announcement, pilot, real-value test, project launch and operational infrastructure receive different meanings and weights.

3 · Live activation check

Release notes show software capability. The public feature API is queried separately for observed amendment enabled/supported state.

4 · Primary-source rule

Verified items require an identified primary source, a supported finding, an explicit limitation and a review date.

5 · Candidate firewall

Automated HTTP, keyword and content-fingerprint changes cannot promote themselves into verified evidence.

6 · Freshness rule

Ledger-event age, polling age, evidence generation time and source-check status remain visible; stale values are never silently treated as live.

7 · Rail separation

XRBC and RLUSD liquidity are displayed as separate observable rails. Neither is a proxy for total XRPL activity, reserve backing or institutional volume.

8 · Score disclosure

The evidence index measures reviewed coverage/maturity across eight stages. The settlement score measures current XRBC market-operating conditions only.

Inspect machine-readable evidence snapshot
Evidence JSON is loading.
Baseline continuity: This release was rebuilt from the deployed v3.0.0 Readiness Evaluator structure and current ecosystem header, then extended with the v3.1 observatory systems. An older external evidence JSON cannot silently downgrade the newer embedded reviewed baseline.
Not claimed: This page does not claim that SWIFT uses XRP or the public XRP Ledger; that XRPL or XRP is “ISO 20022 certified”; that every Ripple customer uses XRP or public XRPL; that a pilot is production adoption; or that token issuance alone transfers legal title.