DAC for OP Stack (similar to Arbitrum's Anytrust)DA client able to:1 Post a batch. This method returns what we call a batch reference. A batch reference contains enough information to retrieve the original payload. It's also serializable to an L1 transaction.- In the basic rollup mode this is a no-op. The reference is the payload itself.- In the DAC mode it will upload the payload to the DAC and return all the information required 2- to verify signatures and fetch the payload later.2 Retrieve a batch. From a serialized batch reference, it returns the associated payload.- In the basic rollup mode it means returning the reference itself, because the reference is the payload.- In the DAC mode, it means deserialize the batch reference and query the DAC to get the payload back.
Improve the OP Stack by giving it access to a flexible DAC. Our contribution largely overclock Optimism Bedrock: in our benchmark, the DAC allow to spend 115 Bn Gas on an OPL2 for ~$300. It opens the OP design space to many usecases, notably on key choices like:Where is the history of what happened on the L2 stored? Several cost saving solutions (Swarm?) alternative to the Mainnet.How available is this data? Can I get a sample? Yes, forever (potentially and always).How does the cost of storing this data impact the costs of the L2? It’s minimal.What happens if the whole L2 goes offline but the DAC stays on? It’s as good as Optimism.
.svg){kind=small}
