Logos Storage: Difference between revisions

From Local Area Network
← Older edit
Second check fixes, plus material from the Circles handbook, Circle reports, LAN and Logos docs, source-checked
Course no longer cited as a source: views attributed to Logos, plain facts stated plainly
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
'''Logos Storage''' is the file-sharing module of the [[Logos]] technology stack. Logos describes it as "Privacy-preserving file sharing and retrieval using content-addressed (CID-based) data." The Logos Field Guide says it was formerly known as Codex. Together with [[Logos Blockchain]] and [[Logos Messaging]] it makes up the initial Logos stack, and people run it on their own machines through [[Basecamp]]. As of November 2026 it is in testing on the Logos [[Testnet]].
'''Logos Storage''' is the file-sharing module of the [[Logos]] technology stack, built for privacy-preserving file sharing and retrieval using content-addressed (CID-based) data. Its predecessor was Codex. With [[Logos Blockchain]] and [[Logos Messaging]] it makes up the initial Logos stack, which people run on their own machines through [[Basecamp]]. As of November 2026 it is in testing on the Logos [[Testnet]].


== What it does ==
== What it does ==
The Logos documentation calls Logos Storage "a filesharing protocol that allows users building on the Logos stack to publish and share files in a decentralised manner." Each node keeps files locally. Each file gets a unique identifier, a content identifier or CID. Anyone with a CID can download the file from the network.
Logos Storage is a file-sharing protocol that lets people building on the Logos stack publish and share files in a decentralised way. Each node keeps its files locally. Each file gets a unique content identifier, or CID, and anyone with the CID can download the file from the network.


The Logos website says that "In future, this module will support decentralised file storage." The node software's README calls the project "pre-alpha".
Logos plans for the module to support decentralised file storage in future. The node software is still pre-alpha.


The Logos activist course ''Building a Parallel Society'' (2026) describes three uses. It calls them "The press", "The archive" and "Distribution". The press lets a group publish without anyone's permission to keep the work available. The archive holds "agreements, decisions, and proof that outlive an order to delete them." Distribution means anyone can serve a copy and any copy can be checked against its address. The course says the module removes "the seized press" and "the cloud account someone else can empty."
Logos describes three uses, which it calls the press, the archive and distribution. The press lets a group publish without needing anyone's permission to keep the work available. The archive holds agreements, decisions and proof that outlive an order to delete them. Distribution means anyone can serve a copy and any copy can be checked against its address. In its account, the module removes "the seized press" and "the cloud account someone else can empty."


== How it works ==
== How it works ==
A user uploads a file to their own Logos Storage node. The node stores it and produces a CID, which the documentation compares to "a file share link." The user shares the CID by some other channel, for example Logos Messaging. Another user's node downloads the file, stores its own copy and makes it available to others.
A user uploads a file to their own Logos Storage node, which stores it and produces a CID that works much like a file share link. The user passes the CID on by some other channel, such as Logos Messaging. When another user's node downloads the file, it stores its own copy and makes that copy available to others.


The documentation calls this "organic replication". Each download adds a copy, so a file that many people want has many copies. The documentation contrasts this with storage networks such as Swarm or Sia, where providers are paid to keep content available. It notes a limit. If no one else is interested in a file, losing the only node that holds it is likely to mean losing the file.
This organic replication means each download adds a copy, so a file that many people want has many copies. Storage networks such as Swarm or Sia work differently, paying providers to keep content available. The approach has a limit. If no one else is interested in a file, losing the only node that holds it is likely to mean losing the file.


A node joins a Storage network through a bootstrap peer, a node that is already part of that network. Logos ships public bootstrap peers for two networks, logos.test and logos.dev. A node started with no bootstrap peer becomes the first member of a new network, and other nodes can join through it. The documentation says public bootstrap peers "are a convenience more than a necessity."
A node joins a Storage network through a bootstrap peer, a node that is already part of that network. Logos ships public bootstrap peers for two networks, logos.test and logos.dev. A node started with no bootstrap peer becomes the first member of a new network, which other nodes can then join through it. The documentation calls public bootstrap peers a convenience more than a necessity.


