Cowrie Research

fedi

5 min read

Fedi, Inc.

  • Name: Fedi, Inc.
  • URL: https://www.fedi.xyz/
  • Category: Bitcoin community-wallet company / Fedimint distribution and setup operator / mini-app and federation-packaging company
  • Tags: bitcoin-ecosystem
  • Summary: Fedi clears the bar for a company note because the practical dependency is not just a Fedimint app exists; it is that a named operator ships the consumer app, curates Mini App distribution, sells and assists wallet-service setup, runs the support and regional-growth surface, and defines the legal and data-handling shell around a privacy-branded Bitcoin product. The useful question is not only how does the app work? but which company decides the easiest way communities discover federations, launch them, customize them, and stay inside one packaged wallet/chat ecosystem?
  • What it does:
    • Operates the Fedi app, which combines a Bitcoin wallet, chat, community spaces, and Mini App distribution on top of Fedimint-based wallet services
    • Packages a community and organization go-to-market surface around wallet services powered by Fedimint, rather than only shipping a neutral client for an existing protocol
    • Runs builder-facing distribution and review workflow for Mini Apps, with featured-catalog placement controlled by Fedi’s submission and review process
    • Sells and assists federation / wallet-service launch through setup pathways including G-Bot chat-based setup plans, partner deployment paths, and direct team follow-up
    • Maintains the broader Fedi tech stack, with the public monorepo describing Rust core, custom Fedimint modules, chat / community logic, and the apps shipped to users
    • Provides the website, app, support, and privacy / terms shell that governs user interaction with Fedi-operated surfaces
  • Key claims:
    • The company pages describe Fedi as a customizable community Bitcoin app combining chat, money, and Mini Apps, while also saying 100+ communities are registered to roll out Fedi and 50+ Mini Apps are available; these are vendor claims, but they show Fedi is selling a company-run distribution shell rather than a thin wallet client
    • The builders page says Fedi is open source, invites developers to build Mini Apps and private Bitcoin ecash applications, and tells builders to submit Mini Apps for review to get featured in the catalog; that makes app admission and promoted distribution a named company surface rather than an open protocol default
    • The wallet-service pages say communities can create a Fedimint-powered wallet service through Fedi-guided setup, including G-Bot plans with fees and direct contact with regional Fedi Masters, which is unusually explicit evidence that the company wants to sit inside deployment and onboarding workflow rather than merely point users at protocol docs
    • The privacy notice and terms identify the operator as Fedi, Inc. and say the company processes personal information in connection with the website and app, may restrict access to the website, and governs use of the hosted services; that matters because the legal and data-handling perimeter is company-shaped even when the product markets privacy-first custody
    • The public GitHub monorepo says it contains the full Fedi tech stack, including custom Fedimint modules, Matrix chat, communities, and the React Native / web apps that ship to users, which reinforces that Fedi is operating a vertically packaged product company around Fedimint rather than only curating a brand site
  • Whitepaper: No standalone company whitepaper is the important artifact here. The strongest primary materials for this pass were the official site, builder and wallet-service pages, G-Bot setup page, privacy / terms pages, and the public monorepo README; see ../whitepapers/fedi-company-primary-sources-2026-08-09.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep fedi focused on the product shell: wallet, chat, community spaces, Mini Apps, and the user-facing way Fedimint services are packaged.
  • Keep this note focused on Fedi, Inc. as the named operator that decides release workflow, featured Mini App admission, federation setup assistance, regional rollout support, and the legal / privacy shell around those surfaces.
  • Keep fedimint as the protocol and custody-model anchor: guardian thresholds, Chaumian ecash, and Lightning-gateway separation still belong to the protocol layer rather than to Fedi as a company.
  • That split matters because what can a user do in the app?, how does Fedimint custody work?, and which company controls the easiest onboarding and distribution path around both? are related but not identical questions.

Control surface

  • Practical leverage sits in app release cadence, community onboarding and setup assistance, G-Bot pricing and support workflow, Mini App review and featured-catalog placement, the support / moderation / contact surface, and the data-handling and account-policy shell around Fedi-operated services.

  • The deeper dependency is distribution gravity: if communities adopt Fedimint through Fedi’s branded wallet, setup service, curated app catalog, and regional operator network, then a meaningful part of the ecosystem’s day-2 reality becomes company-shaped even when the underlying protocol stays open.

  • Fedi does not directly control every federation’s guardian set or every Lightning gateway. The sharper claim is that it controls a large share of the easiest consumer and community path into that world.

  • Read Fedi, Inc. as the distribution and operating shell around a Fedimint-based consumer stack, not as the Fedimint protocol itself.

  • Last reviewed: 2026-08-09 UTC

Graph View

Backlinks