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.

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

Test upgrade procedure for 1.5 on honeypot #462

Closed
4 tasks
marcelstanley opened this issue Jun 24, 2024 · 1 comment
Closed
4 tasks

Test upgrade procedure for 1.5 on honeypot #462

marcelstanley opened this issue Jun 24, 2024 · 1 comment
Milestone

Comments

@marcelstanley
Copy link
Collaborator

marcelstanley commented Jun 24, 2024

📚 Context

Honeypot is the only application owned by Cartesi which is deployed to mainnet and runs v1.3.1.

It's important that we verify that the upgrade procedure devised for the forthcoming release v.1.5 at #461 is tested on such application in order to prevent any issues.

✔️ Solution

We shall test the procedure defined at #461 and make sure it works on a testnet.

📈 Subtasks

  • Test upgrade procedure on devnet
  • Replicate upgrade procedure on a testnet. The results must be kept on record, showing evidence the application funds were kept intact

✅ Definition of Done

  • Update procedure works as expected, the application state is kept intact and no funds are lost in the process
  • Test results are documented
@marcelstanley marcelstanley added the ! High priority label Jun 24, 2024
@marcelstanley marcelstanley added this to the 1.5.0 milestone Jun 24, 2024
@marcelstanley marcelstanley moved this to 📋 Backlog in Node Unit Jun 24, 2024
@endersonmaia
Copy link
Contributor

For honeypot@mainnet, keep in mind that it was kept on 1.3.x version because it was necessary to generate a new snapshot (templateHash) when moving to 1.4.x, so the same would be needed when moving to 1.5.x.

@marcelstanley marcelstanley removed the ! High priority label Jun 24, 2024
@marcelstanley marcelstanley closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Node Unit Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants