paritytech / paritytech/testnet-manager
Don't rotate validator session keys if already set
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In the current validator registration process, session keys are systematically rotated and set before registration even if those were already properly set. Following #39, we now have the code to read on-chain session keys and add this check to prevent this often unnecessary step.
Contributor guide
No contributing guide indexed for this repository
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 with the validator registration process and the session-key reading code introduced by #39. Trace where keys are rotated and set before registration, then verify that properly set on-chain keys are left unchanged while missing or incorrect keys still follow the existing registration flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100