# Derisking 100MGas The following should act as a braindump of things we need to investigate before giving an okay to 100MGas. All worst cases are collected in geth via statetests. The fuzzers used for finding these are not sophisticated and this analysis should be replicated in a less time constrained manner. ## Hard requirements - Modexp repricing: the worst cases we see are around 6 seconds per block (addressed in Fusaka) - BN256Add repricing: the worst cases are around 4.7 seconds per block - BN256Pairing repricing: the worst cases are around 2+ seconds per block ## To investigate - All Opcodes in tight loops - Create & Call chains - Predeployed contracts (deposit, withdrawal queue) - Storage requirements, storage load on datasets - KZG Precompile - BN256Mul precompile - Try to meassure or model the longest execution time for a single block (this involves txs accesing very old random state data, and requires big state). - Check the block filled with the following CL requests - deposits - consolidations - withdrawals/exits - 7702 - BLS - Jumpdest analysis ## Already investigated - ECRecover: not an issue - Blake2f: worst case around 1 sec - Datacopy: not an issue -