Inspect your Safe
Confirm its owners, network and available USDC. The owner signing the execution pays network gas.
Prepare the streaming asset without leaving Bitpont. Your Safe exchanges USDC for its registered USDCx wrapper on the same network.
Ethereum · Base · Arbitrum
Existing Safe 1.4.1 accounts
Choose an operation. Review it with your Safe’s owners.
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.
Saved on this device. A saved proposal is not proof of approval or execution. Refresh its nonce and onchain status before acting.
Confirm its owners, network and available USDC. The owner signing the execution pays network gas.
USDC uses six decimals. Wrapping creates the equivalent amount of USDCx at eighteen-decimal precision. This does not bridge or buy yield.
The Safe grants an exact allowance, upgrades USDC into USDCx and clears the allowance in the same execution batch.
USDCx is the Superfluid wrapper used by this integration. It introduces wrapper and streaming-protocol exposure. Its contract is pinned for each supported network.
No. Create a separate reviewed stream or distribution after the wrapping transaction confirms.
It remains in the Safe. Wrapping does not transfer it to an owner wallet.
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.