# Gitcoin/Allo Development Overview

###### tags: `allo`

Jip and I met yesterday and a couple questions came up on the contract level that we wanted to run by you before any further following up with the client in TG. This will also help to more realistically scope out the work for the proposal:

## Quadratic Funding Clarification

We wanted to confirm that these are direct 1-to-1 grants, and _not_ quadratically matched, in any way?

## Contract Level & Voting Strategy

If so, for the contract level→

- The only voting strategy in Allo at the moment is a Quadratic Funding Voting strategy.
- The voting process as it’s explained in the doc is two rounds:
1. Round one: some sort of unexplained combination atm between signaling votes from MMG token holders and a grant reviewer committee. The impression is that the grant reviewers make the final decision internally while taking into account token holder votes. Greenlit grants move to →
2. Round two: A more formalized snapshot vote(s).

### First Question Area

As no value is transferred with votes, we can create a new voting strategy using their interface limiting everyone to one vote for the first round and with no value transferred. However for this stage it feels somewhat redundant as the final, decisive vote takes place on Snapshot. For the first round we can just check they are a token holder before allowing them to signal vote? So we wanted to get your thoughts on the first round voting mechanism.

## Distribution and Smart Invoice

For distribution, it sounds like they’re already planning on a Safe. For the recipients though they mentioned milestone payments and deliverables. Smart invoice, or a version of it, would fit really well with the above for the milestone-based accountability section (with a more applicable frontend).

### Second Question Area

Smart Invoice is currently unaudited. I imagine Allo is planning on audits before using any contract in production, but wanted to check on this area as if there was an audit it would also benefit Smart Invoice at their expense. If the contract is modified for their use though this is a moot point. There’s also the question onthe audit process, timeline, and potential costs involved. So, we wanted to get your input on how to approach the Smart Invoice audit situation and if it's something we should discuss with Allo.

### tl;dr

1. What are your thoughts on the first round voting mechanism, considering the redundancy with the Snapshot vote?
2. What are your thoughts on a Smart Invoice integration?