BITPONT TREASURY

Invalidate current Safe proposals on Polygon

An owner’s onchain approval cannot be revoked directly. Consuming the nonce prevents other proposals with that nonce from executing. This operation uses the Safe on Polygon.

PolygonSafe 1.4.1 multisigThreshold-approved nonce invalidation
Open your treasury workspace ↓

Polygon · POL for network fees

No transaction prepared.

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

PREPARE AN OPERATION

Invalidate current Safe proposals

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 INVALIDATE CURRENT SAFE PROPOSALS WORK

A clear path from intent to result.

01

Inspect the account

Inspect the Safe’s current nonce and approved proposals.

02

Review the operation

Review the no-op proposal at that exact nonce.

03

Verify the result

Collect the threshold, execute and verify the nonce advanced.

Invalidate current Safe proposals explained.

Can I undo an already executed transfer?

No. This operation invalidates unexecuted proposals at the current nonce; it does not reverse transactions.

Does one owner’s approval cancel everything?

No. The invalidation requires the Safe’s approval threshold and a successful execution at the intended nonce.

Invalidate current Safe proposals on Polygon — Polygon · 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.

POLYGON / Safe nonce

Account, asset and execution

An owner’s onchain approval cannot be revoked directly. Consuming the nonce prevents other proposals with that nonce from executing. This operation uses the Safe on Polygon.

Funds are held by
Safe 1.4.1 multisig
Network fees are paid in
POL
Required Safe version
1.4.1

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