Node

These commands help you answer two questions:

1. “Can the CLI reach the daemon?”
2. “Is the node actually ready to do Lightning/RGB work?”

Basic checks

rgbldk node version
rgbldk node health
rgbldk node ready
rgbldk node status

Tips:

• node health is a quick “API is alive” check.
• node ready is stricter and prints sub-checks (useful when something is not ready).
• node status is a richer status dump.

Get the node_id (you will paste this later)

rgbldk --output json --pretty node id

Example output:

{ "node_id": "03431a20a8ffdc8b0...a4af6de0bd" }

Copy the node_id value.

Get the P2P listen address (you will paste this later)

rgbldk node listen

Example output:

127.0.0.1:61452

Copy the full host:port.

Lock / unlock (local keystore)

If your node is locked, many commands will fail until you unlock it.

Unlocking usually requires a passphrase. This is the “stdin” form (good for scripting):

printf '%s\n' '<PASSPHRASE>' | rgbldk --yes node unlock --passphrase-stdin

Lock again:

rgbldk --yes node lock

unlock-hosted (when control server is separate)

If you are using a hosted control server, the unlock flow looks like:

printf '%s\n' '<CONTROL_TOKEN>' | rgbldk node unlock-hosted \
  --control-connect http://127.0.0.1:<PORT> \
  --control-token-stdin

If you are not sure which unlock mode you need, start by running rgbldk node status and read the error.