Fedimint

Definition: Fedimint is an open-source, modular protocol for federated Bitcoin custody and payments. A federation of independent guardians holds Bitcoin in a threshold-controlled wallet and operates modules that can issue blind-signed eCash notes, manage on-chain deposits and withdrawals, and connect users to Lightning. Members can transfer eCash within a federation without each transfer being recorded as a Bitcoin transaction, but they rely on the federation’s quorum and software to honor deposits and redemptions.12

TypeOpen-source protocol for federated Bitcoin custody and applications
OperatorsGuardians run nodes that coordinate a federation’s configuration and transactions2
Default functionsBitcoin wallet, Chaumian eCash mint, and Lightning integration modules4
Privacy mechanismThreshold blind signatures are used for eCash notes; privacy depends on the protocol, wallet, federation, and payment path3
DirectoryBitcoin Directory

How a Fedimint works

A Fedimint federation is a group of guardians that run compatible nodes and agree on the federation’s setup. They coordinate transaction processing through a Byzantine fault-tolerant consensus protocol. The federation uses a threshold key arrangement for its Bitcoin wallet: a configured quorum must cooperate to authorize a withdrawal. The exact number of guardians and required threshold are set for each federation, so there is no single universal guardian count or signing rule.2

Fedimint is modular. Its documented modules include a wallet module for Bitcoin deposits and withdrawals, a mint module for eCash, and a Lightning module for payments through a gateway. All guardians in a federation need to agree on its installed modules during setup. A federation can add custom modules, but that flexibility also means users should understand which code and rules their chosen federation has enabled.4

Bitcoin deposits, eCash, and redemption

A member can deposit Bitcoin to the federation and receive eCash notes in return. The mint uses blind signatures so a guardian can help issue a valid note without learning which specific note it signed. Later, a holder can present a note for payment or redemption, while the mint checks that the note has not already been spent. This design is intended to reduce the link between issuance and redemption within the federation; it does not make every part of a user’s activity invisible to wallets, network providers, gateways, or other services involved in a payment.13

eCash transfers between members are accounted for by the federation rather than written as separate Bitcoin transactions. Users can later withdraw Bitcoin on-chain or use a supported Lightning route, subject to the federation’s modules, liquidity, fees, and operating conditions. This can make small or frequent payments more practical, but the notes are claims against a particular federation—not Bitcoin UTXOs that the holder can independently spend without its guardians.

Lightning integration

A Lightning gateway connects a federation to the broader Lightning Network. Fedimint’s documentation describes payment contracts that allow a gateway to pay or receive Lightning invoices in exchange for eCash, using a payment preimage to settle the contract. A gateway can be operated by a federation member or another participant, and a federation may have more than one gateway. Users still depend on available routes, liquidity, software compatibility, and the federation’s operation; a gateway does not turn a Fedimint note into a self-custodied Lightning channel balance.24

Trust model and limitations

Fedimint distributes custody among guardians, but it is still a federated custody model. A single guardian or a group below the required threshold should not be able to spend federation funds alone. If a threshold of guardians colludes, it may be able to move funds contrary to members’ wishes. If too few guardians remain available, consensus or withdrawals may stop until the federation recovers. Recovery can depend on the configured keys, guardian data, and backups, so users should assess who runs the federation and how it handles recovery before depositing Bitcoin.23

Blind signatures address one privacy link; they do not remove all metadata or operational risks. A wallet, device, IP network, Lightning gateway, or merchant may learn details through the way a user connects or pays. Federation software and modules also require review and maintenance. Treat eCash held in a federation as a custodial balance backed by that federation’s rules and assets, rather than as a risk-free substitute for holding Bitcoin keys yourself.3

History

  • October 2021: Fedimint’s project blog recorded Blockstream support for MiniMint, an early development effort associated with federated Bitcoin eCash.5
  • March 12, 2022: A Fedimint project post described the approach as an evolution of Bitcoin custody and community banking.6
  • June 30, 2025: The project’s first-half retrospective reported the v0.6 and v0.7 releases and continued work on usability, Lightning integration, and running federations at home. This is a dated project update, not a claim about the latest version.7

Page updated: November 10, 2026.

Related Terms

Related Articles

See Also

Sources

  1. Fedimint. “How It Works.” Accessed November 10, 2026. User overview.
  2. Fedimint. “How Federations Work.” Accessed November 10, 2026. Guardian and federation architecture.
  3. Fedimint. “Privacy and Trust.” Accessed November 10, 2026. Privacy and custody trade-offs.
  4. Fedimint. “Fedimint Technical Reference Documentation.” Accessed November 10, 2026. Technical reference.
  5. Fedimint. “Blockstream Announces Support for Minimint!” October 27, 2021. Project history.
  6. Fedimint. “Fedimint – The Evolution of Bitcoin Custody.” March 12, 2022. Project history.
  7. Fedimint. “Fedimint’s Ecosystem: A Look Back at 2025’s First Half.” June 30, 2025. Project history and development updates.