Concordium / Concordium/concordium-node
Validator 7 - special case
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 24
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 9
Description
**VM name:** [ubuntu@172.31.16.46](mailto:ubuntu@172.31.16.46)
- [ ] Have the node version 8.x.
- [ ] setup debug logs
- [ ] Setup Prometheus with `CONCORDIUM_NODE_PROMETHEUS_LISTEN_PORT=9090` and also I think `CONCORDIUM_NODE_PROMETHEUS_LISTEN_ADDRESS=0.0.0.0`
- [ ] node catches up
- [ ] Register validator that will have a large stake enough to be finalizer.
- [ ] Make sure that the validator is receiving rewards.
- [ ] Wait several paydays.
- [ ] Reduce validators stake - ensure that validator is in cooldown at the time when PU takes in effect
- [ ] **WAIT FOR PROTOCOL UPDATE**
- [ ] After protocol update verify:
- [ ] Stake goes to pre-pre cooldown
- [ ] Rewards are being received for the next payday but not after that.
- [ ] At the snapshot of the payday, stake is in pre-cooldown.
- [ ] At the payday stake goes to cooldown.
- [ ] Move the stake to delegation to a pool
- [ ] At the next payday:
- [ ] Account is delegating
Contributor guide
Research direction
No source files or automated tests are named. Start with the Ubuntu VM checklist, node debug logging, and Prometheus setup, then run the validator stake and protocol-update scenario. Done means every post-update stake, reward, cooldown, and delegation check is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, prometheus
- Domain
- blockchain, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100