# A Reticulum Protocol Specification, Extracted from the Implementation

_General · started by p1ld7a on Thu, Jun 11, 2026 10:00 AM_

---

## Original post

**p1ld7a** · Thu, Jun 11, 2026 10:00 AM

Hello all,

I saw [this post](https://mastodon.online/@VogueLaGalere/116724199151138728) on Mastodon and thought it might be interesting to share it here as well: https://salemdata.net/johnpress/?p=861

---

## Reply 1

**Zenith** · Thu, Jun 11, 2026 10:57 AM

I’m not quite sure what the intended goal of this is

The manual and API reference document everything already. 

A read over of Transport.py will tell you the rest of the nuances

This is also littered with mistakes too, and weird text encoding errors. I will cover the mistakes in the next post. 

This is getting beyond frustrating to deal with as people seem to just be throwing shit at LLMs for no other reason than they can

---

## Reply 2

**aetherlab** · Thu, Jun 11, 2026 11:08 AM

Absolutely!

---

## Reply 3

**Puint** · Sat, Jun 20, 2026 8:56 AM

Hmm, I personally, do no think that the manual and API reference doc is everything that is ever needed and would definately welcome a formal spec. However, I see that this is quote a big task and needs constant updating as well, since reticulum is still moving rapidly at this point.

---