Given we've manipulated storage since v2 launch, we need to make sure the current release doesn't mess it up.
Changes proposed in this pull request
Generate the storage layout based on the current mainnet version. We'll want this merged with the cover products branch and only then merged into release-candidate.
Test plan
Tested using trustmebro science. Akcshually... I cherry picked this on top of cover products and swapped some storage slots inside the cover contract to make sure it fails. Technically still trustmebro science.
Checklist
[ ] Rebased the base branch
[ ] Attached corresponding Github issue
[ ] Prefixed the name with the type of change (i.e. feat, chore, test)
[ ] Performed a self-review of my own code
[ ] Followed the style guidelines of this project
[ ] Made corresponding changes to the documentation
[ ] Didn't generate new warnings
[ ] Didn't generate failures on existing tests
[ ] Added tests that prove my fix is effective or that my feature works
Review
When reviewing a PR, please indicate intention in comments using the following emojis:
:cake: = Nice to have but not essential.
:bulb: = Suggestion or a comment based on personal opinion
:hammer: = I believe this should be changed.
:thinking: = I don’t understand something, do you mind giving me more context?
Context
Given we've manipulated storage since v2 launch, we need to make sure the current release doesn't mess it up.
Changes proposed in this pull request
Generate the storage layout based on the current mainnet version. We'll want this merged with the cover products branch and only then merged into release-candidate.
Test plan
Tested using trustmebro science. Akcshually... I cherry picked this on top of cover products and swapped some storage slots inside the cover contract to make sure it fails. Technically still trustmebro science.
Checklist
Review
When reviewing a PR, please indicate intention in comments using the following emojis: