Skip to content
Back to search

fedimint

Federated E-Cash Mint

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/fedimint/fedimint with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/fedimint/fedimint'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fedimint--fedimint/badge.svg)](/listings/fedimint--fedimint)

HTML

<a href="/listings/fedimint--fedimint"><img src="/api/listings/fedimint--fedimint/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 89 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1 align="center">
  2. <a href="https://fedimint.org">
  3. Fedimint
  4. </a>
  5. </h1>
  6. <p align="center">
  7. <img src="docs/banner.png">
  8. </p>
  9. <p align="center">
  10. <a href="https://github.com/fedimint/fedimint/actions/workflows/ci-nix.yml">
  11. <img src="https://github.com/fedimint/fedimint/actions/workflows/ci-nix.yml/badge.svg" alt="GitHub Actions CI Build Status">
  12. </a>
  13. <a href="https://chat.fedimint.org"><img alt="Developer Discord Chat" src="https://img.shields.io/discord/990354215060795454?label=dev%20chat"></a>
  14. <a href="https://github.com/fedimint/fedimint/discussions">
  15. <img src="https://img.shields.io/badge/community-discussion-blue" alt="GitHub Discussion">
  16. </a>
  17. <a href="https://docs.fedimint.org">
  18. <img src="https://img.shields.io/static/v1?label=Docs&message=master&color=007ec6&logo=GitBook&logoColor=ffffff" alt="docs built from master">
  19. </a>
  20. <a href="https://app.radicle.xyz/nodes/radicle.fedimint.org/rad:z2eeB9LF8fDNJQaEcvAWxQmU7h2PG">
  21. <img src="https://img.shields.io/badge/Radicle-explore-blue" alt="View on Radicle">
  22. </a>
  23. </p>
  24. [Fedimint](https://fedimint.org) is a module based system for building federated applications. It is designed to be a
  25. trust-minimized, censorship-resistant, and private alternative to centralized applications.
  26. > **Fedimint is released under
  27. an [MIT License](https://github.com/fedimint/fedimint/blob/master/LICENSE). This means that the software here is
  28. provided "as is", without warranty of any kind, express or implied. You can find our
  29. latest release [here](https://github.com/fedimint/fedimint/releases/latest).**
  30. Fedimint ships with 3 default
  31. modules - [Bitcoin](https://github.com/bitcoin/bitcoin), [Lightning](https://github.com/lightning/bolts),
  32. and [Chaumian Ecash](https://en.wikipedia.org/wiki/Ecash) - for out-of-the-box best practices for private and
  33. trust-minimized payments. [You can write custom modules](https://github.com/fedimint/fedimint-custom-modules-example)
  34. that define further consensus items and transaction types leveraging the payments modules to build your own federated
  35. applications.
  36. The Fedimint Developer Discord is the best place to get help and ask
  37. questions. [Join the Discord](https://discord.gg/cEVEmqCgWG) and say hi! We are extremely active and work to onboard
  38. developers of all skill levels to Fedimint and associated open-source Bitcoin projects. Fedimint touches many different
  39. areas of Bitcoin development, so there is something for everyone. See below for more information on how to get involved.
  40. ## Using Fedimint
  41. To use Fedimint you only need a client application, that will allow interacting with
  42. Fedimint federations.
  43. You can pick one of Fedimint-supporting applications:
  44. * [Fedi](https://www.fedi.xyz/) - for MacOS, Android and Web browsers
  45. * [Ecash App](https://github.com/fedimint/ecash-app) - Android and desktop wallet
  46. * [Conduit Wallet](https://joschisan.github.io/conduit) - iOS and Android wallet
  47. * [Harbor Wallet](https://harbor.cash/) - desktop wallet
  48. * [Vipr Wallet](https://github.com/ngutech21/vipr-wallet) - Web (PWA) wallet
  49. * `fedimint-cli` - built-in CLI wallet
  50. ## Running your own Fedimint federation
  51. If you are interested in setting up a Fedimint federation, refer to [Running your own Fedimint federation](./docs/deploying.md).
  52. ## Developing Fedimint
  53. We are actively looking for developers to help build Fedimint and associated open-source Bitcoin projects. Fedimint
  54. touches many different areas of Bitcoin development, so there is something for everyone. The best places to get started
  55. are:
  56. - [Fedimint Hacking Guide](./HACKING.md#) for information about working on the code.
  57. - [Fedimint Contributing Guidelines](CONTRIBUTING.md#) for information for contributors.
  58. - [Fedimint Developer Discord Server](https://discord.gg/cEVEmqCgWG): the best place to get help and ask questions.
  59. - [Fedimint Technical Reference Documentation](https://docs.fedimint.org)
  60. - [Fedimint Cryptographic Schemes](https://docs.fedimint.org/crypto/): self-contained write-ups of the pairing-based
  61. cryptography behind Chaumian e-cash ([threshold blind signatures](https://docs.fedimint.org/crypto/tbs.html)),
  62. Lightning v2 preimage encryption ([threshold point encryption](https://docs.fedimint.org/crypto/tpe.html)), and the
  63. dealer-free [distributed key generation](https://docs.fedimint.org/crypto/dkg.html) that sets up a federation's keys.
  64. - [Fedimint Contributor Calendar](https://calendar.google.com/calendar/u/0/embed?src=fedimintcalendar@gmail.com): This
  65. calendar contains all the developer calls and events.
  66. - [Fedimint Developer Calls](https://meet.jit.si/fedimintdevcall): We have developer calls every Monday at 4PM UTC to
  67. review PRs and discuss current development priorities. As a new developer, this is a great place to find good first
  68. issues and mentorship from the core team on how to get started contributing to Fedimint.
  69. - [PR Review Club](https://meet.jit.si/fedimintdevcall): We have PR review calls every Tuesday at 4PM UTC.
  70. - [Weekly Deep Dive](https://meet.jit.si/fedimintdevcall): We have a deep dive every Thursday at 4PM UTC to discuss
  71. technical topics relating to Fedimint in depth: cryptography, Rust programming, consensus, networking, etc. This is a
  72. great place to learn about the internals of Fedimint and Bitcoin. We normally plan these calls based off requests from
  73. contributors on aspects of Fedimint they want to learn more about, so please reach out if you have a topic you want to
  74. learn more about.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.