BITPONT TREASURY

Claim the Safe’s pool proceeds on Base

This operation claims for the Safe itself. It does not redirect another recipient’s entitlement to the owner wallet. This operation uses the Safe on Base.

BaseSafe 1.4.1 multisigOne reviewed Safe operation
Open your treasury workspace ↓

Base · ETH for network fees

← All token distributions actions on Base

No transaction prepared.

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

PREPARE AN OPERATION

Claim the Safe’s pool proceeds

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 CLAIM THE SAFE’S POOL PROCEEDS WORK

A clear path from intent to result.

01

Inspect the account

Inspect the Safe and pool participation.

02

Review the operation

Review the claim with the Safe as recipient.

03

Verify the result

Execute and refresh the Safe’s available USDCx balance.

Claim the Safe’s pool proceeds explained.

Who receives the claim?

The Safe receives proceeds belonging to its own pool participation.

Can I claim for an unrelated address?

This tool binds the claim to the Safe, rather than an arbitrary recipient.

Claim the Safe’s pool proceeds on Base — Base · 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.

BASE / USDCx

Account, asset and execution

This operation claims for the Safe itself. It does not redirect another recipient’s entitlement to the owner wallet. This operation uses the Safe on Base.

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

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