2026-09-07T20:36:38Z https://njump.me Resilum https://njump.me/npub1rhj8lc0aecl6c0rgmxdvz8wgp0nq2ep3jqyy9q7c9npycryq9afsuvffdq https://npub1rhj8lc0aecl6c0rgmxdvz8wgp0nq2ep3jqyy9q7c9npycryq9afsuvffdq.blossom.band/d9bb61a3e8add40e2a2f6e59349856b7cdaaa35c67017873e635baa0c363c38e.jpg https://npub1rhj8lc0aecl6c0rgmxdvz8wgp0nq2ep3jqyy9q7c9npycryq9afsuvffdq.blossom.band/d9bb61a3e8add40e2a2f6e59349856b7cdaaa35c67017873e635baa0c363c38e.jpg https://njump.me/nevent1qqsv7lfw0tya9np37x04t87kk3fzncxc7362yps8gje6squzppelydczyqw7gllplh8rltpudrve4sgaeq97vptyxxgqss5rmqkvynqvsqh4xjqfnlv Resilum Core v0.2.3 — a status command that reads the node aloud<br/><br/>- docs: show the node starting and the peers placed<br/>- discovery: keep iroh and cache-warmed peers among the links<br/>- resilumd: a status command that reads the node aloud<br/>- coordinates: measure each route apart, not all as one<br/>- status: one snapshot for every consumer<br/><br/><a href="https://github.com/Resilum/resilum-core/releases/tag/v0.2.3">https://github.com/Resilum/resilum-core/releases/tag/v0.2.3</a><br/> 2026-09-11T19:47:54Z https://njump.me/nevent1qqsw28vwkw40a5s6se4utf0r270w0cyv36t80l7ujx8ysfwaz4wyzhszyqw7gllplh8rltpudrve4sgaeq97vptyxxgqss5rmqkvynqvsqh4xvh4rnj In reply to <a href='/naddr1qqtx7mn994hx7er994kkzmne94mkz7tn94hh2aqzyqw7gllplh8rltpudrve4sgaeq97vptyxxgqss5rmqkvynqvsqh4xqcyqqq823cz3zl3n'>naddr1qq…zl3n</a><br/>_________________________<br/><br/>We started a devlog for Resilum Core — a Reticulum node in Rust that keeps TCP/IP, Tor, I2P, Yggdrasil, QUIC and ICMP up at once, under one peer identity. When an interface dies the link moves to another one, and the destination hash never changes, so nobody re-adds anybody.<br/><br/>First entry: what a node looks like when it comes up, what it can tell you about the neighbourhood around it, and what is ready today.<br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqtx7mn994hx7er994kkzmne94mkz7tn94hh2aqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3qrhj8lc0aecl6c0rgmxdvz8wgp0nq2ep3jqyy9q7c9npycryq9afsxpqqqp65wf3ngag" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…ngag</a></span><br/> </div> <h1 id="one-node-many-ways-out-2">One node, many ways out</h1> <p>There is a moment every mesh setup runs into: the interface you configured stops working, and the node is simply gone. You edit a config, restart, tell people the new address. Reticulum solves half of this — a destination is a hash, not an address — and then most setups undo it by pinning a node to one interface.</p> <p>Resilum Core is a Reticulum node in Rust that keeps several interfaces up at once, under a single identity, and moves a link to whichever one can currently reach the peer.</p> <h2 id="start-it-and-ask-it-where-it-is-2">Start it, and ask it where it is</h2> <p>The image already carries Tor, Yggdrasil and I2P, and the entrypoint writes every config file on first start. So a node is:</p> <pre><code>cd deploy &amp;&amp; docker compose up -d </code></pre> <p>From there it is worth asking the node what it sees, because that is the part a mesh usually hides from you:</p> <pre><code>resilumd status # interfaces up, addresses announced, links held resilumd status --map # the neighbourhood, placed by latency rather than geography </code></pre> <p>The map is not a metaphor. Peers exchange positions over established links and measure the round trip, so &#34;near&#34; means responsive, not geographically close — a node three countries away on a good path sits closer than the one behind a congested circuit.</p> <p>And the mesh is usable as an internet exit right away:</p> <pre><code>curl -s -x socks5h://127.0.0.1:10808 https://check.torproject.org/api/ip </code></pre> <p><img src="https://npub1rhj8lc0aecl6c0rgmxdvz8wgp0nq2ep3jqyy9q7c9npycryq9afsuvffdq.blossom.band/b509c714059758874ece267d9e837f0b2a1d2776f45c3c623eefa2707f21bd3a.gif" alt="A node starting from a cold container, reporting its status and its neighbours, then carrying a request out to the internet"/></p> <p>There is nothing else to edit. Identity and state persist in a mounted directory, so a restart comes back as the same node.</p> <h2 id="the-build-is-the-same-everywhere-2">The build is the same everywhere</h2> <p>The role follows from what the machine has, not from a different build. Images are published for amd64 and arm64, so the same command works on all of these:</p> <ul> <li><strong>A VPS with a public address</strong> becomes an anchor others can dial, and — opt-in — a usable exit. Turning on the exit means other people&#39;s traffic leaves through your address, with the same exposure as running any public exit. It is off by default for that reason.</li> <li><strong>A single-board computer on a home LAN</strong> becomes the bridge between that LAN and the overlays: it holds the Tor, Yggdrasil and I2P sides so the phones and laptops around it do not have to.</li> <li><strong>A laptop</strong> is a plain client that joins and leaves, and gets a local SOCKS5 port to browse through the mesh.</li> <li><strong>Anything with a Wi-Fi radio</strong> can end up hosting a group for the devices around it, if the election picks it.</li> </ul> <p>Nothing above the link layer knows which interface carried a packet. If Tor dies mid-session, the next announce re-establishes the path over Yggdrasil or QUIC. The destination hash does not change, so nobody re-adds anybody.</p> <h2 id="what-is-ready-2">What is ready</h2> <p>Running today: TCP/IP, UDP, Tor (an external daemon, or an in-process client), I2P over SAM, Yggdrasil, iroh/QUIC with hole punching, and ICMP echo — frames riding inside ping payloads, where the client side needs no privileges at all. On top of the transports: LXMF messaging, a SOCKS5 ingress and an L3 VPN that routes flows into the mesh.</p> <p>Being built right now: BLE, and Wi-Fi Direct, where the daemon raises a P2P group through whichever of NetworkManager, iwd or wpa_supplicant holds the radio.</p> <p>The node is backwards compatible with the reference Python implementation, so it joins the existing network as a peer rather than starting a parallel one.</p> <h2 id="a-mobile-client-is-coming-2">A mobile client is coming</h2> <p>Not as a rewrite: the phone links this same node as a shared library through its C ABI, so the transports, the identity handling and the delivery logic are literally the same code as on a VPS. That is the reason the C ABI exists at all.</p> <p>It is not released yet, and we are not giving a date — when it is out, it will be a post here with a link, not a promise.</p> <h2 id="why-a-devlog-2">Why a devlog</h2> <p>The interesting part of this project is not the feature list, it is the decisions. How BLE peers elect who hosts a group. What the covert ICMP transport can and cannot hide. What broke when a link had to survive its interface dying.</p> <p>New entries go out with each release, plus whatever is worth writing up in between. The current release is v0.2.3.</p> <p>Code, AGPL-3.0: <a href="https://github.com/Resilum/resilum-core">https://github.com/Resilum/resilum-core</a></p> </blockquote><br/>#resilum #reticulum #meshnetwork #p2p #rust #privacy<br/> 2026-09-11T19:47:39Z