https://wiki.scotmesh.net/index.php?action=history&feed=atom&title=What_Reticulum_isWhat Reticulum is - Revision history2026-09-18T22:35:31ZRevision history for this page on the wikiMediaWiki 1.43.9https://wiki.scotmesh.net/index.php?title=What_Reticulum_is&diff=58&oldid=prevScotMesh: Imported from the BookStack wiki (backup 2026-09-11)2026-09-11T14:49:34Z<p>Imported from the BookStack wiki (backup 2026-09-11)</p>
<p><b>New page</b></p><div>=== What is Reticulum? ===<br />
<br />
When people think of a mesh, they usually think of LoRa mesh networks such as MeshCore or Meshtastic. '''Reticulum is a little different.'''<br />
<br />
Reticulum isn't tied to a particular radio technology. Instead, it is a networking system that can use almost anything capable of transporting data to build a network. This could be the traditional Internet, LoRa radio, HaLow, Wi-Fi, Bluetooth/BLE, MeshCore, Meshtastic, or even satellite communications such as Iridium. If we can using it as a Physical Interface<br />
<br />
This means a Reticulum network can span across completely different types of connections. A message could travel over LoRa from one node, across a Wi-Fi link, through the Internet, and then back out over radio to reach its destination.<br />
<br />
The goal is to make communications '''decentralised, resilient and independent of any single network or provider'''. For Scotland, this means we can build a network that connects communities and radio nodes together using whatever connectivity is available in each location.<br />
<br />
In simple terms: '''Reticulum is the glue that allows different types of networks to become one resilient mesh, adding more variety of traffic bearers makes a more resilient mesh.'''<br />
<br />
''' '''<br />
<br />
[[File:reticulum-scotland-drawing-drawio.png|frameless|upright=2.2|reticulum_scotland_drawing.drawio.png]]<br />
<br />
=== The really interesting bit ===<br />
<br />
Reticulum isn't trying to recreate the Internet.<br />
<br />
There are no traditional IP addresses that you need to configure. There is no DNS server that needs to know where everyone is. There is no central registration authority handing out addresses.<br />
<br />
Instead, Reticulum uses '''cryptographic identities'''.<br />
<br />
Your identity is effectively your cryptographic key. From that identity you can create destinations for different applications and services. Other nodes don't need to know your IP address, and you don't need to register your identity with a central server.<br />
<br />
That makes the network much more interesting when you start thinking about infrastructure.<br />
<br />
A node can disappear.<br /><br />
An Internet connection can go down.<br /><br />
A radio link can disappear.<br /><br />
An entire transport node can be switched off.<br />
<br />
'''The network can still function using whatever paths remain available.'''<br />
<br />
=== Bearers: Reticulum doesn't care what carries the data ===<br />
<br />
This is where Reticulum gets particularly powerful.<br />
<br />
The underlying connection is effectively a '''bearer''' for Reticulum traffic.<br />
<br />
That bearer could be:<br />
<br />
* 📻 LoRa<br />
* 📡 Packet radio<br />
* 📶 Wi-Fi<br />
* 🌐 TCP/IP<br />
* 🛰️ Satellite<br />
* 🔵 Bluetooth/BLE<br />
* 🔐 I2P<br />
* Or another supported interface<br />
<br />
From Reticulum's perspective, these are simply different ways of moving data.<br />
<br />
[[Category:Getting Started]]</div>ScotMesh