Closed atarpara closed 11 months ago
@atarapra Thanks for the PR. The reason why I/we decided against 0age
's version is that it's not the official EIP version. If, for whatever reason, someone relies on the codehash of the EIP-1167
, it will fail. I would like to stick with the official version, even though it's not the fully optimised version to keep consistency with the official EIP. @mds1 what's your opinion on this?
@pcaversaccio totally understood. I didn't understood foundry test is failing on ci but in my local machine passed all tests.
FWIW, I once made a Dune dashboard for minimal proxies over all available chains, and only a fraction uses 0age
's version:
Thus, this is also line with our design principles that CreateX should cover most but not all contract creation use cases. But lets wait for @mds1's feedback :).
@pcaversaccio totally understood. I didn't understood foundry test is failing on ci but in my local machine passed all tests.
That's a fuzz edge case unrelated to your changes - I will make a PR to fix this.
@atarapra this PR (https://github.com/pcaversaccio/createx/pull/36) will fix the previously discovered edge case.
Hmm, seems the coverage report doesn't work for external forks due to some permission issues; will take a look.
Hmm, seems the coverage report doesn't work for external forks due to some permission issues; will take a look.
This will fix the coverage issues for external forks: https://github.com/pcaversaccio/createx/pull/37.
Thanks for the PR @atarpara!
I agree with @pcaversaccio that for this factory we should stick to the widely supported standard. Even if it's not the most efficient, it's the most well-supported, and the least-surprising to users deploying minimal proxies. Users that want the 0age version can use CreateX to deploy their deterministically deploy their factory across chains. As a result I'm going to close to this :)
PR Checklist
Solady is using
0age
pattern for the EIP-1167 which has 2 bytes less codesize and saves 4 gas on each call.🐶 Cute Animal Picture