Content
@
0 reply
0 recast
0 reaction
nixo
@nixo
Gas limit increase has been a big CT topic the last few weeks & was discussed on today's ACD call w a proposal to raise the gossip limit 10 -> 15 MiB to accommodate a gas limit increase 🔳 Concern over differing client behaviors & abt pushing untested changes. Forks allow better coordination & fewer issues. Can be coordinated at the fork? 🔳 The testing that ensured 6/9 blobs are safe should be redone if gas / gossip limits changed before the fork. Puts some strain on testing team bandwidth 🔳 A reason to wait for Pectra is EIP-7623, which increases calldata costs. Could reduce potential strain on the network, making a gas limit change safer 🔳 Pectra is the best place to make changes for a # of reasons but devs are not fully in control of this, so the gas limit should be watched closely 🔳 Some advocacy that if an increase needs to happen before Pectra, 36 mil would be the target as it stays below critical limits See here for good nuance: https://x.com/nero_eth/status/1867158840715993549
2 replies
3 recasts
58 reactions
Thomas
@aviationdoctor.eth
I had it set to 40M for a long time since the prior collective push to “pump the gas”, then recently boosted it to 60M, and just this week throttled it back to 36M after reading about the zero-padded blocks. I’m done changing it until at least Pectra and a formal green light from the core dev team!
0 reply
0 recast
6 reactions