Why was a four-cent email cost impossible before?

Because traditional payment infrastructure had transaction fees that exceeded the four-cent payment amount. A credit card transaction has a 15-30 cent minimum fee from processors. PayPal had similar minimums. Below those thresholds, the payment cost more than the payment was worth. The four-cent use case was structurally impossible.

What changed in 2024?

The Lightning Network reached production-grade reliability with sub-cent fees per payment. Cashu added bearer-token semantics on top of Lightning. The combination produces payment infrastructure where four-cent transactions cost about 0.01-0.04 cents in routing fees. Below the level that breaks any practical use case.

What about earlier micropayment attempts?

Hashcash (2002) used proof-of-work but tokens were not transferable as value. Microsoft Passport tried micropayments and failed. Beenz, Flooz, and various other systems all failed because the underlying infrastructure could not support sub-dollar payments. The entire wave of 1990s and early 2000s micropayment experiments failed for the same structural reasons.

Are there other use cases now possible?

Yes. Per-article content access, per-API-call payments, streaming sats for podcasts, paid responses to queries, and many other granular paid interactions. Email cover charges (Rythm) is one application; the same infrastructure supports many others.

What does Rythm do specifically?

Rythm uses the new infrastructure to make a four-cent cover charge for unknown email senders economically viable. The cover charge filters mass-volume cold outreach. Senders pay; the payment lands at the recipient's wallet. Below 2024, this was technically infeasible; in 2026, it works.

Why a 4-Cent Email Cost Was Impossible Before 2024

Charging four cents per email was technically infeasible until 2024. Here is what changed and why the use case finally works.

Charging four cents per email was technically infeasible until 2024. The structural reason is that traditional payment infrastructure has minimum transaction fees that exceed the payment amount. Below 2024, the use case was attempted multiple times and always failed for the same reasons. In 2024, the Lightning Network plus Cashu produced infrastructure that finally makes the use case work. This post is about what changed.

Why Traditional Payment Rails Cannot Process Four-Cent Payments

The structural barrier.

Credit card processors have minimum fees. Stripe, Square, PayPal Direct, and similar processors charge 15-30 cents per transaction as a baseline. For payments under that threshold, the fee exceeds the payment amount.

ACH transfers have similar fees. Domestic bank transfers via ACH typically cost 25-40 cents per transaction. Wire transfers are higher.

International payments are worse. Cross-border fees are 1-5%, with higher minimums.

Mobile money fees vary. Apple Pay, Google Pay, Venmo, and similar services pass through underlying card processor fees.

Crypto exchange fees were also too high. Coinbase Pro, Binance, and others typically have 0.1-0.5% trading fees plus deposit/withdrawal fees that made small Bitcoin payments uneconomical.

On-chain Bitcoin fees are variable. Sometimes a few cents; sometimes dollars. Not reliable enough for sub-cent use cases.

For a sender wanting to pay four cents to reach a recipient, the underlying infrastructure imposed costs that destroyed the use case. The economics were structural; no individual processor could solve it without changing the fundamental fee model.

The Failed Attempts

The history of trying.

Hashcash (2002). Adam Back’s proof-of-work system. Senders had to compute a small hash to send mail. Adopted by some anti-spam systems. Failed because PoW was not transferable as value; recipients could not redeem the work into real income.

Microsoft Passport (1999-2002). Identity infrastructure including micropayment capability. Discontinued for micropayment use because the infrastructure was not viable.

Various email cover charge proposals. Multiple commercial and academic proposals over 25 years. All foundered on the payment infrastructure problem.

Per-message access fees. Attempted by various services. Could not be priced low enough to be acceptable to senders without losing money to processor fees.

Pay-per-impression email. Attempted by various early-2000s startups. Failed because the per-impression revenue did not exceed processor fees.

Pay-to-deliver SaaS. Some 2010s attempts to charge senders for delivery. Could not work because the senders could not pay sub-dollar amounts efficiently.

The pattern: every generation tried; every generation failed for the same reasons.

What the Lightning Network Changed

The breakthrough.

Sub-cent routing fees. Lightning routing fees are typically 0.01-0.1% of the payment amount. For a four-cent payment, the fee is 0.0004-0.004 cents. Below the level that affects any practical use case.

