Yorgos Saslis 73ad1de2a4 node/routing: Enforce routingMaxSize
`limits.routingMaxSize` is documented as "Number of routing table entries
before we start pruning", but the implementation diverges from this.

    DELETE FROM routing WHERE node <> ?1 AND rowid IN
      (SELECT rowid FROM routing WHERE timestamp < ?2 ORDER BY timestamp LIMIT ?3)

`?2` is `now - routingMaxAge`. So if nothing is older than routingMaxAge,
nothing is deleted, however far over routingMaxSize the table has grown. On a
seed following a busy network, entries are refreshed by gossip faster than
they age out, and the cap is never reachable.

For example, on a permissive node with routingMaxSize=1000, routingMaxAge=7d,
I observed:

    routing rows                             94,254
    older than routingMaxAge, ie. prunable       16

Dropping routingMaxAge to 1 day cleared the backlog the 7-day setting had
accumulated -- from 94,254 down to 82,400 rows -- but then stopped, with
8 rows prunable and the table still ... 82x over the cap. The `routing` table
size is therefore decided by arrival rate; the configured max size has no
effect on it.

Split the two evictions so each does what its name says:

- size eviction removes the oldest entries down to `routingMaxSize`,
  regardless of age;
- age eviction then removes anything still older than
`routingMaxAge`.

Size runs first: it takes the oldest rows, so the age pass only fires when
the table was near its limit.
2026-10-08 12:06:06 +02:00
2024-05-17 13:27:18 +02:00
2023-12-13 12:25:12 +01:00
2026-08-30 14:28:36 +02:00
2026-05-28 16:52:02 +01:00
2026-07-24 16:27:02 +02:00
2024-04-29 10:47:03 +02:00
2026-09-04 13:45:43 +02:00
2025-04-17 14:33:36 +02:00
2026-03-30 16:57:51 +02:00
2026-07-24 16:27:02 +02:00
2026-09-08 10:37:22 +02:00
2026-04-15 10:06:05 +02:00
2022-11-16 12:26:12 +01:00
2025-12-08 16:43:50 +00:00
2026-09-07 21:11:46 +02:00
2026-05-28 16:52:02 +01:00
2026-04-30 15:50:29 -04:00
2026-08-30 14:28:36 +02:00
2024-04-29 10:47:03 +02:00

❤️🪵

Radicle Heartwood Protocol & Stack

Heartwood is the third iteration of the Radicle Protocol, a powerful peer-to-peer code collaboration and publishing stack. The repository contains a full implementation of Heartwood, complete with a user-friendly command-line interface (rad) and network daemon (radicle-node).

Radicle was designed to be a secure, decentralized and powerful alternative to code forges such as GitHub and GitLab that preserves user sovereignty and freedom.

See the Radicle home page for general information, and the Zulip chat to talk to the project.

See the Protocol Guide for an in-depth description of how Radicle works.

Installation

Requirements

  • Linux or Unix based operating system.
  • Git 2.34 or later
  • OpenSSH 9.1 or later with ssh-agent

📀 From binaries

Requires curl and tar.

Run the following command to install the latest binary release:

curl -sSf https://radicle.dev/install | sh

Or visit our download page.

📦 From source

Requires the Rust toolchain.

You can install the Radicle stack from source, by running the following commands from inside this repository:

cargo install --path crates/radicle-cli --force --locked --root ~/.radicle
cargo install --path crates/radicle-node --force --locked --root ~/.radicle
cargo install --path crates/radicle-remote-helper --force --locked --root ~/.radicle

Or directly from our seed node:

cargo install --force --locked --root ~/.radicle \
    --git https://seed.radicle.dev/z3gqcJUoA1n9HaHKufZs5FCSGazv5.git \
    crates/radicle-cli crates/radicle-node crates/radicle-remote-helper

Running

Systemd unit files are provided for the node under the /systemd folder. They can be used as a starting point for further customization.

For running in debug mode, see HACKING.md.

Feedback

If you have feedback, feel free to create issues using rad issue, join our Zulip, or email feedback@radicle.dev. Emails sent to this address are automatically posted to our public #feedback channel on Zulip, revealing the From header (which usually contains your name and email address). This allows us to discuss your feedback on Zulip, and, if necessary, respond to you via email.

Contributing

See CONTRIBUTING.md and HACKING.md for an introduction to contributing to Radicle.

Packages

Community members maintain packages for various package managers. This makes it a lot easier to install Radicle and allows tighter integration of Radicle with various distributions. Thanks!

APT (Debian, etc.)

See https://radicle.dev/apt/ and rad:z2nDKoCF4hg6xVrv7v93LmWHDJKUr maintained by Lars Wirzenius and Richard Levitte

Arch

See archlinux.org/packages and gitlab.archlinux.org maintained by tippfehlr and kpcyrd.

NixOS

See search.nixos.org/packages and search.nixos.org/options maintained by @NixOS/radicle.

Also see home-manager-options.extranix.com for usage with home-manager.

License

Radicle is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

S
Description
Radicle Heartwood Protocol & Stack
Readme
38 MiB
Languages
Rust 97.8%
Shell 0.5%
CUE 0.4%
Nix 0.3%
Just 0.3%
Other 0.6%