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

Update contract removal docs #163

Open
Tracked by #959
j1010001 opened this issue May 25, 2022 · 2 comments
Open
Tracked by #959

Update contract removal docs #163

j1010001 opened this issue May 25, 2022 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@j1010001
Copy link
Member

j1010001 commented May 25, 2022 •
edited
Loading

Contract removal remains permissioned with deployment of secure cadence, because it would be possible to circumvent the safety checks performed during contract upgrades.

Scope:
Document existing behaviour, improve error message and share in forums.
@j1010001
Copy link
Member Author

Pending discussion in TPM: https://www.notion.so/dapperlabs/Technical-Product-Meeting-with-Dete-054824f0be334392806e1e39641afe48#5d04b106e12e436f8c9d27a98b5919b6

@turbolent turbolent removed their assignment Sep 23, 2022
@j1010001
Copy link
Member Author

Document the behaviour, improve error message and share in forums.

@j1010001 j1010001 mentioned this issue Oct 19, 2022
Closed
@j1010001 j1010001 added the documentation Improvements or additions to documentation label Jan 13, 2023
@j1010001 j1010001 changed the title Update contract removal to make it permissionless Update contract removal docs Jan 13, 2023
@j1010001 j1010001 mentioned this issue Apr 18, 2023
Open
36 tasks
@turbolent turbolent transferred this issue from onflow/cadence Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@turbolent @j1010001