BITPONT TREASURY

USDCx Payment Streams 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 Payment Streams

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 PAYMENT STREAMS WORK

A clear path from intent to result.

01

Prepare the streaming asset

Wrap supported USDC into USDCx. Exact token allowance, wrapping and allowance cleanup are included in the Safe batch.

02

Set a rate

Enter a 30-day amount and check its actual per-second and daily equivalents. Rounding follows the protocol’s integer rate.

03

Manage the commitment

Streams continue until stopped or terminated by the protocol. Maintain available USDCx and its required buffer; stopping needs a separate approved Safe transaction.

Payment streams explained.

Does a 30-day amount stop after a month?

No. It is a convenient rate input, not an end date. This integration does not schedule automatic cancellation.

Can I reduce or stop a stream?

Select Change a USDCx stream or Stop a USDCx stream, enter the recipient and review a new Safe proposal. Already streamed funds are not recovered.

What balance can I unwrap?

Only available USDCx can be unwrapped. Reserved buffers and ongoing streams affect availability. Check current state again before execution.

Is this an unattended payroll service?

The protocol streams after an approved transaction. Bitpont does not run scheduled payroll, maintain a notification service or stop flows automatically.

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.