ChainSafe / ChainSafe/canton-extending-mainnet
[P2-E8.4] LSU upgrade runbook
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 14d 10h
- Merged PRs (30d)
- 2
Description
Operator manages logical synchronizer upgrades on the dedicated sync independently of the global sync; purchased traffic preserved per `migrationId`.
**Acceptance criteria:**
- [ ] A dedicated-sync LSU preserves granted traffic (mirrors `LsuTransferTrafficTrigger`)
**Epic:** ChainSafe/canton-extending-mainnet#15
_Source: `docs/planning/extending-mainnet-work-plan.md`_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with docs/planning/extending-mainnet-work-plan.md and trace the LSU upgrade workflow for a dedicated sync. Compare the intended behavior with LsuTransferTrafficTrigger, paying attention to migrationId and the separation from the global sync. Done means the runbook explains the operator steps and the dedicated-sync LSU preserves granted traffic.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100