Distribute Tokens

Automating token distribution requires per-recipient idempotency to prevent duplicate sends on a given day. This Skill persists transfer state keyed by list, recipient, and date, ensuring each contributor receives tokens exactly once per scheduled run.

Previewing token distribution before executing transfers is done using a dry-run mode. This builds a full plan showing resolved addresses and balance readiness without moving tokens, allowing safe verification of the entire execution path.

Recovering an interrupted token distribution from a partial run is handled through progressive state persistence. Because each transfer step saves its state, resuming the run skips completed recipients and continues safely without duplicating transfers.

Resolving contributor handles to wallet addresses automatically is supported via the Bankr Agent API. During the RESOLVE phase, the Skill builds a safe execution plan by mapping handles to addresses and performing preflight balance checks.

Configuring contributor lists for automated token payouts is done by populating the memory/distributions.yml file. This configuration-driven approach defines recipient lists, amounts, and handles that the Skill reads to plan and execute transfers.

The Bankr Wallet API supports safe two-phase token transfers through a RESOLVE then EXECUTE workflow. The first phase validates addresses and balances, while the second phase performs the transfers with state persistence after each step.