Skip to content

Batch Sending Qubic: Step by Step

If you regularly send QUBIC to the same group of addresses — payroll, a community distribution, splitting funds across your own accounts — sending one transaction at a time wastes real effort and multiplies the chances of a mistake. Batch send handles the whole list at once, reviewed together before anything is confirmed.

Why Batch Send Exists

Most crypto wallets treat every transaction as a one-off: pick an address, pick an amount, confirm, repeat. That works fine for occasional sends, but it breaks down fast once you're managing anything recurring. Consider a small team being paid in QUBIC monthly — without batch sending, that's ten, twenty, or fifty individual transactions, each one a fresh opportunity to mistype an address or enter the wrong amount, and each one costing you time you didn't need to spend. Batch send collapses all of that into a single reviewed, confirmed operation.

Step-by-Step

  1. 01

    Select Batch Send

    Open the Send section and select "Batch Send" (or "Send to Many," depending on the current wallet UI).
  2. 02

    Add recipients

    Add recipient addresses one at a time, or import a list. The app shows which list formats it accepts on the import screen.
  3. 03

    Enter amounts

    Enter the amount for each recipient — amounts can differ per address, so a batch doesn't need to be an equal split.
  4. 04

    Review the list

    Review the full list and total before confirming.
  5. 05

    Confirm

    Confirm the transaction — all recipients are paid out together, in a single transaction.

Saving a Reusable Template

1

Save as Template

After building your recipient list, look for the "Save as Template" option.
2

Name it

Name the template for easy reuse later — something identifiable like "monthly payroll" or "team distribution".
3

Reuse it

Next time, select the saved template instead of rebuilding the list from scratch — you can still adjust amounts before confirming, even with a saved template.

Templates are particularly valuable if your recipient list is long and stable but the amounts change month to month — you get the accuracy benefit of not re-typing every address, while still being able to update figures before anything is sent.

Double-Check Before You Confirm

Batch transactions send to multiple addresses at once, which means a single mistake affects multiple recipients simultaneously — a wrong address in one row is just as easy to miss as it would be in a single send, but the consequences apply across the whole batch. Review the full recipient list and amounts carefully before confirming — transactions on Qubic, like most blockchains, can't be reversed once sent.

A few specific things worth double-checking:

  • Every address is copy-pasted, not manually retyped, wherever possible
  • The total amount across all recipients matches what you actually intended to send
  • No duplicate addresses were accidentally added, unless intentional
  • Any saved template you're reusing still reflects current amounts, not stale figures from last time
  • The recipient count matches what you expect — an accidentally duplicated or dropped row is easy to miss in a long list without counting
Before confirming any batch transaction of meaningful size, read the list out loud, or have someone else glance at it, rather than just scanning it silently.
A Simple Pre-Send Habit Worth Building

This sounds almost too simple to matter, but it's a genuinely effective way to catch the kind of error your eyes slide past when reviewing your own work quickly — a transposed digit in an amount, or an address that's one character off from what you intended.

Common Uses

  • Recurring payroll or contributor payments in QUBIC
  • Distributing rewards or airdrops to a known list of addresses
  • Splitting a balance across your own multiple accounts in one step
  • One-time distributions to a community or group where sending individually would be impractical
  • Refunding or reimbursing a group of people from a shared pool of funds

What Happens If One Recipient's Address Is Invalid

Validate the list before you send. The wallet checks address formatting when you build a batch, so fix anything it flags at that stage rather than relying on how a mixed batch behaves once submitted — send a small test batch first if you are working from a new list.

Batch Size and Fees

We don't publish a fixed recipient cap or fee table here, because both depend on the network conditions and the release you are running. The wallet shows the applicable limits and any cost as you assemble the batch — read that screen before confirming a large send.

Troubleshooting a Failed Batch Send

If a batch transaction doesn't go through as expected:

  • Confirm your wallet is fully synced before retrying — see our balance troubleshooting guide if you're unsure
  • Check that every address in the list is correctly formatted
  • If the issue persists, report it through official channels with the recipient count and approximate time of the attempted transaction

Comparing Batch Send to Individual Transactions

It's worth understanding what you're actually trading off by using batch send instead of individual transactions, beyond the obvious time savings. Individually sent transactions each get their own confirmation and their own moment of review — some users find this reassuring for very high-value or unusual transfers, where slowing down and confirming one thing at a time reduces the chance of error. Batch send optimizes for the opposite case: a set of transfers you're confident in as a group, where the value of consolidation outweighs the value of reviewing each one in isolation. Neither approach is universally correct — matching the tool to the situation is what matters.

A Realistic Example

Consider a small team of five contributors paid monthly in QUBIC. Without batch send, that's five separate transactions each month, each requiring you to locate the correct address, enter the correct amount, and confirm — twenty-five individual confirmations a year, each one a fresh opportunity for a mistake. With a saved batch template, the same monthly payout becomes one list, reviewed once, confirmed once. The addresses don't change month to month, so the risk of a wrong address drops to nearly zero after the first correctly-verified setup, and only the amounts need updating each cycle.

Keeping Templates Organized

If you manage more than one recurring batch — say, monthly payroll and a separate quarterly community distribution — give each template a clear, distinct name rather than generic labels that could be confused with each other. A moment spent naming templates clearly upfront prevents a much more consequential mistake later: accidentally sending one group's payout using another group's saved list.

When Not to Use Batch Send

For a single, high-value, one-off transfer — sending a large amount to one address you've never sent to before — the extra deliberateness of a standard single-recipient send, reviewed on its own without other recipients in the same list, is arguably the more careful choice. Batch send earns its keep on repeated, familiar transfers, not on the rare, unusually large or unfamiliar one.

Batch Send vs. Single Send: Quick Reference

SituationRecommended Approach
Monthly payroll to a known team
Batch send with a saved template
One-time large transfer to a new address
Single send, reviewed carefully on its own
Recurring community distribution
Batch send with a saved template
Splitting your own funds across your accounts
Batch send
First-ever transaction to any address
Single send, to confirm the address works before including it in future batches

A reasonable habit: send a small test amount individually to any brand-new address before including it in a larger batch template for the first time.