WAX KitInstall

Summary

Unstakes WAX from CPU and NET on a WAX account by submitting an undelegatebw action to the blockchain. The resource-handler code that sends the transaction is not in the provided source, so behavior is inferred from the declared properties.

Inputs

• endpoint (required) — WAX API endpoint: Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
• customEndpoint — Custom API URL. Shown only when the endpoint is Custom.
• account (required) — WAX account name whose resources are unstaked.
• unstakeCpu (required) — Amount of WAX to unstake from CPU. Defaults to 0.
• unstakeNet (required) — Amount of WAX to unstake from NET. Defaults to 0.
• authorization — One or more authorizations. Each has an actor, and a permission of active, owner or custom. A custom permission takes a name.

Output shape

One output item per input item. The result of the unstake transaction is expected, but its exact shape is defined in code that was not provided.

The node needs WAX Kit private key credentials (waxKitPrivateKeyApi). It also checks a license key, which is validated against Lemon Squeezy and cached. With Continue On Fail enabled, a failed item returns json with success false, error, and details. Otherwise the error stops the workflow. The unstaked WAX goes into the refund queue and is typically claimable only after the unstaking delay, so a separate Refund operation is needed.

Examples

Example 1: Release 100 CPU and 50 NET from an account

Endpoint Greymass; Account myaccount11; Unstake CPU 100; Unstake NET 50; Authorization actor myaccount11, permission active.

Example 2: Unstake only CPU

Account myaccount11; Unstake CPU 25; Unstake NET 0.

Links

• n8n community nodes installation guide