Fedimint primary-source snapshot
Fetched: 2026-04-28 UTC
1) Official homepage
Source: https://fedimint.org/
Selected excerpts from the official site:
Community Custody, Private by Design
Open-source federated e-cash for Bitcoin, built for privacy and scale.
Get a wallet, join a federation, and start transacting with private, community-backed Bitcoin.
Become a guardian for your community. Set up and operate a Fedimint federation on your own hardware.
Build your own wallet or integrate eCash payments into your app with the Fedimint SDK.
Additional signals from the source:
- The homepage immediately shows that Fedimint has separate user, guardian, and builder surfaces
- “Community custody” plus “federated e-cash” is the core categorization clue
2) User introduction
Source: https://fedimint.org/users/intro
Selected excerpts from the official docs:
Fedimint is a community custody protocol, run by trusted community members, providing privacy, scalability and extensibility.
To use Fedimint, all you need is a compatible wallet app and an invite to a federation.
No accounts, no KYC — just people you trust.
Additional signals from the source:
- This page is important because it makes the social trust model explicit rather than hiding it behind protocol language
- Fedimint is not claiming trustlessness in the absolute sense; instead it is framing itself as community-trust-minimized infrastructure
3) Guardian introduction
Source: https://fedimint.org/guardians/intro
Selected excerpts from the official docs:
Fedimint guardians are the backbone of every federation.
You hold one key in a multi-signature Bitcoin wallet shared with your fellow guardians.
You operate a Fedimint node next to your Bitcoin node.
A federation needs a minimum of 4 guardians for a robust setup (tolerating 1 Byzantine fault).
The current maximum number of guardians is 20 due to limits in the Bitcoin protocol (pre-taproot).
Additional signals from the source:
- The guardian docs make the custody and operational model unusually concrete
- Minimum guardian counts and fault-tolerance notes are helpful primary-source evidence for how the system is meant to be deployed in practice
4) Federation architecture explainer
Source: https://fedimint.org/guardians/how-federations-work
Selected excerpts from the official docs:
Federation guardians coordinate using AlephBFT, a distributed consensus protocol that ensures the integrity of the federations even if a minority of guardians are malicious or offline.
Bitcoin deposited into a federation is held in a threshold multi-signature wallet.
Fedimint is built in a modular manner, the main modules are:
Ecash module
Wallet module
Lightning module
Any user can run a gateway — it doesn’t have to be a guardian.
Multiple gateways can operate within a single federation, providing redundancy and competition.
Additional signals from the source:
- This is the clearest high-level architecture page for the current protocol surface
- The gateway explanation is especially high-signal because it shows how Fedimint reaches the broader Lightning Network without making every guardian run that role
5) Technical reference documentation
Source: https://docs.fedimint.org/
Selected excerpts from the official docs:
This documentation is automatically generated from the Fedimint source code, and it’s meant for developers, builders and people who want to understand the Fedimint project on an implementation level.
Fedimint is implemented in Rust and consists of multiple Rust crates.
Server side: fedimintd daemon
Client side: fedimint-client library
Fedimint architecture is extensible using a modular design.
core functions of Fedimint are implemented as modules:
ecash
on-chain deposits and withdrawals
lightning integration
Additional signals from the source:
- The implementation-heavy technical docs are an unusually strong primary source for understanding the real software boundary
- The autogenerated crate inventory shows Fedimint as an active protocol/software stack rather than a thin wrapper around an existing wallet
6) SDK site
Source: https://sdk.fedimint.org/
Selected excerpts from the official docs:
Building Ecash into Apps
Rust-powered Client
Includes support for joining federations, sending/receiving ecash, and managing balances.
Ships with zero-setup Lightning Network payments.
Handles the complex state management and storage challenges for browser & mobile wallets.
Framework Agnostic
Additional signals from the source:
- The SDK surface makes it clear that Fedimint is trying to become app infrastructure, not just federation software
- WebAssembly and wallet-state tooling are notable because they widen the addressable developer surface significantly
7) Core GitHub repository README
Source: https://github.com/fedimint/fedimint
Selected excerpts from the official repository:
Fedimint is a module based system for building federated applications.
It is designed to be a trust-minimized, censorship-resistant, and private alternative to centralized applications.
Fedimint ships with 3 default modules - Bitcoin, Lightning, and Chaumian Ecash - for out-of-the-box best practices for private and trust-minimized payments.
You can write custom modules that define further consensus items and transaction types leveraging the payments modules to build your own federated applications.
Additional signals from the source:
- The README broadens the lens from “federated e-cash mint” to a modular app framework
- The custom-modules language is an important clue that Fedimint should not be cataloged only as a wallet or only as a mint
8) GitHub organization overview
Source: https://github.com/fedimint
Selected excerpts/signals from the official org:
Fedimint is a framework for federated applications. The current focus is on building an e-cash federation that makes Bitcoin easier to hold and spend.
Federated E-Cash Mint
Tools for developing Fedimint clients
Open Source Flutter Fedimint App
Additional signals from the source:
- The org inventory helps show that Fedimint has a growing wallet/app and client-tooling ecosystem in addition to the core protocol repo
- This strengthens the case for treating Fedimint as broader infrastructure rather than only one reference app or one node binary
Notes
- Fedimint appears best cataloged as Bitcoin community custody infrastructure / federated e-cash protocol / privacy-preserving payments middleware.
- No single canonical whitepaper or litepaper surfaced in this pass.
- The strongest categorization clue is the combination of community-trust custody, threshold multisig, private e-cash, Lightning gatewaying, and modular builder surfaces.