Does anyone know why the OP Stack selects a gas limit of 30M but a target of 5M? I'm guessing it has to do with the low block times but it seems like this choice means the chain must take on a higher max load, but cannot tolerate a high average load without fee increases (which is happening on base right now).

building open source public goods @a16zcrypto

Ah that actually makes a lot of sense. 

If I understand correctly changing the gas limit for an op stack chain would require updating configs and distributing them to the nodes right? Would it make sense to add these parameters to the system config contract so that chains have more leeway here?

Original logic was pretty simple, goal was 2.5m gas/sec (=5m target) but a high enough limit that any transaction that could fit into an L1 block would also fit into an L2 block.

I think it's to reduce chain bloat - with 2s block times, a 15M gas target or 50% utilization that's met consistently would grow history at 6x the pace of L1, which seems untenable

cc @zain @tynes if I got this wrong