XRPL defensive monitoring · local-first working preview

XRBC Bridge Integrity Tools

Optional Xaman connection active

XRPL Bridge Integrity Monitor

Check whether a claimed bridge deposit actually reached the correct XRP Ledger vault, whether the destination chain created the matching amount, and whether verified reserves still cover bridge liabilities. The page also screens public bridge code for missing safeguards and creates a locally hashed evidence record.

Verify the real depositDo not trust a memo or transaction hash alone. Confirm the destination, result, delivered amount, and bridge-vault balance increase.

Match both blockchainsCompare each XRPL deposit with the destination-chain mint, and each burn or lock with its XRPL withdrawal.

Watch solvencyCompare verified reserves with circulating wrapped assets, pending withdrawals, and unresolved liabilities.

Preserve evidenceGenerate a deterministic JSON evidence pack and local SHA-256 hash without uploading the project from this page.

Plain-language rule: a bridge should never create spendable value on another chain unless the matching value was independently verified on the source chain.

This preview performs defensive local analysis. It does not control a bridge, move funds, prove criminal intent, replace a professional security audit, or guarantee that every vulnerability will be found.

Free public safety directory · reusable XRBC gate for advanced tools

Bridge Warnings Stay Public; Advanced Watchdog Tools Require 10 XRBC

Anyone can browse listed bridges, status colors, known incidents, vault addresses, contracts, review dates, and source links without a wallet. A connected wallet holding at least 10 XRBC unlocks custom bridge profiles, technical scans, deposit analysis, reconciliation, evidence exports, and bridge-review submission files.

Public access active

Reusable participation gate

Connect Xaman and Verify 10 XRBC

XRBC remains in the wallet. This page does not transfer, lock, burn, escrow, consume, or take custody of the tokens.

Not checked

Wallet stateNot connected

XRPL account—

XRBC balance0 XRBC

Amount short10 XRBC

Advanced accessLocked

Balance verificationNot checked

Connection modeReady

Selected bridgeNone selected

Connect Xaman to verify the reusable 10 XRBC balance requirement. Public bridge safety information remains available without connecting.

Advanced controls are locked. Public bridge profiles, warnings, incident reports, verified addresses, and source links remain free.

Xaman wallet identification

Desktop authorization uses Xaman's secure QR flow. Mobile opens Xaman through its secure deeplink. Inside the Xaman xApp, the selected account context is resolved directly.

Server-side advanced API enforcement

The browser gate controls the interface only. When a backend is activated, it must independently re-verify wallet ownership, XRBC balance, request limits, payload size, and duplicate submissions for every protected request.

Free public bridge research is active. Wallet connection is optional and creates no XRPL transaction.

Use every bridge at your own risk. Green, yellow, and red labels are research classifications—not guarantees, endorsements, legal findings, or predictions. Bridge software, operators, contracts, addresses, and status can change after the directory was reviewed.

XRBitcoinCash does not operate the listed bridges and is not responsible for losses, failed transfers, malicious interfaces, incorrect third-party data, delayed updates, or decisions made from this monitor.

Current review state

Bridge Health Dashboard

These values update as the local checks are completed.

No analysis

Overall stateNot reviewed

Backing ratioUnknown

Critical findings0

Last local analysis—

XRP LedgerValidated source transaction

Bridge vaultActual balance must increase

Relayers / witnessesEvidence and signatures

Destination chainMatching mint or release

Seven-stage bridge integrity workspace

Build, Test, Reconcile, and Preserve

Use Beginner mode for plain explanations, Guided mode for the recommended workflow, or Expert mode for full technical fields.

Advanced tools locked

Public safety access stays open: the monitored bridge directory, status colors, incident warnings, addresses, contracts, and supporting sources do not require a wallet. Controls that create custom profiles, run technical analysis, export evidence, or prepare bridge submissions require the reusable 10 XRBC gate.

Persistent local workspace: entries, findings, and evidence are saved in this browser. Download Project creates a portable JSON backup. The page does not require a wallet. Directory refresh requests only the public JSON sources named above.

Stage 1

Identify the Bridge

Tell the monitor which account should receive funds and which chain should create the matching representation.

Not configured

Bridge profile

Choose a bridge from the monitored directory

Selecting an entry automatically fills the destination chain, XRPL vault or door account, contract/module, asset, endpoints, and known warning notes.

Green: popular or established listing; not a safety guarantee Yellow: incomplete verification, changed support, or warning signals Red: reported exploit, halt, insolvency, or material failure

No bridge selected

Use the directory instead of typing technical addresses. Unknown or externally discovered bridges remain yellow until their accounts and contracts are independently verified.

Built-in verified records are available. Refresh checks the separate directory file and an external discovery feed.

Directory update sources and limitations

The same-origin file /xrpl-bridge-directory.json is the curated source of truth and can be updated without editing this HTML. DefiLlama is used only to discover possible new bridge names. Bithomp can be added later through an approved API plan; its public dApp page is not treated as a complete bridge registry.

Bridge name Destination blockchain XRPL bridge vault or door account Destination contract or module XRPL asset XRPL issuer Expected bridge fee Published signer/evidence threshold Maximum single withdrawal (% of reserves) Maximum hourly reserve drain (%)

New bridge review submission: verified advanced users can prepare a structured JSON submission for a new bridge or a correction to an existing record. This beta creates a local submission file; it does not publish or change a directory classification automatically.

Official operator or bridge URL Review request and supporting details

Stage 7

Generate and Verify the Bridge Evidence Pack

The complete local project is canonicalized and hashed with SHA-256. The evidence pack is not uploaded by this page.

Deterministic local record

Schema—

SHA-256—

Generated—

Findings recorded0

No evidence pack has been generated.

Important boundaries

What This Page Can and Cannot Establish

Defensive analysis

It can expose inconsistent public facts

Useful

Examples include a payment sent to the wrong destination, no increase in the bridge vault, a mint without a verified source deposit, duplicate source hashes, or liabilities exceeding reserves.

It cannot prove intent from a coding omission

Caution

A missing check may result from negligence, misunderstanding, poor testing, unsafe design, or deliberate conduct. Intent requires evidence beyond a local code screen.

Public source may not equal deployed software

Caution

Production monitoring should compare signed build hashes, image digests, contract versions, signer lists, and relayer attestations with the reviewed source.

Unknown is not safe

Rule

Unavailable metadata, endpoint disagreement, unverified supply, or an unreadable contract state should remain unknown or blocked rather than being converted into a favorable score.

Local audit trail

Activity Log

The log records local actions taken during this browser session and saved project.