Plain-English definition
What signing preview means
A signing preview translates calldata and verified protocol evidence into a readable summary of what the transaction requests and which material risks remain open.
Proof feature 10 of 10 · Web3 transaction preview before signing
Preview a Web3 Transaction Before Signing
Review the called function, amount effects, fees, permissions, lockups, exit path, code-match state, and warnings before opening a wallet signature.
Questions this page answers
What to verify
- Which contract and function will execute?
- What assets, permissions, fees, or lockups can change?
- Is the target code matched to current review evidence?
Evidence checklist
Evidence that makes this useful
Each item must be tied to an inspectable source or remain clearly labeled as pending, unavailable, or unidentified.
01
Transaction intent
Chain, target, selector, decoded parameters, token, and amount.
02
User impact
Approvals, transfers, shares, debt, fees, lockups, and exit conditions.
03
Trust context
Code match, function coverage, authority state, warnings, and freshness.
Decision use
How to use this proof
Use the preview as decision context before signing; it is a risk signal, not a guarantee that a transaction is safe.
Proof of Audits shows evidence and gaps. It does not guarantee protocol or transaction safety.
Specific answers
Frequently asked questions
Does a clear signing preview make a transaction safe?
No. It makes known intent and evidence easier to inspect, while unknown behavior and changing conditions can still create risk.
What happens when evidence is stale or missing?
The preview should show an explicit pending, mismatch, unverified, or warning state instead of presenting trusted output.