You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't appear to be possible to deterministically redeploy the contracts with the code in this repo anymore, not even by checking out old commits.
Impact
Deterministic contract addresses are either not available or require bespoke procedures when deploying the contract on a new chain. Contract verification becomes in turn more difficult.
To reproduce
Execute the deployment command without broadcasting:
We can also check the difference in the deployment bytecode, for example by comparing this and this. We can see that they only differ in the metadata bytes.
I suspect this issue has been introduced in 24d556b. However, the code needed to replicate the old behavior was in rndlabs/cowswap-contracts, which is a deleted repo.
The text was updated successfully, but these errors were encountered:
Problem
It doesn't appear to be possible to deterministically redeploy the contracts with the code in this repo anymore, not even by checking out old commits.
Impact
Deterministic contract addresses are either not available or require bespoke procedures when deploying the contract on a new chain. Contract verification becomes in turn more difficult.
To reproduce
Execute the deployment command without broadcasting:
Extract the expected deployment addresses:
Compare with current addresses and observe that they all differ:
Expected behaviour
The addresses should be the same.
ComposableCoW version/commit hash
2ba71df3d5fdbfe8b92a540837262e164a0290ab
Additional context
We can also check the difference in the deployment bytecode, for example by comparing this and this. We can see that they only differ in the metadata bytes.
I suspect this issue has been introduced in 24d556b. However, the code needed to replicate the old behavior was in rndlabs/cowswap-contracts, which is a deleted repo.
The text was updated successfully, but these errors were encountered: