Tool AT-W37REV. 2026-A
Calldata decoder: What does this transaction do before you sign?
Calldata is the hex text with which a transaction calls a smart contract. The first four bytes name the function and the rest holds the values, and that is exactly where it says whether you are transferring tokens or giving another address an unlimited approval. The decoder turns this into plain English, including nested multicalls, Uniswap’s Universal Router and Safe transactions. A second input reads EIP-712 signature requests such as Permit and Permit2.
- free
- no sign-up
- reads in your browser
01 / DECODER
Paste calldata or a signature request, read it in plain English
Decoder · calldata and signature requests
The decoder reads what is in the data. It cannot see whether the address behind it is the genuine contract or what the contract actually does with the values; that takes the verified source code or a simulation.
Reads in your browser. Nothing is sent or stored. The tool never needs a seed phrase or a private key.
02 / STRUCTURE
What is in the calldata
When you confirm, a wallet usually shows the recipient and the amount. But if the transaction calls a contract, the substance is in the data field, and that is hex. Its first four bytes are called the selector: Keccak-256 over the function’s signature, that is, its name and parameter types without spaces, and the start of the result. For approve(address,uint256) that is 0x095ea7b3.
The parameters follow in words of 32 bytes each. Numbers are right-aligned, an address takes up the last 20 bytes of its word, and 12 zero bytes come before it. Text, byte sequences and lists have no fixed length. In their place the head holds an offset, and the data follows further back, with its length in front. This is exactly how calls can be packed inside one another: a multicall is a list of byte sequences, and each of them is calldata again.
The example in the figure is a real form that occurs millions of times a day. The decoder reads it like this: “Allows 0x000000000022D473030F116dDEE9F6B43aC78BA3 (Uniswap’s Permit2) to spend an unlimited amount of USDC from your balance until you revoke the approval.”
Fig. 1 · Selector, words and offsets. Encoding according to Solidity’s ABI specification, as of 14 November 2026.
How the decoder reads, and what it checks as it goes
| Type | In the head | What is checked |
|---|---|---|
| uint8 … uint256 | one word | fits the bit width; otherwise Solidity 0.8 and later rejects the call |
| int8 … int256 | one word | two’s complement, sign correctly extended to 256 bits |
| address | one word | 12 zero bytes before it; output with the checksum from EIP-55 |
| bool | one word | only 0 or 1 |
| bytes1 … bytes32 | one word | padded with zeros on the right |
| bytes, string | offset | offset and length lie within the data; text as UTF-8 |
| T[], T[k] | offset, or inline in sequence | length fits within the data before reading |
| (T1,T2,…) | offset, if any part is dynamic | each part by its own rules |
The decoder is built to cope with malformed input: offsets that keep pointing to the same place could turn 96 kilobytes into a billion values. It therefore stops after 50,000 values and reads at most 8 levels deep. After reading, it re-encodes everything and compares. If the result differs, for example because of bytes at the end that belong to no parameter, a note says so.
A selector is only four bytes long and does not reveal the parameter types. Signature databases help, but they are incomplete and do not keep up with new contracts Chen et al. 2022. The decoder does not query a database; anything not in its list it reads with your ABI or signature. The selector and topic calculator works out the selector for a signature and vice versa.
03 / APPROVALS
Approvals: who may do what with your tokens?
A swap, a deposit or a sale often begins with an approval. With it you allow a contract to take tokens from your balance, later too and without a new confirmation. That is intended, because otherwise every application would first have to take your tokens into custody. But it also means that the approval is the real permission, not the swap that follows.
In an analysis of 25.4 million ERC-20 approvals up to July 2021, around 60 percent were unlimited. All 22 applications examined asked for unlimited approvals, only 3 of 31 interfaces explained what that means, and only 5 let the amount be changed Wang et al. 2022. Fraud schemes that abuse approvals start at exactly this point and benefit from how tersely wallets display approvals Adamczyk 2025. The decoder therefore spells out every approval: who, how much and for how long, even when it is buried deep in a bundle.
| Function | What it allows | Scope and duration | Revoking |
|---|---|---|---|
| approve | An address may take ERC-20 tokens from your balance. | up to the amount; the maximum value counts as unlimited; no expiry | approve with 0 |
| setApprovalForAll | An address may transfer all of a contract’s NFTs. | the whole collection, including ones received later; no expiry | the same function with false |
| permit (EIP-2612) | Like approve, but as a signature; anyone can submit it. | the amount; the deadline applies to the signature, and the approval remains afterwards | after submission, like approve |
| Permit2 approve, permit | A contract may move tokens via Permit2; the token must have been approved for Permit2 once for this. | the amount, the maximum value of uint160 counts as unlimited; with an expiry date | lockdown or approve with 0 |
| Permit2 permitTransferFrom | A single withdrawal by signature. | exactly once, until the deadline | before submission: invalidateUnorderedNonces |
According to EIP-20, EIP-721, EIP-1155, EIP-2612 and the Permit2 source code, as of 14 November 2026.
Two things help in everyday use. First, limited amounts: an approval for the amount of the swap is used up afterwards. Correcting it later is not the same thing, because someone who is already authorised can withdraw the old amount before a change and the new one after it Rahimian et al. 2019. Second, tidy up now and then. Block explorers such as Etherscan keep an overview of the approvals granted for every address, and anything you no longer use can be revoked there.
Drainer kits that are rented out as a service consist at their core of exactly these functions: approve, setApprovalForAll, permit, Permit2 He et al. 2025. That is why the decoder recognises them by the function itself and not by the website that requests them.
04 / SIGNATURES
Signatures without a transaction: EIP-712
Not everything a wallet asks you to confirm is a transaction. With EIP-712 you sign a structured message: no gas and no trace on the chain until someone submits it. Permit, Permit2, sale offers on marketplaces using Seaport and approval of a Safe transaction all work this way. The signature still has an effect: whoever holds it uses it to put the approval or the order into force.
A signature request has two parts. The domain says what it applies to: the application’s name, version, chain and contract. The message says what takes effect. The decoder shows both in full, recognises Permit, Permit2, Seaport and SafeTx, and writes the core of it as a sentence. If the message contains a field that does not appear in the type, it reports this, because such a field is displayed but not signed.
| Field | Meaning | What to look for |
|---|---|---|
| name | Name of the application or token | Does it match what you are doing right now? |
| version | Version of the signing format | only for telling things apart |
| chainId | Chain on which the signature is valid | If it is missing, the signature is not bound to any chain. |
| verifyingContract | Contract that verifies the signature | for Permit the token, for Permit2 always 0x000000000022D473030F116dDEE9F6B43aC78BA3 |
| salt | additional distinguishing value | rarely used |
Blind signing: when the device shows only hashes
Hardware wallets often show signature requests they do not recognise only as hashes: with EIP-712, the domain hash and the message hash. If you confirm then, you sign blind. A device on its own is also just a single point that has to be trusted Dabrowski et al. 2021. The decoder calculates the same hashes independently from the request you paste here. If both hashes match the device, you are signing exactly what is written above in plain English. For Safe, the signature hash is the safeTxHash, which the Safe interface also shows.
One thing remains important: a confirmed transaction cannot be reversed, and a submitted approval stays valid until you revoke it. People switching over from banking often assume the opposite Voskobojnikov et al. 2021, and wallets do not make it easy for newcomers to get started Froehlich et al. 2021. That is why the decoder writes without jargon and explains the terms that cannot be avoided.
05 / BUNDLES
Nested calls: Multicall, Universal Router, Safe
Many transactions are bundles. Multicall3 runs several calls to different contracts, multicall(bytes[]) several to the same one. Uniswap’s Universal Router receives a sequence of command bytes and an input for each command. A Safe uses execTransaction to run one call, often a DELEGATECALL to MultiSend, which in turn contains a packed list of calls. The decoder reads every level and numbers the sentences so that it stays clear what is where.
Approvals like to hide in exactly these. In transaction-based phishing, users are lured to copied sites and sign calls there that make their assets available to others; one study found 26,333 such sites in eight months He et al. 2023. A follow-up study counted 130,637 phishing transactions in 300 days that worked through the payload of contract calls Chen et al. 2025. What counts is in the calldata, not on the website. That is also why the decoder always shows addresses in full: fake addresses often match the real one at the start and the end. The Ethereum address checker compares two addresses character by character.
Universal Router commands
| Byte | Command | What it does |
|---|---|---|
| 0x00 | V3_SWAP_EXACT_IN | swap via Uniswap v3, fixed input |
| 0x01 | V3_SWAP_EXACT_OUT | swap via Uniswap v3, fixed output |
| 0x02 | PERMIT2_TRANSFER_FROM | takes tokens via Permit2 |
| 0x03 | PERMIT2_PERMIT_BATCH | submits a Permit2 batch approval |
| 0x04 | SWEEP | pays out the router’s balance |
| 0x05 | TRANSFER | transfers tokens from the router |
| 0x06 | PAY_PORTION | pays out a share (fee) |
| 0x07 | PAY_PORTION_FULL_PRECISION | pays out a share (fee, exact) |
| 0x08 | V2_SWAP_EXACT_IN | swap via Uniswap v2, fixed input |
| 0x09 | V2_SWAP_EXACT_OUT | swap via Uniswap v2, fixed output |
| 0x0a | PERMIT2_PERMIT | submits a Permit2 approval |
| 0x0b | WRAP_ETH | wraps ETH into WETH |
| 0x0c | UNWRAP_WETH | unwraps WETH into ETH |
| 0x0d | PERMIT2_TRANSFER_FROM_BATCH | takes several tokens via Permit2 |
| 0x0e | BALANCE_CHECK_ERC20 | checks a minimum balance |
| 0x10 | V4_SWAP | swap via Uniswap v4 (list of actions) |
| 0x11 | V3_POSITION_MANAGER_PERMIT | permit for a v3 position |
| 0x12 | V3_POSITION_MANAGER_CALL | call on the v3 PositionManager |
| 0x13 | V4_INITIALIZE_POOL | creates a v4 pool |
| 0x14 | V4_POSITION_MANAGER_CALL | call on the v4 PositionManager |
| 0x21 | EXECUTE_SUB_PLAN | runs an embedded sequence of commands |
| 0x40 | ACROSS_V4_DEPOSIT_V3 | bridge via Across (third party) |
According to Commands.sol and Dispatcher.sol, as of 14 November 2026. A set bit 0x80 means the command may fail. Older routers (version 1) use 0x10 to 0x22 for NFT commands; the decoder recognises this from the target address.
For every swap, the plain-English text states the minimum amount. It protects against the rate getting worse between signing and execution. Bots watch pending transactions and place their own orders in front of them Daian et al. 2020, and in a sandwich attack one behind as well Zhou et al. 2021. If the minimum amount is 0, the decoder reports it. The gas calculator works out what a swap costs in gas.
A DELEGATECALL from a Safe is a special case: the code that is called runs with the Safe’s rights and storage, so it can also change the signers or move the balance. For the official MultiSend contracts from Safe this is as intended; for anything else the decoder reports it as a notable point. Proxies are similar: upgradeTo replaces a contract’s logic, and around half of the upgradeable contracts examined were controlled by a single address Salehi et al. 2023.
06 / LIST
Which 89 functions the decoder knows without an ABI
The list covers what wallets most often present in everyday use: tokens and NFTs, vaults, contract administration, Permit2, bundles, Uniswap and Safe. Each selector is calculated from the signature, not copied; the tool’s test compares it with known values and checks that no two entries share the same one.
| Selector | Signature | Standard | What it does |
|---|---|---|---|
| 0xa9059cbb | transfer(address,uint256) | ERC-20 | transfers tokens to an address |
| 0x23b872dd | transferFrom(address,address,uint256) | ERC-20 / ERC-721 | takes tokens using an existing approval; for NFTs the number is the token ID |
| 0x095ea7b3 | approve(address,uint256) | ERC-20 / ERC-721 | grants an approval; the maximum value means unlimited |
| 0x39509351 | increaseAllowance(address,uint256) | ERC-20 (OpenZeppelin) | increases an approval |
| 0xa457c2d7 | decreaseAllowance(address,uint256) | ERC-20 (OpenZeppelin) | decreases an approval |
| 0xd505accf | permit(address,address,uint256,uint256,uint8,bytes32,bytes32) | EIP-2612 | submits a signed approval |
| 0x8fcbaf0c | permit(address,address,uint256,uint256,bool,uint8,bytes32,bytes32) | DAI permit | submits a signed DAI approval (yes/no, without an amount) |
| 0xd0e30db0 | deposit() | WETH | swaps the ETH sent along 1:1 into WETH |
| 0x2e1a7d4d | withdraw(uint256) | WETH | swaps WETH 1:1 back into ETH |
| 0x42842e0e | safeTransferFrom(address,address,uint256) | ERC-721 | transfers an NFT |
| 0xb88d4fde | safeTransferFrom(address,address,uint256,bytes) | ERC-721 | transfers an NFT with additional data |
| 0xa22cb465 | setApprovalForAll(address,bool) | ERC-721 / ERC-1155 | approves or revokes all of a contract’s NFTs |
| 0xf242432a | safeTransferFrom(address,address,uint256,uint256,bytes) | ERC-1155 | transfers units of an ERC-1155 token |
| 0x2eb2c2d6 | safeBatchTransferFrom(address,address,uint256[],uint256[],bytes) | ERC-1155 | transfers several ERC-1155 tokens at once |
| 0x6e553f65 | deposit(uint256,address) | ERC-4626 | deposits tokens into a vault |
| 0x94bf804d | mint(uint256,address) | ERC-4626 | buys vault shares |
| 0xb460af94 | withdraw(uint256,address,address) | ERC-4626 | withdraws tokens from a vault |
| 0xba087652 | redeem(uint256,address,address) | ERC-4626 | redeems vault shares |
| 0xf2fde38b | transferOwnership(address) | Ownable (OpenZeppelin) | hands over administration of the contract |
| 0x715018a6 | renounceOwnership() | Ownable (OpenZeppelin) | gives up administration for good |
| 0x79ba5097 | acceptOwnership() | Ownable2Step (OpenZeppelin) | accepts administration that has been offered |
| 0x2f2ff15d | grantRole(bytes32,address) | AccessControl (OpenZeppelin) | grants a role |
| 0xd547741f | revokeRole(bytes32,address) | AccessControl (OpenZeppelin) | revokes a role |
| 0x36568abe | renounceRole(bytes32,address) | AccessControl (OpenZeppelin) | gives up one’s own role |
| 0x8456cb59 | pause() | Pausable (OpenZeppelin) | pauses the contract |
| 0x3f4ba83a | unpause() | Pausable (OpenZeppelin) | lets the contract run again |
| 0x3659cfe6 | upgradeTo(address) | Proxy (EIP-1967) | replaces the logic behind a proxy |
| 0x4f1ef286 | upgradeToAndCall(address,bytes) | Proxy (EIP-1967) | replaces the logic and calls it straight away |
| 0x87517c45 | approve(address,address,uint160,uint48) | Permit2 | approval with an expiry date via Permit2 |
| 0x2b67b570 | permit(address,((address,uint160,uint48,uint48),address,uint256),bytes) | Permit2 | submits a signed Permit2 approval |
| 0x2a2d80d1 | permit(address,((address,uint160,uint48,uint48)[],address,uint256),bytes) | Permit2 | submits several Permit2 approvals at once |
| 0x36c78516 | transferFrom(address,address,uint160,address) | Permit2 | takes tokens via a Permit2 approval |
| 0x0d58b1db | transferFrom((address,address,uint160,address)[]) | Permit2 | takes several tokens via Permit2 approvals |
| 0x30f28b7a | permitTransferFrom(((address,uint256),uint256,uint256),(address,uint256),address,bytes) | Permit2 | one-off withdrawal with a signature |
| 0x137c29fe | permitWitnessTransferFrom(((address,uint256),uint256,uint256),(address,uint256),address,bytes32,string,bytes) | Permit2 | one-off withdrawal with a signature and order data |
| 0xcc53287f | lockdown((address,address)[]) | Permit2 | sets Permit2 approvals to zero |
| 0x65d9723c | invalidateNonces(address,address,uint48) | Permit2 | invalidates signatures that have not yet been submitted |
| 0x3ff9dcb1 | invalidateUnorderedNonces(uint256,uint256) | Permit2 | invalidates signatures that have not yet been submitted |
| 0x252dba42 | aggregate((address,bytes)[]) | Multicall3 | runs several calls one after another |
| 0xbce38bd7 | tryAggregate(bool,(address,bytes)[]) | Multicall3 | several calls, some of which may fail |
| 0xc3077fa9 | blockAndAggregate((address,bytes)[]) | Multicall3 | several calls with block number |
| 0x399542e9 | tryBlockAndAggregate(bool,(address,bytes)[]) | Multicall3 | several calls with block number |
| 0x82ad56cb | aggregate3((address,bool,bytes)[]) | Multicall3 | several calls, with a choice per call of whether it may fail |
| 0x174dea71 | aggregate3Value((address,bool,uint256,bytes)[]) | Multicall3 | several calls with an ETH amount per call |
| 0xac9650d8 | multicall(bytes[]) | Multicall (OpenZeppelin, Uniswap) | several calls to the same contract |
| 0x5ae401dc | multicall(uint256,bytes[]) | Uniswap SwapRouter02 | several calls with a deadline |
| 0x1f0464d1 | multicall(bytes32,bytes[]) | Uniswap SwapRouter02 | several calls, only on a specific block |
| 0x3593564c | execute(bytes,bytes[],uint256) | Uniswap Universal Router | runs a sequence of commands (swap, Permit2, forwarding) |
| 0x24856bc3 | execute(bytes,bytes[]) | Uniswap Universal Router | runs a sequence of commands |
| 0x44684dc3 | executeSigned(bytes,bytes[],bytes32,bytes32,bool,bytes32,bytes,uint256) | Uniswap Universal Router 2.1 | runs a sequence of commands that an EIP-712 signature approves |
| 0xd04d79a2 | signedRouteContext() | Uniswap Universal Router 2.1 | reads the signer, intent and data of the signed execution in progress |
| 0xdd46508f | modifyLiquidities(bytes,uint256) | Uniswap v4 PositionManager | changes liquidity positions in Uniswap v4 |
| 0x38ed1739 | swapExactTokensForTokens(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swaps a fixed amount of tokens |
| 0x8803dbee | swapTokensForExactTokens(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swaps to a fixed target amount |
| 0x7ff36ab5 | swapExactETHForTokens(uint256,address[],address,uint256) | Uniswap V2 Router | swaps the ETH sent along into tokens |
| 0x4a25d94a | swapTokensForExactETH(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swaps tokens to a fixed amount of ETH |
| 0x18cbafe5 | swapExactTokensForETH(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swaps tokens into ETH |
| 0xfb3bdb41 | swapETHForExactTokens(uint256,address[],address,uint256) | Uniswap V2 Router | swaps ETH to a fixed amount of tokens |
| 0x5c11d795 | swapExactTokensForTokensSupportingFeeOnTransferTokens(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swap for tokens that charge a fee on transfer |
| 0xb6f9de95 | swapExactETHForTokensSupportingFeeOnTransferTokens(uint256,address[],address,uint256) | Uniswap V2 Router | swap for tokens that charge a fee on transfer |
| 0x791ac947 | swapExactTokensForETHSupportingFeeOnTransferTokens(uint256,uint256,address[],address,uint256) | Uniswap V2 Router | swap for tokens that charge a fee on transfer |
| 0xe8e33700 | addLiquidity(address,address,uint256,uint256,uint256,uint256,address,uint256) | Uniswap V2 Router | deposits two tokens into a pool |
| 0xf305d719 | addLiquidityETH(address,uint256,uint256,uint256,address,uint256) | Uniswap V2 Router | deposits tokens and ETH into a pool |
| 0xbaa2abde | removeLiquidity(address,address,uint256,uint256,uint256,address,uint256) | Uniswap V2 Router | withdraws liquidity from a pool |
| 0x02751cec | removeLiquidityETH(address,uint256,uint256,uint256,address,uint256) | Uniswap V2 Router | withdraws liquidity from a pool |
| 0x414bf389 | exactInputSingle((address,address,uint24,address,uint256,uint256,uint256,uint160)) | Uniswap V3 SwapRouter | swaps a fixed amount through one pool |
| 0xc04b8d59 | exactInput((bytes,address,uint256,uint256,uint256)) | Uniswap V3 SwapRouter | swaps a fixed amount through several pools |
| 0xdb3e2198 | exactOutputSingle((address,address,uint24,address,uint256,uint256,uint256,uint160)) | Uniswap V3 SwapRouter | swaps to a fixed target amount |
| 0xf28c0498 | exactOutput((bytes,address,uint256,uint256,uint256)) | Uniswap V3 SwapRouter | swaps to a fixed target amount through several pools |
| 0x04e45aaf | exactInputSingle((address,address,uint24,address,uint256,uint256,uint160)) | Uniswap SwapRouter02 | swaps a fixed amount through one pool |
| 0xb858183f | exactInput((bytes,address,uint256,uint256)) | Uniswap SwapRouter02 | swaps a fixed amount through several pools |
| 0x5023b4df | exactOutputSingle((address,address,uint24,address,uint256,uint256,uint160)) | Uniswap SwapRouter02 | swaps to a fixed target amount |
| 0x09b81346 | exactOutput((bytes,address,uint256,uint256)) | Uniswap SwapRouter02 | swaps to a fixed target amount through several pools |
| 0x49404b7c | unwrapWETH9(uint256,address) | Uniswap V3 Periphery | swaps the WETH in the router back into ETH and pays it out |
| 0x49616997 | unwrapWETH9(uint256) | Uniswap SwapRouter02 | swaps the WETH in the router back into ETH |
| 0x12210e8a | refundETH() | Uniswap V3 Periphery | refunds leftover ETH from the router |
| 0xdf2ab5bb | sweepToken(address,uint256,address) | Uniswap V3 Periphery | pays out leftover tokens from the router |
| 0x6a761202 | execTransaction(address,uint256,bytes,uint8,uint256,uint256,uint256,address,address,bytes) | Safe | executes a Safe transaction signed by several owners |
| 0x8d80ff0a | multiSend(bytes) | Safe MultiSend | several Safe calls in one packed list |
| 0x0d582f13 | addOwnerWithThreshold(address,uint256) | Safe | adds another signer |
| 0xf8dc5dd9 | removeOwner(address,address,uint256) | Safe | removes a signer |
| 0xe318b52b | swapOwner(address,address,address) | Safe | replaces a signer |
| 0x694e80c3 | changeThreshold(uint256) | Safe | changes how many signatures are needed |
| 0x610b5925 | enableModule(address) | Safe | enables a module that may act without signatures |
| 0xe009cfde | disableModule(address,address) | Safe | disables a module |
| 0xe19a9dd9 | setGuard(address) | Safe | places a checking contract in front of every transaction |
| 0xf08a0323 | setFallbackHandler(address) | Safe | sets the contract for unknown calls |
| 0x08c379a0 | Error(string) | Solidity | error message from require or revert |
| 0x4e487b71 | Panic(uint256) | Solidity | programming error, such as an overflow or division by zero |
Selector = first 4 bytes of the Keccak-256 of the signature, e.g. 0xa9059cbb for transfer(address,uint256). As of 14 November 2026.
07 / METHOD
How to read a transaction before you sign it
- Get the data. Copy it from your wallet under “Data” or “Hex”; for a transaction that has already been sent, from Etherscan under “Input Data”. Take the target address (to) along with it.
- Read the plain English. Does the sentence match what you intend to do? If you want a swap, you should not be reading a sentence about a blanket approval for NFTs.
- Go through the notable points. Unlimited approval, no minimum amount, a recipient that is not you, DELEGATECALL: any of them can be intended. What matters is that you know about them.
- Compare addresses. Check the recipient of an approval in full against the address the application itself gives, not just the start and the end.
- If the device shows hashes: compare the domain hash and the message hash with the result here before you confirm.
Where the decoder stops
- No access to the chain. Whether the target address is the genuine contract, whether it is a proxy and what its code does with the values all remain open. The explanation applies to contracts that follow the standard named.
- Unknown selectors. Without an ABI or signature they stay undecoded; the tool does not query an online database. Different functions can share the same selector.
- Amounts in the smallest unit. The tool knows symbols and decimals only for the few tokens in its list; otherwise amounts are given in the token’s smallest unit.
- No simulation. What the transaction finally moves depends on the state of the chain at execution, for example on the rate in a swap.
The decoder is a second view of what is being signed. It does not cover keys and devices; in an analysis of 84 wallet incidents with 5.4 billion US dollars in losses, the attacks are spread across several layers Erinle et al. 2025.
If your own application is to show users what a transaction does before they sign, we will build that with you; how is described under Web3 development. More tools around blockchain, tokens and contracts are collected in the overview of Web3 tools.
08 / RESEARCH
What the research says
The decoder’s notes follow findings from peer-reviewed work. The most important ones are here; the full list with review notes is further down.
- Unlimited approvals are the rule, explanations the exception. Around 60 percent of ERC-20 approvals were unlimited, and only one interface in ten explained them Wang et al. 2022. The decoder therefore writes every approval as a sentence.
- What counts is in the data. Transaction-based phishing works with copied sites and nested payloads He et al. 2023 Chen et al. 2025. That is why the decoder reads independently of the site and down to the eighth level.
- Wallets often display approvals too tersely. A study of approval fraud compared 18 wallets on exactly this point Adamczyk 2025.
- The minimum amount protects the swap. Front-run and sandwiched orders are well documented on decentralised exchanges Daian et al. 2020 Zhou et al. 2021.
- Selectors alone are not enough. Signature databases have gaps Chen et al. 2022; the decoder honestly says “unknown” and shows the raw data.
- Transactions are final. Many people coming from banking do not assume this Voskobojnikov et al. 2021. The rule of thumb in the result therefore says it explicitly.
09 / FOR AI ASSISTANTS
Using this tool from an AI assistant
Assistants such as Claude or ChatGPT that speak the Model Context Protocol (MCP) can call this page’s calculation directly instead of rebuilding it. The server is public, needs no sign-in and stores nothing. The answer always includes the link to this page, the date of the data and the limits of the result.
- Endpoint
https://aureum-tech.com/mcp- Tool
werkzeug_calldata_decoder- Transport
- Streamable HTTP, read-only
| Name | Required | Meaning |
|---|---|---|
calldata | no | Calldata of a transaction as hex, e.g. “0x095ea7b3…” (field “data” or “input”). A transaction JSON with “to” and “data” works too. |
typed_data | no | Alternatively: an EIP-712 signature request as JSON text with types, primaryType, domain and message (as for eth_signTypedData_v4), such as Permit, Permit2, Seaport or SafeTx. |
abi | no | Optional: the contract’s ABI as JSON text (a list, a Hardhat artefact or an Etherscan response). Needed for functions that are not in the tool’s list. |
signatur | no | Optional: one or more Solidity signatures, one per line, e.g. “transfer(address to, uint256 amount)”. Without function names, such as “(address,uint256)”, the calldata is read as plain parameters without a selector. |
an | no | Optional: the transaction’s target address (field “to”). With it the tool recognises known tokens (symbols, decimals) and router versions. |
ihre_adresse | no | Optional: the address of the person signing. The tool then reports recipients that are not this address. |
jetzt_unix | no | Optional: the current time as a Unix timestamp in seconds. Only with it can the tool say whether deadlines have already passed or run unusually long. |
Questions where an assistant should call it
- “What does this calldata do? It starts with 0x095ea7b3 and ends with 64 times f.”
- “My wallet wants me to confirm a Uniswap swap. Here is the calldata; where do the tokens go and is there a minimum amount?”
- “Is this Permit2 signature request an unlimited approval, and until when does it apply?”
- “Which calls are inside this Safe transaction with MultiSend, and does anything run as a DELEGATECALL?”
How the connection works and what MCP can do in your own business is explained on the page about MCP integrations.
10 / COMMON QUESTIONS
Frequently asked questions about calldata, approvals and signatures
What is calldata?
Calldata is the data part of a transaction that is used to call a smart contract. The first 4 bytes are the selector, that is, the first four bytes of the Keccak-256 hash of the function signature, for example 0x095ea7b3 for approve(address,uint256). The parameters follow in words of 32 bytes each, according to Solidity’s ABI specification. Wallets often show this data only as hex; the decoder turns it into plain English.
What does an unlimited approval with approve mean?
With approve(spender, amount) you allow an address to take tokens from your balance. If the amount is the maximum value, 2²⁵⁶ − 1, which is 64 times f in hex, the approval applies to any amount and has no expiry date until you revoke it. Many applications ask for it this way because you then do not have to approve again before every swap. In an analysis of 25.4 million approvals, around 60 percent were unlimited.
How do I revoke an approval?
You revoke an ERC-20 approval with approve and the amount 0, and a blanket approval for NFTs with setApprovalForAll and false. For Permit2 approvals, the function lockdown sets them to zero. Every revocation is itself a transaction and costs gas. Block explorers such as Etherscan show which approvals an address has granted in a separate overview.
What is the difference between approve, permit and Permit2?
approve is a transaction that you send yourself. With permit (EIP-2612) you only sign a message; whoever holds it submits it, and the approval then applies just as with approve. Permit2 is a contract from Uniswap: you approve a token for Permit2 once, and after that you grant approvals there, with an amount and an expiry date, by signature. The decoder reads all three forms.
What is blind signing, and what are the hashes for?
If a hardware wallet cannot display a signature request in readable form, it shows only hashes, with EIP-712 usually the domain hash and the message hash. Anyone who confirms then signs blind. The decoder calculates the same hashes from the request that your browser shows you. If they match the device, you are signing exactly what you read above in plain English.
Why does the decoder not recognise a selector?
It works without an online database, using its own list of 89 common functions. For anything else, it needs the contract’s ABI or signature. For contracts with verified source code, Etherscan displays the ABI. Without it, it shows the parameters as 32-byte words with a possible interpretation. A selector is only 4 bytes, so different functions can share the same one.
Does the decoder tell me whether a transaction is safe?
No. It shows what is in the data and reports factual points that stand out, such as an unlimited approval, a missing minimum amount in a swap or a DELEGATECALL. It cannot see whether the target address is the genuine contract or what its code does with the values. Whether the transaction matches what you intend is for you to decide.
Where does the calldata decoder stop?
It reads without access to the chain and without simulation; it knows amounts in token units only for a few well-known tokens. If you want your own application to show transactions so that users understand what they are approving, we will build that with you, including a review of the contracts and of the intermediate states.
11 / STUDIES AND SOURCES
What the tool is based on
The guide values and notes above are based on these 14 scientific papers. Each one has been checked via its DOI or the publisher’s page (most recently on 14 November 2026): it exists, it has not been retracted, and its findings still hold for this question today.
Wang, D.; Feng, H.; Wu, S. et al. (2022): Penny Wise and Pound Foolish: Quantifying the Risk of Unlimited Approval of ERC20 Tokens on Ethereum. Proceedings of the 25th International Symposium on Research in Attacks, Intrusions and Defenses (RAID 2022), pp. 99–114
Finding Around 60 percent of 25.4 million ERC-20 approvals up to July 2021 were unlimited. All 22 applications examined asked for unlimited approvals, only 3 of 31 interfaces explained the mechanism, and only 5 let the amount be changed.
In the tool The decoder spells out every approval with its recipient and amount and explicitly reports the maximum value as an “unlimited approval”.
doi.org/10.1145/3545948.3545963 · Conference paper
Adamczyk, B. (2025): Dissection of an Approval-Based Trusted-Token Fraud Scheme Used Across Multiple Blockchain Systems. IEEE Access 13, pp. 34467–34482
Finding An almost year-long study examined fraud groups that take millions a month with approvals (approval phishing); this is helped by how wallets display and check approvals. 18 wallets were compared on this.
In the tool That is why the result puts the plain-English text of the approval first, even when it is buried deep in a multicall or a Safe transaction.
doi.org/10.1109/access.2025.3543651 · Journal article
He, B.; Chen, Y.; Chen, Z. et al. (2023): TxPhishScope: Towards Detecting and Understanding Transaction-based Phishing on Ethereum. Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security (CCS), pp. 120–134
Finding In transaction phishing, copied websites lure users into signing transactions that let others take their assets. Between November 2022 and July 2023 the authors found 26,333 such sites and 3,486 accounts belonging to the perpetrators.
In the tool The text explains that what matters is in the calldata and not on the website; the decoder reads it independently of the site that produced it.
doi.org/10.1145/3576915.3623210 · Conference paper
Chen, Z.; Hu, Y.; He, B. et al. (2025): Dissecting Payload-based Transaction Phishing on Ethereum. Proceedings 2025 Network and Distributed System Security Symposium (NDSS)
Finding Phishing through the payload of contract calls: 130,637 phishing transactions in 300 days with more than 341.9 million US dollars in losses, divided into four main and eleven sub-types. For address poisoning alone, perpetrators spent around 13.4 ETH a day on gas.
In the tool The decoder always shows addresses in full with the checksum, never shortened, and reads nested payloads down to the eighth level.
doi.org/10.14722/ndss.2025.230311 · Conference paper
He, B.; Hu, Y.; Chen, Z. et al. (2025): Unmasking the Shadow Economy: A Deep Dive into Drainer-as-a-Service Phishing on Ethereum. Proceedings of the 2025 ACM Internet Measurement Conference (IMC), pp. 430–444
Finding Wallet drainers are sold as a service: operators supply the kits, affiliates run the sites. The study recorded 1,910 profit-sharing contracts, 87,077 payouts and 32,819 phishing sites.
In the tool Because the same kits are used on a massive scale, the decoder recognises the common patterns (approval, blanket approval, permit, Permit2) by the function itself and not by the website.
doi.org/10.1145/3730567.3764476 · Conference paper
Chen, T.; Li, Z.; Luo, X. et al. (2022): SigRec: Automatic Recovery of Function Signatures in Smart Contracts. IEEE Transactions on Software Engineering 48 (8), pp. 3066–3086
Finding Signature databases are incomplete and do not keep up with new contracts. SigRec recovers the selector and parameter types from the bytecode and reached 98.7 percent accuracy doing so.
In the tool An unknown selector therefore stays honestly “unknown”; the decoder then shows the 32-byte words with an interpretation and accepts an ABI or signature.
doi.org/10.1109/tse.2021.3078342 · Journal article
Voskobojnikov, A.; Wiese, O.; Mehrabi Koushki, M. et al. (2021): The U in Crypto Stands for Usable: An Empirical Study of User Experience with Mobile Cryptocurrency Wallets. Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems, pp. 1–14
Finding In 6,859 app reviews of wallets, mistaken assumptions from banking showed up: some people thought transactions were free, reversible and could be cancelled at any time.
In the tool The rule of thumb in the result states explicitly that a confirmed transaction does not come back and an approval stays valid until it expires or is revoked.
doi.org/10.1145/3411764.3445407 · Conference paper
Froehlich, M.; Wagenhaus, M. R.; Schmidt, A. et al. (2021): Don’t Stop Me Now! Exploring Challenges Of First-Time Cryptocurrency Users. Designing Interactive Systems Conference 2021 (DIS), pp. 138–148
Finding In a user study with 34 people, newcomers failed even with widespread wallets that are not built for their needs; the hurdles ranged from the interface to crypto-specific terms.
In the tool The plain-English text manages without jargon, and terms such as selector, approval or DELEGATECALL are explained where they appear in the result.
doi.org/10.1145/3461778.3462071 · Conference paper
Erinle, Y.; Kethepalli, Y.; Feng, Y. et al. (2025): SoK: Design, vulnerabilities, and security measures of cryptocurrency wallets. Computer Networks 273, Art. 111691
Finding A systematisation of wallet designs and attacks using a multi-layer attack model evaluated 84 incidents from 2012 to 2024 with a combined 5.4 billion US dollars in losses.
In the tool From this comes the limit stated in the text: the decoder covers only the “what is being signed” layer, not the security of the key, device or wallet software.
doi.org/10.1016/j.comnet.2025.111691 · Review
Dabrowski, A.; Pfeffer, K.; Reichel, M. et al. (2021): Better Keep Cash in Your Boots - Hardware Wallets are the New Single Point of Failure. Proceedings of the 2021 ACM CCS Workshop on Decentralized Finance and Security, pp. 1–8
Finding Hardware wallets only shift trust from the PC to another device that can be tampered with before or after delivery. The authors call for mutual checking, in which neither a compromised PC nor a compromised wallet can alter transactions unnoticed.
In the tool The decoder calculates the EIP-712 hashes itself so that you can compare them with the hardware wallet’s display: two independent devices, one result.
doi.org/10.1145/3464967.3488588 · Conference paper
Rahimian, R.; Eskandari, S.; Clark, J. (2019): Resolving the Multiple Withdrawal Attack on ERC20 Tokens. 2019 IEEE European Symposium on Security and Privacy Workshops (EuroS&PW), pp. 320–329
Finding If you change an existing ERC-20 approval from N to M, you give the authorised party the chance to withdraw N beforehand and M afterwards. None of the ten countermeasures examined solves this completely.
In the tool The text on approvals explains why even changing an existing approval is a risk, and advises tight amounts rather than later corrections.
doi.org/10.1109/eurospw.2019.00042 · Conference paper
Salehi, M.; Clark, J.; Mannan, M. (2023): Not so Immutable: Upgradeability of Smart Contracts on Ethereum. Financial Cryptography and Data Security. FC 2022 International Workshops, Lecture Notes in Computer Science, pp. 539–554
Finding Six patterns make contracts upgradeable. Of 8,225 unique upgradeable proxies, around half were controlled by a single address, and about 14 percent by a Safe with few signers.
In the tool For upgradeTo and upgradeToAndCall the decoder explains that new code applies afterwards, including to existing approvals, and the limits section names proxies explicitly.
doi.org/10.1007/978-3-031-32415-4_33 · Conference paper
Daian, P.; Goldfeder, S.; Kell, T. et al. (2020): Flash Boys 2.0: Frontrunning in Decentralized Exchanges, Miner Extractable Value, and Consensus Instability. 2020 IEEE Symposium on Security and Privacy (SP), pp. 910–927
Finding Arbitrage bots watch pending transactions on decentralised exchanges, outbid one another on fees and place their own orders in front of users’ orders.
In the tool For every swap the plain-English text states the minimum amount, because it is the protection against worse rates caused by front-run orders.
doi.org/10.1109/SP40000.2020.00040 · Conference paper
Zhou, L.; Qin, K.; Torres, C. F. et al. (2021): High-Frequency Trading on Decentralized On-Chain Exchanges. 2021 IEEE Symposium on Security and Privacy (SP), pp. 428–445
Finding Sandwich attacks frame a swap with an order before it and one after it. A single attacker could earn several thousand US dollars a day on Uniswap this way.
In the tool If a swap’s minimum amount is 0, the decoder reports it as a notable point: the swap then runs at any rate.
doi.org/10.1109/SP40001.2021.00027 · Conference paper
Standards, authorities and manufacturer data
- Contract ABI Specification · Solidity documentation
- EIP-20: Token Standard · Ethereum Improvement Proposals
- EIP-721: Non-Fungible Token Standard · Ethereum Improvement Proposals
- EIP-1155: Multi Token Standard · Ethereum Improvement Proposals
- EIP-2612: Permit Extension for EIP-20 Signed Approvals · Ethereum Improvement Proposals
- EIP-712: Typed structured data hashing and signing · Ethereum Improvement Proposals
- EIP-55: Mixed-case checksum address encoding · Ethereum Improvement Proposals
- EIP-1967: Proxy Storage Slots · Ethereum Improvement Proposals
- Permit2: AllowanceTransfer and SignatureTransfer · Uniswap, source code
- Universal Router: Commands.sol and Dispatcher.sol · Uniswap, source code
- Uniswap v4: Actions.sol · Uniswap, source code
- Multicall3 · mds1, source code
- MultiSend.sol: packed encoding of batched calls · Safe, source code
12 / MORE TOOLS
Still have a question?
All tools around blockchain and smart contracts are in the overview of Web3 tools.
- AT-W32 · Businesses
Blockchain suitability check
Does your project really need a blockchain, or will a database do? - AT-W33 · Businesses
MiCA check
Does your token fall under MiCA, and what obligations follow from that? - AT-W34 · Home & business
Gas calculator
What does a transaction cost on Ethereum, Arbitrum, Optimism, Base or Polygon? - AT-W35 · Home & business
Ethereum address checker
Is this Ethereum address valid and correctly written? EIP-55 checksum and comparison of two addresses. - AT-W36 · Businesses
Selector and topic calculator
Which function selector or event topic belongs to this Solidity signature, and the other way round? - AT-W38 · Businesses
Merkle allowlist generator
Allowlist for a mint or airdrop: Merkle root and proofs from a list of addresses.
Are you building an application whose users should understand what they are signing? We develop smart contracts and interfaces that show approvals and deadlines in plain English before confirmation, from Rodewisch.
+49 3744 4399760[email protected]Mon–Fri 8:00–17:00 · Straße der Jugend 5, 08228 Rodewisch