Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deploy StagedContractUpdates to Crescendo #11

Closed
sisyphusSmiling opened this issue Dec 12, 2023 · 2 comments
Closed

Deploy StagedContractUpdates to Crescendo #11

sisyphusSmiling opened this issue Dec 12, 2023 · 2 comments
Assignees
@sisyphusSmiling
Labels
deployment

Comments

@sisyphusSmiling
Copy link
Contributor

sisyphusSmiling commented Dec 12, 2023 •
edited
Loading

The StagedContractUpdates contract should be deployed to Testnet. Currently, the contract requires a block height for the target update boundary on deployment, so we'll need to know the target height on deployment.

While not a blocker, it would be nice to implement #3 before deployment so behavior is consistent during iteration.
@sisyphusSmiling sisyphusSmiling self-assigned this Dec 12, 2023
@sisyphusSmiling sisyphusSmiling changed the title Deploy StagedContractUpdates to Testnet Deploy StagedContractUpdates to Crescendo Dec 12, 2023
@sisyphusSmiling
Copy link
Contributor Author

Depends on #12

@sisyphusSmiling
Copy link
Contributor Author

Update: Due to changes in the Cadence 1.0 network update plan, StagedContractUpdates will no longer serve the purpose of supporting contract staging. The contract may still be useful for the purposes of delegated contract updates via onchain mechanisms. Deployment of this deprioritized in favor of the contract introduced in #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sisyphusSmiling sisyphusSmiling

Labels
deployment
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sisyphusSmiling