Fedimint

• Name: Fedimint
• URL: https://fedimint.org/
• Category: Bitcoin community custody infrastructure / federated e-cash protocol / privacy-preserving payments middleware
• Tags: bitcoin-ecosystem
• Summary: Fedimint is the protocol anchor in this community-custody lane. The important thing is the guardian set, module mix, gateway dependence, and app surfaces built on top — not generic wallet language. Keep this note on the federation protocol and custody model itself; use fedi for the best-known consumer wrapper and fedi when the sharper question is who packages setup, distribution, and Mini App gravity around that protocol.
• What it does:
  • Lets communities form federations of trusted guardians that jointly custody Bitcoin in threshold multisig and run the Fedimint protocol together
  • Issues privacy-preserving e-cash inside those federations so users can transact privately and instantly within the federation environment
  • Connects federations to Bitcoin and Lightning through built-in wallet and Lightning modules plus a separate gateway role for broader Lightning interoperability
  • Exposes a modular architecture where ecash, wallet, Lightning, and metadata functions are implemented as modules and additional modules can be added at federation setup
  • Provides client libraries, a WebAssembly-capable SDK, CLI tools, and wallet integrations so apps can join federations, manage balances, and send/receive ecash and Lightning payments
  • Publishes an implementation-heavy Rust codebase and technical reference documentation that make the protocol and deployment surface unusually transparent for an early Bitcoin payments stack
• Key claims:
  • The official homepage describes Fedimint as “open-source federated e-cash for Bitcoin, built for privacy and scale” and highlights a three-sided surface for users, guardians, and builders
  • The user introduction says Fedimint is a “community custody protocol” run by trusted community members that provides privacy, scalability, and extensibility without accounts or KYC
  • The guardian docs make the trust model unusually explicit: guardians are expected to be known community members who hold one key each in a multi-signature wallet and operate Fedimint nodes for the people they serve
  • The federation-architecture docs explain that guardians coordinate with AlephBFT consensus, hold Bitcoin in threshold multisig, and rely on ecash, wallet, Lightning, and meta modules as the core protocol building blocks
  • The GitHub README broadens the frame from e-cash mint to a “module based system for building federated applications,” while also stating that Bitcoin, Lightning, and Chaumian ecash ship as the three default modules
  • The SDK docs show that Fedimint is trying to become app infrastructure, not just federation software, by exposing Rust/WebAssembly client components for federation joining, ecash payments, Lightning payments, and wallet-state management
• Whitepaper: No single canonical Fedimint whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official website, guardian/user docs, technical reference documentation, SDK docs, and public GitHub repositories; see ../whitepapers/fedimint-primary-sources-2026-04-28.md.
• Sources:
  • https://fedimint.org/
  • https://fedimint.org/users/intro
  • https://fedimint.org/guardians/intro
  • https://fedimint.org/guardians/how-federations-work
  • https://docs.fedimint.org/
  • https://sdk.fedimint.org/
  • https://github.com/fedimint/fedimint
  • https://github.com/fedimint

Internal linkages

• Best comparison point: cashu.
• Strongest downstream product shell on top of the protocol: fedi.
• Named company boundary for setup, distribution, and featured Mini App workflow around that shell: fedi.

Protocol / company boundary

• Keep projects/fedimint on the federation protocol itself: guardian selection, threshold custody, ecash issuance, module composition, and Lightning-gateway separation.
• Use fedi when the real question is the consumer shell that bundles wallet, chat, communities, and Mini Apps on top of Fedimint services.
• Use fedi when the sharper question is who sells or supports wallet-service setup, curates promoted Mini App distribution, and shapes the easiest mainstream adoption path around Fedimint.
• That split matters because how the custody protocol works, what the leading app exposes, and which company packages the easiest entry path into that app layer are related but different control-surface questions.

Control surface

• The leverage sits in guardian selection, threshold custody policy, module choices, gateway dependence, and the social trust boundary around who runs the federation.

• A separate distribution gravity now sits downstream in fedi and fedi: those notes are the better place to reason about app defaults, setup assistance, Mini App review, and branded onboarding around Fedimint.

• That is why Fedimint matters. It makes community custody explicit instead of hiding it behind a wallet brand, even when wrappers try to make the experience feel more like a consumer app.

• Last reviewed: 2026-08-10 UTC