oasisprotocol / oasisprotocol/oasis-core

Support restricted use accounts

Open
#2,322 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

c:breaking/consensus c:consensus/cometbft c:staking s:needs adr
Dominant language
Go
Stars
369
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
6

Description

SUMMARY

At genesis block, create way to set tokens locked up from investors, grantees, employees to be used for delegation on the network.

ISSUE TYPE

In order to allow for broader token engagement on the network without creating too much liquidity early on, we'd like to have a way for stakeholders to use the tokens promised to them before they're able to transfer them or sell them on an exchange.

COMPONENT NAME

Consensus layer

ADDITIONAL INFORMATION

when does lockup end? -- example would be a tiered lockup with a certain amount of tokens released at 4 months, 8 months, 12 months.

  • what exactly can be done with locked up tokens -- locked tokens can be delegated and rewards can be earned on those tokens. locked up tokens cannot be sold or transferred.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the consensus layer's genesis-block handling, the only entry point identified in the issue. Clarify the tiered release schedule and permitted operations, then define completion around accounts whose locked tokens can be delegated and earn rewards but cannot be transferred until release.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.