• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Honey DAOHoney DAOby0x654750C0643097E242651270136e9fF8343e89d1haikukoten.lens

How should we remove inactive members?

Voting ended over 4 years agoSucceeded

As you know that ~30% of the HoneyDAO members have been active, which lead to problems like not reaching quorum. Upon careful consideration, I have framed the following parameters to remove inactive members. Members will be removed in batches, with each batch having unique parameters to replace inactive members with active members. If the proposal passes, members who meet these given criteria will be removed:-

  1. Never voted in Snapshot, (if no one comes in this filter, see 2.) (https://bafybeibgjfmgmgcs4wuigvtu7bptegcqxas3ln4xpd7czz7o2satuopb5e.ipfs.infura-ipfs.io/)
  2. Anyone who didn’t vote in the last 5 closed proposals (https://bafybeih4gw7d7k4nsk2dnecbi2otdjgq3erx3aboixigzyqpfiaqdzwvay.ipfs.infura-ipfs.io/)

You have the following options:-

  1. Remove the members who have never voted in Snapshot
  2. Remove anyone who didn’t vote in the last 5 closed proposals
  3. Do not remove any members

I have created a post on post-purge - https://hive.honeydao.com/t/post-purge-adds-removes-and-ex-member-support/247 where I have mentioned how HoneyDAO will help invested ex-members post purge. Removed members can be added if the DAO wishes on adding them for whatever reason.

Once the proposal passes, a new token with updated features will be up, members will not be required to do anything during the process. Snapshot will be updated with the contract address. The contract will be in Polygon. A multisig will be created with some of the core members as owners. The multisig will be the only owner of the contract, hence can add or remove members. The multisig will also be used as a Treasury in the Polygon network.

Off-Chain Vote

Members never voted in Snapshot
49 68.1%
Didn't vote in last 5 proposal
23 31.9%
Do not remove member
0 0%
Download mobile app to vote

Timeline

Jul 19, 2021Proposal created
Jul 19, 2021Proposal vote started
Jul 23, 2021Proposal vote ended
Oct 26, 2023Proposal updated