Curious about a word? Tap a dotted term for its meaning.

CASE 01 / INSPECT THE PERMISSION

What did you just sign?

Inspect four wallet requests, predict the authority they create, and test what happens after disconnecting, revoking or waiting.

Fictional case · Browser-localReviewed 14 Nov 2026Model boundaries & sources ↗

Follow the case.

  1. Inspect the scope

    Identify the website or spender, token, amount, network, and any deadline. A friendly button label is not the permission itself.

  2. Predict and decide

    Classify authentication, a direct payment, a limited allowance or unlimited permission. Sign or reject the fictional request.

  3. Test later access

    Disconnect the website, confirm a revocation, or leave the allowance alone. For a permit, compare submission before and after its deadline.

  4. Read the receipt

    See what moved immediately, what a spender could take later, and how much remains. Replay the same request with a different control.

The scenario controls load with JavaScript. The explanation, checklist and model boundaries remain available below.

TAKE IT WITH YOU

The question to keep asking.

A signature can authenticate, pay, or authorize later spending. Match the exact authority to your intended action; check the resulting permission after the transaction confirms.

YOUR PRACTICAL CHECKLIST

Model boundaries & mechanism sources

FOLLOW THE CONNECTIONS

Understand what sits underneath.