Skip to content

Conversation

@pmikolajczyk41
Copy link
Member

@pmikolajczyk41 pmikolajczyk41 commented Nov 3, 2025

companion PR: OffchainLabs/nitro#3947
part of NIT-3121

@cla-bot cla-bot bot added the s CLA signed label Nov 3, 2025
@pmikolajczyk41 pmikolajczyk41 changed the title [NIT-3121] Extend ArbitrumChainParams with uncompressed batch size arbitrum: [NIT-3121] Extend ArbitrumChainParams with uncompressed batch size Nov 3, 2025
@joshuacolvin0 joshuacolvin0 changed the title arbitrum: [NIT-3121] Extend ArbitrumChainParams with uncompressed batch size arbitrum: Extend ArbitrumChainParams with uncompressed batch size Nov 7, 2025
GenesisBlockNum uint64
MaxCodeSize uint64 `json:"MaxCodeSize,omitempty"` // Maximum bytecode to permit for a contract. 0 value implies params.DefaultMaxCodeSize
MaxInitCodeSize uint64 `json:"MaxInitCodeSize,omitempty"` // Maximum initcode to permit in a creation transaction and create instructions. 0 value implies params.DefaultMaxInitCodeSize
MaxUncompressedBatchSize uint64 `json:"MaxUncompressedBatchSize,omitempty"`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chains that don't have MaxUncompressedBatchSize set already will initialize it to zero which causes a backwards incompatibility issue. I'd suggest accessing MaxUncompressedBatchSize through a ChainConfig accessor method like we have below and setting a default there to the original value if MaxUncompressedBatchSize == 0. I think it means you'll need to pass around a ChainConfig instead of an ArbitrumChainParams object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

s CLA signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants