Port In Framework Upgrades

[0xmovses]

Summary

As discussed in our calls last week. We need to apply the framework migrations after the old DB is replaced with the new one and after we run an initial round of verifications.

Why? Because doing so would mutate the state of the chain and therfore we would not be able to make equality checks against state keys or at the rest level. The framework would have been upgraded, therefor state has changed.

Because of this, it is a non-goal to test our framework migrations against the current movement network state (implicitly, using the current test tooling that helps us to do so).

Acceptance Criteria

Instead, we must do the upgrades against the latest fully replaced aptos DB that contains the current movement network state, but is running against aptos full core node.

So:

• Run the framework upgrades (previously pre-governance and post-governance upgrade txs) against the aptos-core full node binaries locally

cc @andygolay

[andygolay]

Ah yep makes sense. Great catch.