Content pfp
Content
@
0 reply
0 recast
2 reactions

jw 🦺 ERC6551 pfp
jw 🦺 ERC6551
@0xjw.eth
What optimizer settings are folks using to deploy production contracts these days? Any best practices?
1 reply
1 recast
2 reactions

Spencer Graham 🧢 pfp
Spencer Graham 🧢
@spengrah.eth
biggest unlock for me / my project has been `bytecode_hash = "none"`, which makes it easier/possible for multiple people to deploy the same contract to the same address with a create2 factory like foundry's. Without that setting, the local directory path can influence the create2 inputs and the resulting address
1 reply
0 recast
1 reaction

jw 🦺 ERC6551 pfp
jw 🦺 ERC6551
@0xjw.eth
Woah, TIL! Does that setting affect the ability to verify contracts?
1 reply
0 recast
1 reaction

Spencer Graham 🧢 pfp
Spencer Graham 🧢
@spengrah.eth
hasn't been a problem at all for me thus far
1 reply
0 recast
0 reaction

jw 🦺 ERC6551 pfp
jw 🦺 ERC6551
@0xjw.eth
Interesting - the foundry docs mention that there might be some issues with verification: https://book.getfoundry.sh/forge/deploying?highlight=bytecode_hash#verifying-contracts-with-no-bytecode-hash
1 reply
0 recast
0 reaction