OSS Token Distribution (Patrons)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- blockchain
Research direction
No files, tests, or implementation entry points are named. Start by reviewing the Distribution Method and Future Questions sections, then clarify the allocation basis, Merkle distribution automation, and vesting periods; the work is done only once those mechanics and an implementation scope are defined.
Written by the indexing model from the issue text.
Description
In the future OSS tokens may achieve utility outside Dev Protocol like Governance or utility. An excellent way to reward Patrons for supporting projects, when OSS tokens receive exterior use cases, would be to give a fixed percent for Patrons. If treasury holds 5% then 2.5% would be given to Patrons that supported that project.
Distribution Method
Tokens would be distributed based on the same logic as the Geyser liquidity program: the amount of capital and the time staked relative to other Patrons in the pool. The more money and time a Patron provides to a project the more of the allocation they receive.
Benefits
- Patrons join to fund projects they believe in
- Patrons are incentivized to fund projects that will make use of OSS tokens which creates organic incentive model
- Projects not creating use cases or developing are less staked due to the opportunity cost
- This DIP injects immense positive feedback loops without changing the core protocol
Future Questions
- How to automate the Merkle distribution without using snapshots each time
- Vesting periods
- 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 ·
-
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 ·
-
core layers usability
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#47 · 3 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 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 ·