block DB interface

[wen-coding]

Summary

Interface only — no implementation, no consumer rewiring yet.

The data.Store interface captures what data.State needs from a durable backing store to replace the current DataWAL (separate file WALs for blocks and FullCommitQCs). Adds a by-hash block index that the WAL didn't have — needed for the /block_by_hash RPC path.

Surface

type Store interface {
    // Writes — synchronous on durability
    WriteBlock(ctx, n GlobalBlockNumber, *types.Block) error
    WriteQC(ctx, *types.FullCommitQC) error           // QC carries its GlobalRange
    PruneBefore(ctx, n GlobalBlockNumber) error

    // Reads
    ReadAll(ctx) (*Loaded, error)                     // startup replay
    ReadBlockByNumber(ctx, n)    (utils.Option[*types.Block], error)
    ReadBlockByHash(ctx, hash)   (utils.Option[*types.Block], error)
    ReadQCByBlockNumber(ctx, n)  (utils.Option[*types.FullCommitQC], error)  // QC covering block n

    // Lifecycle
    Close(ctx) error
}

Contract highlights (full docs in the file)

• Concurrency: all methods safe for concurrent use.
• Crash safety: Writes are synchronous on durability — a Write returns only after the record is on disk. Cross-write atomicity is the caller's problem (the consumer handles reconcile in the style of DataWAL.reconcile).
• What Store does NOT persist: AppHashes (recovered from app.Info().LastBlockAppHash + re-execution; data.State.inner.appProposals is in-memory only), and per-tx execution results / logs / events (those live on the receipt store per the Giga Transaction Query proposal). GlobalBlock.FinalAppState is extracted from qc.Proposal().App() — derivable from the persisted QC, no separate AppHash record needed.
• GlobalRange convention: half-open interval [GlobalRange.First(), GlobalRange.Next()). The QC covers GlobalBlockNumbers First, First+1, …, Next-1, and Next is the First of the next contiguous QC.
• QC contiguity: caller (data.State.runPersist) guarantees each QC's First equals the previous one's Next; implementations may but need not enforce.
• Idempotency: duplicate writes (same n + same hash for blocks, same GlobalRange.First for QCs) are silent no-ops.
• n on WriteBlock: required because *types.Block does NOT carry its GlobalBlockNumber — block.Header().BlockNumber() is the per-lane number (different typedef). The lane→global mapping lives in the QC's GlobalRange.
• No separate hash arg on WriteBlock: derivable via block.Header().Hash(); implementation indexes it automatically.
• Reads return utils.Option: "not yet written" / "pruned" surface as utils.None. Reads are non-blocking; wait semantics live above the interface in data.State.

What's not in this PR

• No implementation. mem implementation, persistent implementation, all follow-ups.
• No consumer rewiring. data.State.NewState / runPersist / runPruning still talk to DataWAL; that swap happens once an implementation exists.

Test plan

• go build ./sei-tendermint/internal/autobahn/data/... — clean
• gofmt -s -l — clean
• go vet — clean
• No tests intentionally — interface only, nothing to exercise yet.

🤖 Generated with Claude Code

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	May 15, 2026, 9:38 PM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.29%. Comparing base (823a78d) to head (ccc3121).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3445   +/-   ##
=======================================
  Coverage   59.29%   59.29%           
=======================================
  Files        2125     2125           
  Lines      175629   175629           
=======================================
+ Hits       104144   104145    +1     
+ Misses      62404    62403    -1     
  Partials     9081     9081           

Flag	Coverage Δ
sei-chain-pr	75.54% <ø> (?)
sei-db	70.62% <ø> (+0.21%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.