Logos Blockchain: Difference between revisions

From Local Area Network
New article from the Building a Parallel Society course, source-checked
 
Second check fixes, plus material from the Circles handbook, Circle reports, LAN and Logos docs, source-checked
Line 4: Line 4:
The Logos documentation calls the blockchain "the foundational infrastructure of the Logos technology stack". It gives Logos applications a common context for interaction and lets them rely on the consensus guarantees of the whole network. The documentation says nodes "can participate with consumer hardware and any amount of stake."
The Logos documentation calls the blockchain "the foundational infrastructure of the Logos technology stack". It gives Logos applications a common context for interaction and lets them rely on the consensus guarantees of the whole network. The documentation says nodes "can participate with consumer hardware and any amount of stake."


The Logos website says developers can use it to "deploy programs, run AMMs, transfer tokens, and build financial primitives with built-in privacy."
The Logos website describes what developers can do on the Logos Execution Zone (LEZ), the first Zone built on the blockchain (see below). It says they can "deploy programs, run AMMs, transfer tokens, and build financial primitives with built-in privacy." AMMs, or automated market makers, are programs that let people trade tokens against a shared pool.


The Logos activist course ''Building a Parallel Society'' (2026) describes what the module enables. It says many independent machines agree on what happened and run shared rules as written, so that no one can rewrite the record afterwards. It lists uses such as "a treasury, a membership roll, a vote, an agreement that executes as agreed", and accounts that can be public or private "so a group's business is not everyone's business." The course says the module removes "the ability to exclude participation and the ability to edit the record."
The Logos activist course ''Building a Parallel Society'' (2026) describes what the module enables. It says many independent machines agree on what happened and run shared rules as written, so that no one can rewrite the record afterwards. It lists uses such as "a treasury, a membership roll, a vote, an agreement that executes as agreed", and accounts that can be public or private "so a group's business is not everyone's business." The course says the module removes "the ability to exclude participation and the ability to edit the record."
The documentation describes two building blocks for shared records of this kind.
* '''Logos SQL''' is a library that gives each participant a local SQLite database and shares the history of writes through the blockchain. The documentation says it suits "participants who need shared data without relying on one organisation to host the database for everyone."
* '''Shared private accounts''' on the LEZ let every member of a group derive the same keys from one group master secret (GMS). The documentation warns that "any GMS holder can derive every key and spend the account." A rule that needs several members to approve has to be written into the program.


== How it works ==
== How it works ==
The documentation describes two layers.
The documentation describes two layers.
* '''Bedrock''' is the base layer. It is "a large-scale validator network" that provides consensus, data availability and lightweight verification. Its consensus protocol, Cryptarchia, is a form of Private Proof of Stake. The Logos website says this is a mechanism "where validator identities and stake amounts remain hidden."
* '''Bedrock''' is the base layer. It is "a large-scale validator network" that provides consensus, data availability and lightweight verification. Consensus is the process by which nodes agree on one record. Data availability means that the data behind each block can be fetched by anyone who needs to check it. Bedrock's consensus protocol, Cryptarchia, is a form of Private Proof of Stake, in which nodes take part in proportion to the tokens they hold. The Logos website says this is a mechanism "where validator identities and stake amounts remain hidden."
* '''Zones''' are Layer 2 blockchains that sit on Bedrock. "Applications do not run directly on Bedrock." Each Zone defines its own state transitions and relies on Bedrock for consensus. The main example is the Logos Execution Zone (LEZ), described as "the initial Zone for the messaging and storage applications of the Logos stack, with support for private token transfers and program execution."
* '''Zones''' are Layer 2 blockchains that sit on Bedrock. A Layer 2 is a chain that runs on top of another and relies on it for consensus and data availability. "Applications do not run directly on Bedrock." Each Zone sets its own rules for how its records change and relies on Bedrock for consensus. The main example is the LEZ, described as "the initial Zone for the messaging and storage applications of the Logos stack, with support for private token transfers and program execution."


A third part, the '''Blend Network''', is a service in which declared Blend nodes "provide network-level privacy for block proposers participating in consensus." The documentation says it "virtually eliminates the chance of linking a block proposer or transaction sender to their block or transaction".
A third part, the '''Blend Network''', is a service in which declared Blend nodes "provide network-level privacy for block proposers participating in consensus." Block proposers are the nodes that add new blocks to the chain. The documentation says Blend "virtually eliminates the chance of linking a block proposer or transaction sender to their block or transaction".


The node software is open source in the logos-blockchain organisation on GitHub. Its README says it "combines zero-knowledge proofs, a mix network for anonymity, and a modular service architecture". The node is "the reference implementation of the Logos Blockchain specifications".
=== Two kinds of privacy ===
The Blockchain FAQ separates the privacy of the people who run the network from the privacy of transactions. It says Bedrock "is designed primarily to protect the privacy of block proposers." If proposers could be identified, the FAQ says, "they could become targets for coercion or denial of service attacks by hostile actors." Transfers on Bedrock itself are public. The FAQ says "Notes and their transfers are recorded openly on the ledger, similar to Bitcoin". Notes are the token units of Bedrock's ledger. The FAQ leaves transaction privacy to the Zones and says it "is supported natively on the LEZ, in addition to public transactions".
 
The node software is open source in the logos-blockchain organisation on GitHub. Its README says it "combines zero-knowledge proofs, a mix network for anonymity, and a modular service architecture". A zero-knowledge proof shows that a statement is true without revealing the data behind it. A mix network passes messages through several relays that shuffle them, so that observers cannot easily tell who sent what. The node is "the reference implementation of the Logos Blockchain specifications".


The documentation notes that its overview describes the blockchain "as it will exist on mainnet", and that some features "may not be available on the current testnet."
The documentation notes that its overview describes the blockchain "as it will exist on mainnet", and that some features "may not be available on the current testnet."
Line 22: Line 29:
Basecamp includes a Blockchain app. The Logos website says it lets a user run a node and track its status, peers, rewards and mining. Basecamp also has an LEZ Wallet that holds LEZ tokens on the user's own machine.
Basecamp includes a Blockchain app. The Logos website says it lets a user run a node and track its status, peers, rewards and mining. Basecamp also has an LEZ Wallet that holds LEZ tokens on the user's own machine.


The Logos procedure for running a node from Basecamp is written for Testnet v0.3. The user opens the Applications section with Discover Applications and installs the Blockchain app from the Blockchain category, which brings in the Blockchain Module as its core module. The procedure sets both to version 0.3.2. Once installed, the node connects to testnet peers and syncs the chain, and the wallet can be funded by mining so that the node proposes blocks. Port forwarding is not required. For the testnet the procedure asks for an SSD with 1 to 2 GB free.
The Logos procedure for running a node from Basecamp is written for Testnet v0.3. The user opens the Applications section with Discover Applications and installs the Blockchain app from the Blockchain category, which brings in the Blockchain Module as its core module. The procedure sets both to version 0.3.2. The app then sets up the node through a Quick start or an Advanced wizard, which writes a configuration and creates keys. Once set up, the node connects to testnet peers and syncs the chain. Port forwarding is not required. For the testnet the procedure asks for an SSD with 1 to 2 GB free. It lists Linux, Apple Silicon Macs and Windows 11 through WSL2, the Windows subsystem for Linux, since the node has no native Windows build.
 
A node proposes blocks only once its wallet holds testnet notes. The procedure says "Notes can be obtained by engaging in PoW mining", that is, by proof-of-work computation on the user's own machine. Logos calls this mechanism EmPoWering and introduced it with Testnet v0.3. Logos says "EmPoWering adds another route in". Testnet tokens usually come from a faucet, a service the project runs that hands out free tokens. Logos says it means "nobody needs to approve a request before a new participant can hold tokens and start transacting." The procedure says new tokens can take up to 3.5 hours to count towards consensus. Each block a node leads "mints a reward voucher", which the app's Rewards tab redeems into spendable balance.


The official module catalogue, logos-co/logos-modules-release on GitHub, lists eleven modules under Logos Blockchain. They include the core node module and its interface, the Execution Zone module and wallet, and token, AMM and price oracle modules. On 1 November 2026 the catalogue pinned the core module at version 0.3.4 and the Blockchain interface at 0.3.5. The catalogue README says a new version becomes visible in Basecamp within a few minutes of being merged.
The official module catalogue, logos-co/logos-modules-release on GitHub, lists eleven modules under Logos Blockchain. They include the core node module and its interface, the Execution Zone module and wallet, and token, AMM and price oracle modules. On 1 November 2026 the catalogue pinned the core module at version 0.3.4 and the Blockchain interface at 0.3.5. The catalogue README says a new version becomes visible in Basecamp within a few minutes of being merged.


