A familiar swap interface can still request an unfamiliar spender
Verify the transaction even on a familiar domain because a compromised interface can request different permissions or destinations.
Explore the reference
Check permissions, signatures and contracts before putting assets at risk.
49 guides · Page 1 of 3
Verify the transaction even on a familiar domain because a compromised interface can request different permissions or destinations.
An offchain signature can authorize later token movement even when signing itself has no network fee.
A DEX or aggregator does not need the recovery phrase that controls your wallet; identify the request as a secret-exposure risk.
Avoid copying lookalike recipient addresses planted in transaction history around wallet activity.
Review the exact affected contracts, time window and permissions after an aggregator announces a security incident.
Treat token scanner results as scoped evidence, including unknown states, rather than a guarantee of future sellability.
Understand why an old remaining allowance can matter again after more of the same token arrives in an account.
Understand why confirmed swaps are not normally reversible and which destination-dependent recovery paths may exist.
Unused permit signatures require scheme-specific invalidation; clearing a visible allowance may not permanently cancel the signature.
A pending private transaction can lose its intended propagation protection if a wallet rebroadcasts it through a public endpoint.
Check wallet installation provenance before entrusting an extension with signing access or recovery material.
Use readable transaction review to verify intent while recognizing that it does not audit the underlying protocol.
Token permissions are chain-local; clearing an allowance on one chain does not automatically clear similar permissions elsewhere.
A consumed SignatureTransfer authorization does not create a recurring spender allowance, but the token approval to Permit2 can remain.
A successful small token sale is evidence for that transaction, not a guarantee that a later larger exit will work.
A separately confirmed approval can remain active when a later swap reverts or never submits.
Distinguish ordinary account connection from token approval, signing and broader delegated permissions.
Disconnecting ends an application session, while token approvals remain in the token contract until changed or otherwise exhausted.
Compare the permission exposure of a narrowly sized allowance with a reusable unlimited approval.
Recognize immediate outgoing gas transfers as possible key compromise and avoid repeatedly funding an account controlled by a sweeper.