Clearpool proposes XRPL expansion and CPOOL-to-CLEAR token migration

Clearpool has submitted a governance proposal that ties a migration from its current CPOOL token to a new CLEAR token with an expansion of its lending platform onto the XRP Ledger (XRPL). The plan includes institutional credit products, a treasury recapitalization, and a fee‑backed token buyback program.

Token migration and supply changes

Under the proposal, existing CPOOL holders would receive CLEAR at a 1:1 ratio. Seventy percent of the initial CLEAR allocation would be used for this migration, raising the total supply from 1 billion CPOOL to 1.125 billion CLEAR. The remaining allocation would be distributed as follows: 10% to the ecosystem, 15% to the treasury, and 5% to contributors. An unlock schedule would increase circulating CLEAR to 1.428 billion over three years, with half of all protocol fees earmarked for open‑market CLEAR buybacks and permanent token burns.

Institutional credit products on XRPL

Clearpool aims to build credit products that leverage two pending XRPL standards: Single Asset Vaults (XLS‑65) and the Lending Protocol (XLS‑66). The vault standard would pool funds under defined management rules, while the lending protocol would use those vaults to issue, service, and repay fixed‑term loans. Borrower assessment and credit terms would be set off‑chain by participating institutions, with the ledger recording the resulting loan data.

Ripple involvement and RLUSD lending

Ripple has pledged capital to support yield products denominated in XRP and its stablecoin RLUSD. The proposal envisions an RLUSD‑denominated working‑capital fund for fintech and payment companies, with Ripple participating as a limited partner. RLUSD is issued by Standard Custody & Trust Company under a New York‑state charter and is backed by cash and cash equivalents.

Governance and next steps

The proposal entered the Snapshot governance process, with a 14‑day community discussion period before a token‑holder vote. Implementation of the XRPL credit products depends on validator approval of the XLS‑65 and XLS‑66 standards.