On this page
    Articles / Trading access and infrastructureReturn to article archive

    Bithomp Adds RLUSD–USDC Swap Access Through XRPL DeFi

    The material change is an easier wallet-connected trading route, not a new stablecoin or a new XRPL market. Bithomp is exposing RLUSD ↔ USDC swaps through its DeFi interface while the underlying XRP Ledger DEX and RLUSD/USDC liquidity already existed.

    What changed

    Bithomp announced a direct user interface for swapping RLUSD and USDC on the XRP Ledger using Ledger Wallet or another XRPL-compatible wallet. The development is about access to existing XRPL trading infrastructure through Bithomp DeFi.

    Bithomp already exposes XRP Ledger token activity and DEX swap data through its API. Its documentation distinguishes DEX swaps executed through an AMM from swaps matched through order-book offers, which is consistent with the interface sitting on top of native XRPL trading infrastructure rather than creating a separate off-chain market.

    This is not a new RLUSD/USDC market

    The RLUSD/USDC pair was not created by this announcement. Bithomp already exposes an XRPL AMM pool for RLUSD and USDC, including reserves, trading fee, LP supply and swap history.

    That distinction matters for historical treatment. SOG should not describe this as an RLUSD launch, a USDC launch, a new XRP Ledger deployment, or the creation of the first RLUSD/USDC market. The new information is the Bithomp-facing wallet and swap route.

    Both assets were already on the XRP Ledger

    Ripple documentation identifies RLUSD as an XRP Ledger issued token and provides the XRPL mainnet issuer account. Circle separately describes USDC on XRPL as a native form of USDC and documents XRPL-specific access through Circle Mint and ecosystem applications.

    The Bithomp feature therefore connects two already-existing XRPL stablecoin deployments. It does not establish a new chain deployment for either asset.

    What the interface changes

    For users, the important change is operational: a person can connect an XRPL-compatible wallet, select RLUSD and USDC, and submit a swap through a dedicated trading interface rather than manually navigating an order book or AMM pool.

    Bithomp's XRPL AMM documentation explains that XRPL AMMs can interoperate with the traditional order-book DEX. Its API documentation likewise identifies DEX swaps as either AMM-based or order-book-offer based. The interface can therefore be understood as an access layer over native XRPL liquidity rather than a new custodied exchange balance.

    Why SOG is not creating a canonical event

    Current SOG treatment: article-only, non-canonical infrastructure and access development.

    The announcement does not change RLUSD or USDC lifecycle status, reserve backing, issuer identity, redemption terms, peg state, or chain deployment. It also does not provide the jurisdiction-specific evidence required for a canonical SOG Market Access record.

    SOG therefore keeps the development outside the canonical Event and Market Access layers for now. A wallet or interface improvement can be historically useful without automatically becoming a stablecoin lifecycle event.

    Confirmed facts and boundaries
    QuestionSOG treatment
    Can Bithomp users access an RLUSD ↔ USDC swap interface?Yes. Bithomp announced the route and linked its DeFi trading interface.
    Can Ledger Wallet be used?Yes, according to Bithomp's announcement; other XRPL-compatible wallets are also described as supported.
    Was the RLUSD/USDC XRPL market created by this announcement?No. An RLUSD/USDC AMM pool already existed on XRPL.
    Did either stablecoin receive a new XRPL deployment?No. RLUSD and USDC were already available on XRPL.
    Did reserve or redemption terms change?No such change is established by the reviewed material.
    Does this prove universal access in every jurisdiction?No. No country-wide or jurisdiction-wide availability inference is made.
    What would trigger a later canonical review
    • a dated, material change to RLUSD or USDC issuance, redemption, reserve, legal, or lifecycle state;
    • a new chain deployment or migration supported by issuer documentation;
    • a provider-specific market-access change with explicit jurisdiction, function, effective date and network scope;
    • a material XRPL liquidity or trading change that crosses SOG's event threshold rather than only improving the user interface.
    Sources