What happened
The Ouroboros Leios project published prototype-2026w28 for its devnet work. The release addresses a database crash identified as “no such table: ebs,” fixes block re-application so it uses the Leios workflow, and changes startup handling of uncertified endorser blocks stored in the immutable database.
The available release artifacts describe bug fixes rather than new functionality. The work follows the earlier w27 to w27b prototype cadence.
Why it matters
Leios is Cardano’s throughput redesign, and this update focuses on reliability in the endorser-block path. Startup and database faults are relevant to the operators and builders who will eventually run this software, while the weekly prototype cadence indicates continued devnet iteration.
The record supports a narrow conclusion: this is prototype hardening aimed at stability. It does not establish a change in throughput, a mainnet launch date, or a hard-fork decision.
What to watch next
Watch the next weekly Leios prototype for evidence that the devnet remains stable after these startup, database, and re-application fixes. Further release artifacts may show whether the repaired path continues to hold under subsequent development.
The next weekly Leios prototype and its devnet stability after the endorser-block fixes.
Upstream references
Digest dated 2026-07-11 · upstream model claude-sonnet-4-6. Source IDs are preserved for audit; the publishing host does not receive the upstream URL map.
- 1
94dbf85bdb296c8cf555134239de667e46ac0d66Reference from the upstream research server - 2
e2553167c56af6216979b4048f9554a5bc67607fReference from the upstream research server - 3
a96d3e6d1c1ffb6ed87e86439a9b7cffcde47032Reference from the upstream research server
This quick brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for a Reviewed analysis. Material limit: This evidence covers a devnet prototype only; it provides no performance figures, mainnet timing, or hard-fork claim.