liftedinit / liftedinit/roadmap
Token "lock out" / frozen funds
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description: A Liftoff Program member has requested a way for funds to be deposited into a Multi-sig account and then have all outbound transfers of tokens be locked until an expiry date and time.
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 tokens in a multi-sig account to be locked until an expiry date so that they can not be transacted.
- Should be achievable via many-rs.
- Should be able to set an expiry date and time for when the tokens are released from lock up.
- Should be able to input the amount token that will be locked up.
- Should be able to input the account address that where the tokens are being locked up in.
- Should be able to transact tokens after they are unlocked after the expiry.
- Should be deployed to dev.
- Should be able to be demoed.
Tasks:
Contributor 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.
Research direction
No files, tests, or entry points are mentioned. Start by locating the many-rs integration and clarifying how multi-sig token locking, expiry, amounts, and account addresses should be represented; done means the feature works through unlock, is deployed to dev, and can be demonstrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100