Fast settlement. Lightning payments settle in 1-3 seconds. Sender does not have to wait; recipient does not have to wait.

No minimum payment size. Lightning supports payments down to fractions of a cent (millisat-denominated).

Permissionless. No central operator gates access. Anyone with a Lightning wallet can send or receive.

Decentralized. Network of nodes; no single point of failure.

The Lightning Network solved the cost-per-payment and speed problems that defeated traditional rails.

What Cashu Added

The bearer-instrument layer.

Tokens that move with the message. Cashu tokens can be embedded in email bodies, text messages, or other transport. The token does not require the sender and recipient to coordinate per-payment.

Privacy through blinded signatures. The mint cannot link issuance to redemption. Stronger privacy than Lightning alone.

Reusable infrastructure. A user can mint tokens once and use them in many emails. The mint operation does not have to happen per-message.

Mint-agnostic from the recipient’s perspective. Recipients can accept tokens from any reputable mint; senders pick where they bought tokens.

Composable with Lightning. Token redemption produces a Lightning payment. The two layers compose cleanly.

The Cashu layer added what pure Lightning was missing for the email use case: a bearer instrument that travels with the message rather than requiring a separate payment exchange.

Why the Combination Works for Email

The match between the protocol and the use case.

Sender does not need to know recipient’s wallet. The sender mints a token at a public mint; the token can be redeemed by whoever holds it. The recipient does not need to coordinate with the sender about wallet specifics.

Recipient does not need a relationship with the sender’s mint. Rythm reads the mint URL from the token and routes accordingly. The recipient’s user experience is uniform regardless of which mint the sender used.

The payment can be small. Four cents is comfortable for both parties. Senders do not feel the cost; recipients receive small but accumulated income.

The payment is fast. No waiting for confirmation. The melt happens in seconds; sats arrive at the recipient’s wallet.

The payment is private. The mint cannot link the original sender to the eventual recipient. Network observers see Lightning operations but not token contents.

The integration with email is clean. The token sits in the email body; everything else is metadata-level. SMTP does not need to change.

The combination matches the email use case’s requirements specifically. For other use cases (per-article content, per-API call), the same infrastructure works but the integration details differ.

What Was Possible Before vs After

A comparison.

Before 2024. Cover charges for email were a recurring proposal that always failed. The infrastructure could not support the price point. Senders could not pay four cents efficiently. Recipients could not receive small payments without infrastructure overhead exceeding the income.

After 2024. A sender pays four cents to mint a Cashu token. The token travels in the email. The recipient melts the token to their Lightning wallet. The mint pays a few cents per recipient (which the recipient absorbs, leaving them with about 3.95 cents). The infrastructure cost is below 1% of the payment. The use case works.

The shift is not gradual. It is discontinuous. Either the infrastructure supports sub-cent payments at scale or it does not. Lightning + Cashu does; everything before did not.

Other Use Cases the Same Infrastructure Enables

The breadth.

Per-article content access. A reader pays a small amount to read an article. Below the level that requires subscription commitment.

Per-API call. A service charges per API call rather than per monthly tier. Useful for usage-based billing.

Streaming sats for podcasts. Listeners stream tiny amounts per second to podcast hosts. The Podcasting 2.0 use case.

Pay-per-search. A search service charges per query. Privacy-aware alternatives to ad-supported search.

Paid responses. Users pay for high-quality responses to questions on Q&A platforms.

Content tipping. Tip jar mechanics for any creator without infrastructure overhead.

Pay-per-action games. Games that charge per action rather than per session.

The list keeps growing. Each application benefits from the same underlying infrastructure work.

A Specific Honest Note

A four-cent cover charge for email was structurally impossible before 2024 because the underlying payment infrastructure could not support sub-cent transactions efficiently. Multiple generations of attempts failed for the same reason.

In 2024+, Lightning’s sub-cent routing fees plus Cashu’s bearer-instrument property produced infrastructure that finally supports the use case. Rythm is one application; many others are possible.

The shift represents an actual change in what is technically and economically feasible. Not a gradual improvement; a structural threshold that has been crossed.