Create the pool
The Safe becomes administrator. New pools use nontransferable units and admin-only distribution permissions.
Allocate supported treasury funds by relative units instead of repeatedly calculating separate payouts. Manage pool funding and recipient participation inside Bitpont.
Ethereum · Base · Arbitrum
Existing Safe 1.4.1 accounts
Saved on this device. A saved proposal is not proof of approval or execution. Refresh its nonce and onchain status before acting.
The Safe becomes administrator. New pools use nontransferable units and admin-only distribution permissions.
Units are relative allocation weights, not token amounts. Set each recipient’s units in an approved operation before distributing.
Distribute an amount, start or update a pool stream, stop funding, or claim and connect this Safe’s own eligible pool participation.
No. It removes future allocation under those units; it does not reverse money already distributed.
Pool creation returns a new address. Use that verified address for subsequent unit-setting and funding proposals. Each operation is reviewed separately.
This integration creates a pool administered by the selected Safe. Existing modules and guards can affect the Safe’s behavior.
Stop active pool streams and claim eligible proceeds. Unwrap available USDCx or prepare a separate payment from the Safe.
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 →