Hi everyone,
Following the wave of high-value signing-flow and supply-chain attacks (most notably the 2025 Bybit Safe incident and numerous access-control losses), I am proposing a new ERC focused on making transaction signing independently verifiable and human-meaningful.
Core idea:
Standardize a Verification Payload + independent simulation interface + scoped capabilities so that “what you see is what you sign” becomes enforceable rather than aspirational.
Motivation:
Analysis of major incidents (including the February 2025 Bybit ~$1.4–1.5B Safe multisig compromise and numerous other access-control / signing-flow losses) shows that the majority of high-value thefts no longer rely solely on classic smart-contract bugs. Instead they exploit:
Blind or semi-blind signing of opaque calldata.
Compromised frontends / supply-chain attacks that show a benign UI while presenting malicious calldata for signature.
Lack of independent, machine-checkable simulation before signature.
Overly broad and long-lived approvals / authorizations.
Weak ceremony requirements for multisigs and high-value smart accounts.
Existing standards (EIP-712, ERC-1271, EIP-4337, EIP-7702, ERC-7683 intents, etc.) provide excellent building blocks but do not mandate or standardize the full secure verification loop that signers and verifiers need. This ERC fills that gap at the application layer.
Core Concepts:
Verification Payload, A structured object containing the raw transaction/UserOperation + mandatory metadata.
Semantic Intent, Human- and machine-readable description of the effect (e.g. Transfer 1000
USDC to 0xabc, Upgrade Safe implementation to 0xdef, Install module X with permissions Y
Independent Simulator, Any party (wallet, hardware device, third-party verifier, another signer) that can re-simulate the exact payload and produce a canonical result.
Scoped Capability A short-lived, purpose-limited authorization token (EIP-712 typed data or ERC-1271-compatible) that grants only specific actions.
Key questions:
1. Is the VerificationPayload structure the right shape, or should we lean more heavily on existing intent standards (ERC-7683 etc.)?
2. How strict should the multisig ceremony requirements be for “STVA-compliant” status?
3. Should we define explicit compliance levels (Basic / Standard / Strict)?
4. Best way to integrate with EIP-7702 authorizations and modular accounts (ERC-7579/6900)?
5. Any existing work this overlaps with that I should reference or merge with?
Looking forward to feedback and especially input from wallet teams (Safe, Ambire, MetaMask, Rabby, hardware vendors), custody providers, and security researchers.