BITPONT TREASURY

Safe Bulk Payments on Avalanche | Bitpont

Each Avalanche execution contains at most 50 recipients. The Safe holds the payment asset; the executing owner needs AVAX on Avalanche for gas.

AvalancheSafe 1.4.1 multisig500 recipients · 50 per batch

Set up your operation ↓

Avalanche · AVAX for network fees

01Inspect Safe
02Prepare proposal
03Collect approvals
04Review execution

01 / YOUR SAFE

Connect the right treasury

Capabilities depend on the selected network.

Connect an owner wallet and enter your existing Safe. Funds belong to the Safe; the connected owner pays network gas.

No transaction prepared.

PREPARE AN OPERATION

Safe Bulk Payments

ActionPayment asset

Recipients

1 of 500 recipients

Find a recipient

Exact payment total—

Add the first recipient to begin.

Import or paste a recipient CSV

Address and amount, one recipient per line

Import CSV file

Up to 500 distinct recipient addresses. No ENS names. Import replaces the current list only when every row is valid.

Other networks and operations remain available in the complete Treasury history.

Payment runs

Up to 500 recipients, split into transactions of at most 50 payments. Each transaction needs its own Safe approvals and gas. Completed batches stay recorded; an unresolved batch blocks the next one.

Other networks and operations remain available in the complete Treasury history.

RETURN TO A REVIEW

Saved proposals

Filter proposals

Saved on this device. A saved proposal is not proof of approval or execution. Refresh its nonce and onchain status before acting.

Advanced Safe execution permissions

Transactions & recovery

HOW SAFE BULK PAYMENTS WORK

A clear path from intent to result.

Build your recipient list

Add editable recipient rows or import a CSV. Fix duplicate addresses and amount errors before preparing. Save an unfinished draft on this device or export valid recipients for review.

Review one transaction at a time

A payment run is split into batches of at most 50 recipients. Each has an exact Safe hash, fresh nonce, owner approvals and separate gas cost.

Execute and reconcile

After the owner threshold is met, review the transaction and gas before signing. Bitpont checks the Safe execution event, not just the outer transaction receipt.

Safe bulk payments explained.

Is this a bulk transfer from my personal wallet?

This tool spends funds held by an existing Safe 1.4.1 multisig. The connected owner wallet pays gas. Use Portfolio asset actions for supported personal-wallet transfers.

Can I upload a payroll spreadsheet?

Export a CSV with address and amount columns. Names, formulas, ENS names and extra columns are not accepted. One asset is used per batch; totals retain exact token precision.

Does batching guarantee lower fees?

No. Cost depends on the network and calls. Owner hash approvals are separate onchain transactions. Review the execution estimate rather than assuming a saving.

What if one transfer fails?

The batch uses Safe MultiSendCallOnly when it contains multiple calls. A reverted call reverts that execution batch. A nonstandard token can instead return false without reverting. Bitpont checks transfer results before execution and exact custom-token Transfer events afterward; unresolved delivery must be reconciled before any retry.

KEEP EXITS AVAILABLE

Keep the exit available.

Withdraw supplied USDC or reduce variable debt from the same Safe. Withdrawals depend on available liquidity and the Safe’s collateral health. Lending supports the existing USDC reserves on Ethereum and Base.

Streams keep paying until they are stopped or the protocol terminates them. Keep sufficient USDCx for ongoing payments and protocol buffers. Safe owner approvals take time; do not wait for the balance to run out.

Stop a direct payment stream or pool stream, then unwrap the available USDCx balance. Claimed distribution funds remain in the Safe until a separate payment or unwrap is approved.

New pools use nontransferable units and admin-only distribution. Pool ownership, balances, units and fees are read again before execution. Safe modules and guards can impose additional behavior or permissions.

Plan the next move →Prepare assets on Ethereum →Wallet balances & asset tools →

These tools use your selected wallet. Safe assets require a Safe-approved operation; the owner wallet and Safe have separate balances.

AVALANCHE / AVAX, USDC & ERC-20

Account, asset and execution