Airdrop Utility
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
- Tech stack
- blockchain
- Domain
- blockchain, documentation
Research direction
Start by reviewing the Airdrop Template and the budget spreadsheets to determine where the client-airdrop table belongs, then inspect the handbook structure for the Execution Lead instructions. Phase 1 is done when the spreadsheet distribution table and handbook guidance are documented; Phase 2 requires a separate design for xDAI data, merkle-root publishing, naming, and claiming.
Written by the indexing model from the issue text.
Description
A utility for distributing client project airdrops to:
- Builders (80% - based on aggregate builder budget split)
- Sourcing Leads (10% - based on commission split)
- Rep-Holders (10% - based on square root of rep balance)
Phase 1: Manual
- Client sends tokens to Execution Lead
- Execution Lead calculates token distribution from Airdrop Template and exports to CSV
- Execution Lead distributes tokens by uploading the CSV to disperse.app
TODO
- add table for distributing client airdrops to the bottom of budget spreadsheets that will have an airdrop
- Add instructions to handbook for Execution Leads
Phase 2: Automated
- App lets the Execution Leads generate and publish the token distribution on-chain
- Pull rep-holder data from xDAI
- Upload distribution as merkle root?
- $project_name.dorg.eth` is generated and pointed to the contract
- Clients send tokens to
$project_name.dorg.eth - Rep-holders can check and claim accumulated airdrops across client projects
- Dominant language
- No language data
- Stars
- 17
- Forks
- 12
- 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 dOrgTech/docs
-
Handbook
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Handbook
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Handbook
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
polkadot-js/api#6279 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
StabilityNexus/Chainvoice#219 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NethermindEth/nethermind#13669 · 1 comment ·
-
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 68/100