Ripple CTO Emeritus Calls for Overhaul in Stablecoin Representation

David Schwartz, the leading architect of the XRP Ledger and former CTO of Ripple, criticized the early assumptions made in the crypto sector regarding the representation of digital dollars. He highlights how initial design decisions around dollar-based tokens overlooked significant distinctions, resulting in a structural problem that, while invisible in stablecoin transactions today, negatively impacts user experience.

What Was Mistaken in the Initial Design?

At the time, developers believed that using only the “USD” currency code for all dollar stablecoins was sufficient. It was assumed that wallets would internally match the issuer and currency, then display appropriate labels for users. Hence, a universal representation structure for each asset was deemed unnecessary.

Now the landscape has shifted with the rise of decentralized finance, which has seen many major issuers create their dollar tokens. Users now choose between different abbreviations like USDT, USDC, and RLUSD instead of simply sending money. Schwartz points out that the issue lies more in how these assets are presented to users than in the underlying technology.

Could a Dual-Layer Representation Solve the Problem?

Schwartz proposes a solution where asset representation is approached in two distinct layers. The first layer would involve a global tag representing the core asset, such as the U.S. dollar. The second layer would be a user-defined tag, allowing receivers to select which issuers’ tokens they accept as dollars according to personal preferences.

In his model, Schwartz expressed openness to accepting RLUSD, USDT, or USDC as dollar equivalents. However, another user or business could choose a more narrow list of issuers in their wallet settings. This approach would maintain the same core asset perception while allowing trust to be individualized.

The technical aspect of solving this problem has already been addressed by the XRP Ledger’s trust line mechanism. This allows users to define which assets and issuers they are willing to accept explicitly. Nonetheless, this technical solution has yet to render stablecoin payments intuitive and invisible for the broad user base due to interface challenges.

• Wallets must incorporate flexible issuer and currency code evaluation.
• Most current crypto wallets fail to consider issuer information adequately.
• The representation problem isn’t technical but rooted in user interface design.

Until wallets learn to process issuer information alongside currency codes, stablecoin payments will remain a complex tool catering to a narrow user group, according to Schwartz.