From 10efb863fa4f7a3d546651eea94998452182559d Mon Sep 17 00:00:00 2001 From: Javier Cortejoso Date: Fri, 18 Oct 2024 09:40:02 +0200 Subject: [PATCH] Increase MaxInputSize to 16MB in op-alt-da On `celo10` branch I've observed in the batcher: ``` {"t":"2024-10-17T15:24:33.473665645Z","lvl":"crit","msg":"Application failed","message":"failed to setup: failed to init channel config: max frame size 999999 exceeds altDA max input size 130672"} ``` With previous `celo` versions this size limit was not enforced, and we increased the max frame size to 16MB in the derivation pipeline ([PR](https://github.com/celo-org/optimism/pull/228)). --- op-alt-da/params.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/op-alt-da/params.go b/op-alt-da/params.go index 86339200f7fc..1c16ad0c7792 100644 --- a/op-alt-da/params.go +++ b/op-alt-da/params.go @@ -2,8 +2,10 @@ package altda // MaxInputSize ensures the canonical chain cannot include input batches too large to // challenge in the Data Availability Challenge contract. Value in number of bytes. +// For EigenDA, batch size is not a limiter for Data Availability Challenge contract, +// so this is set to 16MB (current EigenDA batch size limit) // This value can only be changed in a hard fork. -const MaxInputSize = 130672 +const MaxInputSize = 16_000_000 // TxDataVersion1 is the version number for batcher transactions containing // altDA commitments. It should not collide with DerivationVersion which is still