Skip to main content



To create a working copy of a project on a user's machine. This working copy is where a person can make and publish changes to a project locally.


To create a network connection to another Radicle peer. Connected peers spread information between each other via gossip.


A peer who has pushed code to a project.


Any peer who can sign on behalf of the project, which means their state is trusted within the context of the project. There can be one or more delegates of a given project. For example, cloudhead (with a Peer ID of hyn9diwfnytahjq8u3iw63h9jte1ydcatxax3saymwdxqu1zo645pe) is the delegate of the radicle-cli project, which means their master branch is the de facto standard. There can be multiple delegates for a given project

display name

A non-unique human-readable name chosen by a Radicle user. Like a "nickname" for someone's Peer ID. This will be possible to change in the future.


Following a project replicates it to your machine. This allows the follower to subscribe to updates from the project's maintainer(s) or other remotes. It is also a way to signal interest in the project or peer by further replicating the data across their network, making it available to other people on the network. See Tracking.


Forking a project in Radicle clones a working copy to your machine and publishes it as a project to the network.


A free and open source distributed version control system.


A means of peer-to-peer communication that relies on the interactions of peers to disseminate information. Participants in the Radicle network share and spread data by keeping redundant copies of projects locally and sharing updates with peers. This allows data to be disseminated according to use and value: the more peers who are interested in certain data the more available it is made to the network. See Gossip.


A user who manages and pushes updates to the canonical view of a project. A maintainer is explicitly associated with the project at the time of creation or later, via the project metadata (see Data Model), but there may be multiple maintainers of a project, all maintaining their own trees. At creation, the creator of the project is the sole maintainer.


How Radicle Upstream refers to the default development branch of a project.


Radicle uses Git as a database. This means everything is stored in a single Git monorepo. Please see here for more details.


A peer running an instance of the Radicle Link protocol. There can only be one node running per device.


A sequence of characters used to encrypt a peer's private key (See Identities) to enable access to the Radicle network. It's also needed to fetch and push changesets to the Radicle network.


A device running the Radicle Link protocol.

peer ID

Part of your identity on the Radicle network. It identifies your device, a non-unique display name and the code you publish on the Radicle network, and is secured with an Ed25519 keypair.

personal URN

A unique identifier that allows you to register a permanent name with our opt-in integration with the Ethereum network.


A project consists of source code, issues, and proposed changesets. It carries a unique, shareable project URN. A project also includes the identities of all its maintainers. The entirety of the project data and metadata, including social artifacts such as comments, are stored within the project's repository on the user's machine. Projects are the principle unit of replication.

project name

A human-readable name that is chosen for a project. It is not guaranteed to be unique.

project URN

A unique identifier for a specific project on the Radicle network, roughly akin to the way GitHub identifies projects with user-name/project-name. Required for sharing a project with collaborators and cloning.


To make data public to the network. Once something is published, it may be fetched and replicated by connected peers.

A peer-to-peer replication protocol built on Git. See How it Works.

Radicle network

The network of peers that replicate and gossip data with Radicle Link.

Radicle Upstream

An open-source desktop application (graphic user interface, GUI) built to interact with and enable access to the Radicle network. However, in the future, it will be one of many potential clients that users can use to access the Radicle network.


Another peer's view of a project. Remotes can be pulled/fetched from. Maintainers of a project may choose to track other peer's views of their project by adding them as a remote. In the context of a project, maintainers of a repository may choose to track the views of other owners by adding them as a remote to the project. If the remote repository is found to track other remotes, the tracking repository shall also transitively track those, up to a configurable N degrees out.


An always-on node that automatically tracks discovered projects and serves data to their connected peers, thereby increasing the availability of these projects on the network. More on the role and impacts of seeds.


The repository in which code contributions for a project are intended to be merged once they pass the review process (i.e. canonical upstream or mainline). The upstream is often the repository of the project's original maintainer or creator. For everyone but the creator of this repository, upstream will be a remote repository.


Any individual who has created a Radicle ID on the Radicle network via the Upstream client.