BITPONT TREASURY

USDCx Distribution Pools on Ethereum | Bitpont

Use the configured Superfluid contracts on Ethereum. The Safe's owners approve each change. USDCx balances and reserved buffers are checked before execution.

EthereumSafe 1.4.1 multisigReviewed Safe proposals
Set up your operation ↓

Ethereum · ETH for network fees

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

Capabilities depend on the selected network.

No transaction prepared.

PREPARE AN OPERATION

USDCx Distribution Pools

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

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 DISTRIBUTION POOLS WORK

A clear path from intent to result.

01

Create the pool

The Safe becomes administrator. New pools use nontransferable units and admin-only distribution permissions.

02

Assign recipient units

Units are relative allocation weights, not token amounts. Set each recipient’s units in an approved operation before distributing.

03

Fund and manage

Distribute an amount, start or update a pool stream, stop funding, or claim and connect this Safe’s own eligible pool participation.

Distribution pools explained.

Does setting zero units reclaim payments?

No. It removes future allocation under those units; it does not reverse money already distributed.

Can I combine pool creation and every allocation in one click?

Pool creation returns a new address. Use that verified address for subsequent unit-setting and funding proposals. Each operation is reviewed separately.

Who controls the pool?

This integration creates a pool administered by the selected Safe. Existing modules and guards can affect the Safe’s behavior.

How do I exit?

Stop active pool streams and claim eligible proceeds. Unwrap available USDCx or prepare a separate payment from the Safe.

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.

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

ETHEREUM / USDC / USDCx

Account, asset and execution

Use the configured Superfluid contracts on Ethereum. The Safe's owners approve each change. USDCx balances and reserved buffers are checked before execution.

Funds are held by
Safe 1.4.1 multisig
Network fees are paid in
ETH
Native USDC contract
0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48

Balances and execution conditions are checked again before signing. A saved page is not a balance or liquidity quote.