A standard interface and workflow for verifiable, human-readable transaction simulation, scoped authorization, and independent verification of signing payloads for EOAs, smart accounts, and multisigs.
author: @MATOBOYCRYPTO65
status: Draft
type: Standards Track
category: ERC
created: 2026-10-27
Abstract:
This ERC defines a standard for Secure Transaction Verification and Authorization (STVA) It provides:
1. A canonical way to attach structured, human-readable metadata and semantic intent to any transaction or UserOperation.
2. A mandatory independent simulation and verification interface that wallets, signers, and verifiers can call.
3. Scoped, revocable capability tokens attestations for privileged operations (upgrades, large transfers, module installation, ownership changes).
4. Clear requirements for multisig and smart-account signing ceremonies that resist frontend supply-chain attacks and UI spoofing.
The goal is to make what you see is what you sign cryptographically enforceable and independently verifiable, addressing the dominant real-world loss vectors observed in 2024–2026 (signing-flow compromises, blind signing, and multisig UI attacks).
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.