Multisig Threshold Change Risk Explainer

WHAT IT DOES

Multisig Threshold Change Risk Explainer analyzes proposed multisig threshold changes and explains their security impact before you sign or vote. The tool reads the threshold change transaction calldata to identify the proposed threshold, fetches the current threshold and signer count from the contract, and detects critical risk patterns including threshold reduction to 1 (single-signer control), threshold set above the number of signers (impossible to execute), and threshold changes that don't match the multisig's typical activity. The tool then uses AI to generate a plain-language explanation of the threshold change: what the current threshold is, what it is changing to, how this affects the security of the multisig (e.g., easier or harder to execute transactions), and whether the change appears legitimate or suspicious. Results include a risk level, current threshold, proposed threshold, signer count, change direction (increase/decrease), flags, and a comprehensive AI-generated explanation. The tool operates entirely read-only — no transactions are sent, no signatures are required. The AI assessment is designed to help you understand the security implications of a threshold change before you approve it.

HOW TO USE

Connect your EVM wallet using the "Connect" button in the header. Select the network where the multisig contract is deployed from the dropdown menu. Enter the multisig contract address. Paste the threshold change transaction calldata (hex string starting with 0x) from the pending transaction. Optionally enter the proposed threshold if you know it. Click "Explain threshold change" to begin the analysis. The tool decodes the calldata to identify the proposed threshold, reads the current threshold and signer count from the contract, detects critical risk patterns, and sends the data to the AI for a plain-English threshold change explanation. Results appear within seconds, showing the multisig contract, chain, risk level, current threshold, proposed threshold, signer count, change direction, flags, and a comprehensive AI-generated explanation written in clear, conversational language.

THRESHOLD CHANGE DETECTION AND SECURITY SCORING

The tool uses a signature-based decoding engine to analyze threshold change transactions. It matches the function signature against known threshold change functions — changeRequirement (0x44b1b8f9) and changeThreshold (0x7065cb48) — and extracts the proposed threshold from the calldata parameters. The tool then reads the current threshold and signer count from the contract to provide context for the change. Critical security risks are detected when: the proposed threshold is reduced to 1 (single signer can execute, critical security failure), the proposed threshold exceeds the signer count (transactions become impossible to execute), or the threshold is decreased below 3 (reduces security). The change direction is identified as increasing (more confirmations required, more secure) or decreasing (fewer confirmations required, less secure). The AI receives all this data and is prompted to explain the threshold change in plain language — stating what the current threshold is, what it is changing to, how this affects security, and whether the change appears routine or suspicious. The AI is also instructed to state plainly what it cannot verify — that it reads on-chain data and decodes calldata, not the proposer's intent, off-chain context, or the appropriateness of the threshold for the signer set.

WHAT IT CANNOT SEE

This tool cannot definitively verify the true intent of a threshold change — only reads on-chain data and decodes calldata. It cannot detect off-chain coordination or malicious intent not reflected in calldata — a threshold change that appears routine could be part of a coordinated attack. The tool cannot predict whether the change will be approved or executed — it can only analyze the proposed change. Legitimate threshold changes may be made for operational reasons — reducing a threshold is not always malicious. The tool cannot verify that the threshold is appropriate for the signer set — it can only flag mathematically risky changes. The tool cannot detect if the multisig contract has been compromised. The tool cannot detect if the proposer is acting maliciously. The tool cannot predict the outcome of the threshold change. The tool cannot detect off-chain governance processes or social context that might make a threshold change more or less suspicious. The tool cannot verify that the threshold change is consistent with the multisig's typical activity patterns.

PLEASE NOTE

Multisig Threshold Change Risk Explainer supports EVM-compatible chains only (Ethereum, BSC, Polygon, Arbitrum, Optimism, Avalanche, and others). The tool is read-only and never requests wallet signatures or transaction approvals. Threshold change assessments are AI-generated from on-chain data and calldata decoding — always verify threshold changes through the multisig contract's official interface and your wallet's transaction preview before signing. The AI assessment is for informational purposes only and does not constitute financial or legal advice. Never approve a threshold change you do not fully understand. A threshold of 1 means any single signer can execute transactions — this is a critical security risk for any multisig holding significant assets.