EVM Transaction Safety Preview#

Use this free preview when an agent is about to sign or route an EVM transaction and needs a fast, no-payment triage before installing the paid ClawMart toolkit.

What this free preview does#

Run a lightweight pre-signing check:

AreaPass signalCommon failureChain + targetChain id, RPC target, and contract address match the intended actionSigning on the wrong EVM chain or interacting with a spoofed contractCalldata intentFunction selector and decoded params match the user’s instructionBlind calldata, unexpected delegatecall/proxy target, hidden approvalValue + allowanceNative value and ERC-20 approval amount are expected and boundedInfinite approval, excessive value, unknown spenderToken/contract riskToken has sane metadata/liquidity/ownership signalsHoneypot, blacklistable token, owner-controlled tax, low-liquidity baitSimulation postureA dry run is available or the transaction is paused for reviewAgent signs without knowing state changes or revert reason

Minimal workflow#

1. Capture chain, from address, to address, value, calldata, and any token/spender being approved.
2. Decode the function selector and compare the decoded intent to the user’s instruction.
3. Check that value/allowance are bounded and that spender/recipient are expected.
4. If token risk or state changes matter, use the paid ClawMart toolkit for live explain/simulate/risk checks before signing.
5. If any field is missing, ambiguous, or inconsistent, stop and request a safer transaction plan rather than signing.

Paid upgrade path#

Install EVM Transaction Safety Toolkit on ClawMart when you need production-backed live checks:

https://www.shopclawmart.com/listings/evm-transaction-safety-toolkit-89902e40

Backends used by the paid package:

• https://evm-tx-toolkit.mtree.workers.dev/v1/tx/explain — decode and explain confirmed transactions
• https://evm-tx-toolkit.mtree.workers.dev/v1/tx/simulate — pre-flight simulation and revert/state-change summary
• https://evm-tx-toolkit.mtree.workers.dev/v1/token/risk_scan — ERC-20 risk scoring

Safety limits#

• Do not request, reveal, or store seed phrases, private keys, session keys, or raw wallet credentials.
• Do not sign or broadcast transactions from this preview; it is a checklist only.
• Do not approve unlimited token allowances unless the user explicitly requests it and risk has been checked.
• If calldata cannot be decoded or simulation fails unexpectedly, pause instead of guessing.

Anti-patterns#

• Treating a friendly dapp name as proof that the to address is safe.
• Signing approvals before checking spender and allowance.
• Skipping simulation because a transaction is “small.”
• Reusing a stale decoded calldata explanation after the transaction body changes.