Fedi

• Name: Fedi
• URL: https://www.fedi.xyz/
• Category: Bitcoin community app / Fedimint wallet-service platform / private chat and mini-app ecosystem
• Tags: bitcoin-ecosystem
• Summary: Fedi is the consumer shell on top of Fedimint. Wallet, chat, Mini Apps, and federation setup all sit in one app, but the sharper cut is still product packaging: how community wallet services, conversations, and add-on tools are bundled into one user path. The named operator boundary around release workflow, Mini App review, setup assistance, and the legal shell now lives in fedi. Useful app layer, not a protocol anchor.
• What it does:
  • Combines a Bitcoin wallet, private chat, and community spaces inside one app
  • Exposes Mini Apps so communities and developers can add tools such as exchanges, virtual cards, AI tools, and other extensions inside the app experience
  • Positions Fedimint-powered wallet services as a core operating model, with pathways for communities or operators to create their own federations / wallet services
  • Offers features aimed at everyday users such as sending and receiving bitcoin, stable-balance functionality, and messaging plus money movement in the same interface
  • Publishes builder-facing documentation and open-source code so developers can contribute to the app and build Mini Apps or related services
  • Connects the consumer app, community layer, and wallet-service creation workflow into one ecosystem rather than treating them as separate products
• Key claims:
  • The homepage describes Fedi as a “privacy-first Bitcoin app” that combines a wallet, chat, and community spaces in one flexible app
  • The user-facing product page says users can send and receive bitcoin, stabilize it against price swings, message privately, and customize the app with Mini Apps
  • The builders page says Fedi is open source and explicitly invites developers to build Mini Apps and private Bitcoin e-cash applications on the Fedimint protocol
  • The wallet-service creation page frames Fedi as infrastructure for “privacy-first Bitcoin wallet service[s]” and says Fedimint-powered wallet services are fast, private, secure, and community-driven
  • The setup guide explains the underlying Fedimint model in practical terms: threshold custody by guardians, private Chaumian ecash, and separate Lightning gateways, showing that Fedi is tightly coupled to community-operated custody architecture rather than generic app-wallet rails
  • The public GitHub repository says it contains “all source code for the Fedi tech stack,” which reinforces that Fedi is shipping a broader platform than a thin mobile client
• Whitepaper: No canonical Fedi whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official website, builder and wallet-service pages, setup guide, and public source repository; see ../whitepapers/fedi-primary-sources-2026-04-28.md.
• Sources:
  • https://www.fedi.xyz/
  • https://www.fedi.xyz/fedi-for-you
  • https://www.fedi.xyz/fedi-for-builders
  • https://www.fedi.xyz/create-a-wallet-service
  • https://fedibtc.github.io/fedi-docs/docs/fedimint/intro/
  • https://github.com/fedixyz/fedi

Internal linkages

• Company / operator boundary for release workflow, Mini App review, setup assistance, and the app’s legal shell: fedi.
• Protocol substrate and custody-model anchor: fedimint.
• Bearer-money contrast when the app shell matters less than the mint: cashu.

Protocol / company boundary

• Keep this note on the product shell: wallet, chat, community spaces, Mini Apps, and the way Fedimint services are presented to end users.
• Use fedi when the useful question is who curates featured Mini Apps, sells and supports federation setup, ships the release cadence, or governs the hosted website / app legal boundary.
• Keep fedimint as the protocol anchor for guardian thresholds, Chaumian ecash, and Lightning-gateway separation.
• That split matters because what does the app expose?, how does the custody protocol work?, and which company shapes the easiest adoption path around both? are related but not identical questions.

Control surface

• At the product layer, leverage sits in federation selection, wallet-service defaults, Mini App placement, chat-plus-payments packaging, and how much user flow stays inside Fedi’s shell instead of a raw Fedimint client.

• For the named operator layer around release workflow, featured-catalog review, setup pricing, support, and privacy / terms policy, read fedi.

• That makes Fedi important as a distribution layer for community custody, not as the underlying custody or e-cash protocol.

• Keep the note reading upward toward Fedimint, with Cashu as the cleaner bearer-money contrast.

• Last reviewed: 2026-08-09 UTC