Before you start
- Use a fictional order, a disposable test wallet, or calldata from a documented example. Compare the decoded data with the intended chain, contract and action. Keep real balances out of the rehearsal.
- Use the provider’s official contract definitions for the applicable network and version. You can complete the comparison without publishing an order or submitting a transaction.
Data and access
Setup steps
OpenSea
For a Seaport order, inspect the offer and consideration arrays. Compare the items, token contracts, identifiers, amounts, time window and consideration recipients with the expected order. If the order uses a conduit, check which conduit would handle transfers and review any separate approval.
Check. The order identifies the intended offered asset and consideration recipients. Record any conduit authorization separately.
Lido
For a WithdrawalQueueERC721 request, check whether the call uses stETH or wstETH and compare the amounts and request owner with the expected values. The owner receives the withdrawal request NFT. Inspect a claim separately, checking the request ID and the recipient for the particular claim method.
Check. The decoded call shows the expected asset, amount and request owner, or the expected claim ID and recipient for a claim.
Alchemy
For a disposable EVM transaction, preview the call with eth_call or use debug_traceCall on a chain and endpoint that support it. Supply the intended sender, target, value and calldata. Review a revert or the trace’s call targets at the recorded block. The preview uses that state and does not submit the transaction.
Check. Record the block and the returned data, revert or trace. Compare its call target and value with the intended request.
Compare with the intended action
Write down the contract, action, assets and recipient alongside the decoded request. Change one field in the fictional example and check that your review catches it before any signature or transaction is sent.
Spot changes before you approve - Order or call matches
- Compare the asset, amount, recipient and destination contract with the intended action. Check any separate token permission the action relies on.
- One field changed
- In the disposable example, change one amount or address. Identify the exact difference in the decoded request and leave the altered request unsigned.
- Preview result
- If you used a read-only preview, save its block and result alongside the original request. That records what the preview saw at that block.
Check. Your comparison identifies the changed field before any approval. Record which app or verifier showed it.
Check your result
The original request matches the intended action and the altered field is visible in your review. Record whether you inspected an order, a contract call or a read-only simulation since each carries different information.
If you get stuck
The wallet displays a generic contract interaction
Decode the calldata or typed data against the official contract or order format. Compare the target and chain first. If you simulate a call, check which block and sender the simulation used before interpreting a result.