LEZ is changing its programming model so private transactions can share public state.
0.3 is the experimental first version. 0.4 is the target, and anything built on 0.2 or 0.3 will need porting. All open λPrizes now target 0.4.
Read before you build. https://t.co/GOU4ESLore
The @Logos_network Blockchain node package for Dappnode has been bumped to 0.3.1 to match the current testnet.
Install: http://my.dappnode/installer/public/logos-blockchain-node.public.dappnode.eth
⚠️This is an unofficial release. To try it, make sure to check "Bypass signed safe restriction".
LEZ is changing its programming model so private transactions can share public state.
0.3 is the experimental first version. 0.4 is the target, and anything built on 0.2 or 0.3 will need porting. All open λPrizes now target 0.4.
Read before you build. https://t.co/GOU4ESLore
The testnet is going live: install the new blockchain module!
The chain starts at 4:30 PM CEST today. Install blockchain_module 0.3.1 now. Your node will sit idle until chain start, then begin producing blocks automatically.
Genesis bootstrap nodes: use your existing keystore
This assumes your keystore.yaml is at <dir>/keystore.yaml:
sh
logosctl call blockchain_module stop
logosctl package install blockchain_module --version 0.3.1 --yes
logosctl module load blockchain_module
mv <dir>/user_config.yaml <dir>/user_config-0.3.0.yaml
logosctl call blockchain_module migrate_user_config <dir>/user_config-0.3.0.yaml <dir>/keystore.yaml
This writes a 0.3.1-compatible config from your existing keystore, so your stake key stays the same.
Then delete the state and db directories next to the config (they hold old chain data that can’t be reused on the new genesis), and start:
sh
logosctl call blockchain_module start <dir>/user_config.yaml ""
Join the Logos 0.3.0 genesis as a bootstrap node.
You need a node identity on the machine that will run the node, and one public key to post here.
1. Generate your config and keystore
(module installed and daemon running)
```
logosctl module load blockchain_module
logosctl call blockchain_module generate_user_config '{"output": "user_config.yaml", "use_persistence_paths": true}'
```
The result prints the absolute path of your user_config.yaml. Your keystore.yaml is in the same directory.
2. Reply with your stake key
```
grep -A 8 'public_keys' <dir>/keystore.yaml | grep Stake
```
3. Back up keystore.yaml.
Your genesis stake is assigned to this key and the module will not generate a second keystore in the same place. Lose the file, lose the stake.
LEZ private accounts exist onchain only as commitments and nullifiers.
Atomic swaps on LEZ execute both legs or neither, no party holds the other's value mid-trade.
Cryptarchia's leader lottery runs locally and winners prove eligibility with a Groth16 Proof of Leadership. No one can identify the next proposer ahead of time.
Blend onion-routes block proposals through cover traffic and random per-hop delays to cut the link to the proposing node.
Negotiation can run over the Mixnet, which carries Sphinx packets across 3 hops so observers can't tell who is talking to whom.
Transactions face two kinds of hazards:
𖤓 Insiders who may exploit privileged access
𖤓 Outsiders who can act when sensitive information leaks
PriFi takes aim at both.
To lower risk and cost, and make onchain finance more viable for more participants.
https://t.co/mesZ5kyR3d
Blend's connection monitoring has been rebuilt.
A new monitoring layer implements connection-level rate-limiting with observation windows that persist across reconnects.
The Blend Network adds a layer of anonymity for block proposers on top of Cryptarchia, the Logos Private Proof of Stake consensus protocol.
https://t.co/kHpT1KwCQQ
What happened
- Week one: ~1,700 node IDs joined. Of 484 reachable nodes, 84% ran on one hosting network (HostRush, Dallas and Jamestown NY). Only 12 to 14 nodes ran the Blend Network, which carries every block and transaction.
- Oct 2-5: PoW mining claims and traffic overloaded Blend. One bootstrap node lost 21-39% of its Blend deliveries, and an orphan storm hit on Oct 4-5. By Oct 6-7, mempools held ~2k-25k transactions.
- Oct 6, morning: forks deepened fast. Reorgs went from 3 to 73 to 114 blocks, against a finality depth of 120.
- Oct 6, 11:00 UTC: bootstrap node 2 forked off onto branch B and finalised it. Node 2 was wiped and resynced at ~14:25, and branch B stopped producing blocks. By then, 37 nodes (35 on HostRush) had finalised branch B and couldn't switch back.
- Epoch 16 estimate: Cryptarchia keeps individual stake private, so total stake is estimated from block production in a set window. Branch B produced 0 blocks in the window for epoch 16, so its estimate dropped to the floor of 1.
- Oct 7, 01:00: epoch 16 began and branch B's nodes won almost every slot, producing ~900 and then 2,700 blocks/h against ~120/h on a healthy chain.
- Those blocks flooded gossip at ~1,000 blocks/s. Orphan queues filled, responding nodes fell from 478 to 89, the network split across up to 185 tips, and the main chain slowed to ~12 blocks/h.
What changes with the restart
1. Longer finality. Testnet v0.3.0 used a finality depth of 120 blocks to move through more epochs faster and exercise more of the protocol, even though analysis and simulations pointed to 2,000+. Finality time is going up.
2. Safer PoW defaults. Mining used every available CPU and never stopped, which cut node capacity and made congestion worse. The new default is 1 mining thread, and your node stops mining automatically once it reaches a balance threshold.
3. Shorter mempool TTL. Mempools ballooned to ~30k transactions, mostly expired PoW claims that would never land on-chain but kept loading the network. The default TTL drops to 1 hour, and clients resubmit if needed.
4. A larger Blend Network. A bigger bootstrap set of Blend nodes will carry traffic from the whole network, and more operators will get support to join Blend so it stays decentralised with no single point of failure.
Testnets exists to find these limits before mainnet. Thank you to every node operator who ran a node and sent detailed reports. Many of those reports helped piece this together.
Between Oct 2 and Oct 7, the Logos Blockchain network split into as many as 185 competing chain tips. With this many forks asking every operator to re-sync isn't reasonable, so the blockchain network will restart with a new module tomorrow (Oct 8) with the mitigations below.
Only the blockchain component restarts, not the Logos testnet. Logos Storage and Logos Delivery stay online.
The λPrize winner buried in here: an AI agent with its own private wallet on Logos
Spends within owner-set limits autonomously. Asks permission over encrypted chat when it needs more.
Private infra + AI agents is an underexplored design space. Most agent wallets are fully transparent onchain 📖
The Logos Dev Update for September 2026 is out.
This month saw Testnet v0.3 go live, delivering proof-of-work participation, decentralised sequencing, downloads over Mix, and bringing Monero and Ethereum wallets to Basecamp.
Read the full update: https://t.co/1pJZui6SvU