Nano Node RPCInstall

Summary

Create and sign a Nano block using either a wallet account or a private key. Choose the block type and provide the account’s final raw balance, representative, and previous block hash; the node requires enable_control = true.

Inputs

• Block Type (required) — Select State, Send, Receive, or Change.
• Balance (required) — The account’s final balance as a decimal integer in raw units. The UI notes that a balance lower than the previous balance is treated as a send subtype.
• Representative (required) — Nano account address to use as the block’s representative.
• Previous (required) — Previous block hash for the account, or 0 for its first block.
• Wallet — Wallet ID containing the account to create the block for.
• Account Address — Account address to create the block for when using a wallet.
• Private Key — Private key to sign the block directly instead of specifying a wallet and account. Providing it grants control over that account.
• Source — Source send block hash for a receive block.
• Destination Address — Recipient account address for a send block.
• Link — Alternative to Source and Destination: use the recipient public key for a send, source block hash for a receive, or 0 for a representative-only change.
• Work — External work value as a 16-digit hexadecimal string.
• Difficulty — Optional work difficulty threshold.
• Work Version — Optional work version string; the UI documents work_1 as the default.
• JSON Block Format — Whether to return block contents as a JSON object instead of a JSON string; defaults to true.
• Options — Request timeout in milliseconds (default 15000, range 1000–600000) and maximum retries for transient RPC failures (default 2, range 0–10).

Output shape

A single result from the Nano node RPC create-block operation.

The source pack exposes the createBlock RPC call but omits its implementation body, so the exact response fields and whether the JSON Block Format option changes the returned shape cannot be confirmed. The operation-scoped properties declare the JSON format option; the node configuration must have enable_control = true.

Links

• n8n community nodes installation guide