Voting flow

[kittybest]

As a user/badgeholder, I want to submit my ballot to vote on projects

Dependencies

• move the cli commands about publishing message to frontend (or import maci-cli package) - see Integrate cli package into demo #12
• add support for user signups - see Feat(frontend): signup flow #4

Requirements

• allow badgeholders to add projects to /ballot page (already implemented in EasyRetroPGF)
• allow badgeholders who have 1. connected their wallet & 2. signed up w/ MACI to submit their ballot
• disable ability to vote if user has already submitted a ballot
• Integrate maci sdk message publishing for saved ballot

Details

For this demo, let's just assume the "happy path" that each badgeholder will only submit 1 ballot. Looks like the app already enforces this:

Submitting the ballot should trigger publishMessage on the Poll contract.

Questions to sort out

• Do we need to submit a tx for every single project in the ballot, or how can we batch these messages (to reduce number of txs & gas costs)? clr.fund does some batching of their votes, so perhaps we can use a similar approach?
• Need to reverse array of votes, since they’re processed in reverse order? Sort out appropriate nonce for each

[samajammin]

Do we need to submit a tx for every single project in the ballot, or how can we batch these messages (to reduce number of txs & gas costs)? clr.fund does some batching of their votes, so perhaps we can use a similar approach?

Looks like this is where they batch the messages: https://github.com/clrfund/monorepo/blob/develop/contracts/contracts/FundingRound.sol#L196

Then they call that from the frontend to submit votes/contributions:
https://github.com/clrfund/monorepo/blob/develop/vue-app/src/components/ContributionModal.vue#L194

We'll want to investigate how we might optimize this, so that a user is submitting as few on-chain txs as possible...