For privacy, Logos Storage uses a mix network, which the documentation calls Mix. Mix makes it harder for observers to work out who is downloading a file. The overview describes the aim as protecting both providers and downloaders "when fully mature". The Mix page states the current position: "as of storage v3.0.0, only nodes downloading benefit from the privacy protections of Mix. Nodes providing content must remain public and identifiable."
For privacy, Logos Storage uses a mix network called Mix, which makes it harder for observers to work out who is downloading a file. When fully mature it is meant to protect both providers and downloaders. As of storage v3.0.0 only downloading nodes benefit, and nodes providing content must remain public and identifiable.


The node software, logos-storage-nim, lives in the logos-storage organisation on GitHub. The documentation says Logos Storage is provided as a Logos module and needs the Logos runtime to work.
The node software, logos-storage-nim, lives in the logos-storage organisation on GitHub. Logos Storage is provided as a Logos module and needs the Logos runtime to work.


== In Basecamp ==
== In Basecamp ==
The Logos website says "The storage module ships with Basecamp. Files move directly between peers." The Logos procedure for Basecamp, written for Testnet v0.3, installs the Storage app from the Package Manager. The app brings in the storage_module as a dependency. An onboarding wizard sets up the node in guided or advanced mode.
The storage module ships with Basecamp, and files move directly between peers. The Basecamp procedure, written for Testnet v0.3, installs the Storage app from the Package Manager. The app brings in the storage_module as a dependency, and an onboarding wizard then sets up the node in guided or advanced mode.


The app can share files, download files by CID and delete them. Deleting a file removes its blocks, the pieces in which the file is stored, from disk. A user can also fetch a file's manifest and download the file privately over Mix. The documentation calls the manifest "the representation of a file on the network", which carries its name, size and type. The procedure says "A private download is not advertised to the network." A status dot shows whether other nodes can reach the node. An orange dot means it "is not reachable from the network but falls back to the relay network", which can slow transfers. The documentation lists the Storage app and its module among the Basecamp apps that run natively on Windows.
The app can share files, download them by CID and delete them. Deleting a file removes its blocks, the pieces in which the file is stored, from disk. The app can also fetch a file's manifest, the record that represents the file on the network and carries its name, size and type. It can download a file privately over Mix, and a private download is not advertised to the network. A status dot shows whether other nodes can reach the node. An orange dot means it cannot be reached from the network and falls back to the relay network, which can slow transfers. The Storage app and its module are among the Basecamp apps that run natively on Windows.


Basecamp also uses Logos Storage to install its own apps. The documentation says Basecamp "ships with the storage_module module, which runs a Logos Storage node". A catalogue can publish each package on Logos Storage as well as over HTTPS. When the package is on Logos Storage and the local node is running, Basecamp downloads it from there. Otherwise it falls back to HTTPS. A setting chooses the source: Any, Logos only or HTTP only. Logos says this lets users "fetch packages from the Storage network instead of relying primarily on GitHub."
Basecamp also uses Logos Storage to install its own apps. It ships with the storage_module, which runs a Logos Storage node. A catalogue can publish each package on Logos Storage as well as over HTTPS. Basecamp downloads a package from Logos Storage when it is there and the local node is running, and otherwise falls back to HTTPS. A setting chooses the source: Any, Logos only or HTTP only. Logos presents this as a way to fetch packages from the Storage network instead of relying mainly on GitHub.


On 1 November 2026 the official module catalogue, logos-co/logos-modules-release on GitHub, listed two Logos Storage modules: the storage module and its interface. It pinned both at version 3.0.2. The documentation notes that module versions "are pinned independently" and do not necessarily match the testnet version number. Its command-line procedure for Testnet v0.3 pins the storage module at 3.0.0.
On 1 November 2026 the official module catalogue, logos-co/logos-modules-release on GitHub, listed two Logos Storage modules, the storage module and its interface, and pinned both at version 3.0.2. Module versions are pinned independently and do not necessarily match the testnet version number. The command-line procedure for Testnet v0.3 pins the storage module at 3.0.0.


