Start with the connection request

A basic connection lets a site learn the account and network you choose to share. Reading public balances and transaction history does not require a token spending approval. Review the requested accounts, networks, and permissions in your wallet.

Treat every subsequent prompt as a new request. A familiar site name does not explain what a particular signature or transaction authorizes.

Read spending permissions carefully

An ERC-20 allowance lets a specified spender move a specified token up to the permitted amount. Review the token contract, spender, network, and spending cap. Some approval mechanisms use signatures, so a request without a gas payment can still carry financial authority.

For recurring or advanced permissions, also inspect the amount, frequency, expiry, and conditions. The limits matter as much as the application requesting them.

Disconnecting and revoking are different

Disconnecting a site removes its wallet connection; it does not automatically remove onchain token allowances. Manage those approvals separately using a method that supports the correct network. An ordinary onchain revocation requires a transaction and gas.