Unfortunately, we have to inform you about security vulnerabilities in the network protocol that Radicle nodes use to communicate amongst each other.
https://radicle.dev/2026/09/23/disclosure-of-vulnerability-in-network-protocol
Remote
Radicle
@radicle@toot.radicle.dev
mastodon 4.6.6The sovereign forge. Local-first, peer-to-peer and secure code collaboration.
1594 Followers
0 Following
15 Posts
Joined April 26, 2026
Website:
Bluesky:
Pronouns:
it/its
Radicle 1.9.1 is out!
Thanks to the folks who reported bugs they witnessed in Radicle 1.9.0!
👾 Release notes https://radicle.dev/2026/05/22/radicle-1.9.1
👾 Get the latest radicle.dev/download 🌱
Summer is setting in, and Radicle 1.9.0 (Hawthorn) has been released ☀️
👾 Check out our update https://radicle.dev/2026/05/19/radicle-1.9.0
👾 Get the latest radicle.dev/download 🌱
If you have not tried out Radicle yet, then check out our new quick start guide 🚀
https://radicle.dev/guides/quick-start
Get Radicle up and running in an afternoon!
Replying to
@jonny@neuromatch.social @happyborg@fosstodon.org @RuchiraSDatta@mathstodon.xyz @alienghic@timeloop.cafe We know that. There's a gateway at https://radicle.network . For the rest the only thing we can ask for is patience, or to join us and help getting there quicker. We're open source and welcome contributions.
Note also that we very much value all other projects that work to reverse concentration on GitHub. We are in loose contact with folks at @Codeberg@social.anoxinon.de for example, and are also cheering for federation efforts in @forgejo@floss.social. We're not zero-sum players...
Replying to
@RuchiraSDatta@mathstodon.xyz @alienghic@timeloop.cafe @jonny@neuromatch.social @happyborg@fosstodon.org Radicle is designed to work without servers. You can connect any two nodes and sync data. People can also connect their nodes on a LAN and sync code without access to any federation instance. There are nodes that are servers with high uptime, yes, but they run the same code as you.
Your user identity is not a row in the database of whoever runs the Forgejo instance, but the signing key on your filesystem.
Some people compare Radicle to BitTorrent.
Replying to
@happyborg@fosstodon.org @RuchiraSDatta@mathstodon.xyz @alienghic@timeloop.cafe @jonny@neuromatch.social For the utility of the token please refer to the Radworks, i.e. https://radworks.org/ and https://community.radworks.org
Radicle itself does not use or depend on any blockchain or cryptocurrency.
To use Radicle you do not need to own any cryptocurrency, have a cryptocurrency wallet or any of that.
Earlier iterations of Radicle, some years ago, were tightly integrating with a blockchain, but this is not the case anymore since at least 2023.
Replying to
@ligasser please see https://radicle.network We are working on a landing page that is not scoped to a particular node and the repositories it seeds, but gives an overview of (many nodes of) the network and repositories directly.
Replying to
@vagrantc@floss.social Radicle only supports Ed25519 keys. If your card does Ed25519, it should be fine to use as your user identity. However, it is currently not possible to use your smartcard for the Radicle node process, since it does ECDH and encryption in a way that is not supported by SSH Agent. It is technically already possible to use two different keys for your user ID and node ID, see radicle-node --secret. The UX is not polished, so unless you're adventurous, please wait until we release it.
Replying to
@vagrantc@floss.social Thanks for the praise, it fills our hearts with a nice warm and fuzzy feeling when we hear that people are happy with the tools we develop! 😃 Thanks also for your criticism! You are right; the SSH Agent might not have been the best choice here for the long term. It regularly causes confusion. But we also can't change that on a whim. You know, we have a 1.0.0 out, want to batch breakage, and all that 😊
Replying to
@halfbyte@ruby.social With Radicle, members of your coop would agree to mutually seed their repositories. The peer-to-peer architecture makes it easy to participate. For practical reasons you would need a few nodes with relatively overlapping uptime, like shifts with handovers, but the resource requirements are low. You can run a Radicle node on a Raspberry Pi, and certainly as a daemon on your main machine. It is all FOSS. Check it out at https://radicle.dev
Replying to
@alienghic@timeloop.cafe @jonny@neuromatch.social @happyborg@fosstodon.org Correct. New nodes first connect to {iris,rosa}.radicle.network (Tor onion services available for both). From there, nodes learn the addresses of other nodes. We also expose some node addresses via DNS-SD at bootstrap.radicle.network via the service name "radicle-node", see https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=radicle-node And we plan to use DNS-SD directly in the future. You can also configure/run your own separate network, only connecting to exactly the nodes you intend to be connected to.