What is a Cashu mint?

A Cashu mint is a service that issues and redeems Cashu tokens. A user deposits Lightning sats at the mint; the mint issues tokens of equivalent value. The tokens can later be redeemed at the same mint for a Lightning payment. The mint operates a Lightning node and runs the cryptographic protocol for token issuance and redemption.

How does a Cashu mint make money?

Mints typically charge a small fee on token issuance, redemption, or both. Fees are usually expressed in basis points or as a fixed amount per operation. The fees cover the operational costs (Lightning channel rebalancing, infrastructure, key management) and provide a small margin. Some mints operate at break-even or as public goods.

What are the operational costs of running a mint?

Lightning infrastructure (node hosting, channel liquidity, rebalancing), software development and maintenance, key management for the mint's signing key, monitoring and uptime, and customer support. The biggest variable cost is Lightning liquidity (channels need inbound and outbound capacity to handle issuance and redemption flows).

Why are mints decentralized?

Because the Cashu protocol allows anyone to run a mint. Users choose which mints to trust based on the operator's reputation, fees, and policies. There is no central authority. Multiple mints can operate independently and tokens from one mint cannot be redeemed at another (each mint issues its own tokens).

How does Rythm interact with mints?

Rythm is mint-agnostic. Cashu tokens carry their issuing mint's URL. When a token arrives in an email, Rythm identifies the mint from the token, verifies the token, and melts it through that specific mint. Users never have to choose mints; senders pick where they bought tokens, and Rythm handles the routing.

The Economics of a Cashu Mint

Cashu mints bridge Lightning sats and bearer tokens. Here is how mints make money, where their costs are, and why decentralization works.

Cashu mints are the operational layer of the Cashu protocol. They are the services that issue tokens, hold the underlying Lightning sats, and redeem tokens when presented. Understanding mint economics matters for anyone using Cashu in production because mint operators, mint reliability, and mint fees affect the user experience. This post is about how mints actually work as businesses.

The earlier piece in this series covered the protocol mechanics. See the cashu protocol explained for email use cases for the cryptographic background.

What a Mint Actually Does

A Cashu mint is a service with three primary operations.

Mint operation. A user (or wallet) sends Lightning sats to the mint. The mint receives the payment, generates Cashu tokens of equivalent value, and returns them to the user. The mint now holds the underlying Lightning balance; the user holds the tokens.

Melt operation. A user (or wallet) presents tokens to the mint along with a Lightning invoice. The mint verifies the tokens, confirms they have not been previously redeemed, and pays the invoice from the underlying Lightning balance. The tokens are consumed; the destination wallet receives sats.

Swap operation. A user (or wallet) presents tokens and asks for new tokens of equivalent total value. Useful for breaking large tokens into smaller ones or for receiving change from a partial spend. Internal to the mint; does not involve Lightning.

Behind the scenes, the mint runs a Lightning node, manages channel liquidity, signs token issuances, and maintains a database of redeemed tokens (to prevent double-spend).

Why Mints Charge Fees

The realistic cost structure.

Lightning liquidity. Mints need both outbound and inbound Lightning channel capacity. Outbound is needed for melt operations (paying invoices when users redeem). Inbound is needed for mint operations (receiving sats when users deposit). Maintaining channel balance through rebalancing operations has direct cost (rebalancing fees, occasional liquidity purchases from LSPs).

Channel opening costs. When a channel needs to be opened or closed, on-chain Bitcoin fees apply. These are real costs that depend on Bitcoin fee market conditions.

Infrastructure. Server hosting, monitoring, backups, key management hardware. Modest at small scale; meaningful at large scale.

Software maintenance. The mint software needs ongoing development as the Cashu protocol evolves. Some mints run open-source implementations; some maintain custom forks.

Key management. The mint’s signing key is the basis of all issued tokens. Compromise of the key would allow forgery of tokens. Hardware key management adds cost.

Customer support. Users have questions, redemption errors, edge cases. Some level of human attention is required.

To cover these costs and stay viable, mints charge fees. The fee structure varies.

Common Fee Structures

What mints actually charge.

Issuance fees. A small fee on the mint operation. Common: 0-10 basis points (0-0.1%) plus the underlying Lightning routing cost.

Redemption fees. A small fee on the melt operation. Common: 0-10 basis points plus the underlying Lightning routing cost.

Lightning routing fees. When the mint pays a Lightning invoice during a melt, the routing through the Lightning network has a small cost (typically 0.01-0.1% of the payment amount). This is passed through to the user.

