# W3HC self-review I tried to use [DAOmeter](https://www.daometer.xyz/) DAO evaluation framework (see [MakerDAO example](https://www.daometer.xyz/review/makerdao)) to rate the Web3 Hackers Collective ([W3HC DAO](https://www.tally.xyz/gov/web3-hackers-collective)). Our mission statement is "We want to buid integrations through mentoring and learning". We have only three members a current treasury of 4k USD eq. We're using Gov ([Github repo](https://github.com/w3hc/gov) and [docs](https://w3hc.github.io/gov-docs/)) which is a DAO framework built with Open Zeppelin’s Governor contract in combination with NFTs. Any proposal should meet one of the following criteria: - Organize local hackathons, workshops and meetups - Request retroactive funding for a successful integration - Develop and maintain Gov: a DAO framework built with Governor and NFTs - Help people to setup their own DAO Score (self-review): **82%** (246/300) ## Review ### Community |||| |---|:---:|---| | Are there community stewards? | Yes | 10 | | Are there regular community updates or reports for members? | Semi Weekly | 10 | | Do regular contributors exist? | Yes | 10 | | Is there a contributor payroll? | None | 1 | | Do contributors get rewarded? | Yes | 10 | | Is there a formal onboarding process | Multiple documentation per role | 10 | | Is there a formal offboarding process? | Yes | 10 | | Are there working groups? | No | 0 | | Is the core team of the DAO anonymous? | No | 10 | #### Comments We don't have a contributor payroll in place yet, but contributors do get rewarded. We have a formal onboarding process (the members have to vote to welcome a new member). The offboarding can be active (you just burn your membership NFT), or passive (members can vote to ban a member). We don't have formal 'working groups' yet. ### Voting |||| |---|:---:|---| | Who has the voting power? | Tokens Owned | 5 | | How is voting accessed? | Tokens Owned | 5 | | What type of voting tools are used to enable the voting process? | Standard | 5 | | Are there delegates?| Yes | 10 | | Are delegates compensated? | No| 0 | | Is there a reported list of active delegates? | Yes | 10 | #### Comments We're in a one-person-one-vote style: only sthe holders of the membership NFT are allowed to vote. I don't see why 'tokens staked' would be better than 'tokens owned'. There is no staking in place. We're using Tally a a voting tool, so it's 'standard' and I'm not sure if it's better to have a custom UI for voting. We'll release a first version of [Gov UI](https://github.com/w3hc/gov-ui) in the coming weeks. ### Documentation |||| |---|:---:|---| | Is the DAO’s financial reporting public? | Yes | 10 | | Is the code repository of governance public? | Yes | 10 | | Is the DAO’s governance process documented? | Yes | 10 | | Are the DAO’s tokenomics documented? | Yes | 10 | | Is the DAO’s code open source? | Yes | 10 | ### Security |||| |---|:---:|---| | What type of security module does the DAO have? | None | 0 | | How frequent is the code being audited? | Continuous | 10 | | Has the DAO experienced a catastrophic loss of funds? | No | 10 | | Does the DAO have active admin keys? | No | 10 | #### Comments This is documented here. Gov is a combination of Open Zeppelin's Governor contract and an ERC-721. These have been audited multiple times. ### Treasury |||| |---|:---:|---| | What is the DAO’s treasury type? | Governance | 10 | | What type of treasury software is used by the DAO? | Custom | 10 | | Is there a dedicated person or team assigned to the DAO’s treasury? | Yes | 10 | | How diverse is the treasury?| Native token below 90% | 10 | #### Comments We don't have any 'native tokens'. People use their membership NFT to vote. ### Proposal |||| |---|:---:|---| | Are there preliminary discussions for a proposal? | Yes | 10 | | Is proposal data stored on-chain? | Yes | 10 | #### Comments We consider that preliminary discussions are essential. We usually discuss, hopefully get to a consensus, and then submit a proposal.