{"id":1056,"date":"2026-07-09T11:47:41","date_gmt":"2026-07-09T19:47:41","guid":{"rendered":"https:\/\/salemdata.net\/johnpress\/?p=1056"},"modified":"2026-07-09T11:47:41","modified_gmt":"2026-07-09T19:47:41","slug":"reticulum-finding-the-definitive-source","status":"publish","type":"post","link":"https:\/\/salemdata.net\/johnpress\/?p=1056","title":{"rendered":"Reticulum: Finding The Definitive Source"},"content":{"rendered":"
<h1>Where, oh where, is the current Reticulum source of truth?<\/h1>\n<p>Currently the Reticulum protocol is accepted as defined within the Python code implementation created by Mark Qvist.\u00a0 There is no formal specification\u00a0for the Reticulum protocol.\u00a0 Hence the protocol is derived from Mark’s Python source tree.\u00a0 The question I faced: where can I obtain the current high watermark of the implementation?\u00a0 Mark’s GitHub page states development is “happening elsewhere.”<\/p>\n<img class=" wp-image-1060" src="https:\/\/salemdata.net\/johnpress\/wp-content\/uploads\/2026\/07\/20260709_114344_Thu.png" alt="" width="530" height="255" \/> GitHub markqvist\/Reticulum Project README.md\n<p>As of 10:00 AM, Thursday, July 9, 2026, the source of truth among the releases varies.<\/p>\n<h2>Releases As Of 7\/8\/26<\/h2>\n<p>GitHub is 1.3.4<\/p>\n<p> <\/p>\n<img class="size-full wp-image-1058" src="https:\/\/salemdata.net\/johnpress\/wp-content\/uploads\/2026\/07\/20260709_103138_Thu.png" alt="" width="874" height="557" \/> GitHub for project markqvist\/Reticulum\n<p>The PyPI [Python Package Installer] page for rns is: 1.3.7<\/p>\n<p> <\/p>\n<img class="size-full wp-image-1057" src="https:\/\/salemdata.net\/johnpress\/wp-content\/uploads\/2026\/07\/20260709_100829_Thu.png" alt="" width="621" height="885" \/> pypi.org project page for rns\n<p>I use Chad Attermann’s <a href="https:\/\/github.com\/attermann\/microReticulum">microReticulum<\/a> project which is written in C++ and can be loaded onto a Lilygo T-Beam SUPREME.\u00a0 Chad’s project relies upon the GitHub release, currently at 1.3.4.\u00a0 (See https:\/\/github.com\/attermann\/microReticulum\/issues\/68 “Reticulum: Source of Truth #68”.) If I am going to make the investment of time to bring my testing harness up to the high watermark, I’d prefer I be at 1.3.7 so I can assume I do not have to keep following the high watermark.<\/p>\n<h1>Fetching the definitive source of truth<\/h1>\n<p>With ChatGPT’s help searching the varied sources, I came up with this method to fetch from Mark Qvist his current release using his rnsgit tool.\u00a0 (The riddle, of course, is knowing the correct reticulum address which can change or become inactive.\u00a0 Rather that pour through the various forums, many of which become stale, I relied on ChatGPT to search for me.) The command that finally resolved the ambiguity was:<\/p>\n<pre>rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\\r\n \u00a0fetch latest:all \\\r\n \u00a0--signer bc7291552be7a58f361522990465165c<\/pre>\n<p><em>Caution<\/em>: the above does not create a protocol specification. It only identifies the current signed implementation release I was able to retrieve over Reticulum as of the date shown.<\/p>\n<h3>Recipe<\/h3>\n<p>1) Install a dedicated Python virtual environment for Reticulum; all command hereafter <em>assume you are operating within such an isolated environment<\/em>.<\/p>\n<p>2) Verify which version of rns you have:<\/p>\n<pre>python3 -m pip show rns \r\nName: rns \r\nVersion: 1.3.7 \r\nSummary: Self-configuring, encrypted and resilient mesh networking stack for LoRa, packet radio, WiFi and everything in between \r\nHome-page: https:\/\/reticulum.network\/ \r\nAuthor: Mark Qvist \r\nAuthor-email: mark@unsigned.io \r\nLicense: Reticulum License \r\nLocation: \/home\/jlpoole\/rnsenv\/lib\/python3.13\/site-packages \r\nRequires: cryptography, pyserial \r\nRequired-by: lxmf, lxst, nomadnet, sbapp \r\n[ rnsenv|script ] jlpoole@jp ~\/tmp\/reticulum-rngit-fetch<\/pre>\n<p>3) If your rns version does not match, I found upgrading with pip did not take me from 1.3.4 to 1.3.7; I had to remove version 1.3.4 and then install anew:<\/p>\n<p>pip install rns<\/p>\n<img class=" wp-image-1061" src="https:\/\/salemdata.net\/johnpress\/wp-content\/uploads\/2026\/07\/20260709_122035_Thu.png" alt="" width="694" height="317" \/> directory.rns.recipes\/\n<p>4) Edit your rns configuration file, ~\/.reticulum\/config,\u00a0 to point to some <em>active<\/em> rns servers.\u00a0 A list of active servers may be accessed at: https:\/\/directory.rns.recipes\/<\/p>\n<p> <\/p>\n<pre>[interfaces]<\/pre>\n<pre>[[RNS Sideband]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = sideband.connect.reticulum.network\r\ntarget_port = 7822\r\n\r\n[[Beleth RNS Hub]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = rns.beleth.net\r\ntarget_port = 4242\r\n\r\n[[RMAP]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = rmap.world\r\ntarget_port = 4242\r\n\r\n[[Nexus Backbone PH]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = 212.227.208.95\r\ntarget_port = 4242<\/pre>\n<p>5) Start your rns daemon in its own console (within your virtual Python environment):<\/p>\n<pre>\u00a0 \u00a0 rnsd -v<\/pre>\n<img class="size-full wp-image-1062" src="https:\/\/salemdata.net\/johnpress\/wp-content\/uploads\/2026\/07\/20260709_122234_Thu.png" alt="" width="898" height="309" \/> rns daemon\n<p>6) In another console (within your virtual Python environment), test if you can “rnpath” (similar to ping) the address:<\/p>\n<pre>(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ rnpath 7649a50d84610232d1416b41d2896aff \r\nPath found, destination <7649a50d84610232d1416b41d2896aff> is 5 hops away via <521c87a83afb8f29e4455e77930b973b> on TCPInterface[RNS Sideband\/sideband.connect.reticulum.network:7822] \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ date \r\nThu Jul \u00a09 11:16:17 PDT 2026 \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $<\/pre>\n<p>Assuming you successfully resolved the path, you can use the tool <strong>rnsgit<\/strong><\/p>\n<pre>rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\ \r\n\u00a0fetch latest:all \\ \r\n\u00a0--signer bc7291552be7a58f361522990465165c<\/pre>\n<p>Here’s my fetch attempt and the results:<\/p>\n<pre>(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\ \r\n\u00a0fetch latest:all \\ \r\n\u00a0--signer bc7291552be7a58f361522990465165c \r\nTransferring manifest.rsm: 100% (3.76 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\nRelease manifest validated, signed by <bc7291552be7a58f361522990465165c> \r\nFetching 5 artifacts... \r\n\u00a0Transferring rns-1.3.7.tar.gz: 100% (516.65 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring rns-1.3.7-py3-none-any.whl: 100% (603.49 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring rnspure-1.3.7-py3-none-any.whl: 100% (603.62 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring Reticulum Manual.epub: 100% (4.07 MB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring Reticulum Manual.pdf: 100% (5.03 MB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ ls -la \r\ntotal 13864 \r\ndrwxr-xr-x 2 jlpoole jlpoole \u00a0\u00a0\u00a04096 Jul \u00a09 11:17 \u00a0. \r\ndrwxr-xr-x 5 jlpoole jlpoole \u00a0\u00a0\u00a04096 Jul \u00a09 10:55 \u00a0.. \r\n-rw-r--r-- 1 jlpoole jlpoole 4072754 Jul \u00a09 11:17 'Reticulum Manual.epub' \r\n-rw-r--r-- 1 jlpoole jlpoole 5029143 Jul \u00a09 11:17 'Reticulum Manual.pdf' \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0603491 Jul \u00a09 11:16 \u00a0rns-1.3.7-py3-none-any.whl \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0516648 Jul \u00a09 11:16 \u00a0rns-1.3.7.tar.gz \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0\u00a0\u00a03763 Jul \u00a09 11:16 \u00a0rns_1.3.7.rsm \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0603624 Jul \u00a09 11:16 \u00a0rnspure-1.3.7-py3-none-any.whl \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $<\/pre>\n<p>Here’s what is in the rns-1.3.7.tar.gz<\/p>\n<pre>(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch_20260709_1117 $ mkdir -p ~\/tmp\/rns-1.3.7_src_20260709_1117 \r\ntar -xzf rns-1.3.7.tar.gz -C ~\/tmp\/rns-1.3.7_src_20260709_1117 --strip-components=1 \r\ncd ~\/tmp\/rns-1.3.7_src_20260709_1117 \r\nfind . -maxdepth 2 -type f | sort | less \r\n(rnsenv) jlpoole@jp ~\/tmp\/rns-1.3.7_src_20260709_1117 $ find . -maxdepth 2 -type f | sort \u00a0\r\n.\/CRNS\/__init__.py \r\n.\/PKG-INFO \r\n.\/README.md \r\n.\/RNS\/Buffer.py \r\n.\/RNS\/Channel.py \r\n.\/RNS\/Destination.py \r\n.\/RNS\/Discovery.py \r\n.\/RNS\/Identity.py \r\n.\/RNS\/Link.py \r\n.\/RNS\/Packet.py \r\n.\/RNS\/Resolver.py \r\n.\/RNS\/Resource.py \r\n.\/RNS\/Reticulum.py \r\n.\/RNS\/Transport.py \r\n.\/RNS\/__init__.py \r\n.\/RNS\/_version.py \r\n.\/rns.egg-info\/PKG-INFO \r\n.\/rns.egg-info\/SOURCES.txt \r\n.\/rns.egg-info\/dependency_links.txt \r\n.\/rns.egg-info\/entry_points.txt \r\n.\/rns.egg-info\/requires.txt \r\n.\/rns.egg-info\/top_level.txt \r\n.\/setup.cfg \r\n.\/setup.py \r\n(rnsenv) jlpoole@jp ~\/tmp\/rns-1.3.7_src_20260709_1117 $<\/pre>\n<h2>Conclusion<\/h2>\n<p>For my purposes, the signed RNS-distributed release is the best practical source of truth. GitHub is still useful for history, issue discussion, and derivative projects, but the current implementation watermark appears to be the signed release retrievable over Reticulum itself.<\/p>\n<\/div>

Where, oh where, is the current Reticulum source of truth?<\/h1>\n

Currently the Reticulum protocol is accepted as defined within the Python code implementation created by Mark Qvist.\u00a0 There is no formal specification\u00a0for the Reticulum protocol.\u00a0 Hence the protocol is derived from Mark’s Python source tree.\u00a0 The question I faced: where can I obtain the current high watermark of the implementation?\u00a0 Mark’s GitHub page states development is “happening elsewhere.”<\/p>\n

\"\"
GitHub markqvist\/Reticulum Project README.md<\/figcaption><\/figure>\n

As of 10:00 AM, Thursday, July 9, 2026, the source of truth among the releases varies.<\/p>\n

Releases As Of 7\/8\/26<\/h2>\n

GitHub is 1.3.4<\/p>\n

 <\/p>\n

\"\"
GitHub for project markqvist\/Reticulum<\/figcaption><\/figure>\n

The PyPI [Python Package Installer] page for rns is: 1.3.7<\/p>\n

 <\/p>\n

\"\"
pypi.org project page for rns<\/figcaption><\/figure>\n

I use Chad Attermann’s microReticulum<\/a> project which is written in C++ and can be loaded onto a Lilygo T-Beam SUPREME.\u00a0 Chad’s project relies upon the GitHub release, currently at 1.3.4.\u00a0 (See https:\/\/github.com\/attermann\/microReticulum\/issues\/68 “Reticulum: Source of Truth #68”.) If I am going to make the investment of time to bring my testing harness up to the high watermark, I’d prefer I be at 1.3.7 so I can assume I do not have to keep following the high watermark.<\/p>\n

Fetching the definitive source of truth<\/h1>\n

With ChatGPT’s help searching the varied sources, I came up with this method to fetch from Mark Qvist his current release using his rnsgit tool.\u00a0 (The riddle, of course, is knowing the correct reticulum address which can change or become inactive.\u00a0 Rather that pour through the various forums, many of which become stale, I relied on ChatGPT to search for me.) The command that finally resolved the ambiguity was:<\/p>\n

rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\\r\n \u00a0fetch latest:all \\\r\n \u00a0--signer bc7291552be7a58f361522990465165c<\/pre>\n
Caution<\/em>: the above does not create a protocol specification. It only identifies the current signed implementation release I was able to retrieve over Reticulum as of the date shown.<\/p>\n
Recipe<\/h3>\n
1) Install a dedicated Python virtual environment for Reticulum; all command hereafter assume you are operating within such an isolated environment<\/em>.<\/p>\n
2) Verify which version of rns you have:<\/p>\n
python3 -m pip show rns \r\nName: rns \r\nVersion: 1.3.7 \r\nSummary: Self-configuring, encrypted and resilient mesh networking stack for LoRa, packet radio, WiFi and everything in between \r\nHome-page: https:\/\/reticulum.network\/ \r\nAuthor: Mark Qvist \r\nAuthor-email: mark@unsigned.io \r\nLicense: Reticulum License \r\nLocation: \/home\/jlpoole\/rnsenv\/lib\/python3.13\/site-packages \r\nRequires: cryptography, pyserial \r\nRequired-by: lxmf, lxst, nomadnet, sbapp \r\n[ rnsenv|script ] jlpoole@jp ~\/tmp\/reticulum-rngit-fetch<\/pre>\n
3) If your rns version does not match, I found upgrading with pip did not take me from 1.3.4 to 1.3.7; I had to remove version 1.3.4 and then install anew:<\/p>\n
pip install rns<\/p>\n
\"\"
directory.rns.recipes\/<\/figcaption><\/figure>\n
4) Edit your rns configuration file, ~\/.reticulum\/config,\u00a0 to point to some active<\/em> rns servers.\u00a0 A list of active servers may be accessed at: https:\/\/directory.rns.recipes\/<\/p>\n
 <\/p>\n
