By increasing max gas and max bytes, more transactions can be included in blocks.
Regen ledger is sometimes experiencing IBC bottlenecks on ICA transactions which require more gas for execution.
On blockchains where there is a lot of activity and apps txs for block space, or there are high levels of smart contract executions, setting higher max gas can ensure that more transactions can be included in the proposed blocks.
One disadvantage is that blocks may contain more data and thus increase the rate at which disk space is consumed.
Regen currently has these settings:
~$ regen q params subspace baseapp BlockParams
key: BlockParams
subspace: baseapp
value: '{"max_bytes":"200000","max_gas":"2000000"}'
Joe Bowman, lead dev at Quicksilver states:
…So every other chain I am aware of has a max gas of at least 40m. Regen has 2m. Most ICA txs are measured in the 0.75million+ of gas per message. We have somewhat successfully mitigated this by sending 2 messages per transaction, rather than the usual 20 or so. But this is painful, and has caused a bunch of knock on issues for relayers.
Validators, developers, and community members are invited to discuss what the optimal block params should be.
I propose Joe’s recommendation of 40m (“max_gas”:“40000000”). This is a 20x increase.
Max bytes, which is currently 200k, I suppose should be increased also by the same ratio, which would be 4mb for max block size.
In principle, blocks would not actually be 4mb each, they would only include the necessary transactions at current usage rates. However, having these higher limits in place will allow more room for development and activity on Regen Ledger.
For a comparison here are baseapp params from other appchains:
Juno
‘{“max_bytes”:“22020096”,“max_gas”:“100000000”}’
22mb / 100m
Stargaze
‘{“max_bytes”:“26214400”,“max_gas”:“75000000”}’
26mb / 75m
Gravity Bridge
‘{“max_bytes”:“100000000”,“max_gas”:“2000000000”}’
100mb / 2B
Please weigh in with your conside