Applied research for public good protocols, focusing on cryptography, privacy, and communication. Research for @Logos_network | @Logos_devs.
in a series of tubes
Joined July 2019
- Tweets617
- Following51
- Followers3.6K
- Likes2.2K
Logos Research retweeted
Era support has merged into the Logos Blockchain node. An era schedule maps an epoch to a versioned ruleset, and every node service, from the time service to Blend, now follows it.
This lays the groundwork for hard forks. A rule change can take effect at a scheduled epoch, and services keep the old era running through a transition window before retiring it. ↓
Logos Research retweeted
Run a full Logos node on Testnet v0.3.
One logosctl session runs blockchain, storage and delivery.
The guide covers install, mining to fund your node, optional Blend Network, and health checks.
Run what you depend on.
docs.logos.co/run-a-node
Logos Research retweeted
Protect anonymity (libp2p-mix)
Prevent spam (RLN)
At the same time!
Logos contributors have proposed a combined architecture for the Logos Mix and Logos Delivery modules. Mix would act as the entry and exit node for Delivery traffic, and it would become simpler in the process.
The Mixnet already routes messages over three hops with an RLN rate limit at each one. This proposal covers how Delivery hands messages into the Mixnet and takes them back out.
Next up is designing a peer and connection management interface both modules share.[POST]
Logos contributors have proposed a combined architecture for the Logos Mix and Logos Delivery modules. Mix would act as the entry and exit node for Delivery traffic, and it would become simpler in the process.
The Mixnet already routes messages over three hops with an RLN rate limit at each one. This proposal covers how Delivery hands messages into the Mixnet and takes them back out.
Next up is designing a peer and connection management interface both modules share.
Logos Research retweeted
A combined Mix and Delivery module architecture has been proposed, with the Logos Mix module acting as entry and exit node for Logos Delivery.
Delivery is the p2p transport inside Logos Messaging, and the Mixnet gives its senders anonymity. The proposal simplifies how the two connect. A shared peer and connection management interface comes next. ↓
Logos Research retweeted
Mix key rotation for forward secrecy now has a spec PR and a first implementation PR, which adds the key ring and candidate-key processing to the mix library.
Rotating mix node keys means a key compromised later can't decrypt packets captured before the rotation. It hardens the Mixnet, the anonymity layer under Logos Messaging and Logos Storage downloads. ↓
Logos Research retweeted
Logos Execution Zone v0.3.2 is out. It adds the Zone SDK's inscription re-funding fix, which addresses previous disruptions seen on testnet.
LEZ posts its state to Logos Blockchain as inscriptions on a channel. When a pending inscription goes stale, the sequencer can now re-fund it, so Zone state keeps landing on chain. ↓
Logos Research retweeted
Request for feedback: the Logos Oracle Network spec now has a dispute mechanism. A proposer pushes the median of observations finalised on Logos Blockchain to LEZ, and other nodes get a window to challenge it.
LON is a permissionless price oracle for LEZ with no closed operator set. Fees, rewards, and slashing are still open. Join the discussion on the forum. ↓
Logos Research retweeted
Request for feedback: new research draft on trust-minimised interopability between Logos Blockchain zones.
A staked committee attests to facts from a source zone, a dispute window opens, and dishonest proposers get slashed. ↓
Two Mantle RFCs are in review: a private UTXO ledger for Logos Blockchain, and programs that govern channel notes.
Today every Mantle note shows its value and owner. Under RFC-480 a spend publishes only nullifiers and new commitments, with a ZK-proof that the inputs exist, are owned, and balance. RFC-481 lets Zones hold shared funds under rules the ledger enforces.
RFC-480 makes every note private, including leader rewards. Each block pays its leader a note under a one-time key, which retires the voucher scheme. The transfer circuit is measured to prove at about 1.7s on one thread, and 0.24s on 32 threads. Shared pools are left to RFC-481.
github.com/logos-co/logos-li…
![[RFC] Mantle: Private UTXO ledger by thomaslavaur · Pull Request #480 · logos-co/logos-lips](https://pbs.twimg.com/card_img/2118570597320142849/JsQVw-8g?format=jpg&name=800x419)
RFC-481 builds on this change. A program is a Groth16 circuit registered on chain, and only its proof can move the notes it governs, so a Zone can hold AMM reserves or lending funds that no single key controls. Program notes and payments to them are public. Open for review on GitHub.
github.com/logos-co/logos-li…
![[RFC] Mantle: Programs governing channel notes by thomaslavaur · Pull Request #481 · logos-co/log...](https://pbs.twimg.com/card_img/2118570702458826752/8ub0TJHr?format=jpg&name=800x419)
Logos contributors have proposed a combined architecture for the Logos Mix and Logos Delivery modules. Mix would act as the entry and exit node for Delivery traffic, and it would become simpler in the process.
The Mixnet already routes messages over three hops with an RLN rate limit at each one. This proposal covers how Delivery hands messages into the Mixnet and takes them back out.
Next up is designing a peer and connection management interface both modules share.[POST]
Logos contributors have proposed a combined architecture for the Logos Mix and Logos Delivery modules. Mix would act as the entry and exit node for Delivery traffic, and it would become simpler in the process.
The Mixnet already routes messages over three hops with an RLN rate limit at each one. This proposal covers how Delivery hands messages into the Mixnet and takes them back out.
Next up is designing a peer and connection management interface both modules share.
The proposal and its discussion are in this GitHub issue. Comments welcome: github.com/logos-co/logos-de…
Logos Research retweeted
The release notes include the node quick-start. Also in 0.3.4: service startup timeouts are removed and Zone SDK fixes are backported.
github.com/logos-blockchain/…
Logos Research retweeted
Logos Blockchain module 0.3.4 is now live. Nodes on 0.3.2 will get automatic config upgrades, Blend connection maintenance gets fixes, and a batch of bug fixes ships with it.
Blend hides who proposed a block by relaying the proposal through other nodes, so the connections between those nodes have to stay healthy for proposer privacy to hold. ↓
If most observers in a permissionless oracle push a wrong value, no other layer can stop it. The Logos Oracle Network is being designed to solve that problem.
The latest spec proposes a dispute flow. Price observations finalise on Logos Blockchain, a sampled proposer posts the median to LEZ, and other nodes get a window to challenge it. Successful challengers would be rewarded.
The dispute window makes LON slow by design, so sub-second uses like perp DEXs are out of scope. Fees and slashing are undefined, and TWAP bounds, reputation scoring, and stake sizing are still ideas under discussion.
If you work on oracle security or mechanism design, read the post and reply with your views.
The forum post covers the tech, the honest-majority assumption, and the economic and social security ideas still in play. Discuss here: forum.research.logos.co/t/lo…
For information on the protocol, the spec PR outlines the dispute mechanism and the end-to-end flow:
github.com/logos-co/logos-li…
