UNSIGNED

Before you sign,
take it apart.

UNSIGNED turns an encoded crypto request into a reading you can compare with your intent.

Review a request
Function selector095ea7b34 bytes
Address argument424242424242424242424242424242424242424220 bytes
Amount argumentffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff32 bytes
One example. Three fields to read.Take the request apart
0x095ea7b3

This is permission
to spend.

approve
4bytes identify
the function

An ERC-20 approval sets an allowance for a spender. The instruction grants permission; it does not transfer tokens by itself.

Decoded from the selector.
Contract behaviour remains unverified.

Read every
last byte.

This argument names the spender in an approval. Matching the address to your intent is a comparison, not proof of who controls it.

0x
01420242034204420542064207420842094210421142124213421442154216421742184219422042
Example spender argument20 bytes / 40 hex characters
0x4242424242424242424242424242424242424242All bytes visible. No hidden middle.

Your limit was 250.
The request says more.

The encoded amount is the largest uint256 value. That is far beyond the 250 USDC allowance in this example’s intent.

Intended ceiling250 USDC6 supplied decimals
Encoded amount in base units115792089237316195423570985008687907853269984665640564039457584007913129639935

See where
they separate.

The method and spender match the stated intent. The requested amount exceeds its ceiling.

Your intentEncoded request
MethodapproveapproveMatches
Address42 × 20 bytes42 × 20 bytesMatches
Amount≤ 250MAXExceeds limit

One field differs from your stated limits.

Matching is not a safety verdict.Inspect this reading

The request is
still unsigned.

A reading makes the differences visible. It does not establish the network, token identity, address trust or execution outcome.

Open your review

Current exampleMaximum approval / 1 differing field