In this guide
What this covers
Paying fourteen people one transaction at a time is fourteen chances to fat-finger an address. Batching collapses that into one signature and one review surface. This guide covers running the batch and reading the review before you sign.
Before you start
- A funded treasury balance on the network you are paying from.
- Your recipient list. ENS names, Base names, saved labels, and raw addresses can be mixed freely.
1. Name the list, not the addresses
Pay the August contributor list from my Base treasury — 14 recipients, USDC.Maren resolves names against your address book and reports every resolution. Anything it cannot resolve blocks the batch rather than being quietly skipped.
2. Review the table before the total
The total is the least useful number here. Work the table:
| Check | What to look for |
|---|---|
| Count | Matches the list you intended to pay |
| Resolution | Every row resolved, none unresolved |
| First-time flags | Each new address is one you actually expect |
| Amounts | Spot-check the largest two or three rows |
3. Sign once
The batch is atomic. All fourteen transfers land together or none do — there is no partial payout to reconcile afterwards, which is the entire point of batching for payroll.
The first-time recipient flag exists because a wrong address that resolves cleanly is the failure mode that actually costs money. Treat every flag as a deliberate confirmation.
4. Keep the receipt
Maren returns a per-recipient record with amounts, addresses, and transaction hashes — exportable, and the artifact your finance process wants.
Tips
- Save recurring recipients with labels. Reviewing names is far more reliable than reviewing hex.
- Run the same batch on testnet first when the list is new.
- Driving payroll from your own system? The same flow is available over the API with the identical review payload.
Troubleshooting
One address will not resolve. Usually an expired name or a typo'd label. Fix the entry; do not substitute a raw address you have not verified.
Batch rejected for insufficient balance. The check includes the network fee. Top up, or trim the batch.
The controls behind this workflow
- Every address is resolved and shown before signing; unresolved entries block the batch.
- First-time recipients are flagged explicitly rather than folded into the total.
- The batch is atomic — either all transfers land or none do.
Guides describe how to operate Maren. They are not financial advice, and figures shown are illustrative. You approve every transaction before it is signed.