Concordium / Concordium/concordium-node
Validator 6 - special case
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 24
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 9
Description
**VM name:**[ubuntu@172.31.48.45](mailto:ubuntu@172.31.48.45)
- [ ] Setup Prometheus with `CONCORDIUM_NODE_PROMETHEUS_LISTEN_PORT=9090` and also I think `CONCORDIUM_NODE_PROMETHEUS_LISTEN_ADDRESS=0.0.0.0`
- [ ] Setup debug logs
- [ ] Have the node version 8.x.
- [ ] 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.
- [ ] Remove validator - 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.
- [ ] Stake is released at the payday after the cooldown
Contributor guide
Research direction
Start by provisioning the listed Ubuntu VM, configuring Prometheus and debug logs, and running a node on version 8.x. Follow the validator and protocol-update checklist; done means the specified stake transitions, reward cutoff, cooldown, and release behavior are all observed after the update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, prometheus
- Domain
- blockchain, observability, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100