VOID Local Multibox Nimo Rejoin Operator Runbook v1
Marker: VOID_LOCAL_MULTIBOX_NIMO_REJOIN_OPERATOR_RUNBOOK_V1
Status: operator_runbook_ready
Manual rejoin
Run this only against a local node you administer. The POST asks that node to hand the address to its outgoing connection path and may update local peer state.
curl --fail-with-body --silent --show-error -X POST -H 'content-type: application/json' --data '{"addr":"192.168.1.99:4701"}' http://127.0.0.1:4100/p2p/dial | jq .
Accepted handoff: {"ok":true,"dialing":"..."} means the HTTP handler accepted the address for handoff. It does not prove that canonical address parsing succeeded, a socket was opened, or Nimo connected.
Immediate rejection: {"ok":false,"error":"..."} reports why the request was rejected. Keep the response body, correct the address or local-node problem, and do not retry blindly.
Verify the connection
Check local health, then confirm Nimo appears in the P2P peer snapshot:
curl -fsS http://127.0.0.1:4100/health | jq . curl -fsS http://127.0.0.1:4100/p2p/peers | jq .
Expected Nimo peer id: 042c8b22f14cf343139e9bc806937bf3
Boundary
This runbook is public-safe operator guidance. Its manual /p2p/dial POST uses an existing local peer-state mutation route; the runbook does not enable automatic peer dialing. It does not enable wallet send, money movement, WC settlement, validator admission, public WC self-serve earning, or a public internet mesh claim.
Nimo HTTP and SSH were not observed from Precision during the sealed runtime check.