15
wallet request patterns
Wallet Permission Lab
Know what authority a wallet prompt may create
CoinPork members can study 15 common request patterns—from basic connections and transfers to allowances, permits, NFT operators, typed data, session keys, and smart-account batches—without pasting a real payload, address, signature, or transaction.
75
fixed evidence checks
Print + MD
generic worksheet exports
Device-local
fixed states only
Authority patterns
From visible context to reusable and composite authority
Each pattern separates what the request may enable, what its appearance does not prove, five evidence questions, and an exit or revocation path. Counts remain unresolved until critical evidence is marked confirmed; the lab never produces a safety score.
ConnectionContext Only
Wallet connection request
A site asks a wallet to expose public account context and establish an application session.
- Reveal selected public addresses
- Expose network context
TokenReusable Authority
Bounded token allowance
A token holder authorizes a spender contract to transfer up to a stated amount later.
- Let a spender pull tokens later
- Remain active after the initiating page closes
TokenReusable Authority
Unlimited token allowance
A token approval grants the spender an effectively maximum reusable allowance rather than the planned amount.
- Pull the current token balance
- Pull later-received tokens
SignatureComposite Authority
Permit2 authorization
A Permit2 flow can combine an existing token approval with a signed spender, amount, nonce, and expiration authorization.
- Use a shared approval contract
- Delegate bounded spending by signature
NftReusable Authority
NFT collection-wide approval
An owner authorizes an operator to transfer every applicable item in an NFT collection.
- Move all current collection items
- Move later-acquired items
SignatureComposite Authority
Typed-data signature
Structured data asks for a signature whose effect depends on its domain, types, fields, verifying contract, and downstream consumer.
- Authorize off-chain orders
- Create relayed on-chain authority
DelegationComposite Authority
Session key or delegated authorization
A wallet delegates a bounded set of future actions to another key, application, module, or policy for a period of time.
- Approve future actions without repeated wallet prompts
- Restrict or expand functions, assets, and limits
Smart AccountComposite Authority
Smart-account batch or user operation
A smart-account request can bundle calls, sponsorship, modules, upgrades, value movement, and delegated authority into one approval.
- Execute multiple contract calls
- Install or use account modules
Included with paid membership
Search, compare, review, print, and export all 15 patterns
The protected lab stores only canonical pattern/check IDs and fixed evidence states. It does not accept or inspect real request content.
This is generic education and an organizational review aid—not a decoder, simulation, verification, certification, endorsement, security guarantee, or transaction recommendation. Use trusted current tools and authoritative sources for the actual request. Never paste secrets, addresses, payloads, signatures, or transaction data.