Distribute Tokens

You can automate recurring payouts by using a two-phase resolve→execute workflow with per-recipient idempotency. This approach validates distribution plans before execution and persists state after each transfer to ensure safe recovery from partial runs.

Per-recipient idempotency tracks individual transfer states persisted across runs to prevent duplicate token re-sending. This mechanism enables safe recovery from partial runs by skipping contributors who have already received their allocated payouts.

Yes, you can dry-run token distributions to validate plans before executing transfers. The two-phase workflow explicitly separates handle resolution and address validation from the actual execution, allowing you to preview the planned distribution safely.

Yes, a configured Bankr Wallet API key is required to distribute tokens to multiple recipients. The workflow uses this API for explicit balance preflight checks, handle resolution, address validation, and executing the actual token transfers.

The best way to recover from a partial failure during multi-recipient token distribution is persisting distribution state after each transfer. This creates a full audit trail and allows the system to resume payouts without duplicating transfers to completed recipients.

Automated token distribution requires handle resolution during the first phase to validate recipient addresses before executing transfers. This preflight check ensures that the Bankr Wallet API sends tokens only to verified, correctly resolved wallet addresses.