The Logos website states that "Testnet v0.3 is live." The documentation's table of testnet endpoints lists 0.3 as the current version, with a public blockchain explorer at testnet.blockchain.logos.co. A version 0.4 is listed with all endpoints still to be decided. The Blockchain interface README points users to a testnet faucet for funds.
The Logos website states that "Testnet v0.3 is live." The documentation's table of testnet endpoints lists 0.3 as the current version, with a public blockchain explorer at testnet.blockchain.logos.co. A version 0.4 is listed with all endpoints still to be decided.
 
== In use ==
The [[Tools]] page lists projects built on the LEZ: [[Medusa]], [[Evice Wallet SDK]], [[LNS]], [[LEZ Atomic Swaps]], [[Private Token Balance Attestation]], [[Private M-of-N Multisig]], [[DistributionX]], [[Forum-protocol]] and [[Logos Autonomous Agent]]. It lists three that work with the blockchain node or Bedrock: [[Logos-blockchain-ui (xAlisher)]], [[Node Remote]] and [[SoliCamp]].
 
Circles also run nodes. In July 2026 Logos reported that Circles in [[Circles/Lisbon|Lisbon]], [[Circles/Delhi|New Delhi]], Brno, [[Circles/Los Angeles|Los Angeles]], Florianópolis and [[Circles/Rome|Rome]] were running a Logos node. In April 2026 the [[Circles/Mexico City|Mexico City Circle]] reported a live workshop, held in Spanish, on installing and running a node. The [[Circles/Kampala|Kampala Circle]] reports that it is building Transparent SACCO, a ledger on the Logos Blockchain for savings and credit cooperatives, with the LEZ as one of its workstreams. Its October 2026 report says "Money stays in mobile money and bank accounts, while the chain records deposits, approvals and expenses with evidence." See [[Issue 2/Every Shilling Accounted For]].


== Names ==
== Names ==
The Logos documentation glossary defines Nomos as "An old name for the Logos Blockchain." The ''Logos Field Guide'' (2026), a guide for anyone publishing or building under Logos, says that "Logos Blockchain was previously known as Nomos." It asks for current module names in public-facing work and says Nomos, Waku and Codex are used "only when helping people map old names to current modules."
The Logos documentation glossary defines Nomos as "An old name for the Logos Blockchain." The ''Logos Field Guide'' (2026), a guide for anyone publishing or building under Logos, says that "Logos Blockchain was previously known as Nomos." It asks for current module names in public-facing work. It keeps the name Nomos for repo names, older documents, technical history and migration context.


