Repository navigation

Issues

New issue

Release 0.6.3
#4981 · github-actions opened on Sep 21, 2026
81
Release 0.7.0
#5179 · github-actions opened on Oct 12, 2026
42
Release 0.7.1
#5509 · github-actions opened on Nov 6, 2026
4

RUSTSEC-2026-0459: libsqlite3-sys via C SQLite CVE-2026-119375
EspressoSystems/espresso-network#5541 · opened on Nov 10, 2026
Decide whether we still need the DA committee
EspressoSystems/espresso-network#5529 · opened on Nov 9, 2026
Remove StrictMembership, the test-only Membership implementation
EspressoSystems/espresso-network#5528 · opened on Nov 9, 2026
Set up alerts for light client metrics on query nodes
EspressoSystems/espresso-network#5513 · opened on Nov 9, 2026
1
Release 0.7.1
EspressoSystems/espresso-network#5509 · opened on Nov 6, 2026
4
Missing data: ensure data is fetch proactively
EspressoSystems/espresso-network#5508 · opened on Nov 6, 2026
Fresh pruned node serves no reward balances until L1 finalizes past its state start
EspressoSystems/espresso-network#5506 · opened on Nov 6, 2026
RUSTSEC-2026-0441: pin-utils is unmaintained
EspressoSystems/espresso-network#5505 · opened on Nov 6, 2026
Lean specification for stake table
EspressoSystems/espresso-network#5501 · opened on Nov 5, 2026
Retry and failure policy: data sources, retry classes, what may fail
EspressoSystems/espresso-network#5485 · opened on Nov 4, 2026
Open: identify a component, create spec and refactor
EspressoSystems/espresso-network#5472 · opened on Nov 3, 2026
State transition: pure core for espresso-node
EspressoSystems/espresso-network#5471 · opened on Nov 3, 2026
Agent review: check architecture cohesion, not only correctness
EspressoSystems/espresso-network#5470 · opened on Nov 3, 2026
Input boundary: one trait for data from outside the node
EspressoSystems/espresso-network#5469 · opened on Nov 3, 2026
Process: spec deltas with changes, checked requirement ids
EspressoSystems/espresso-network#5468 · opened on Nov 3, 2026
Names: term map for overloaded and duplicated names
EspressoSystems/espresso-network#5467 · opened on Nov 3, 2026
Persistence: one contract for all backends and table ownership
EspressoSystems/espresso-network#5466 · opened on Nov 3, 2026
Event delivery and task lifecycle
EspressoSystems/espresso-network#5465 · opened on Nov 3, 2026
L1 dependency: one failure policy
EspressoSystems/espresso-network#5464 · opened on Nov 3, 2026
Startup and restart: one init path and a list of required state
EspressoSystems/espresso-network#5463 · opened on Nov 3, 2026
Epoch membership: one owner for epoch arithmetic and held epochs
EspressoSystems/espresso-network#5462 · opened on Nov 3, 2026
Catchup: define what it fetches, from whom, and when it is done
EspressoSystems/espresso-network#5461 · opened on Nov 3, 2026
Retention and pruning: define who may delete what
EspressoSystems/espresso-network#5460 · opened on Nov 3, 2026
A transaction in an abandoned block is dropped by dedup until it expires
EspressoSystems/espresso-network#5435 · opened on Oct 30, 2026
Streams from below the pruned height wait forever instead of failing
EspressoSystems/espresso-network#5430 · opened on Oct 29, 2026

Navigation Menu

Repository navigation

Issues

Issues

RUSTSEC-2026-0459: `libsqlite3-sys` via C SQLite CVE-2026-119375

Decide whether we still need the DA committee

Remove StrictMembership, the test-only Membership implementation

Set up alerts for light client metrics on query nodes

Release 0.7.1

Missing data: ensure data is fetch proactively

Fresh pruned node serves no reward balances until L1 finalizes past its state start

RUSTSEC-2026-0441: `pin-utils` is unmaintained

Lean specification for stake table

Retry and failure policy: data sources, retry classes, what may fail

Open: identify a component, create spec and refactor

State transition: pure core for espresso-node

Agent review: check architecture cohesion, not only correctness

Input boundary: one trait for data from outside the node

Process: spec deltas with changes, checked requirement ids

Names: term map for overloaded and duplicated names

Persistence: one contract for all backends and table ownership

Event delivery and task lifecycle

L1 dependency: one failure policy

Startup and restart: one init path and a list of required state

Epoch membership: one owner for epoch arithmetic and held epochs

Catchup: define what it fetches, from whom, and when it is done

Retention and pruning: define who may delete what

A transaction in an abandoned block is dropped by dedup until it expires

Streams from below the pruned height wait forever instead of failing