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

Add C1.0 migration metric for evaluating migrated state #3243

Closed
j1010001 opened this issue Apr 16, 2024 · 2 comments · Fixed by onflow/flow-go#5988
Closed

Add C1.0 migration metric for evaluating migrated state #3243

j1010001 opened this issue Apr 16, 2024 · 2 comments · Fixed by onflow/flow-go#5988
Assignees

Comments

@j1010001
Copy link
Member

j1010001 commented Apr 16, 2024

Issue to be solved

We need to know what is the percentage of on-chain state which has been migrated as a result of Cadence 1.0 migration. This will help us make better go/no-go decision for the testnet and mainnet upgrade to C1.0.

The ideal outcome IMO is to say "from total X of Values stored on chain, Y has been successfully migrated and Z was not because the related contract was not staged."

In addition, for each on-chain contract we want to know how many on-chain values/objects relate to it and maybe how much storage is used by those. This will help us evaluate if there are any significant contract that are not staged that hold significant number of on-chain state.

Suggested Solution

No response

@bluesign
Copy link
Contributor

this is only good for mainnet, but also nothing is staged for mainnet. I think good approach would be to match staged contracts to mainnet.

@j1010001
Copy link
Member Author

this is only good for mainnet, but also nothing is staged for mainnet. I think good approach would be to match staged contracts to mainnet.

Yes, We need to push for devs to stage for TN and MN at the same time, as we are getting closer to TN upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants