bitpontBitpont Treasury Guide: Bulk Payments, Streams & Safe Approvals
Prepare payment runs, collect Safe approvals, manage supported streams and verify which recipients were paid.
On this page
Updated 27 October 2026
Send a Safe payment run
- Inspect the Safe.
Choose a supported network and enter the Safe address. Inspect owners, threshold and balances. Connecting one owner wallet does not satisfy a multi-owner approval threshold.
- Choose the asset and recipients.
Select the supported payment asset or inspect a custom standard token contract. Enter or import address and human-readable amount rows. Review duplicates, exact totals and decimals. A payment run supports up to 500 recipients, split into proposals of at most 50.
- Prepare and review each proposal.
Check every recipient, amount, contract call, Safe nonce and hash. Preparation does not send payments. Collect the required owner approvals, then review execution with fresh Safe state.
- Verify the executed batch.
Check the transaction result and actual transfers before continuing. A partially completed run is not a reason to resend its completed batches. Keep the saved proposal and payment-run records.
Send SOL or supported SPL tokens
Open Solana payments, choose the owning wallet and the supported token or mint. Review up to 500 recipients and the transaction-sized batches the planner creates. Token account creation may add rent costs. Review each batch and retain its signature. A rejected later batch does not reverse earlier confirmed payments. Unsupported token behavior must be resolved before sending.
Streams, distributions and lending
Safe treasury controls also expose eligible USDCx stream creation, changes and stopping, distribution-pool operations and Aave USDC actions on supported networks. A stream rate is an ongoing obligation, not a one-off transfer. Check the recipient, rate units and available balance. Stopping a stream does not reverse amounts already transferred. Distribution units determine proportions and are not themselves token amounts.
Wrapping USDC into USDCx changes the asset you hold. Unwrapping, lending withdrawal and repayment are separate supported actions, each with its own review. Do not treat tokens committed to a loan or stream as freely available for a payment run.
Bounded Safe automation
Open Treasury’s Execution permissions section. Availability depends on an operator-configured deployment of the exact execution module. New authorization can remain disabled while existing rules can still be revoked. A configured address is not proof of an independent audit.
- Inspect and enable.
Select the Safe network and address, then Enable execution module. Bitpont checks the Safe owners, implementation and module bytecode. Prepare the proposal, review its hash, collect owner approvals and review Safe execution. Enabling a module is a powerful permission; use only an independently reviewed deployment.
- Authorize the exact rule.
Choose Authorize an exact rule and enter the rule JSON prepared by your integration operator. Review every target, calldata, native value, precondition and postcondition. Amounts are integer base units. Confirm the executor, activation time, expiry, interval, maximum runs and gas-price cap. The rule supports one to eight calls and one to four required postconditions.
- Collect owner approvals.
Export the verified proposal and share it with the other Safe owners through your chosen channel. They select the same Safe and network, import it on Bitpont, refresh onchain state and review their approval. An approval is not execution. Once the threshold is reached, review Safe execution and wait for finality.
- Stop future runs.
Use the rule ID to prepare Revoke a rule, or choose Disable the module to stop all its future runs for this Safe. Both require the Safe owner threshold. A pending revocation does not prevent a run from being executed first. Previously created approvals and protocol positions remain; manage them separately.
The operator must run and monitor an executor. Saving a proposal does not start a hosted automation service. Calls and limits cannot adapt or refresh quotes automatically. The runs are same-chain; this is not automatic cross-chain liquidation protection. Review exact calldata with a qualified integrator rather than pasting an untrusted rule.
If approval or execution changes
Reinspect the Safe after an owner, nonce or network change. A stored proposal hash is not evidence that it executed. For a submitted transaction, check recovery before preparing a replacement. Do not clear records while a result is unresolved.