== See also ==
== See also ==
Line 36: Line 50:
* [[Testnet]]
* [[Testnet]]
* [[Run a node]]
* [[Run a node]]
* [[Tools]]
* [[Logos Storage]]
* [[Logos Storage]]
* [[Logos Messaging]]
* [[Logos Messaging]]
Line 45: Line 60:
* [https://logos.co/basecamp Basecamp], Logos, accessed 4 November 2026
* [https://logos.co/basecamp Basecamp], Logos, accessed 4 November 2026
* [https://docs.logos.co/blockchain Introduction to the Logos Blockchain], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain Introduction to the Logos Blockchain], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain/faq Blockchain FAQ], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain/logos-sql Introduction to Logos SQL], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/lez/accounts/set-up-shared-private-lez-account Set up a shared private LEZ account], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain/get-started/run-blockchain-node-from-basecamp Run a Blockchain node from Basecamp], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain/get-started/run-blockchain-node-from-basecamp Run a Blockchain node from Basecamp], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/blockchain/get-started/claim-leader-rewards-in-basecamp Claim leader rewards in Basecamp], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/basecamp/install-logos-basecamp Install Logos Basecamp], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/get-started/testnet-endpoints Testnet endpoints], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/get-started/testnet-endpoints Testnet endpoints], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/get-started/glossary Glossary], Logos documentation, accessed 4 November 2026
* [https://docs.logos.co/get-started/glossary Glossary], Logos documentation, accessed 4 November 2026
* [https://logos.co/media/article/logos-testnet-v03-live Logos Testnet v0.3 is Now Live], Logos, 30 September 2026
* [https://logos.co/media/article/empowering EmPoWering: Joining Logos Blockchain Without an Intermediary], Logos, 20 October 2026
* [https://logos.co/media/article/movement-recap-testnet Building the Parallel Beside Logos Testnet v0.1], Logos, 17 July 2026
* [https://forum.logos.co/t/1603 Logos Circle Mexico City_April 2026], Logos Forum, 21 April 2026
* [https://forum.logos.co/t/2279 Logos Circle Kampala Report – October 2026], Logos Forum, 26 October 2026
* [https://github.com/logos-blockchain/logos-blockchain logos-blockchain README], GitHub, accessed 4 November 2026
* [https://github.com/logos-blockchain/logos-blockchain logos-blockchain README], GitHub, accessed 4 November 2026
* [https://github.com/logos-blockchain/logos-blockchain-ui logos-blockchain-ui README], GitHub, accessed 4 November 2026
* [https://github.com/logos-co/logos-modules-release logos-modules-release README], GitHub, commit of 1 November 2026
* [https://github.com/logos-co/logos-modules-release logos-modules-release README], GitHub, commit of 1 November 2026
* [https://github.com/logos-blockchain/logos-blockchain-module/blob/b1eed5994eb289d0021c15e183cd170601334603/metadata.json logos-blockchain-module metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* [https://github.com/logos-blockchain/logos-blockchain-module/blob/b1eed5994eb289d0021c15e183cd170601334603/metadata.json logos-blockchain-module metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* [https://github.com/logos-blockchain/logos-blockchain-ui/blob/df4fea7d4f351a5359321688d9bcf85155f14f10/metadata.json logos-blockchain-ui metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* [https://github.com/logos-blockchain/logos-blockchain-ui/blob/df4fea7d4f351a5359321688d9bcf85155f14f10/metadata.json logos-blockchain-ui metadata.json], GitHub, as pinned in the catalogue on 1 November 2026
* LAN, Issue 2, Logos, October 2026
* Building a Parallel Society, Logos activist course, 2026
* Building a Parallel Society, Logos activist course, 2026
* Logos Field Guide, Logos, 2026
* Logos Field Guide, Logos, 2026

Revision as of 21:10, 4 November 2026

Logos Blockchain is the blockchain module of the Logos technology stack. Logos describes it as "Privacy-preserving, decentralised computing and consensus." It was formerly called Nomos. Together with Logos Storage 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 runs on a public Testnet.

What it does

The Logos documentation calls the blockchain "the foundational infrastructure of the Logos technology stack". It gives Logos applications a common context for interaction and lets them rely on the consensus guarantees of the whole network. The documentation says nodes "can participate with consumer hardware and any amount of stake."

The Logos website describes what developers can do on the Logos Execution Zone (LEZ), the first Zone built on the blockchain (see below). It says they can "deploy programs, run AMMs, transfer tokens, and build financial primitives with built-in privacy." AMMs, or automated market makers, are programs that let people trade tokens against a shared pool.

The Logos activist course Building a Parallel Society (2026) describes what the module enables. It says many independent machines agree on what happened and run shared rules as written, so that no one can rewrite the record afterwards. It lists uses such as "a treasury, a membership roll, a vote, an agreement that executes as agreed", and accounts that can be public or private "so a group's business is not everyone's business." The course says the module removes "the ability to exclude participation and the ability to edit the record."

The documentation describes two building blocks for shared records of this kind.

  • Logos SQL is a library that gives each participant a local SQLite database and shares the history of writes through the blockchain. The documentation says it suits "participants who need shared data without relying on one organisation to host the database for everyone."
  • Shared private accounts on the LEZ let every member of a group derive the same keys from one group master secret (GMS). The documentation warns that "any GMS holder can derive every key and spend the account." A rule that needs several members to approve has to be written into the program.

How it works

The documentation describes two layers.

  • Bedrock is the base layer. It is "a large-scale validator network" that provides consensus, data availability and lightweight verification. Consensus is the process by which nodes agree on one record. Data availability means that the data behind each block can be fetched by anyone who needs to check it. Bedrock's consensus protocol, Cryptarchia, is a form of Private Proof of Stake, in which nodes take part in proportion to the tokens they hold. The Logos website says this is a mechanism "where validator identities and stake amounts remain hidden."
  • Zones are Layer 2 blockchains that sit on Bedrock. A Layer 2 is a chain that runs on top of another and relies on it for consensus and data availability. "Applications do not run directly on Bedrock." Each Zone sets its own rules for how its records change and relies on Bedrock for consensus. The main example is the LEZ, described as "the initial Zone for the messaging and storage applications of the Logos stack, with support for private token transfers and program execution."

A third part, the Blend Network, is a service in which declared Blend nodes "provide network-level privacy for block proposers participating in consensus." Block proposers are the nodes that add new blocks to the chain. The documentation says Blend "virtually eliminates the chance of linking a block proposer or transaction sender to their block or transaction".

Two kinds of privacy

The Blockchain FAQ separates the privacy of the people who run the network from the privacy of transactions. It says Bedrock "is designed primarily to protect the privacy of block proposers." If proposers could be identified, the FAQ says, "they could become targets for coercion or denial of service attacks by hostile actors." Transfers on Bedrock itself are public. The FAQ says "Notes and their transfers are recorded openly on the ledger, similar to Bitcoin". Notes are the token units of Bedrock's ledger. The FAQ leaves transaction privacy to the Zones and says it "is supported natively on the LEZ, in addition to public transactions".

The node software is open source in the logos-blockchain organisation on GitHub. Its README says it "combines zero-knowledge proofs, a mix network for anonymity, and a modular service architecture". A zero-knowledge proof shows that a statement is true without revealing the data behind it. A mix network passes messages through several relays that shuffle them, so that observers cannot easily tell who sent what. The node is "the reference implementation of the Logos Blockchain specifications".

The documentation notes that its overview describes the blockchain "as it will exist on mainnet", and that some features "may not be available on the current testnet."

In Basecamp

Basecamp includes a Blockchain app. The Logos website says it lets a user run a node and track its status, peers, rewards and mining. Basecamp also has an LEZ Wallet that holds LEZ tokens on the user's own machine.

The Logos procedure for running a node from Basecamp is written for Testnet v0.3. The user opens the Applications section with Discover Applications and installs the Blockchain app from the Blockchain category, which brings in the Blockchain Module as its core module. The procedure sets both to version 0.3.2. The app then sets up the node through a Quick start or an Advanced wizard, which writes a configuration and creates keys. Once set up, the node connects to testnet peers and syncs the chain. Port forwarding is not required. For the testnet the procedure asks for an SSD with 1 to 2 GB free. It lists Linux, Apple Silicon Macs and Windows 11 through WSL2, the Windows subsystem for Linux, since the node has no native Windows build.

A node proposes blocks only once its wallet holds testnet notes. The procedure says "Notes can be obtained by engaging in PoW mining", that is, by proof-of-work computation on the user's own machine. Logos calls this mechanism EmPoWering and introduced it with Testnet v0.3. Logos says "EmPoWering adds another route in". Testnet tokens usually come from a faucet, a service the project runs that hands out free tokens. Logos says it means "nobody needs to approve a request before a new participant can hold tokens and start transacting." The procedure says new tokens can take up to 3.5 hours to count towards consensus. Each block a node leads "mints a reward voucher", which the app's Rewards tab redeems into spendable balance.

The official module catalogue, logos-co/logos-modules-release on GitHub, lists eleven modules under Logos Blockchain. They include the core node module and its interface, the Execution Zone module and wallet, and token, AMM and price oracle modules. On 1 November 2026 the catalogue pinned the core module at version 0.3.4 and the Blockchain interface at 0.3.5. The catalogue README says a new version becomes visible in Basecamp within a few minutes of being merged.

The Logos website states that "Testnet v0.3 is live." The documentation's table of testnet endpoints lists 0.3 as the current version, with a public blockchain explorer at testnet.blockchain.logos.co. A version 0.4 is listed with all endpoints still to be decided.

In use

The Tools page lists projects built on the LEZ: Medusa, Evice Wallet SDK, LNS, LEZ Atomic Swaps, Private Token Balance Attestation, Private M-of-N Multisig, DistributionX, Forum-protocol and Logos Autonomous Agent. It lists three that work with the blockchain node or Bedrock: Logos-blockchain-ui (xAlisher), Node Remote and SoliCamp.

Circles also run nodes. In July 2026 Logos reported that Circles in Lisbon, New Delhi, Brno, Los Angeles, Florianópolis and Rome were running a Logos node. In April 2026 the Mexico City Circle reported a live workshop, held in Spanish, on installing and running a node. The Kampala Circle reports that it is building Transparent SACCO, a ledger on the Logos Blockchain for savings and credit cooperatives, with the LEZ as one of its workstreams. Its October 2026 report says "Money stays in mobile money and bank accounts, while the chain records deposits, approvals and expenses with evidence." See Issue 2/Every Shilling Accounted For.

Names

The Logos documentation glossary defines Nomos as "An old name for the Logos Blockchain." The Logos Field Guide (2026), a guide for anyone publishing or building under Logos, says that "Logos Blockchain was previously known as Nomos." It asks for current module names in public-facing work. It keeps the name Nomos 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.