Multi-Sig Spending Policy Setter

WHAT IT DOES

Multi-Sig Spending Policy Setter is a developer tool that lets you set, update, or remove spending policies for multisig wallets. Spending policies define rules for how multisig wallets can spend funds — including per-transaction limits for specific tokens, time-based restrictions, and other constraints that enhance security and governance. This tool reads the current policy state from the policy contract, then allows you to set a new policy with token-specific limits, update existing limits, or remove the policy entirely. The tool provides a preview of the policy contract, multisig address, action, token limits, time restrictions, and estimated gas cost before you execute, enabling secure and transparent policy management.

HOW TO USE

Connect your EVM wallet via the BGWallet bridge. Enter the spending policy contract address and the multisig wallet address. Select the action — Set Spending Policy, Update Policy Limits, or Remove Policy. For set or update actions, enter token limits in the format "token:limit, token:limit" (e.g., "0x...:1000, 0x...:5000"). Optionally, set a time restriction in seconds. Click "Preview Policy" to see the policy contract, multisig address, action, token limits, time restriction, and estimated gas cost. Review the details carefully. Click "Set Policy" to sign and broadcast the transaction. The tool provides a transaction hash for tracking and confirms the policy update.

TECHNICAL MECHANISM

The tool reads the current policy state from the policy contract using view functions like `getPolicy(multisig)` or `getTokenLimits(multisig)`. It validates that the token addresses are properly formatted and that the limits are positive numbers. When executing, the tool encodes a transaction to the policy contract's management functions — typically `setPolicy(multisig, tokens, limits, timeRestriction)`, `updatePolicy(multisig, tokens, limits)`, or `removePolicy(multisig)`. The tool uses the contract's ABI to encode the call and submits it via the connected wallet. The entire operation is atomic — if the policy update fails, the transaction reverts and the policy remains unchanged. The tool estimates gas using `estimateGas` and displays the estimated cost before execution.

WHAT IT CANNOT SEE

This tool cannot guarantee that the spending policy will be enforced by all dApps or that the limits will remain accurate if the multisig implementation changes. Different multisig implementations have different policy enforcement mechanisms — some may not support policy-based restrictions at all, while others may use different interfaces. The tool cannot predict upgrades to the policy contract or the multisig contract that may change the policy management interface. Additionally, the tool cannot verify that the dApps you use will respect the spending limits. Always test policies with the specific multisig implementation and dApps you intend to use. This tool is an aid for policy management, not a guarantee that the policy will be enforced.

PLEASE NOTE

EVM chains only. This tool relies on the BGWallet connector and will not function on Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The user is responsible for ensuring the supplied policy contract address is correct and that the contract supports policy management functions. Not all multisig implementations support spending policies — check your protocol's documentation first. Token limits must be formatted as "token_address:limit" separated by commas — the tool validates this before execution.