Concordium / Concordium/concordium-node
Delegator 5 - special case
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 24
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 9
Description
- [ ] Have delegator in active pool
- [ ] Delegator is receiving rewards
- [ ] Remove delegator - ensure that delegator 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
No file or test entry point is named; start by reviewing the delegator lifecycle and the protocol update referenced in this checklist. Reproduce the active-pool, removal, cooldown, snapshot, payday, reward, and release steps, then mark the issue done only when every post-update expectation is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100