-
Notifications
You must be signed in to change notification settings - Fork 366
Added 1.4.1 canonical support #1234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added 1.4.1 canonical support #1234
Conversation
Hmm, looks like contracts aren't deployed to the right address. |
Do you have advice on how to handle it? Maybe, commit hash where I could deploy at the correct addresses, or maybe I need to change something, because I have no idea. |
This worked for me:
Using a local development node, the contracts end up at the right address:
|
The |
Thank you, bro, for your advice on cloning the repo by version works for me too. Now, I have such addresses.
|
Out of curiosity, what were you doing before? |
I cloned the repo main branch and just switched to the other branches, that's all. I didn't clone using -b parameter. |
I suspect your repo was in a weird state then, because the only difference between my suggestion and what you were doing, is that I suggested starting from a fresh clone. It would have been equivalent to do: git clone https://github.com/safe-global/safe-smart-account.git
cd safe-smart-account
git checkout release/v1.4.1
# continue with the same steps from here... |
Add new chain
Please fill the following form:
Provide the Chain ID (Only 1 chain id per PR).
Relevant information:
PR Singleton Factory
PR Chainlist
PR Etherscan
I have tried such branches: release/v1.4.1, v1.4.1-2, v1.4.1-1. My addresses didn't change at all. I see CHANGELOG.md, but I have no idea why it was deployed to another address.