Quadratic Voting: Burning DEV
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- blockchain
Research direction
Begin by reviewing the repository's existing quadratic-voting and DEV-token contracts, then determine how the proposed escrow and non-transferable voting rights fit the current design. Done means the contract behavior, vote calculation, DEV burning, and user interface are specified and covered by tests; the issue names no files or test entry points.
Written by the indexing model from the issue text.
Description
Proposal
Allow voters in Dev Protocol's Quadratic voting process to buy additional votes by sending DEV to a smart contract which then returns votes and burns received DEV.
Overview
Dev Protocol currently uses Quadratic voting for governance. Under Quadratic voting individuals buy votes for their preferred alternative, paying the square of the number of votes purchased. Quadratic cost uniquely makes the marginal cost proportional to votes purchased, encouraging voting proportional to the value and thus maximizing welfare.
Incentives
-
Large DEV holders will burn DEV to receive additional votes which should encourage them to maximize the protocol's value in order to receive a return on investment of their burned DEV. This will diminish attacks through governance.
-
Dev Protocol creates another token sink which reduces the effects of inflation.
Technical Implementation
Escrow contract that holds non-transferrable voting rights. Users transfer DEV to receive voting rights. Escrow then burns DEV received. Interface shows user how many additional votes they'll receive for DEV sent.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dev-protocol/DIPs
-
priority - high tokenomics
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#76 · 4 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
dev-protocol/DIPs#61 · 2 reactions ·
-
layers
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#52 · 2 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
dev-protocol/DIPs#50 · 28 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
dev-protocol/DIPs#48 · 13 comments ·
All issues in dev-protocol/DIPs
Similar issues
-
removeToken
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cowprotocol/token-lists#1514 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Merit-Systems/x402scan#1217 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
MystenLabs/sui#28056 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
foundry-rs/starknet-foundry#4598 ·