### Allocation - Technical Flow

In the current phase, the Polygon Village Grants team will assist with Community Treasury operations, aggregating approved applications and the preparation of corresponding on-chain transactions. A set of on-chain mechanisms is proposed to facilitate the flow of funds.

The address of the current interim SAFE contract, introduced in [PIP-17](https://github.com/maticnetwork/Polygon-Improvement-Proposals/blob/main/PIPs/PIP-17.md) and to which Community Treasury emissions stream to, is `0x2ff25495d77f380d5F65B95F103181aE8b1cf898`.

A new governance contract (Aragon) is proposed that will govern the Community Treasury.

A non-upgradeable OpenZeppelin ERC20Votes will be used as a voting token held by two SAFE contracts. Transfers, Approvals and Delegation will be disabled and tokens will be distributed upon contract deployment. Two roles are furthermore distinguished, Proposer and Executor.

- 50.00000001 tokens will be distributed to the Proposer SAFE (`0x2ff25495d77f380d5F65B95F103181aE8b1cf898`) wallet operated by Polygon Labs,
- 49.99999999 tokens will be distributed to the Executor ⅗ consensus multisig wallet (`0xb7b02DbC9D054A8BA90b2172B4f8d2D79aC7d3a0`) operated by the Community Treasury Board.

The Proposer is responsible for proposal creation, with 50 votes being the requirement.

Once a proposal has been created, both the PROPOSER and EXECUTOR's `yes` votes are necessary to execute a proposal, with 100 votes being the required consensus.

The above setup ensures that while Polygon Labs may assist the Community Treasury Board with day-to-day administrative and other non-managerial operations, it may not execute any transactions, including the distribution of funds, without the CTB's on-chain approval.