nspcc-dev / nspcc-dev/neofs-dev-env
Use different keys for side and main chain validators
Open
Nobody has claimed this yet.
enhancement
I3
S3
U4
- Dominant language
- Makefile
- Stars
- 10
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Side chain validators won't be main chain validators in most of the cases. With different keys there won't be any extra GAS income for alphabet node in main chain, so we will be able to find economy issues faster.
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
The issue proposes using distinct keys for side-chain and main-chain validators to make GAS-related economy issues easier to detect. It names no files, tests, or entry points, so first identify where validator keys and chain roles are configured; done would require the two validator groups to use different keys without breaking the local development environment.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100