ECO-1906 Cannon Proving

[johnwhitton]

Key Refactors Include

Proving Logic Prover.sol

• Chain Block Proofs replace L1,L2,L3 world states and only storing the lastest state for each proof
• setChainConfiguration provides an ownable function to allow the configuration of source and destination chains on each chain
• Settlement Chain Introduce the concept of a settlement chain - this will enable L3 chains to prove against L2 chains using the same proving algorithms such as bedrock and cannon.
• Upgradeable Proving Contract We've made the Prover Upgradeable, the thought is that it will only needed to be upgraded when we introduce a new proving mechanism. Adding additional destination chains can be done by SetChainConfiguration. The benefit of upgrading is that we can also keep all the states (including the intents that have been proven) when upgrading.
• proveL2WorldStateBedrock replaces proveOutputRoot and moving forward will be renamed proveWorldStateBedrock as this proving mechanism should also work on L3's as long as their settlement chain is correctly configured
• proveL2WorldStateCannon introduces support for the Cannon proving Mechanism will also be renamed to proveWorldStateCannon as this proving mechanism should also work on L3's as long as their settlement chain is correctly configured

[nknavkal]

yeah its fine for now, a lot of this is going to get overhauled soon though so dont lose these comments. I don't really think its worth addressing any of them within the context of this architecture, just save it for the commit where we move everything into the master prover implementation

[nknavkal]

what are these .openzeppelin files?

[johnwhitton]

Open Zeppelin comes from the faxt that we're using the

import "@openzeppelin/contracts-upgradeable/proxy/utils/UUPSUpgradeable.sol";
import "@openzeppelin/contracts-upgradeable/access/OwnableUpgradeable.sol";

and

    "@openzeppelin/hardhat-upgrades": "^3.2.0",
    "@openzeppelin/contracts": "^5.0.2",
    "@openzeppelin/contracts-upgradeable": "^5.0.2"

[nknavkal]

just a note for making this a little less clunky, maybe we can make a bunch of IntentProtocol objects, make all their fields the various contracts, constants etc and then we could import them all in one fell swoop? would be more extensible for future networks too i would think

[johnwhitton]

Good Idea 🙏

[nknavkal]

is there a reason you're doing it this way rather than just doing .connect() in the script itself? much cleaner

[johnwhitton]

Open for discussion, original though was to put all the signer, provider and contract configuration in the setup, so that it could be used by multiple scripts.
I think a bigger conversation is the role of this repository in providing examples for prover and solver services or whether we move this to a separate repository.

[nknavkal]

is there an expectation that a user calls this? seems like a helper, should make it private and just stick a call into whatever public function would be using it

[johnwhitton]

Good point, should revisit this initial thought is that proving services may use it to validate the GameStatus Storage.