WAX KitInstall

Summary

Stakes WAX tokens for CPU on a given WAX account by submitting a delegate-bandwidth transaction through the selected API endpoint. The resource handler code is not included in the source pack (the obfuscated entry module only dispatches to it), so details below come 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 set to Custom.
• account (required) — WAX account name to stake CPU for.
• amount (required) — Amount of WAX to stake for CPU (default 1).
• transfer (required) — Whether to transfer ownership of the staked tokens to the account (default false).
• authorization — One or more authorizations, each with an actor, a permission (active, owner, or custom) and a custom permission name when custom is chosen.

Output shape

One output item per input item, with the result of the stake transaction in json.

The exact result fields can't be confirmed from the provided source. If Continue On Fail is enabled, a failed item returns json with success:false, error and details. The node requires the waxKitPrivateKeyApi credential and checks a license key (a Lemon Squeezy lookup, cached for one hour) before running.

Examples

Example 1: Stake 10 WAX to CPU on your own account using the default endpoint.

endpoint=Greymass, account=myaccount, amount=10, transfer=false, authorization actor=myaccount permission=active

Example 2: Stake CPU for another account and give it ownership of the stake.

account=friendaccount, amount=5, transfer=true, authorization actor=myaccount permission=active

Links

• n8n community nodes installation guide