BITPONT TREASURY

Connect the Safe to a distribution pool on Ethereum

Connecting controls the Safe’s pool participation. It does not grant administrator permissions or assign new recipient units. This operation uses the Safe on Ethereum.

EthereumSafe 1.4.1 multisigOne reviewed Safe operation
Open your treasury workspace ↓

Ethereum · ETH for network fees

← All token distributions actions on Ethereum

No transaction prepared.

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

PREPARE AN OPERATION

Connect the Safe to a distribution pool

Advanced Safe execution permissions

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.

Continue a shared proposal

Import a proposal JSON file. You will review its Safe, network, amounts and current approvals before taking action.

Transactions & recovery

HOW CONNECT THE SAFE TO A DISTRIBUTION POOL WORK

A clear path from intent to result.

01

Inspect the account

Inspect the Safe and exact pool address.

02

Review the operation

Review the connection operation for this Safe.

03

Verify the result

Execute after approval and verify the connected participation state.

Connect the Safe to a distribution pool explained.

Does connecting create allocation units?

No. The pool administrator assigns units separately.

Does this make the owner the recipient?

No. The Safe is the participating account; the signing owner only authorizes the operation.

Connect the Safe to a distribution pool on Ethereum — Ethereum · Bitpont Treasury preview.

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 / USDCx

Account, asset and execution

Connecting controls the Safe’s pool participation. It does not grant administrator permissions or assign new recipient units. This operation uses the Safe on Ethereum.

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

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