-
Notifications
You must be signed in to change notification settings - Fork 375
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
Remove TransferWhitelist contract #10318
Conversation
20662ce
to
38705af
Compare
I think it's worth noticing that even if we delete the contract itself, our on-chain contract Registry does not have a function to remove, so the deployed implementation will keep being a core-contract. I do not see a downside with deleting the contracts, as it is already verified in Celo Explorer: https://explorer.celo.org/mainnet/address/0xb49E4d6F0B7f8d0440F75697E6c8b37E09178BCF/contracts#address-tabs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good other than the comment + the GrandaMento CK test failure, which like it's probably caused by the stableToken contract address now being migrated one contract earlier than before ( ithout the transferWhiteList contract migration happening)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
edit: flagging that the build is failing, would double check that but once this is updated + build is passing, good to go 👍
The current build failures are present in master. See
I can wait until master is green again and rebase then to get the the tests green. |
since it is possible that someone will try to verify previous releases and since this contract is part of previous releases it might happen that verification will fail (or we should double check that it will not fail). See #10318 (comment).
02357ab
to
b2ab3c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
since it is possible that someone will try to verify previous releases and since this contract is part of previous releases it might happen that verification will fail (or we should double check that it will not fail). See #10318 (comment).
b2ab3c3
to
3694a4d
Compare
The contract is not used anymore. See also celo-org/celo-blockchain#2110.
Otherwise the test fails when one of the migrations before the cUSD deployment changes.
since it is possible that someone will try to verify previous releases and since this contract is part of previous releases it might happen that verification will fail (or we should double check that it will not fail). See #10318 (comment).
3694a4d
to
1f5920d
Compare
The contract is not used anymore. See also celo-org/celo-blockchain#2110.