== In use ==
== In use ==
Projects on the [[Tools]] page that use Logos Storage include [[Reelcut]], [[Backpack]], [[Whistleblower]], [[Forumer]] and [[Logos Autonomous Agent]].
Projects on the [[Tools]] page that use Logos Storage include [[Reelcut]], [[Backpack]], [[Whistleblower]], [[Forumer]] and [[Logos Autonomous Agent]].


In July 2026 Logos reported a community-built Basecamp module, IA Archiver, which "lets Basecamp users follow trusted LEZ archive channels and preserve Internet Archive items on Logos Storage." In an interview excerpted in LAN Issue 1, the [[Circles/Delhi|Delhi Circle]] said Logos technology could serve the coordination around a volunteer-run education initiative it supports. It named "A materials archive on Logos Storage" as one such use. See [[Issue 1/Under a Tree]].
In July 2026 Logos reported a community-built Basecamp module, IA Archiver, which lets Basecamp users follow trusted LEZ archive channels and preserve Internet Archive items on Logos Storage. In an interview excerpted in LAN Issue 1, the [[Circles/Delhi|Delhi Circle]] said Logos technology could serve the coordination around a volunteer-run education initiative it supports. One use it named was a materials archive on Logos Storage. See [[Issue 1/Under a Tree]].


== Names ==
== Names ==
The Logos documentation glossary defines Codex as "A preceding protocol that informed the development of Logos Storage." Its list of repositories says the storage node was "formerly nim-codex". The ''Logos Field Guide'' (2026), a guide for anyone publishing or building under Logos, says "Logos Storage was formerly known as Codex." It asks for current module names in public-facing work. It keeps the name Codex for repo names, older documents, technical history and migration context.
The Logos documentation glossary describes Codex as a preceding protocol that informed the development of Logos Storage. Its list of repositories gives the storage node's former name as nim-codex. The ''Logos Field Guide'' (2026), a guide for anyone publishing or building under Logos, puts it differently: Logos Storage was formerly known as Codex. The guide asks for current module names in public-facing work and keeps the name Codex for repo names, older documents, technical history and migration context.


== See also ==
== See also ==
Line 65: Line 65:
* [https://logos.co/media/article/movement-recap-testnet Building the Parallel Beside Logos Testnet v0.1], Logos, 17 July 2026
* [https://logos.co/media/article/movement-recap-testnet Building the Parallel Beside Logos Testnet v0.1], Logos, 17 July 2026
* LAN, Issue 1, Logos, September 2026
* LAN, Issue 1, Logos, September 2026
* Building a Parallel Society, Logos activist course, 2026
* Logos Circles training material, 2026
* Logos Field Guide, Logos, 2026
* Logos Field Guide, Logos, 2026


{{Page status|Outline}}
{{Page status|Outline}}
[[Category:Logos]]
[[Category:Logos]]

Latest revision as of 23:55, 4 November 2026

Logos Storage is the file-sharing module of the Logos technology stack, built for privacy-preserving file sharing and retrieval using content-addressed (CID-based) data. Its predecessor was Codex. With Logos Blockchain and Logos Messaging it makes up the initial Logos stack, which people run on their own machines through Basecamp. As of November 2026 it is in testing on the Logos Testnet.

What it does

Logos Storage is a file-sharing protocol that lets people building on the Logos stack publish and share files in a decentralised way. Each node keeps its files locally. Each file gets a unique content identifier, or CID, and anyone with the CID can download the file from the network.

Logos plans for the module to support decentralised file storage in future. The node software is still pre-alpha.

Logos describes three uses, which it calls the press, the archive and distribution. The press lets a group publish without needing anyone's permission to keep the work available. The archive holds agreements, decisions and proof that outlive an order to delete them. Distribution means anyone can serve a copy and any copy can be checked against its address. In its account, the module removes "the seized press" and "the cloud account someone else can empty."

How it works

A user uploads a file to their own Logos Storage node, which stores it and produces a CID that works much like a file share link. The user passes the CID on by some other channel, such as Logos Messaging. When another user's node downloads the file, it stores its own copy and makes that copy available to others.

This organic replication means each download adds a copy, so a file that many people want has many copies. Storage networks such as Swarm or Sia work differently, paying providers to keep content available. The approach has a limit. If no one else is interested in a file, losing the only node that holds it is likely to mean losing the file.

A node joins a Storage network through a bootstrap peer, a node that is already part of that network. Logos ships public bootstrap peers for two networks, logos.test and logos.dev. A node started with no bootstrap peer becomes the first member of a new network, which other nodes can then join through it. The documentation calls public bootstrap peers a convenience more than a necessity.

For privacy, Logos Storage uses a mix network called Mix, which makes it harder for observers to work out who is downloading a file. When fully mature it is meant to protect both providers and downloaders. As of storage v3.0.0 only downloading nodes benefit, and nodes providing content must remain public and identifiable.

The node software, logos-storage-nim, lives in the logos-storage organisation on GitHub. Logos Storage is provided as a Logos module and needs the Logos runtime to work.

In Basecamp

The storage module ships with Basecamp, and files move directly between peers. The Basecamp procedure, written for Testnet v0.3, installs the Storage app from the Package Manager. The app brings in the storage_module as a dependency, and an onboarding wizard then sets up the node in guided or advanced mode.

The app can share files, download them by CID and delete them. Deleting a file removes its blocks, the pieces in which the file is stored, from disk. The app can also fetch a file's manifest, the record that represents the file on the network and carries its name, size and type. It can download a file privately over Mix, and a private download is not advertised to the network. A status dot shows whether other nodes can reach the node. An orange dot means it cannot be reached from the network and falls back to the relay network, which can slow transfers. The Storage app and its module are among the Basecamp apps that run natively on Windows.

Basecamp also uses Logos Storage to install its own apps. It ships with the storage_module, which runs a Logos Storage node. A catalogue can publish each package on Logos Storage as well as over HTTPS. Basecamp downloads a package from Logos Storage when it is there and the local node is running, and otherwise falls back to HTTPS. A setting chooses the source: Any, Logos only or HTTP only. Logos presents this as a way to fetch packages from the Storage network instead of relying mainly on GitHub.

On 1 November 2026 the official module catalogue, logos-co/logos-modules-release on GitHub, listed two Logos Storage modules, the storage module and its interface, and pinned both at version 3.0.2. Module versions are pinned independently and do not necessarily match the testnet version number. The command-line procedure for Testnet v0.3 pins the storage module at 3.0.0.

In use

Projects on the Tools page that use Logos Storage include Reelcut, Backpack, Whistleblower, Forumer and Logos Autonomous Agent.

In July 2026 Logos reported a community-built Basecamp module, IA Archiver, which lets Basecamp users follow trusted LEZ archive channels and preserve Internet Archive items on Logos Storage. In an interview excerpted in LAN Issue 1, the Delhi Circle said Logos technology could serve the coordination around a volunteer-run education initiative it supports. One use it named was a materials archive on Logos Storage. See Issue 1/Under a Tree.

Names

The Logos documentation glossary describes Codex as a preceding protocol that informed the development of Logos Storage. Its list of repositories gives the storage node's former name as nim-codex. The Logos Field Guide (2026), a guide for anyone publishing or building under Logos, puts it differently: Logos Storage was formerly known as Codex. The guide asks for current module names in public-facing work and keeps the name Codex for repo names, older documents, technical history and migration context.

See also

Sources

Page status: Outline. Stub · Outline · Usable · Guide · Star. Anyone can improve this page and change its status.
Retrieved from "https://alienware-1.tailb5c716.ts.net/index.php?title=Logos_Storage&oldid=887"