Factory smart contract to make easier and safer usage of the `CREATE` and `CREATE2` EVM opcodes as well as of `CREATE3`-based (i.e. without an initcode factor) contract creations.
My personal opinion is that we should not use a via_ir = true configuration due to the following reasons:
Deployment costs should not matter (via_ir wins here),
The new pipeline doesn't offer any huge gas savings (I always use the default optimiser steps dhfoDgvulfnTUtnIf),
Block explorer verification will be easier by not using via_ir since otherwise you must upload a standard JSON input file as Etherscan and Blockscout don't allow in the UI to configure the optimiser settings.
➛ My personal opinion is to choose optimizer_runs = 6_942_000 since optimizer_runs = 10_000_000 doesn't offer any additional significant gas savings & because of the meme factor 😄.
Context
Gas reports for
CreateX
:Summary Runtime Costs
My personal opinion is that we should not use a
via_ir = true
configuration due to the following reasons:via_ir
wins here),dhfoDgvulfnTUtnIf
),via_ir
since otherwise you must upload a standard JSON input file as Etherscan and Blockscout don't allow in the UI to configure the optimiser settings.➛ My personal opinion is to choose
optimizer_runs = 6_942_000
sinceoptimizer_runs = 10_000_000
doesn't offer any additional significant gas savings & because of the meme factor 😄.Option 1
Configuration:
optimizer = true
optimizer_runs = 6_942_000
via_ir = false
Option 2
Configuration:
optimizer = true
optimizer_runs = 10_000_000
via_ir = false
Option 3
Configuration:
optimizer = true
optimizer_runs = 6_942_000
via_ir = true
☠️💀
Option 4
Configuration:
optimizer = true
optimizer_runs = 10_000_000
via_ir = true
☠️💀