Ripple Removed Qivalis Post After Stablecoin Link Criticism

By Nathan Brooks

Ripple deleted a social media post and a related blog article about Qivalis after crypto commentator WrathofKahneman challenged the claimed link between Ripple and the consortium’s planned euro stablecoin. Qivalis comprises 37 European banks.

The deleted material highlighted BBVA and DZ BANK, both Qivalis members, as existing users of Ripple Custody. It also asked about the readiness of other member banks for launch. WrathofKahneman said Ripple had made no announcement establishing a role in the token project.

What did WrathofKahneman challenge?

WrathofKahneman, whose account is @WKahneman, said: “Ripple had not announced new partners, a role in the Qivalis stablecoin or direct participation in the project.”

That distinction matters because a custody relationship with a member bank does not, by itself, establish that Ripple Custody will hold reserves, operate infrastructure, distribute the token or participate in governance. The source does not assign those functions to Ripple. It says the deleted post drew attention to existing customers while the commentator challenged the implied project connection.

The post also asked “whether other consortium banks would be ready when Qivalis launches its stablecoin.” For a 37-bank consortium, the broader question was practical: whether institutions beyond BBVA and DZ BANK would be prepared to use the planned product.

How does Fireblocks fit?

Qivalis selected Fireblocks in April 2026 to build technology for tokenization, custody, wallets and compliance. The selection places Fireblocks at the center of the announced technology work and gives Qivalis a named infrastructure provider separate from Ripple’s relationships with BBVA and DZ BANK.

The planned euro stablecoin is described as MiCA-compliant. The source identifies no issuing legal entity, launch date, reserve structure, governance model, blockchain network or token standard. Those details remain unavailable, so any description of the token’s final production design would go beyond the confirmed record.

What does the deletion change for banks and market participants?

For Qivalis members and potential users, the practical change is evidentiary rather than technical. The removal withdraws Ripple’s own presentation of the connection; it does not alter Fireblocks’ April 2026 selection, the participation of BBVA and DZ BANK, or the description of the planned token as MiCA-compliant.

For counterparties, the relevant distinction is between a named service provider to a member bank and a contracted participant in the stablecoin. BBVA and DZ BANK were identified as Ripple Custody users. Fireblocks was selected to build the token’s technology. Ripple’s participation in the consortium or stablecoin remains unannounced in the source.

The deletion also should not be read as a finding that the underlying custody relationships never existed. The report identifies BBVA and DZ BANK as existing users. What it does not report is any extension of those relationships to Qivalis’s planned token, including reserve custody or operating responsibilities.

Where does the project stand?

Qivalis brings together 37 banks, while Fireblocks holds the reported technology assignment across four functions: tokenization, custody, wallets and compliance. The source provides no launch timetable or detail on how member banks would coordinate adoption.

That absence limits any conclusion about operational readiness. A MiCA-compliant description addresses a regulatory characteristic, not the full set of controls needed for issuance, settlement and wallet operation. The source supplies no information on redemption, reserves, smart-contract design or cross-bank settlement, and it does not support assigning those functions to Ripple, Fireblocks or any bank.

Ripple’s withdrawal narrows the public narrative around the project. It does not fill the project documentation gaps, and it does not change the announced supplier lineup.

The next market-structure checkpoint is any Qivalis launch disclosure, particularly whether it identifies the issuer, chain, token standard and compliance roles rather than leaving them inferred from existing custody relationships.