[interfaces]<\/pre>\n
[[RNS Sideband]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = sideband.connect.reticulum.network\r\ntarget_port = 7822\r\n\r\n[[Beleth RNS Hub]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = rns.beleth.net\r\ntarget_port = 4242\r\n\r\n[[RMAP]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = rmap.world\r\ntarget_port = 4242\r\n\r\n[[Nexus Backbone PH]]\r\ntype = TCPClientInterface\r\nenabled = yes\r\ntarget_host = 212.227.208.95\r\ntarget_port = 4242<\/pre>\n
5) Start your rns daemon in its own console (within your virtual Python environment):<\/p>\n
\u00a0 \u00a0  rnsd -v<\/pre>\n
\"\"
rns daemon<\/figcaption><\/figure>\n
6) In another console (within your virtual Python environment), test if you can “rnpath” (similar to ping) the address:<\/p>\n
(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ rnpath 7649a50d84610232d1416b41d2896aff \r\nPath found, destination <7649a50d84610232d1416b41d2896aff> is 5 hops away via <521c87a83afb8f29e4455e77930b973b> on TCPInterface[RNS Sideband\/sideband.connect.reticulum.network:7822] \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ date \r\nThu Jul \u00a09 11:16:17 PDT 2026 \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $<\/pre>\n
Assuming you successfully resolved the path, you can use the tool rnsgit<\/strong><\/p>\n
rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\ \r\n\u00a0fetch latest:all \\ \r\n\u00a0--signer bc7291552be7a58f361522990465165c<\/pre>\n
Here’s my fetch attempt and the results:<\/p>\n
(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ rngit release rns:\/\/7649a50d84610232d1416b41d2896aff\/reticulum\/reticulum \\ \r\n\u00a0fetch latest:all \\ \r\n\u00a0--signer bc7291552be7a58f361522990465165c \r\nTransferring manifest.rsm: 100% (3.76 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\nRelease manifest validated, signed by <bc7291552be7a58f361522990465165c> \r\nFetching 5 artifacts... \r\n\u00a0Transferring rns-1.3.7.tar.gz: 100% (516.65 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring rns-1.3.7-py3-none-any.whl: 100% (603.49 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring rnspure-1.3.7-py3-none-any.whl: 100% (603.62 KB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring Reticulum Manual.epub: 100% (4.07 MB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n\u00a0Transferring Reticulum Manual.pdf: 100% (5.03 MB) \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $ ls -la \r\ntotal 13864 \r\ndrwxr-xr-x 2 jlpoole jlpoole \u00a0\u00a0\u00a04096 Jul \u00a09 11:17 \u00a0. \r\ndrwxr-xr-x 5 jlpoole jlpoole \u00a0\u00a0\u00a04096 Jul \u00a09 10:55 \u00a0.. \r\n-rw-r--r-- 1 jlpoole jlpoole 4072754 Jul \u00a09 11:17 'Reticulum Manual.epub' \r\n-rw-r--r-- 1 jlpoole jlpoole 5029143 Jul \u00a09 11:17 'Reticulum Manual.pdf' \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0603491 Jul \u00a09 11:16 \u00a0rns-1.3.7-py3-none-any.whl \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0516648 Jul \u00a09 11:16 \u00a0rns-1.3.7.tar.gz \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0\u00a0\u00a03763 Jul \u00a09 11:16 \u00a0rns_1.3.7.rsm \r\n-rw-r--r-- 1 jlpoole jlpoole \u00a0603624 Jul \u00a09 11:16 \u00a0rnspure-1.3.7-py3-none-any.whl \r\n(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch $<\/pre>\n
Here’s what is in the rns-1.3.7.tar.gz<\/p>\n
(rnsenv) jlpoole@jp ~\/tmp\/reticulum-rngit-fetch_20260709_1117 $ mkdir -p ~\/tmp\/rns-1.3.7_src_20260709_1117 \r\ntar -xzf rns-1.3.7.tar.gz -C ~\/tmp\/rns-1.3.7_src_20260709_1117 --strip-components=1 \r\ncd ~\/tmp\/rns-1.3.7_src_20260709_1117 \r\nfind . -maxdepth 2 -type f | sort | less \r\n(rnsenv) jlpoole@jp ~\/tmp\/rns-1.3.7_src_20260709_1117 $ find . -maxdepth 2 -type f | sort \u00a0\r\n.\/CRNS\/__init__.py \r\n.\/PKG-INFO \r\n.\/README.md \r\n.\/RNS\/Buffer.py \r\n.\/RNS\/Channel.py \r\n.\/RNS\/Destination.py \r\n.\/RNS\/Discovery.py \r\n.\/RNS\/Identity.py \r\n.\/RNS\/Link.py \r\n.\/RNS\/Packet.py \r\n.\/RNS\/Resolver.py \r\n.\/RNS\/Resource.py \r\n.\/RNS\/Reticulum.py \r\n.\/RNS\/Transport.py \r\n.\/RNS\/__init__.py \r\n.\/RNS\/_version.py \r\n.\/rns.egg-info\/PKG-INFO \r\n.\/rns.egg-info\/SOURCES.txt \r\n.\/rns.egg-info\/dependency_links.txt \r\n.\/rns.egg-info\/entry_points.txt \r\n.\/rns.egg-info\/requires.txt \r\n.\/rns.egg-info\/top_level.txt \r\n.\/setup.cfg \r\n.\/setup.py \r\n(rnsenv) jlpoole@jp ~\/tmp\/rns-1.3.7_src_20260709_1117 $<\/pre>\n
Conclusion<\/h2>\n
For my purposes, the signed RNS-distributed release is the best practical source of truth. GitHub is still useful for history, issue discussion, and derivative projects, but the current implementation watermark appears to be the signed release retrievable over Reticulum itself.<\/p>\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"
<h1>Where, oh where, is the current Reticulum source of truth?<\/h1> <p>Currently the Reticulum protocol is accepted as defined within the Python code implementation created by Mark Qvist.\u00a0 There is no formal specification\u00a0for the Reticulum protocol.\u00a0 Hence the protocol is derived from Mark’s Python source tree.\u00a0 The question I faced: where can I obtain the current […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_gfmr_meta_descriptions":[],"_gfmr_multilingual_taxonomy_terms":[],"footnotes":""},"categories":[131,130,1],"tags":[],"class_list":["post-1056","post","type-post","status-publish","format-standard","hentry","category-microreticulum","category-reticulum","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/posts\/1056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1056"}],"version-history":[{"count":6,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/posts\/1056\/revisions"}],"predecessor-version":[{"id":1067,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=\/wp\/v2\/posts\/1056\/revisions\/1067"}],"wp:attachment":[{"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1056"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1056"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salemdata.net\/johnpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}