fix(ctp): re-deploy RetroReceiver with new owner#2683
Conversation
🦋 Changeset detectedLatest commit: 9a46595 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
This PR changes implementation code, but doesn't include a changeset. Did you forget to add one? |
tynes
left a comment
tynes
left a comment
There was a problem hiding this comment.
The deployments directory is in the npm package, this should get a changeset
smartcontracts
force-pushed
the
sc/ctp-update-ddd
branch
from
b53d200 to
99264fa
Compare
Done |
|
Hey @smartcontracts! This PR has merge conflicts. Please fix them before continuing review. |
smartcontracts
force-pushed
the
sc/ctp-update-ddd
branch
from
99264fa to
ce1bd6f
Compare
Re-deploys the RetroReceiver with a new default owner called the Dedicated Deterministic Deployer address. When deploying authenticated smart contracts deterministically to the same address on many chains, it's necessary to have a known static owner that then transfers ownership to the final owner after deployment (which can be different on every chain). This PR re-deploys the original contract with that new default owner, the DDD.
smartcontracts
force-pushed
the
sc/ctp-update-ddd
branch
from
ce1bd6f to
85a1e90
Compare
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
Closes #2683 --------- Co-authored-by: Emilia Hane <elsaemiliaevahane@gmail.com>
Closes #2683 --------- Co-authored-by: Emilia Hane <elsaemiliaevahane@gmail.com>
3 participants
Description
Re-deploys the RetroReceiver with a new default owner called the
Dedicated Deterministic Deployer address. When deploying authenticated
smart contracts deterministically to the same address on many chains,
it's necessary to have a known static owner that then transfers
ownership to the final owner after deployment (which can be different on
every chain). This PR re-deploys the original contract with that new
default owner, the DDD.