The YAM treasury does not have enough YAM to pay contributors fully for this month. This proposal recommends minting YAM to pay contributors monthly as part of the on-chain transactions. Only the amount of YAM owed to contributors would be minted in these transactions, and a new vesting procedure, using Sablier, would be implemented to further align incentives (vote 2).
As discussed in this post and subsequent snapshot vote, 370,000 new YAM was minted to make up for the YAM trapped in the original Vesting Pool contract.
The current balance in the treasury is 100,280, which will not cover this upcoming month's payroll obligations of ~130,000 YAM. There are a few options to proceed:
This proposal puts forward option 1 as the preferred choice.
Option 1 negates the need to guess as how much YAM needs to be minted (an impossible task to get right) and constrains the maximum quantity to be a function of the treasury size. It focuses the discussion not on whether minting YAM is good or bad, but whether the contributions of contributors is worthwhile (option 3 also has this trait). It allows token holders fine grained control over how much YAM is created via the grants approval process. Unlike option 3, it limits treasury burn. I wrote more about why this is preferable here.
Vesting will be voted on in a second vote.
If this proposal is passed, the following process would be carried out:
mint() function on the YAM token contract for the amount determined in step 1.If this proposal is not passed this month then no YAM will be paid this month. The owed amounts will be recorded on github and backpay will be included in the next month's on-chain proposal.
The minting of YAM for any purpose other than contributor compensation is out of scope of this proposal.