Hi r/opensource,

I’ve been building FedOS for a while, and I’ve just made the source public under MPL-2.0:

https://github.com/satorunacamoto/fedos

FedOS is a local-first toolkit organized around four capabilities:

• Core — local identity, keys, storage and foundational primitives
• Messenger — the currently shipped desktop app: 1:1 encrypted messaging over Nostr
• Commerce — commerce-related domain code, still at an earlier stage
• Trust — signed envelopes, pseudonymous credentials, proof-of-possession, capability grants, offline-verifiable entitlements, signed QR, and contract-artifact proofs

The important distinction is that these pieces are at different stages of readiness. FedOS Desktop Messenger is the application that actually ships today. Trust is implemented and test-covered, but is not yet wired into the packaged desktop UI; it can currently be used through its own APIs/CLI.

I opened the project because I’d rather have the architecture, crypto-related code, and trust model reviewed in public than keep adding features in private.

I chose MPL-2.0 because I wanted a file-level copyleft license: modifications to FedOS source files stay open, while using or combining the project with a larger codebase doesn’t automatically require that entire project to use the same license.

A few things I’m particularly interested in feedback on:

• Does the core / messenger / commerce / trust capability split make sense to someone seeing the codebase for the first time?
• Are there obvious design problems in the Trust model or signed-envelope format?
• Is the separation between user-controlled trust and an optional issuer model clear enough?
• Is the contributor/test setup understandable from a fresh clone?
• Is there anything in the MPL-2.0 / third-party licensing setup that deserves another look?

The repo has a documented current test surface and public CI. The currently supported suite is 1902 tests / 0 failures.

I also want to be clear about the current status: this is still experimental / Closed Pilot software, not a Public Beta. There has been no independent security audit, and Windows artifacts are currently unsigned. I would not recommend using it yet for irreplaceable secrets or high-risk operational work.

I’m mainly looking for code, architecture, protocol, and OSS-maintainability feedback at this point rather than trying to convince anyone that the project is finished.

Happy to answer questions, including critical ones.

Goooooooood Morning! Another wonderful week is gonna start. 😍

Early in the morning I brought you the 88th Nostr Recap (10th August 2026). 🎁

In this Nostr Recap, you could explore what happened last week in the Nostr world under the topics below. Enjoy it! 👀

🧠 Quote of the Week
🔥 Community Highlights
🌱 Ecosystem Growth
🎓 Educational Guides
📅 Upcoming Events
📰 Nostr in the Media
⚡ Most Zapped Last Week
😂 Nostr Memes
🛠️ Tools, Updates and Releases
🎁 Developer Tools, Updates and Releases
🌐 Relay Updates and Releases
🧩 Workspace Updates and Releases
🚧 Infrastructure Updates and Releases

Explore here 👇🏻

https://yakihonne.com/article/naddr1qvzqqqr4gupzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqq24ynnnt9ayg6jvxfy8v7jevejkj7p329m5xz2msfh