Fedimint 🔆

Fedimint. Decentralised #Bitcoin custody for the world.

Read more at

[elsirion 🔅 @EricSirion]

Multiple Fedimint implementations were part of the original vision, now with the help of AI the dream is becoming reality 🥹

Time to call the fedimint repo minimint again? Has my holding out finally paid off? 😝

[Fedimint 🔆 @fedimint]

Another Fedimint implementation just dropped! 🚀

[thesimplekid @thesimplekid]

@EricSirion /goal

https://t.co/O7KEaov7BY

[Fedimint 🔆 @fedimint]

The bug results from an interaction between misunderstood HTLC interception behavior and our LN-ecash swap validation logic that evaded previous scans.

We continue to do our own AI-accelerated security research and appreciate external research findings at [email protected]

[Fedimint 🔆 @fedimint]

We found a bug in our legacy Lightning integration and are contacting public gateway operators.

User funds, federations, and ecash are not affected.

Gateways using LDK Node or our newer LNv2 protocol are also not affected. We still recommend staying up to date.

🧵

[Fedimint 🔆 @fedimint]

If we haven’t reached out, please update to v0.12.1 ASAP, or shut down your Lightning gateway in the meantime if that’s not feasible.

Users of federations without an active Lightning gateway will still be able to make ecash and on-chain transactions.

https://t.co/M9EKKP30sx

[Ayush Bansal @bansalayush247]

ecashmesh⚡️

evidence-aware routing for Ecash across @CashuBTC , @fedimint and eventually @lightning

beyond fees: liquidity, reliability, proof freshness and route risk

which Ecash route should I use, and why?

building for @bitshala boss battle 2026
🔗 https://t.co/Kdu34ILV09

[elsirion 🔅 @EricSirion]

Why multiple implementations make sense for security beyond a certain point:

[Bitcoin Ekasi @BitcoinEkasi]

Using @fedibtc and a self-hosted @fedimint federation to make Bitcoin everyday money!

This is Good Hope federation, running on 7 @start9labs devices, spread out across the Western Cape province of South Africa.

We use it every day. But it's still mind blowing. Every single time.

[elsirion 🔅 @EricSirion]

Calling on fellow cypherpunks to build alternative Fedimint implementations.

The Liquid hack shows once again that single points of failure are what will break our systems and that includes the code we write.

Security is an asymmetric game: an attacker has to find one weakness, while defenders have to find all. AI has permanently changed the attacker-defender balance for the worse. This is a fundamental problem for the entire freedom tech space and only mitigatable by aggressively reducing single points of failure. Federations are meant to do exactly that, but just like Liquid, Fedimint shares the “single implementation” problem.

If we still want to bring privacy and freedom to the world we need to work together more than ever to reduce these single points of failure. For me that means seeking help to bootstrap independent Fedimint implementations. We are still early, but I've started extracting a specification that others could build off and would love to collaborate with any fellow cypherpunks who want to join us in that mission. In particular, I’d love to work with @callebtc and the @CashuBTC team, who have much more experience with a multi-implementation ecash protocol while the Fedimint team brings federation experience to the table.

While AI exposes existing vulnerabilities and wreaks havoc in our ecosystem, it is also an opportunity for talented engineers to be far more productive than ever before. I’ve been talking with @fedibtc and there is funding for a small, crack team to pull this off. If this sounds interesting as a funder, please reach out! The idea is for the teams to be purposefully disconnected from the existing Fedimint implementation and to work autonomously, communicating mainly through the spec process.

If you too believe that privacy and freedom are needed more than ever, please join us!

[Obi Nwosu 🔅 @obi]

Congrats to the team for this huge milestone.

Years of feedback and research to make this major upgrade to the protocol.

Super excited to see the result and incorporate it into the Fedi app for a faster, smoother, and even more scalable offering. 👀✅🚀

[Fedimint 🔆 @fedimint]

Since v0.11.0 over 300 commits from more than 20 developers went into this release. Big thanks to all contributors, sponsors, integrators and testers! 💪

Full release notes: https://t.co/gXwktxMfFr

[Fedimint 🔆 @fedimint]

Fedimint v0.12.0 "Second Nature" is here! 🚀

The highlights:
* v2 modules (lnv2, mintv2, walletv2) now the default for new federations ✨
* Much lower Lightning payment latency ⚡️
* @iroh_n0 1.0 networking 🌐
* Wallet recovery without downtime 🔄

https://t.co/gXwktxMfFr

[Fedimint 🔆 @fedimint]

For app developers: UniFFI bindings bring the client to Kotlin & Swift 📱, new fee APIs show costs before you commit 🤑, and clients stay fully usable while recovering — no more waiting for restore to finish. 🔄

[elsirion 🔅 @EricSirion]

@PavolRusnak @iroh_n0 Without Iroh we couldn't have made Fedimint as easy to run as it is today, so huge props to them!

It's the future that IPv6 should have been 😁

https://t.co/Plg0SmJBJa

[Frank Corva @frankcorva]

We're live with @fedimint founder and @fedibtc co-founder, @EricSirion!

Please drop your questions for Eric in the comments.

[Fedimint 🔆 @fedimint]

Iroh is what enables Fedimint to be as easy to run on a home networks or on an old phone as it is to run in the cloud!

[Pavol Rusnak @PavolRusnak]

This is interesting: https://t.co/v7niBI2j1o

Basically Tailscale but on application level, not network level. Uses QUIC so it is super fast and runs on embedded hardware too!

@iroh_n0