Closed protolambda closed 9 hours ago
This is not really a blocker for the design itself, but worth noting a chore we should do: in various places in our docs, we talk about the statelessness of our components. That statelessness is much weaker already with things like the SafeDB, but this would definitely push us far enough that we'd want to amend documentation.
This is stale, a version of this called fromda
package, to store L1 <> L2 increments in a stupid-simple append-only way (single type of entry), was implemented in the op-supervisor.
Description
Proposal to enshrine the idea of a "block safety index", such that other (existing and new) features can be built against this in a unified way.
In particular, as we enter Holocene steady-batch-derivation work, and Interop devnet 2, I believe there is a need for a shared block-safety-index feature, to reduce overall protocol complexity by unifying solutions to the same problem.