---
# System prepended metadata

title: Untitled

---

**hDAO vote ideas** to amplify original creators, punish bad actors and giving collectors a voice

- basic idea: **hDAO owners can give hKARMA** to users by upvoting or downvoting other users
- hDAO holders are **eligible to vote** if their hDAO holdings are more than 0.1% of all hDAOs in existence
- a **voting cycle** is 1024 blocks of the tezos blockchain (that's ~16 hours or so). The lenght of the cycle could be **adjusted by later hDAO govt vote**
- an eligible hDAO voter has the **right to upvote** 50 users and the **right to downvote** 50 users per cycle (these numbers could be adjusted)
- a vote of a hDAO holder is **weighted with his hDAO ownership** percentage: eg: 1 (basic vote) x 0.75 (if he holds 0.75 % of all hDAOs) = 0.75
- optionally a hDAO owner's vote could be additionally **amplified by their own hKARMA**: hDAO vote (0.75) * (hDAO owner's hKARMA * 0.01)
- if the hDAO holder has **negative hKARMA** his vote should decrease in weight
- if the hDAO holder has **positive hKARMA** his vote will inrease in weight
- **hKARMA per user** is then calculated like this: sum of all hDAO votes received + hKARMA of last cycle
- **filtering on hKARMA**: once hKARMA is in place, works from users with a negative hKARMA of less than -X won't show up in the feed (and collction button is deactivated)
- **new feeds** could be created, taking hKARMA into consideration
- a **minting cooldown** could be established: users with good hKARMA can upload more often than those with no or negative hKARMA
- **upvoting and downvoting costs gas** as the votes will be stored onchain
- **frontend**: ideally only eligible users would see an upvote downvote button after they synced and if they have votes to spend



so:
```
basic_vote = 1
vote_eligibility = if hDAO_on_account is >= 0.1% of all_hDAO
hDAO_vote_weight = (all_hDAO/100) * hDAO_on_account
hKARMA_vote_weight = hKARMA_on_account * 0.01
final_vote_weight = hDAO_vote_weight + hKARMA_vote_weight
final_vote = 1 * final_vote_weight
number_of_upvotes_per_cycle = 50
number_of_downvotes_per_cycle = 50
neg_hKARMA_threshold = -5
hDAO_vote_cycle_lenght = 1024 blocks
```
Take into account that in the future, hDAO tokens can be openly traded on DEX like quipuswap or Dexter, maybe on hicetnunc? 

Maybe we sould also run some simulations to see how the numbers play out...

To store and process this data as efficient as possible, there might be necessary changes or adjustments to be considered. Let me know what you think. rgds, djangobits