Token vesting
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
Start by reviewing the many-rs capability and the Streamflow vesting reference linked in the issue. Define the schedule, token, recipient, withdrawal, deployment, and demo requirements, then verify the completed feature on dev against each checklist item.
Written by the indexing model from the issue text.
Description
Description: A Liftoff Program member has requested a way for automated token vesting or the ability to withdraw a maximum up to the vesting amount.
Notes: If we did this then technically we could make a user a multi sig that is a 1 of 1 but the funds themself would be governed by the expiry and vesting schedule, the act of actually withdrawing would be up to the user. By virtue of it being a 1 of 1 and not owned by the distributor the funds are in complete custody of the recipient with no clawback of funds potential. This feature supports Web3 Treasury management via Alberto.
Story ROI: This feature supports Web3 Treasury management via Alberto that was requested by a customer and is valuable to Lifted internally as well.
As a company, I want the Recipient to receive scheduled releases of tokens at an increment of time so that incentives are aligned.
- Should be achievable via many-rs.
- Should be able to set a vesting schedule for when the tokens are released (ex. monthly, weekly, daily, etc.).
- Should be able to input the token that will be released.
- Should be able to input the number of tokens that will be released on the set schedule dates.
- Should be able to set the vesting schedule's total duration (when it ends).
- Should be able to input the Recipient's address that will receive of the tokens.
- Should be able to transact tokens after they are received by the Recipient unless "locked" or frozen.
- Should be deployed to dev.
- Should be able to be demoed.
Resource: https://streamflow.finance/vesting
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 liftedinit/roadmap
-
gwen ui
Difficulty 3/5 1-2 days Newbie friendliness 35/100
liftedinit/roadmap#115 ·
-
gwen ui
Difficulty 3/5 1-2 days Newbie friendliness 35/100
liftedinit/roadmap#114 ·
-
Gwen - ContactsOpenbackend gwen story ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#113 ·
-
gwen ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#111 ·
-
gwen ui
Difficulty 4/5 3-5 days Newbie friendliness 35/100
liftedinit/roadmap#108 ·
All issues in liftedinit/roadmap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Arbiter-xyz/arbiter-contract#179 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
beginner hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
hiero-ledger/hiero-sdk-js#4509 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Orbit-xyz/orbit-docs#14 ·