• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
APWineAPWineby0xAFe4043c9FFd31753c5bE2B76dfc45AaA70ebD6fdydymoon.sismo.eth

APGP 11 : Bounties budget handled by a community multisig

Voting ended almost 4 years agoSucceeded

Summary: Reward some community actions with bounties

Context: I recently set up Dework on APWine discord, which is a platform allowing users to create bounties (tech or non-tech) which are tasks needed for the DAO.

Either the team can create tasks, or the community can make suggestions to create new tasks so don’t hesitate if you have ideas of bounties, share it here.

Once a contributor is assigned to a task, it’s possible to submit what was done, which will have to be approved by a reviewer to receive the rewards.

I created a multisig to handle the bounties budget, and would like to propose to add signers from the community. The next APGP will be about the multisig elections.

Rationale: The goal of this proposal is to allocate a small amount of APW to test Dework with the community before voting on a bigger budget if the test is successful, and to add signers from the community to handle the bounties multisig.

On the APGP 10, we voted to allocate 250K/262.5K APW of unclaimed airdrop to rewards veAPW holders.

The idea would be to use the 12.5K APW left on the contract As the tokens are on mainnet, we’ll need to bridge it to Polygon and send it to the multisig.

In order to reach 8 signers for the multisig, the community will be able to apply in the APGP 12. The goal is to have 5 / 8 signers.

Means: 12.5K APW from the unclaimed airdrop

Technical implementation: Bridge 12.5K APW to Polygon and transfer to the new multisig

Voting options: Yes, allocate 12.5K APW to try dework No, do nothing Abstain

Off-Chain Vote

Yes, allocate 12.5K APW
28.8M votes93.5%
No, do nothing
1.99M votes6.5%
Abstain
6.4K votes0%
Download mobile app to vote

Discussion

APWineAPGP 11 : Bounties budget handled by a community multisig

Timeline

May 12, 2022Proposal created
May 12, 2022Proposal vote started
May 17, 2022Proposal vote ended
Sep 01, 2025Proposal updated