You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P2] Verify header blob for blocks with transactions too #47
Priority: P2 (feature / coverage) · Effort: S (after the DA cache issue)
Problem
pkg/exporters/verifier/verifier.go:223-226: blocks with transactions only verify the data namespace. Their header blobs are never checked, so header-namespace submission failures on those blocks go unnoticed.
Proposed fix
For blocks with transactions, verify both header and data, and record each outcome under its own type label.
Pros / Cons
✅ Full coverage of what the tool claims to verify.
⚠️ About 2× Celestia calls; do this after the DA-height cache issue, which makes it nearly free. submission_*{type="header"} counts will jump, so mention it in the release notes.
Unblocked: #40 (the Celestia per-DA-height cache) shipped in #58. Note that the header path uses Blob.Get by commitment, which differs per block and is not cached. Verifying headers for tx blocks therefore costs one extra Celestia RPC per tx block, plus one ev-node call already done today. The DA timestamp lookup is cached.
Activity
auricom commentedon Oct 20, 2026
Unblocked: #40 (the Celestia per-DA-height cache) shipped in #58. Note that the header path uses
Blob.Getby commitment, which differs per block and is not cached. Verifying headers for tx blocks therefore costs one extra Celestia RPC per tx block, plus one ev-node call already done today. The DA timestamp lookup is cached.