ON-DEVICE · NO WALLET CONNECTION · FREE

Read the permission.
Before you sign.

DeFi approvals are easy to sign and hard to read. SignScope translates unsigned EIP-712 permits and token approval calldata into a reviewable checklist: spender, token, chain, amount, and expiry.

Paste unsigned JSON only. Never paste a signature, seed phrase, private key, or confidential wallet record. No automatic connections, approvals, transactions or RPC calls.

Sample · Base / USDC offline preview

TOKEN APPROVAL

Permit
NetworkBase · 8453
Spender0x2222…2222
Maximum amount1 USDC
DeadlineJan 2030
Read before granting accessDisplay is illustrative. A known selector is not proof of a trusted contract.
Browser-only analysis $0
0wallet connections
0external API calls
250+offline tests passed
4+permit and calldata families

Your signature scope, in plain terms.

Copy the unsigned structured message shown by a trusted app or a developer console. The browser parses it locally. Unknown data stays unknown; we never call any request “safe to sign.”

No wallet needed
Unsigned input40KB limit

No signatures. No signed transaction blob. No seed phrases. No private keys. All parsing stays on your device.

Permit2 AllowanceTransfer grants reusable approval to the declared spender; SignatureTransfer binds the intended caller in the signed EIP-712 hash while final recipient/requestedAmount come from later calldata. A local JSON preview cannot verify that later call.

For the common “I only want to swap 50 USDC” question: compare that hypothetical amount with an UNSIGNED approval request. Only recognized Base (8453) canonical Circle USDC (6 decimals) is compared. Never paste a signed transaction, wallet keys, or private actual positions. Unknown token, chain or spender stays UNKNOWN. This is NOT the current onchain allowance or a “safe to sign” verdict.

Pure browser JavaScript. No tracking or network destinations. No signatures or transactions.

Scope receiptnot a risk score
INSPECTION RESULTNo input yet

Your preview appears here.

Try a fictional sample or paste your own unsigned message. This tool does not authenticate a dApp, check smart-contract bytecode, or simulate a transaction.

—Attention signals
—Structure recognized?

What to review

  • Compare the displayed chain, contract, spender and amount with independent official documentation.
Ready for a local check. Nothing uploaded.

This is a diagnostic explanation of untrusted inputs, never an endorsement to sign or a complete safety assessment.

Four checks that change the conversation.

01

Who could move tokens?

Extract spender or recipient from recognized Permit, Permit2 and ERC-20 approve requests. If Permit2 SignatureTransfer does not include a recipient, the tool flags that missing context.

02

How much and how long?

Flag uint256/uint160 maximum approvals, zero amounts, unreadable values, expired and unusually long deadlines. Display USDC units only for Circle's known Base contract.

03

Which chain and contract?

Show EIP-712 chainId and verifyingContract or the calldata target. Compare them against addresses you independently expect; warn about missing fields or mismatches.

04

What remains unknown?

Custom contracts, Permit2 transfer recipients supplied later, dynamic calldata, approvals previously granted and real-world trust cannot be resolved from one unsigned JSON blob.

⚠
Not a transaction simulator or revocation tool.

For live allowance inspection and revocation, use an independently verified service such as Revoke.cash. SignScope does not connect to your wallet or modify approvals. It does not guarantee protection from phishing.

NEW · ACTUAL DEFI DEVELOPER PROBLEM

When Permit2 estimateGas reverts, check the call flow.

Our free, private Permit2 Debug Lab compares AllowanceTransfer vs SignatureTransfer method names, who actually calls the contract, the declared spender, token limits and expiration. Start with a fictional example; no wallet or transaction is involved. It is not a real revert simulator or a safety certificate.

Motivated by a real external Uniswap debugging question; not endorsed by Uniswap or any wallet provider.

Debug a Permit2 call locally — FREE ↗

Useful first. Payment by choice.

The basic scope explainer stays free. Paying does not grant you a “safe to sign” verdict. We can discuss a bounded technical review before any invoice.

FREE / SELF-SERVICE
$0 forever

Unsigned scope explanation

Paste JSON, compare expected chain and spender, and download an evidence-limited report. Browser-local, no wallet connection, no uploads, no sign-up.

Use the free checker ↗
OPTIONAL / DIRECT USDC SUPPORT
1 USDC suggested tip

Support independent tooling

If this free tool helps you, you can voluntarily send native Circle USDC on Base mainnet to the existing same-owner VM5 merchant wallet below. This is a tip, not an investment or paid audit order.

BASE USDC RECIPIENT (PUBLIC)0x6b01efA0705E91a7aca54271510bf9e594717f34
Open 1 USDC ERC-681 wallet request ↗

An ERC-681 URI is a payment request only. Verify Base chain, Circle native USDC, full recipient and amount inside your wallet before confirming; compatibility varies. No charge occurs by viewing this page.

CUSTOM / AGREED SCOPE FIRST
15 USDC proposed fixed pilot

Technical permit scope review

For a developer or protocol operator: one publicly shareable unsigned EIP-712 specimen, scope interpretation, clear assumptions and a concise red/green test outline. AI-assisted and independently scoped.

View 15 USDC fixed offer ↗ Ask about scope before buying ↗ See a FREE fictional sample report ↗

This is one buyer-initiated fixed-price listing on the original same-owner Clawlancer seller, NOT an automatic charge or completed contract. Work begins only after the funded order and a permitted public/nonsecret scope are mutually accepted. Do not send funds outside the verified marketplace. A marketplace listing is not a commissioned order; scope, acceptance, AI assistance and terms must be agreed in writing first. No private keys, signing, financial advice, formal security audit, or guaranteed safe-to-sign verdict.

Payee disclosure: SignScope's VM2 frontend and the optional existing VM5 USDC recipient belong to one beneficial human owner. No fabricated independent customer or multi-wallet purchase is claimed. Gas fees, taxes and local law may apply.

What SignScope does not promise

No chain lookups, wallet connection, transaction simulation, signature validation, approval revocation, automated monitoring, financial return or protection guarantee. Users must independently verify any token and spender contract, inspect the wallet's original signing dialog, and use an authoritative revoke checker for existing permissions. Unknown scope means ask for help or decline to sign, not "probably safe."