• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
AavegotchiAavegotchiby0xA5643D9B4A2049d578a690269Dbc13426b352672hardkornate.lens

1000 GHST Bounty for designing, implementing and passing reporting standards proposal

Voting ended over 2 years agoSucceeded

Author: HARDKOR GotchiID: 20019 Quorum requirement: 20% (9M) Vote duration: 7 days XP Reward: 10 XP for each Aavegotchi in the voter’s wallet

This is a 1000 GHST bounty to be paid from DAO Foundation Treasury as this is development of DAO governance.

The deliverables are -

  • Design reporting framework that requires less than one hour a month from a project and has outputs that contain correctly formatted information that can be easily leveraged in social media, blog posts, and Discord announcements
  • Create all needed templates/forms
  • Pass a CORE Prop to enact the standards

Payment upon passage of CORE prop

Why do we need this?

We've just started getting DAO development going and it's become a sore point between contributors, that no one is really held responsible to report anything on any timeframe or in what detail. This is not fair to the people doing the work or the people trusting them to do it. For the good of the community, we need to establish some basic standards regarding what you should be reporting, how often, where, in what format, and provide the basic tools(forms) to make this easy for contributors to accomplish. This protects the DAO by preemptively answering questions and protects contributors by empowering them to be in compliance, and therefore shielded from constant update requests.

Who will do it? Anyone can and should, but there is already a few people interested, so go to the discussion and join in. This is ideally some light work done by one to four people.

Off-Chain Vote

YES - Fund the bounty
5.94M GHST88.1%
NO - Do not fund the bounty
804.49K GHST11.9%
Download mobile app to vote

Discussion

Aavegotchi1000 GHST Bounty for designing, implementing and passing reporting standards proposal

Timeline

Oct 18, 2023Proposal created
Oct 18, 2023Proposal vote started
Oct 25, 2023Proposal vote ended
May 24, 2025Proposal updated