hashgraph / hashgraph/solo-weaver
feat(consensus): consensus node add command
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
Implement `solo-provisioner consensus node add` command to add a new consensus node to an existing running network.
Parent epic: #408
Depends on: #1044, #1064
### Context
Adding a node to a running network is distinct from initial install. It likely involves updating the network roster (via NetworkGenesis or a roster update mechanism) and creating a new ConsensusCapsule that joins the existing network. Full design TBD — this ticket is a placeholder to track the requirement.
### Scope (preliminary — design TBD)
- `solo-provisioner consensus node add --node-id --account-id [--namespace] [--orbit]`
- Create ConsensusCapsule for the new node
- Update network roster to include the new node
- Handle state sync / catch-up for the new node
- Config CRs for the new node (may reuse existing or create new)
### Open questions
- How does the roster update work for a running network?
- Does the new node need a state snapshot to fast-sync?
- Is this a DAB (dynamic address book) operation?
### Acceptance Criteria
- [ ] Design finalized
- [ ] New node added to running network
- [ ] Roster updated
- [ ] New node catches up and participates in consensus
Contributor guide
Assessment
This issue has not been assessed yet.