runtianz

Updated the case study section for us to look into the reference swap implementation we offered. Will add another study to cryptographic primitives later.

I think `enum` is more liek a syntax sugar to the dispatching logic that we can already implement in Move right now. The key thing that `enum` solution would be...

I'll include the consensus config in the proposal generator!

Is this issue solvable by extending Move core language / Move Prover? e.g: Have an attribute such that a function can never pass signer along?

Yea I saw the witness pattern being used in Sui Move quite extensively.

Are the rust changes relevant? Looking at the description I'm not seeing why we need to change the rust code?

Another thing is in order to be able to use the tool in production we may need to cherry pick the api change to the production branch. cc @davidiw

Sry pushed to the wrong branch :(

Fixed @movekevin's comments

Updated the PR with the refactor. Tho it doesn't look cleaner than before either... lemme know if you would like to keep it or not cc @movekevin