RSK contract deployments and upgrades #217

New Issue

raucao · 2022-07-15T11:27:25Z

raucao commented

2022-07-15 11:27:25 +00:00

(Migrated from github.com)

There are still a couple of issues when deploying the new contracts from the hardhat branch to RSK testnet (as opposed to Rinkeby).

raucao added the

bug

enhancement

labels 2022-07-16 15:20:27 +00:00

raucao added the

dev environment

label 2022-07-16 15:23:32 +00:00

raucao commented

2022-07-25 07:53:11 +00:00

Good news: there are actually no errors or other issues left with RSK testnet deployments (at least after the recent changes to the deployment script).

You can find all contracts that were deployed to RSK testnet from your machine in .openzeppelin/unknown-31.json. Implementations are only newly deployed if a proxy cannot point to an existing one on the same chain. Also, there's an "admin" contract, via which actual proxy updates are executed, and which also doesn't get redeployed for the same keys.

Good news: there are actually no errors or other issues left with RSK testnet deployments (at least after the recent changes to the deployment script). You can find all contracts that were deployed to RSK testnet from your machine in `.openzeppelin/unknown-31.json`. Implementations are only newly deployed if a proxy cannot point to an existing one on the same chain. Also, there's an "admin" contract, via which actual proxy updates are executed, and which also doesn't get redeployed for the same keys.

raucao self-assigned this 2022-07-25 07:53:37 +00:00

bumi was assigned by raucao

2022-07-25 07:53:37 +00:00

hueso was assigned by raucao

2022-07-25 07:53:37 +00:00

raucao added the

kredits-1

label 2022-07-25 07:53:43 +00:00

raucao closed this issue

2022-07-25 07:56:52 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kredits/contracts#217