oasisprotocol / oasisprotocol/oasis-core
Store TokenSymbol in consensus staking state
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Store TokenSymbol and TokenValueExponent in consensus staking state. These two staking genesis parameters are currently always read from genesis and are not stored in the consensus state.
Storing these in consensus state would make it consistent with other parameters and would also enable the runtime to query these from the consensus state (and potentially in future updating these on-chain).
Also check if there are any others such parameters that are not stored in the state.
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
Start by locating the consensus staking state and the genesis handling for TokenSymbol and TokenValueExponent. Compare other staking genesis parameters to determine which are persisted in consensus state. Done means these two values are stored and queryable there, with any additional missing parameters identified and addressed as appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100