Spread. Some mints implement a small spread between the value of issued tokens and the equivalent Lightning sats. Functions like a fee but is hidden in the issuance amount.

Free tier. Some mints (especially public-good mints or test mints) charge no fees and operate at break-even or with subsidization.

For Rythm’s use case, the fees are absorbed in the safety buffer math. We covered the buffer formula at the cashu protocol explained for email use cases and why bearer tokens are the right primitive for email payments.

The Liquidity Constraint

The biggest variable cost for most mints is Lightning liquidity management.

Why liquidity matters. When a user requests a melt, the mint pays a Lightning invoice. The mint needs outbound channel capacity equal to the melt amount. If the mint is heavily used for melts but lightly used for mints, outbound liquidity drains and the mint can no longer process melts until liquidity is replenished.

How mints manage liquidity. Through a combination of rebalancing operations (paying fees to other Lightning nodes to move liquidity around), purchasing inbound liquidity from Lightning Service Providers, and active routing to customers who need outbound (creating natural inbound).

The cost of liquidity management. Direct cost (rebalancing fees, LSP purchases) plus operational complexity (monitoring, alerting, manual intervention). For a small mint, this is a few hours a month. For a large mint, it is a continuous operational concern.

Why this is the structural margin. Mints that manage liquidity efficiently can charge low fees and stay solvent. Mints that manage poorly either go offline or charge high fees to compensate. The skill of liquidity management is the moat.

Why Mints Are Decentralized

The Cashu protocol is permissionless: anyone can run a mint. This produces a structural decentralization that has economic consequences.

No single mint controls the protocol. Tokens issued by one mint can only be redeemed at that same mint. There is no central clearing or interoperability layer that any one mint controls.

Users choose which mints to trust. A user accepting tokens from a mint is implicitly trusting that mint to honor the redemption later. Reputable mints earn trust; problematic ones lose users.

Competition keeps fees low. Multiple mints competing on fee structures and reliability. Users gravitate toward better mints; better mints earn more flow; more flow makes the operations more efficient.

Failure of one mint does not cascade. If a mint goes offline or is compromised, only tokens issued by that specific mint are affected. The broader Cashu ecosystem continues.

No regulatory choke point. Distributed across many independent operators. Different operators in different jurisdictions. The protocol does not depend on any single point of regulatory pressure.

The structural property is that the protocol is resilient because no single mint matters too much. The economics work because competition is permissionless and users have choice.

What Could Go Wrong

Honest about the failure modes.

A mint’s signing key is compromised. The attacker can forge tokens. Mitigated by key management practices and by the limited blast radius of any single mint.

A mint goes insolvent. Cannot honor redemptions. Mitigated by users diversifying across multiple mints and by mint reputations being public.

A mint becomes unreliable. Slow redemptions, occasional failures, customer support delays. Users migrate to better-operated mints.

Lightning network outages. The mint depends on Lightning being available. Mitigated by Lightning’s own decentralization.

Regulatory action against a specific mint. Targets one operator without affecting the protocol. Other mints continue.

The blast radius of any single failure is limited to the users of that specific mint. The protocol’s resilience is structural.

How Rythm Handles Mint Variance

Rythm’s design treats mints as interchangeable infrastructure.

Mint-agnostic at the protocol layer. A Cashu token carries the URL of its issuing mint. Rythm reads the URL, queries the mint to verify the token, and melts through that specific mint. Different tokens in different emails go to different mints; Rythm routes each one appropriately.

No mint preference at the user layer. The user does not choose mints. Senders attach tokens from whichever mint they used; Rythm handles the routing.

Per-mint circuit breakers. If a specific mint becomes slow or unreliable, Rythm’s circuit breaker logic handles it gracefully. Failures of one mint do not affect processing of tokens from other mints.

Multi-mint future. As the Cashu ecosystem matures, more mints will operate. Rythm’s design extends to handle the multi-mint case without architectural change.

We covered this at why Rythm chose Cashu over other ecash implementations.

A Specific Honest Note

Cashu mints are the operational layer that makes the protocol work. They are real services with real costs and real fees. Understanding the economics helps explain why mint diversity is a feature, why fees are structurally low but nonzero, and why the protocol’s decentralization produces resilience.

For Rythm users, the mint layer is invisible. Senders pick where they bought tokens; Rythm handles the routing transparently. The structural property that matters is that no single mint is a choke point, no single mint failure cascades to the broader system, and the user’s experience does not depend on mint operator decisions.