feat(consensus): consensus node add command
Maintainers usually reply within 1 day
@leninmehedy is already working on this.
Since Aug 22, 2026.
Assessment
This issue has not been assessed yet.
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 <N> --account-id <A> [--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
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hashgraph/solo-weaver
-
ci: pin Go version in Build and Unit Test workflows (>=1.26.6 floats to 1.27.2 and breaks golangci-lint)Possibly taken @leninmehedy claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
hashgraph/solo-weaver#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hashgraph/solo-weaver#1248 ·
Maintainers usually reply within 1 day
-
Design
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hashgraph/solo-weaver#1118 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hashgraph/solo-weaver#879 ·
Maintainers usually reply within 1 day
-
Improvement Story
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hashgraph/solo-weaver#864 ·
Maintainers usually reply within 1 day
All issues in hashgraph/solo-weaver
Similar issues
-
unbounded value for n in `/v1/logs` can panic/OOMPossibly taken A pull request linked to this issue is open or already merged. Opensmall item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
canonical/pebble#1127 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 89/100
open-policy-agent/opa#9366 · 1 reaction ·
Maintainers usually reply within 1 day
-
defect
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nats-io/nats-server#8752 ·
Maintainers usually reply within 1 day
-
enhancement needs-acceptance wg/router-models-inference-runtime
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vllm-project/semantic-router#5015 · 1 comment ·
Maintainers usually reply within 1 day
-
fileserver: precompressed sidecar's Content-Encoding and Content-Length end up on error responsesPossibly taken @NitinKumar004 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
caddyserver/caddy#8204 ·
Maintainers usually reply within 1 day