XRPL-TX Bridge
XRPL-TX Bridge is the current TX-era identity of the bridge historically documented as XRPL-Coreum Bridge. It connects XRP Ledger and TX through an XRPL multi-signing account, a TX-side bridge contract, and a relayer set. Independent on-chain reporting says approximately 200,000 XRP left the bridge on August 9, 2026; the bridge was reported halted while the incident remained unresolved.
Bridge facts
- Canonical name
- XRPL-TX Bridge
- Type
- Interoperability Protocol
- Status
- Paused
- Confidence
- Medium
- Primary chains
- XRP Ledger, TX Chain
- Primary assets
- XRP
- Operator
- XRPL-TX Bridge relayer set
- Ecosystem
- TX
- Launch date
- Unknown
- End date
- Unknown
- Terminal reason
- Not applicable / unknown
- Last reviewed
- 2026-08-12
- Last verified
- 2026-08-12
Incident cases
XRPL-TX Bridge August 2026 XRP loss2026-08-09
Independent reproducible on-chain analysis supports a gross 199,916.3 XRP outflow from the XRPL-Coreum / current XRPL-TX Bridge through 94 successful outgoing payments over about 87 minutes on August 9, 2026. A broader approximately 97-minute activity window includes preceding wrapped-TX activity and is not used as the duration of the XRP-only drain. Current public relayer source code contains a validation path consistent with the reported relayer-logic hypothesis, but BIR does not treat that code observation or the independent reproduction as tx/Coreum first-party proof of the production exploit path.
Evidence records
- XRPL-to-Coreum relayer incoming-transaction processCoreumFoundation · Tier 1 · 2025-09-05
- XRP bridge loses 200K XRP after relayer logic flawcrypto.news · Tier 2 · 2026-08-11
- Coreum Bridge $200K Exploit: 17 Signers and One Missing Destination CheckSigIntZero · Tier 2 · 2026-08-18
Official URL status
Official URL recorded as live: https://docs.tx.org/docs-bridge/introductionHelp maintain bridge history
Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.