Why Rythm Chose Cashu Over Other Ecash Implementations

Rythm uses Cashu specifically among the available ecash protocols. The choice was deliberate and reflects specific properties of the email payment use case. This post is the technical explanation of why Cashu fits and what the alternatives offer.

The intended audience is technically minded readers from the Bitcoin and Lightning communities, software engineers evaluating the architecture, or anyone interested in the design choices. We use technical terminology where precision matters.

The Ecash Landscape in 2026

Ecash is a category of digital cash protocols. The original concept dates to David Chaum’s 1982 paper on blinded signatures. Modern implementations vary in trust models, technical foundations, and operational maturity.

The main families:

Cashu. Modern open-source ecash protocol with Lightning settlement. Active developer ecosystem, multiple compatible implementations (Nutshell, cdk, others), specification at the cashubtc/nuts repository. Used by multiple wallet implementations and a growing number of mints.

Fedimint. Federation-based ecash where the mint is operated by multiple guardians (typically 3-of-5 or 5-of-7 threshold) using multi-signature schemes. Open source, with active deployment in the Bitcoin community. Stronger trust model than single-mint ecash.

Historical Chaumian ecash. The 1980s and 1990s academic and commercial implementations (DigiCash, etc.). Mostly historical; not actively deployed.

Research and experimental protocols. Various academic and research projects exploring novel ecash designs. Limited deployment.

For practical email use cases in 2026, Cashu and Fedimint are the realistic choices. Other protocols are either historical or not yet production-ready.

Why Cashu Fits Email Use Cases

Five properties make Cashu particularly well-suited for the email cover charge use case.

Active developer ecosystem. Cashu has multiple compatible mint implementations (Nutshell, cdk), multiple compatible wallet implementations (Cashu.me, Boltz, Minibits, Macadamia, Zeus, others), and a substantial developer community. Specification updates happen through the NUTs (Notation, Usage, Terminology) process. The ecosystem is mature enough to build production products on.

Lightning settlement. Cashu’s mint and melt operations both use Lightning for the underlying value transfer. This integrates with existing Lightning infrastructure that has been validated through years of production use. We covered Lightning specifically at how Lightning Network solves the micropayment problem.

Bearer-instrument design. Cashu tokens are bearer instruments that fit naturally inside email bodies. The token is just a string. We covered this design choice at why bearer tokens are the right primitive for email payments.

Blinded-signature privacy. Cashu uses BDHKE-based blinded signatures so the mint cannot link issuance to redemption. The privacy property is meaningfully stronger than Lightning alone. For email payments where sender-recipient privacy matters, this is real value.

Multi-mint architecture. Cashu wallets and integrators can use multiple mints simultaneously, diversifying mint trust. Rythm uses multi-mint support so users are not dependent on any single mint’s continued operation. This addresses the structural concern that ecash mints are trusted entities.

The five properties together produce a protocol that fits the email use case more directly than alternatives.

What Fedimint Offers

Fedimint’s main differentiator is the federation trust model.

The federation. Multiple guardians (typically 3-of-5 or 5-of-7) jointly operate the mint. Issuance and redemption require threshold signatures from the guardians.

Trust diversification. No single guardian can rug-pull. The federation as a whole would have to be compromised or coordinate maliciously, which is structurally harder than a single operator.

Coordination overhead. The federation has to coordinate to operate. Outages of individual guardians are tolerated up to the threshold; outages above the threshold halt operation.

Use case fit. Fedimint excels for community-scale ecash where a known group of guardians is trusted collectively. Bitcoin community organizations, family-and-friends groups, and similar contexts fit well.

Email use case fit. For a global email payment system, Fedimint is more infrastructure than the use case requires. The federation needs guardians; cross-organization deployment requires coordinating guardians across many organizations. Cashu’s single-mint model with multi-mint diversification is operationally simpler.

For Rythm specifically, Cashu’s simpler model with multi-mint diversification provides adequate trust diversification without the coordination overhead.

What Historical Ecash Got Right

The 1980s-1990s ecash protocols (DigiCash, Mondex, others) demonstrated the underlying feasibility of digital cash. They failed for reasons specific to their era:

Centralized issuers. Single corporate issuers that could change practices, raise fees, or shut down. The trust model did not scale.

Pre-Bitcoin settlement. Without Lightning or similar infrastructure, settlement required traditional banking rails with their inherent friction.

Regulatory uncertainty. The legal status of digital cash was unclear in the 1990s. Most projects shut down due to regulatory pressure or commercial failure.

Low internet adoption. The user base was insufficient to drive critical mass.

The current generation addresses each of these. Cashu’s open-source ecosystem replaces centralized issuers. Lightning replaces traditional rails. Regulatory clarity is improving. Internet adoption is universal.

Why Not Build a New Ecash Protocol

A reasonable question: why use an existing protocol rather than design a new one specifically for the email use case?

The answer:

Network effects matter. An ecash protocol is more useful as more wallets and mints support it. Building a new protocol means starting from zero on the network effect. Using an existing protocol with a developer ecosystem benefits from that ecosystem.

Specification effort is non-trivial. Designing a sound ecash protocol with cryptographic security guarantees takes years of expert effort. Reusing the work the Cashu specification has done is more efficient than redoing it.

Interoperability matters. A protocol that interoperates with existing wallets and mints is more useful than one that does not. Cashu has interoperability; a new protocol would have to build it.

Scope creep. Building a new protocol expands Rythm’s scope from “email payment automation” to “ecash protocol design.” The expanded scope requires expertise and resources better spent on the email-specific use case.

The right answer was to use Cashu and contribute to its ecosystem rather than fragment it.

Where Cashu Falls Short

Honest assessment of Cashu’s limits:

Single-mint trust. Each individual mint is a trusted entity. Multi-mint diversification mitigates this but does not eliminate it. A user’s tokens at a specific mint are subject to that mint’s continued operation.

Liquidity dependent on mint. Mints have liquidity limits. Very large transactions are not the protocol’s strong point.

Bearer-instrument trade-offs. Lost tokens are unrecoverable. Theft is final. Both are mitigated by keeping per-payment amounts small.

Operational complexity for self-hosted mints. Running a Cashu mint requires technical operation. Most users delegate to public mints.

These limits are acceptable for the email cover charge use case but might be limiting for other use cases.

A Specific Honest Note

Rythm chose Cashu deliberately for the specific email payment use case. The choice reflects Cashu’s properties (active ecosystem, Lightning settlement, bearer instruments, blinded signatures, multi-mint) and the use case requirements (small payments, low coordination overhead, email-medium fit).

Other ecash protocols have specific advantages for their use cases. Fedimint is excellent for community-scale ecash. Historical protocols are interesting context. Future protocols may emerge with different properties.

For Rythm specifically, Cashu is the right choice in 2026. The choice may be revisited as the ecosystem evolves.

For the related guides, see the cashu protocol explained for email use cases, why bearer tokens are the right primitive for email payments, how Lightning Network solves the micropayment problem, non-custodial architecture, why Hashcash failed and Cashu won’t, and is a cover charge just spam tax with extra steps. For the broader frame, see what non-custodial means in 2026 and what is an email paywall. Rythm is $1.65 per month, cancel anytime.