Skip to content

Conversation

@Bashmunta
Copy link
Contributor

Replaced the single 512 capacity with per-operation consensus maxima from cltypes, so each pool size reflects “max per block × operations_multiplier” as intended. This also resolves the root cause for the unused beaconCfg parameter without changing the public API and keeps room for future per-network tuning

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant