New Markets & Native APYs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- blockchain
Research direction
Start with issue #40's Specification and Overview, which propose separate Dev Protocol forks for each New Market. No files, tests, entry points, or acceptance criteria are named; the work is done only when the market-specific APY design and implementation scope are defined clearly enough to guide development.
Written by the indexing model from the issue text.
Description
dip: <#40>
title: <New Markets & Native APYs>
status: WIP
author: Scott G
created: 2021-01-05
Simple Summary
This proposal calls for New Markets (example: Research) to have their own native APY based on DEV staked and assets onboarded.
Abstract
Currently, if a New Market is added to Dev Protocol the assets are lumped together. For a Market's creators this is detrimental because the work of one sector is not equivalent to the work of another. For example, a Youtube content creator vs. an OSS developer. Each Market should have its own Native APY to provide so that the APY places a value on the Market's creator's work. This proposal also prevents the devaluation of work from different Markets, increases Market health, and creates Market APY arbitrage opportunity.
Motivation
This proposal also prevents the devaluation of work from different Markets, increases Market health, and creates Market APY arbitrage opportunity.
Specification
Overview
The feature will be implemented by creating a fork of the Dev Protocol for each New Market.
Copyright
Copyright and related rights waived via CC0.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
MystenLabs/sui#28056 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
filecoin-project/solstice#76 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CypherBoxLLC/Cypher-Box#283 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·