BITPONT TREASURY

Bulk crypto payments. One reviewed batch.

Pay contributors, settle invoices or distribute operating funds without rebuilding a transfer for every recipient.

Up to 50 distinct recipientsETH, USDC, USDCx or standard ERC-20 tokensEthereum, Base and Arbitrum
Set up your operation ↓

Ethereum · Base · Arbitrum
Existing Safe 1.4.1 accounts

  1. 01Inspect Safe
  2. 02Prepare proposal
  3. 03Collect approvals
  4. 04Review execution

No transaction prepared.

PREPARE AN OPERATION

What should the treasury do?

Recipients

1 of 50 recipients

Exact payment total—

Add the first recipient to begin.

Import or paste a recipient CSV
Up to 50 distinct recipient addresses. No ENS names. Import replaces the current list only when every row is valid.

RETURN TO A REVIEW

Saved proposals

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

Transactions & recovery

HOW BULK PAYMENTS WORK

A clear path from intent to result.

01

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.

02

Agree on one batch

Every recipient and amount is bound to the Safe transaction hash. Owners can exchange the proposal JSON and verify the same nonce.

03

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.

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 →