Hey @th0rgal , great writeup. The properties you asked for in the zk verified approach (each validator included once, assigned to the correct module, matched to consensus-layer state) are the statement we’ve been building. We just posted a working proof of it, verified on mainnet: Proposal: Exact validator-set accounting for the Lido second-opinion oracle . The module-reallocation concern you raise is why per-module totals are on the roadmap of the grant proposal as Milestone 3: the attribution is already proven, and exposing the sums is the easy part. Would value your read on the construction, the counter-closure and the four-bucket join especially.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Proposal: Second Opinion ZK Oracle | 8 | 335 | May 10, 2026 | |
| LIP-23: Negative rebase sanity check with second opinion | 5 | 1188 | October 16, 2024 | |
| Proposal to fund the SP1 ZK Oracle in Ethereum | 5 | 142 | December 17, 2025 | |
|
[Security Disclosure] 25/7/2026 Minor Underreporting of Total Protocol CL-side balances in Accounting Oracle Report
|
2 | 572 | August 6, 2026 | |
| LIP-25: Staking Router v2.0 | 3 | 832 | October 8, 2024 |