Rm π solvency

[enricobottazzi]

No description provided.

[enricobottazzi]

@alxkzmn can you help me on the contracts side of this? As part of the PR I added a script gen_commitment in zk_prover that output the commitment to the MerkleSumTree in a json file that can be consumed by contracts.

To dos:

• verifyInclusionProof should also require that rootSums used as public input match the ones committed to in the previous phase
• rename rootSums to rootBalances
• Update tests to consume commitment_solidity_calldata.json
• Add testing to cover the case in which the CEX commits to a fake rootBalances during the commitment phase that will make verifyInclusionProof to fail. Similar to the attack described here => Refactor the contract according to V1 consolidation spec #178 (comment)

[alxkzmn]

@alxkzmn can you help me on the contracts side of this? As part of the PR I added a script gen_commitment in zk_prover that output the commitment to the MerkleSumTree in a json file that can be consumed by contracts.

To dos:

* [x]  `verifyInclusionProof` should also require that `rootSums` used as public input match the ones committed to in the previous phase

* [x]  rename `rootSums` to `rootBalances`

* [x]  Update tests to consume `commitment_solidity_calldata.json`

* [x]  Add testing to cover the case in which the CEX commits to a fake `rootBalances` during the commitment phase that will make `verifyInclusionProof` to fail. Similar to the attack described here => [Refactor the contract according to V1 consolidation spec #178 (comment)](https://github.com/summa-dev/summa-solvency/pull/178#discussion_r1381385661)

Done!