Concordium / Concordium/concordium-node
Validator 10 - special case
- Dominant language
- Haskell
- Stars
- 108
- Forks
- 24
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 9
Description
**VM name:** [ubuntu@172.31.16.49](mailto:ubuntu@172.31.16.49)
Run the old node, catch up half way and update the node to version 7.x before Protocol Update. Notice that the node should still be catching up when PU takes the effect.
- [ ] Install the node version 7.0.5
- [ ] Set the node up for Stagenet, enable debug logs.
- [ ] Setup Prometheus with `CONCORDIUM_NODE_PROMETHEUS_LISTEN_PORT=9090` and also I think `CONCORDIUM_NODE_PROMETHEUS_LISTEN_ADDRESS=0.0.0.0`
- [ ] Start the node and start to catch up
- [ ] Update the node to version 7.x before Protocol Update but the node should still be catching up while PU is in effect.
- [ ] **WAIT FOR PROTOCOL UPDATE**
- [ ] After protocol update verify:
- [ ] Node is still catching up.
Contributor guide
Research direction
Follow the checklist in this issue: install node version 7.0.5, configure Stagenet and Prometheus with the listed settings, then start catch-up before updating to version 7.x. Wait for the Protocol Update and verify that the node is still catching up afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, prometheus
- Domain
- blockchain, distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100