Payout operations · batch planning

Pay a hundred people without fat-fingering it

Paste a recipient list — airdrop, payroll, grants, validator rewards. Every address is checksum-validated against the real SS58 codec, amounts convert to plancks with exact BigInt math, the list is split into atomic utility.batch_all batches sized for the chain limit, fees are estimated from the runtime polynomial, and you download CLI-ready batch files plus the exact quantus batch send commands. This page plans; it never touches the chain or your keys.

Batch format + atomicity: quantus-cli src/cli/send.rs Batch sizing: CLI README airdrop example (Sept 30, 2026) Length fee: runtime polynomial, 100,000 plancks/byte

Step 1 · Recipients

Who gets paid

One recipient per line: <address> <amount in QTC> — space, comma, or tab separated. A header row (address,amount), blank lines, and # comments are skipped. Amounts are decimal QTC (up to 12 places).

Upload list (.txt / .csv) 0 lines

Step 2 · Validation review

Every row, checked

—

Each valid address gets its human checkphrase — the same five-word phrase the quantus CLI prints next to payout destinations — so you can verify recipients out of band.

Line	Recipient	Checkphrase	Amount (QTC)	Plancks	Status
Paste a recipient list above to start the review.

Step 3 · Batch plan

Batches sized for the chain

Transfers per batch Sender wallet name (for the generated commands) Tip per batch (QTC, optional) Signing scheme (signature size → length fee)

Default 256 comes from the Quantus team's own airdrop example (up to 256 transfer(s) each, CLI README Sept 30, 2026). The chain's live limits win: run quantus batch config --limits and match this box to the safe limit it prints.

How the fee floor is computed

This is the length-fee floor only: bytes × 100,000 plancks. It excludes the weight-based fee component, which the CLI quotes exactly before you confirm. Treat the floor as the minimum the sender must hold on top of the recipient total.

Sender balance check

Sender balance (QTC)

Enter the funding wallet's balance to check it covers recipients + fee floor.

Step 4 · Export

Take the plan to the CLI

Batch files use the exact format quantus batch send --batch-file expects: [{"to":"<SS58>","amount":"<plancks>"}, …], amounts as raw smallest-unit integer strings.

Validate a recipient list first.

Run script preview

—

Command reference

quantus batch config --limitsPrint the chain's live safe/recommended batch limits — match the planner's batch size to it.

quantus batch send --from <wallet> --batch-file transfers-batch-1.jsonSubmit one batch. Amounts are raw plancks; the CLI validates them again before signing.

quantus batch send --from <wallet> --batch-file f.json --tip 0.1Optional tip (QTC) per batch extrinsic to prioritize inclusion.

Safety

Read before you run

Atomic batches. The CLI builds utility.batch_all: every transfer in a batch succeeds, or the whole batch fails — no partial payouts. (Asserted by the CLI's own unit test.)
Test with batch 1. Pay the first batch alone, verify it on the explorer, then run the rest.
Never re-run blind. A timed-out or failed submission may still have landed on chain. Check the sender's nonce / the explorer before re-running, or recipients get paid twice.
No passwords on the command line. The CLI reads wallet passwords from a hidden prompt or --password-file — never paste one into a terminal command or a file you share.
Verify checkphrases out of band. Confirm each recipient's five-word phrase with them directly before the run — the phrase is the last line of defense against a pasted wrong address.
This page is a planner. It never signs, never submits, never sees your keys. Execution happens in your own quantus CLI.