# What Happens When You Disconnect Your Wallet from a dApp?

![Realistic Web3 security scene showing a wallet disconnecting from a dApp while separate ERC-20 token approvals and signed Permit2 permissions remain active, with subtle Terenval Wallet branding on an Android phone](hero.webp)

**Disconnecting a crypto wallet from a decentralized application (dApp) normally ends the site's active wallet connection or removes its permission to request account access through that wallet. It does not automatically revoke smart-contract approvals already recorded on a blockchain.** A previously approved spender may still be able to transfer ERC-20 tokens within its allowance, and a previously approved NFT operator may retain authority under the NFT contract. A signed permit can also remain usable according to its own nonce, deadline, and contract rules.

That distinction is the most important safety fact in this guide: **Disconnect stops or restricts a communication channel; Revoke changes an authorization.** Some authorizations live inside your wallet software, others live on-chain, and still others are signed messages that have not yet appeared on-chain. No single button necessarily cancels all three.

> **Short answer:** When you disconnect your wallet from a dApp, you usually stop that dApp from using the existing wallet connection to request account access, signatures, or transactions. **Your tokens stay at their blockchain addresses, existing on-chain allowances remain until changed or exhausted, NFT approvals remain until changed or otherwise invalidated, and some previously signed permits can still be submitted.** If the dApp was suspicious, disconnect, check every relevant network for approvals, revoke risky allowances through a verified tool, inspect any permits you signed, and move funds to a fresh wallet if signing keys or a recovery phrase may have been exposed.

The distinction is explicit in [MetaMask's disconnection guidance](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp), the [ERC-20 token standard](https://eips.ethereum.org/EIPS/eip-20), and [Uniswap's Permit2 documentation](https://developers.uniswap.org/docs/protocols/permit2/overview). This article focuses on Ethereum and EVM-compatible dApps. Other ecosystems use different authorization models and require their own security procedures.

## Key Takeaways

- **Disconnecting is not revoking.** It changes wallet-to-dApp access, not ERC-20 allowances or NFT operator settings recorded in smart contracts.
- **A wallet address is public information.** Disconnecting can stop a site from requesting it through the wallet, but cannot make past disclosures, historical transactions, or known addresses disappear.
- **Normal connection does not expose a seed phrase.** A dApp ordinarily requests account access and proposes transactions; your wallet remains responsible for key custody and signing decisions.
- **An approval can survive for months or years.** A standard ERC-20 allowance may remain until its amount is consumed or the token contract's allowance state changes.
- **NFT permissions are separate.** `approve` and `setApprovalForAll` on ERC-721/1155 assets must be considered independently from fungible-token permissions.
- **A signature can outlive a browser session.** EIP-2612 and Permit2 authorizations have specific validity and cancellation rules; closing a tab does not revoke the cryptographic signature.
- **WalletConnect sessions can persist.** End sessions in your wallet's session manager, not just by closing the dApp page.
- **A signed login can create a website session.** Disconnecting a wallet does not reliably log you out of the site's own cookie-based account session.
- **Revocations generally need blockchain confirmation.** Changing a live ERC-20 approval commonly requires a transaction and gas on the corresponding network.
- **Network matters.** Checking Ethereum does not cover allowances on Base, Arbitrum, Optimism, Polygon, or BNB Smart Chain.
- **A compromised recovery phrase is a different emergency.** Revoking approvals cannot make a stolen private key safe again.
- **Terenval Wallet users should confirm actual features in their installed version.** Do not assume support for WalletConnect, dApp sessions, on-chain allowance scanning, Permit2 cancellation, or NFT approval management without product verification.

## What Does Connecting a Wallet to a dApp Actually Do?

A dApp may be a decentralized exchange, NFT marketplace, lending service, bridge, blockchain game, or governance interface. The website is an ordinary application interface, even if some of its financial operations are performed by smart contracts.

When you click **Connect Wallet**, the dApp typically asks an injected wallet provider or connection protocol for one or more public account addresses. The wallet may ask you to choose an account and approve access. A connected dApp can then show a personalized portfolio, prepare transaction requests, ask for signatures, or suggest network changes, subject to wallet permissions and the user's approval flows.

**Connection alone does not inherently grant a smart contract permission to take ERC-20 tokens.** A normal connection is not the same as an `approve` transaction, an NFT `setApprovalForAll` authorization, or a signed permit. Those are separate decisions, although an unsafe interface can confuse users into approving them together.

### What information can a connected dApp see?

Depending on the wallet and permission settings, a connected application may obtain your selected public address, active chain, and responses to supported RPC requests. With a known public address it can independently query public blockchain balances and past transactions. It may also learn information you enter on the website or information collected by its own analytics, cookies, or servers.

**Disconnecting is not a privacy eraser.** It generally stops *future access through a particular permission or active session*, but it does not compel the service to forget your address or other previously collected data. A public-chain balance remains observable to anyone who already knows the address.

### Can a connected dApp send transactions without you signing?

For an ordinary externally owned account, a request to sign or send a new transaction generally requires authorization from the wallet and its signing key. A malicious page cannot normally create a valid transaction from your private key merely because the connection is active. However, **a previously authorized contract can use its existing on-chain allowance without another transaction signature from you**; a previously issued transferable permit can also create risk.

Smart accounts, session keys, delegated execution, account-abstraction policies, and automation protocols may have additional authorization paths. Always review their permissions separately rather than applying an ordinary wallet connection model to every product.

## Disconnect vs. Revoke: Four Different Security Layers

There are at least four distinct kinds of access, each requiring the correct control. Confusing them creates a dangerous gap between what the user thinks has been disabled and what the blockchain still permits.

| Layer | Typical example | Where it exists | What disconnecting usually changes | Separate action if needed |
|---|---|---|---|---|
| Wallet-to-dApp connection | Site can request account information via wallet provider | Wallet/browser or active connection session | Removes or limits the site's active access | Disconnect in wallet connection manager |
| Website login session | Sign-In with Ethereum followed by session cookie | Website and browser | May have no effect on website login | Log out and invalidate sessions at site |
| On-chain spending authorization | ERC-20 allowance; NFT operator approval | Token/NFT contract on each chain | **Nothing** to the stored approval | Revoke or reduce appropriate approval on-chain |
| Off-chain signed authorization | EIP-2612 permit or Permit2 signed message | Signed data held by whoever received it; applicable contract state | **Nothing** to the signature itself | Contract-specific nonce invalidation, cancellation or expiry |

**Decision rule:** Ask which layer you want to stop. If the goal is **“Do not send me wallet prompts”**, disconnect the session. If the goal is **“This spender must not transfer my tokens”**, revoke the allowance or operator approval. If the goal is **“This website must no longer treat me as logged in”**, terminate the website session. If the goal is **“The signature I already gave must no longer work”**, investigate that signature format's invalidation mechanism.

### Why a disconnect notification can be misleading

A green success message such as *Disconnected*, *Wallet removed*, or *Session ended* usually confirms only that the interface's connection operation succeeded. It is not blockchain evidence of revoked allowances. For a token-approval revocation, look for the applicable successful transaction and verify the resulting allowance or operator state on the correct chain.

## What Actually Happens When You Press Disconnect?

The wallet or dApp may stop exposing an account to that website, remove access permissions, close a session, and update the connected-account interface. Different wallets implement the user interface differently; the exact behavior cannot be inferred from a button label alone.

In a browser-injected-wallet model, disconnecting often changes the wallet's account-sharing permission for a given website origin. [EIP-2255](https://eips.ethereum.org/EIPS/eip-2255) describes wallet permission concepts, while [EIP-1193](https://eips.ethereum.org/EIPS/eip-1193) standardizes a provider communication interface. These are **client-side access arrangements**, not automatic edits to the state of token contracts.

**Technical precision:** the `disconnect` event defined by EIP-1193 refers to the provider's loss of connectivity to all supported chains. It is **not itself a universal standard command for revoking website account permissions**. User-facing “Disconnect site” controls may therefore work through wallet-specific permission systems, separate connection libraries, or WalletConnect session termination.

### Does Disconnect cost gas?

Ordinarily no. Ending a wallet session or removing website account-sharing permission is a local/off-chain operation, so you should not need blockchain gas merely to disconnect. If a tool asks you to sign and broadcast a transaction, inspect its exact purpose: it may be performing an on-chain revocation instead, or could be a malicious request masquerading as a cleanup operation.

### What does not happen?

Your wallet is not deleted. Your recovery phrase does not change. Your public addresses are not destroyed or hidden from chain observers. Completed blockchain transactions are not reversed. Token allowances and NFT approvals are not automatically set to zero, and pending transactions do not vanish from the network just because the dApp page closes.

## Why Can a dApp Still Move Tokens After It Is Disconnected?

Ethereum ERC-20 tokens implement an allowance mechanism. The token owner can authorize a **spender address** to transfer up to a permitted amount of a specific token. In the standard flow, the owner approves a spender using the token's `approve` method; the authorized spender can then call `transferFrom`, subject to the current allowance, balance, and contract behavior.

Consider a wallet with **2,000 units of an ERC-20 token**, which earlier approved a swap router to spend **5,000 units**. Disconnecting the exchange's website removes the connection but leaves the allowance state of the token contract unchanged. If the spender is callable in a way that results in an authorized transfer, it may still be capable of taking tokens within the surviving allowance, including tokens received later, until the relevant authorization is removed or exhausted.

An ERC-20 allowance alone does not mean every contract will drain funds, nor does a malicious website necessarily control the particular spender contract. **Risk depends on the actual spender contract, its code, upgrade or administrative controls, and who can invoke its token-moving functionality.** Nevertheless, an unneeded or unlimited allowance increases potential exposure if the authorized mechanism is misused or compromised.

### Example: what each action actually changes

| Action | dApp connection | ERC-20 allowance | Funds already transferred |
|---|---|---|---|
| Disconnect site | Generally removed | Unchanged | Unchanged |
| Clear browser cookies | Website session may reset | Unchanged | Unchanged |
| Set a token allowance to zero successfully | May remain connected | Reduced to zero for that token/spender pair | Unchanged |
| Set a lower finite allowance | May remain connected | Reduced to selected amount | Unchanged |
| Move remaining tokens to a new uncompromised account | May remain connected at old address | Old allowance may persist for old account | Only the moved funds leave old address |

**Important:** a token approval attaches to an owner, spender, token contract and chain. It is not normally a blanket power over every token and every network in a wallet. However, multiple separate approvals can create broad exposure, and specialized approval contracts such as Permit2 create additional layers.

### Can someone spend native ETH with ERC-20 approval?

A standard ERC-20 `approve` does not grant permission to transfer **native ETH** from an ordinary account. Native ETH is not an ERC-20 token contract balance. But wrapped ETH (WETH) is an ERC-20 token, and token approvals can apply to it. Other smart-account, delegated, or signature-based authorization systems may have broader scopes, so distinguish token allowance limits from general signing authority.

## ERC-20 Approvals: Limited, Unlimited, and Repeated Use

Token interfaces sometimes ask for an exact spending amount, a high cap, or an effectively unlimited allowance. “Unlimited approval” typically means setting an allowance near the maximum integer supported by the token. It does not mean the spender has your secret phrase or can automatically take assets from another owner address; it does mean the token-contract permission may authorize more future transfers than you presently intend.

| Approval model | Typical benefit | Principal risk | Review recommendation |
|---|---|---|---|
| Exact amount | Limits authorized token value | May require additional approvals later | Prefer for infrequent transactions if available |
| Larger capped amount | Fewer repeat approval transactions | More value potentially exposed | Reassess remaining allowance regularly |
| Effectively unlimited amount | Convenience for frequent protocol use | Long-lived exposure, including newly received tokens | Use only after evaluating spender trust and operational need |
| Zero allowance | Prevents ordinary transfers by that spender under that allowance | Does not undo past transfers or other permissions | Confirm zero result on-chain |

An allowance transaction is separate from the swap, deposit, or lending action it enables. A user may approve a spender on Monday, use it once, and leave a significant remainder enabled afterward. If the protocol ceases to be useful, the owner can usually reduce or revoke that allowance in the token contract through an appropriate wallet or approval-management interface.

### What does a successful ERC-20 revoke look like?

For a conventional ERC-20 token, revocation commonly involves calling the token's `approve(spender, 0)` method, sometimes using a wallet or explorer interface that labels the action **Revoke**. The transaction must be confirmed by the network and the resulting allowance should be checked directly. Nonstandard token behavior or certain tokens requiring a zero-first pattern can complicate updating an existing nonzero allowance.

An event log is useful but **the current contract state is the decisive check**. A transaction being “submitted” or “pending” is not equivalent to a confirmed zero allowance. You may also see gas estimates, custom-token warnings or a wallet prompt whose function name resembles the original approval operation. Verify the destination contract and amount before confirming.

## NFT Approvals: Disconnect Does Not Cancel Operators

NFT permissions differ from fungible-token allowances. Under [ERC-721](https://eips.ethereum.org/EIPS/eip-721), a wallet can approve another address for a particular token ID or authorize an operator to manage all of the owner's NFTs in that collection with `setApprovalForAll`. Under [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155), an operator can likewise be authorized to act on the owner's holdings covered by that contract.

**Disconnecting an NFT marketplace does not automatically call `setApprovalForAll(false)`.** If the operator retains approval, a compromised or malicious operator can remain a risk even after the marketplace website shows “Disconnected.”

| Permission | Scope | Typical revocation | Does Disconnect revoke it? |
|---|---|---|---|
| ERC-721 token-level `approve` | One NFT token ID | Clear/replace approval where supported; transfer can also clear it by standard rules | No |
| ERC-721 `setApprovalForAll` | Operator over owner's collection tokens | `setApprovalForAll(operator, false)` | No |
| ERC-1155 `setApprovalForAll` | Operator across the owner's applicable token IDs in that contract | `setApprovalForAll(operator, false)` | No |
| ERC-20 `approve` | Spender limit for one token contract | `approve(spender, 0)` or supported allowance update | No |

**Practical check:** Look at the *operator contract address*, *collection address*, *network*, and *approval status*. A familiar marketplace name is not enough to establish the safety of an unfamiliar operator address. Also remember that individual NFT sale listings and signed orders may have independent cancellation rules beyond token operator approval.

## Do Signed Messages and Permits Survive a Disconnect?

**Yes, potentially.** A wallet signature is a cryptographic statement made with a signing key. Its validity normally depends on what was signed and how the receiving protocol verifies it—not on whether the user currently has the dApp's website open.

Not all signatures are dangerous token permits. A well-formed [Sign-In with Ethereum (ERC-4361)](https://eips.ethereum.org/EIPS/eip-4361) message is generally used to authenticate to a website, while other typed-data signatures can authorize trading orders, token allowances, transfers, or contract-specific operations. You cannot assess them safely by assuming “a signature costs no gas, therefore it has no financial effect.”

### EIP-2612: token approvals through a signature

[ERC-2612](https://eips.ethereum.org/EIPS/eip-2612) defines a `permit` extension enabling a token owner to sign an allowance authorization off-chain. An authorized submitter can later relay that signature to the token contract, which checks items such as the owner, spender, value, nonce, domain separator, and deadline before updating allowance state.

A signature that has not been submitted on-chain may **not appear in an ordinary token-approval dashboard**. Disconnecting does not retract a copy already given to the dApp or an attacker. Its usefulness depends on whether the signature is still valid, whether its nonce has changed, and whether the deadline or other verification conditions permit execution.

**A blanket `approve(0)` is not a guaranteed cancellation of every unsubmitted permit.** If an old signed permit can still be submitted, the protocol may subsequently set allowance again. EIP-2612 invalidation commonly involves changing the relevant nonce through a valid permit or other token-specific mechanism, or waiting for expiry; inspect the token implementation and use trustworthy tools rather than guessing.

### Permit2: two distinct permission layers

Uniswap's [Permit2](https://developers.uniswap.org/docs/protocols/permit2/overview) has an important two-layer design. First, the token owner grants a standard ERC-20 approval **to the Permit2 contract**. Second, Permit2 can administer separate spender allowances or enable specified one-time transfers using signed messages and contract-specific nonce and expiry rules.

| Permit2 component | What it controls | Typical cleanup consideration |
|---|---|---|
| ERC-20 token approval to Permit2 | Token contract permits Permit2 to transfer the token | Review or revoke base approval at token level |
| Permit2 `AllowanceTransfer` permission | Permit2 tracks amount and expiry for a particular spender | Reduce/revoke spender allowance; inspect nonce and deadline |
| Permit2 `SignatureTransfer` authorization | Signature authorizes specified nonce-scoped transfer | Determine whether nonce can be invalidated before use or authorization expires |

The **one-time signature mode** is not the same as a standing per-spender allowance. Some authorizations are single-use; others are standing and time-bound. Do not say “all Permit2 approvals last forever” or “all Permit2 signatures are harmless”: the contract route, scope, nonce, amount and expiry decide the exposure. Revoking the underlying token-to-Permit2 allowance can remove an important transfer route for that token, but application-specific authorization and signature records still merit review.

### Can a message be cancelled after it was signed?

Sometimes, but **there is no universal “unsign” button**. Possible paths include a protocol's cancellation transaction, nonce invalidation, operator revocation, expiration, or, for website authentication, logout and session invalidation. Which path works depends on the exact typed-data domain and smart-contract rules. A previously executed transfer cannot be reversed by cancelling the signature afterward.

If you suspect a malicious permit was signed, use the original token or protocol's trusted documentation and, where appropriate, a reputable tool such as [Revoke.cash's permit explainer](https://revoke.cash/learn/approvals/what-are-eip2612-permit-signatures). Never enter your recovery phrase into a “permit cancellation checker.”

## Does WalletConnect Disconnect Differ from Browser-Wallet Disconnect?

WalletConnect allows wallets and dApps to communicate through a session. A session can outlive the tab or browser window in which it was established. Closing the website or switching apps should **not** be treated as proof that the session was deleted.

The [WalletConnect session documentation](https://github.com/WalletConnect/walletconnect-docs/blob/main/docs/walletkit/react-native/usage.mdx) describes session termination and `session_delete` notifications. In a compatible wallet, open its active connections or sessions section, inspect the dApp, networks and accounts in scope, and explicitly disconnect the session you no longer need.

### Why disconnect from the wallet side?

A dApp's own button may update its UI even if its website session or a different connected wallet remains active. The wallet's session list gives a second place to check which sessions its software still recognizes. Names of menus change between vendors and versions, so rely on the wallet's own current interface and help documentation rather than a generic screenshot.

A WalletConnect session can include permissions for multiple chains and methods, but **it is not identical to granting an ERC-20 token allowance**. Terminating the session stops the communication channel; token approvals on any of those chains still need on-chain review.

### A browser extension can have more than one connected account

A dApp may have access to one or more accounts, and a wallet may let you change the subset exposed to that site. Removing one account is not necessarily the same as disconnecting the entire site from every account. Always check which account is selected when reviewing permissions, approvals, or transfer activity.

## Does Disconnect Log You Out of a Website?

**Not necessarily.** A dApp can maintain a normal web session after a wallet-based sign-in. The wallet connection provides a public address and may let you sign a login challenge; a server then issues a cookie or token that keeps a website account authenticated.

[ERC-4361](https://eips.ethereum.org/EIPS/eip-4361) standardizes a Sign-In with Ethereum message format, including domain and nonce concepts. It does not promise that disconnecting a wallet automatically revokes every login session the website has already created.

If privacy or account access matters, sign out of the dApp separately, clear relevant browser sessions if necessary, and use any available **Log out of other devices / Revoke sessions** control. A website might also retain a record of your public address, analytics data, or trade history, even after logout; this is distinct from blockchain authorization.

## How to Safely Disconnect a Wallet From a dApp

Use the wallet's current interface rather than relying on a stale menu path. In [MetaMask's documented workflow](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp), for example, the wallet has a **Permissions** area that lists connected dApps and lets the user disconnect individual connections or all of them. Other wallets may label the section **Connected sites**, **Active sessions**, **DApp connections**, **WalletConnect**, or **Permissions**.

1. **Identify the dApp and origin.** Confirm the full domain; visually similar names and subdomains can represent different sites.
2. **Open the wallet's connection or permissions manager.** Avoid acting only inside a suspicious website if you can disconnect from your wallet itself.
3. **Review which accounts and chains are exposed.** Check whether you are removing one account's access or the full session.
4. **Disconnect the unwanted dApp or session.** Confirm that it no longer appears as connected in the wallet's list.
5. **Sign out of the dApp separately.** Do this if the site also authenticated you using a wallet signature.
6. **Inspect approvals on-chain.** This is a separate operation, described below; disconnect is not evidence of approval removal.
7. **If compromise is suspected, classify it.** A mere unwanted connection calls for different remedies than a malicious allowance, unsafe signature, or leaked seed phrase.

**Security rule:** A legitimate wallet connection is not an occasion to reveal a recovery phrase. If a website asks for your seed phrase, private key or backup file to “finish disconnecting,” stop immediately.

## How to Find and Revoke Token Approvals Safely

An approval audit should be deliberate. Blindly signing every “revoke” button in an unfamiliar site can create a second risk; review the transaction and choose established, accurately typed addresses.

### Step 1: determine the owner address and networks

Write down the public account address of the wallet you used and identify where it interacted with contracts. Typical EVM networks include Ethereum Mainnet, Base, Arbitrum One, Optimism, Polygon PoS, and BNB Smart Chain. A hex-formatted address can look the same across these networks, but **each network has its own contract state and approvals**.

If you connected more than one wallet account, repeat the review for each potentially exposed owner address. If you used different wallets, do not assume the session or permissions are shared between them.

### Step 2: open a reputable approval viewer

Use the approval checker linked by the appropriate block explorer or an established approval-management interface. The official [MetaMask approval-revocation guide](https://support.metamask.io/more-web3/learn/how-to-revoke-smart-contract-allowances-token-approvals/) discusses approval checkers and allowance-management tools. [Revoke.cash](https://revoke.cash/) is another commonly used option.

Before connecting to any revocation tool, verify the URL from an authoritative source or a trusted bookmark. A read-only inspection of a public address may be possible without granting a new wallet session, depending on the tool. **Never supply private keys or seed phrases.**

### Step 3: identify the approval, not just the brand label

For each finding, inspect **network, owner, token/collection contract, approved spender or operator, approved amount, and where possible transaction history**. Look for unlimited allowances, unfamiliar spender addresses, protocols you no longer use, unexpectedly broad NFT approvals, and multiple networks with related exposure.

A spender name or logo is merely an interface label. The on-chain spender address and contract behavior determine authority. A malicious spender might impersonate an established service, so do not rely solely on the name displayed by a third-party dashboard.

### Step 4: revoke or reduce the specific permission

Select the permission you intend to remove. For standard ERC-20 this typically means setting the allowance to zero; for ERC-721/1155 `setApprovalForAll`, setting approval to **false**. Review the wallet transaction carefully, including the network, destination contract, intended function, gas cost and resulting permission setting.

**Do not transfer assets, approve a new unknown spender, or sign unrelated permits as part of a claimed “revoke.”** A genuine revocation should have an understandable effect on the relevant contract state.

### Step 5: wait for finality and verify again

A submitted transaction is not necessarily mined. Check the status in a trusted explorer, then refresh the allowance or operator state after confirmation. If the transaction fails, is replaced, or remains pending, do not claim the permission has been revoked.

If the wallet has no native approval-management feature, use a compatible trusted external tool rather than claiming your wallet can perform a function it does not expose. A small gas balance on the **correct network** is often needed to complete the revocation.

### Step 6: separately review permits and other authorizations

A dashboard showing no ERC-20 allowances is **not a complete proof of safety**. Consider whether you signed EIP-2612, Permit2, an NFT order, an account-abstraction authorization, or another protocol-specific message. Some off-chain signatures may be invisible to public allowance scans until exercised. Apply the cancellation method supported by the actual protocol.

## Which Chain Must You Check: Ethereum, Base, Arbitrum, or BNB Chain?

Each EVM chain maintains independent state. For example, a wallet address may approve a token spender on Ethereum Mainnet and have no approval for that token on Base; it can also have entirely different approvals on Base or Arbitrum. A chain's token contracts and spender contracts are distinct, even when wallets show the same human-readable token ticker.

| Network | What to review | Common oversight |
|---|---|---|
| Ethereum Mainnet | ERC-20, NFT and signature-derived authority | Mistaking website disconnect for on-chain revoke |
| Base | Base-specific spender and token contracts | Checking only Ethereum Mainnet |
| Arbitrum One | Arbitrum token and router approvals | Assuming a cross-chain bridge removed approvals |
| Optimism | Local allowances and operator permissions | Missing a second dApp account |
| Polygon PoS | Local token, NFT and contract state | Confusing bridged or look-alike assets |
| BNB Smart Chain | BEP-20-style token allowances and operators | Assuming identical 0x addresses imply shared permissions |

A token with the same symbol on two chains may have a different contract address or implementation. Check the actual chain and contract rather than trusting a ticker. If you know you used a different ecosystem such as Solana, consult its specific authorization and account-management model; ERC-20 revocation instructions do not automatically apply.

## What Does Revoking Approvals Cost?

**Reading public contract state is generally free of blockchain gas; changing contract state usually is not.** A standard allowance revocation is a transaction executed on a network and commonly requires a network fee paid in that chain's native gas asset. Prices fluctuate with network conditions, execution complexity, transaction type and chain rules.

For illustration only, if a hypothetical revocation uses **45,000 gas** at an effective **0.5 gwei**, its execution cost would be **22,500 gwei**, or **0.0000225 ETH** on a chain where ETH is the gas token. This is arithmetic, *not* an estimate of the current fee, and it excludes network-specific or protocol-specific components that may apply. A different gas price or actual gas used produces a different total.

| Operation | Typically an on-chain transaction? | Usually needs gas? | Reverses prior asset transfers? |
|---|---|---|---|
| Disconnect dApp session | No | No | No |
| Log out of website | No | No | No |
| Read allowance from explorer | No | No | No |
| Revoke ERC-20 allowance | Yes | Yes | No |
| Disable NFT operator approval | Yes | Yes | No |
| Invalidate on-chain nonce | Depends on protocol | Often yes | No |
| Wait for a signed permit to expire | No new transaction | No, but may leave a risk until expiry | No |

### Is an expensive revoke still worth it?

Evaluate **maximum potentially exposed assets, identity of the spender, likelihood of misuse, time remaining before authorization expires, and gas cost**. For high-value assets or a suspicious spender, risk reduction can outweigh the transaction fee. For a harmless unused allowance with negligible exposure, a user may make a different decision. Avoid claiming an exact financial return from a security transaction.

## Practical Risk Assessment: Not Every Approval Has the Same Exposure

A basic audit should distinguish a connection you simply forgot from a genuine ability to move valuable tokens. There is no safe universal score that replaces reading contracts, but the following diagnostic framework can help set review priorities.

| Situation | Main exposure | Priority | Appropriate first step |
|---|---|---|---|
| Unknown dApp connected, no transactions or signatures known | Ongoing prompts and account disclosure | Moderate | Disconnect, inspect activity and website sessions |
| Known dApp with exact small allowance | Limited authorized token amount | Context-dependent | Review spender and whether allowance still needed |
| Unknown spender with unlimited allowance over valuable tokens | Potentially large continuing token exposure | High | Confirm identity, urgently evaluate and revoke |
| NFT collection-wide approval for unfamiliar operator | Broad NFT transfer authority | High | Review and disable suspicious operator |
| Suspicious Permit2 signature, not yet executed | Possible future on-chain transfer or allowance | High and time-sensitive | Investigate nonce/deadline and supported invalidation |
| Seed phrase or private key disclosed | Full signing-key compromise | Critical | Move assets to a newly generated secure wallet |
| Already completed malicious transfer | Assets already moved | Critical for remaining funds | Preserve evidence, secure remaining holdings, report |

**Limitations:** “High” here is a qualitative risk triage, not a live assessment of a specific contract, token value, or exploit probability. Some approved contracts are upgradeable, some have restricted transfer paths, and some custom permissions are not captured by generic explorers.

## Seven Realistic Scenarios: What Actually Protects You?

### Scenario 1: You connected to a DEX but never signed anything else

If you only approved sharing a public account address, disconnecting should end the wallet connection or permission path according to that wallet's implementation. Inspect your transaction and signature history anyway if the site looked suspicious, but **do not assume a token allowance exists merely because you connected**. There may be no on-chain permission to revoke.

### Scenario 2: You swapped once and approved a high spending cap

The swap itself may be complete, yet the router's token allowance can remain. Check that token, spender address and chain. If you do not plan future interactions and the risk is meaningful, revoke or lower the remaining allowance. Disconnecting the website alone is insufficient.

### Scenario 3: You listed an NFT, then disconnected the marketplace

The marketplace page may show “Wallet disconnected,” but an NFT collection-level operator approval may still exist. Review both the NFT operator permission and any signed marketplace orders under the marketplace's rules. Cancelling a listing and revoking the operator are distinct actions; some orders have on-chain cancellation mechanisms or expirations.

### Scenario 4: You signed a message that looked like a normal login

Determine whether it was actually SIWE authentication or typed data containing spender, value, token, nonce, or deadline fields. A valid signed token permit may be usable later even if your wallet shows no pending transaction. Disconnect, verify message details if saved, inspect relevant protocol documentation and invalidate signatures where possible.

### Scenario 5: You closed a WalletConnect browser tab

The session may remain active in the wallet. Open its active sessions screen and explicitly disconnect the dApp. Then review any previous on-chain approvals separately; closing a tab is not equivalent to either session termination or allowance revocation.

### Scenario 6: You revoked an approval but the transaction is still pending

Until the successful change is included on-chain and sufficiently confirmed, the earlier allowance may continue to apply. Some competing transactions can be ordered ahead of a revocation, and already confirmed transfers are final. Monitor the transaction status, do not trust a pending badge, and seek reliable incident-specific advice if funds are at immediate risk.

### Scenario 7: You entered your recovery phrase into a “security checker”

Treat the underlying private keys as compromised. **Do not rely on Disconnect or Revoke as a complete solution.** Generate a fresh wallet in a trusted environment, secure its backup, prioritize transferring remaining assets where feasible, and review secondary permissions and connected accounts. Never enter the same compromised phrase into another tool claiming to undo the leak.

## What to Do Immediately After Connecting to a Suspicious dApp

There is no single response appropriate to every mistake. Triage the event by the **highest authority you may have granted**.

1. **If you only connected:** Disconnect via your wallet, review the website session, verify activity and scan for unknown authorizations. A simple connection does not automatically prove funds can be taken.
2. **If you approved token or NFT spending:** Identify the precise owner, token, spender/operator, network and scope. Use an established checker to revoke or reduce suspicious access; verify final on-chain state.
3. **If you signed typed data or a permit:** Preserve the signed message details if available. Investigate whether the signature can still execute, its chain, deadline and nonce. Use the relevant protocol's trusted cancellation/invalidation procedure.
4. **If you already signed an unknown transaction:** Check the actual transaction hash and its status. A pending transaction may execute regardless of whether the app has been disconnected.
5. **If you leaked a private key or recovery phrase:** Treat all keys derived from that backup as exposed. Move assets to securely generated fresh keys where feasible, without entering secrets into websites or fake support tools.
6. **If assets have been stolen:** Preserve transaction IDs, addresses, timestamps and URLs; report to the relevant services and authorities. Recovery is not guaranteed and blockchain transfers generally cannot be reversed.

Use official [Ethereum.org scam response guidance](https://ethereum.org/community/support/scams/) as a reference. Attackers commonly pose as “security support” and offer paid recovery or one-click rescue links; such offers can compound the loss.

## Can Disconnecting a dApp Recover Stolen Crypto?

**No.** Disconnecting is a preventive access-management step. It does not reverse a transfer that was validly included in a block. Revoking an allowance may protect remaining tokens against further transfers by that spender after the revoke takes effect, but it cannot rewind completed theft.

Even a legitimate revocation tool is not a recovery service. If you see an unfamiliar withdrawal, look up the actual transaction in an explorer, identify the initiating account and contract calls if possible, and preserve evidence. Do not assume every unexplained transfer is an allowance exploit; stolen keys, malicious signatures, compromised accounts, NFT operators and smart-account delegations can produce different on-chain behavior.

## How Often Should You Audit Wallet Approvals?

There is no blockchain rule requiring a weekly or monthly audit. A useful risk-based practice is to **review approvals after interactions with unfamiliar dApps, after a notable security incident, before leaving a protocol unused for a long time, and whenever a wallet holds valuable tokens subject to broad allowances**. Some users also prefer a periodic review, but the cadence should fit their activity and the assets at risk.

If a dApp requires frequent approval, consider whether a smaller spending cap or protocol-specific expiry can reduce exposure without excessive operational friction. Revoke obsolete authorizations, but remember that reconnecting to a protocol later may legitimately require granting permission again.

## Common Misconceptions About Disconnecting Crypto Wallets

| Myth | Reality |
|---|---|
| “Disconnect means the dApp forgets my wallet address.” | It may stop current account sharing; the address and public chain history remain available. |
| “Disconnected means a router cannot move my tokens.” | Existing on-chain allowance can remain until changed or exhausted. |
| “Closing my tab logs me out of everything.” | WalletConnect and website login sessions may persist. |
| “A gasless signature cannot risk funds.” | Some signed permits and orders create later executable authority. |
| “I revoked Ethereum approvals, so Base and Arbitrum are safe.” | Each network's approvals must be checked separately. |
| “A hardware wallet prevents approval exploits.” | Hardware devices protect keys, but previously authorized contract logic can still spend within permission scope. |
| “Revoke recovers tokens already stolen.” | It normally only changes future authorization; past confirmed transfers remain. |
| “Every approval scanner finds every signed threat.” | Unsubmitted off-chain signatures and specialized permissions may not appear. |
| “A strange approval always means a hack.” | Legitimate applications also use spenders and operators; identity, scope and contract behavior matter. |

## Using Terenval Wallet Responsibly Around dApps

[Terenval Wallet](https://wallet.terenval.com/?lang=en) is presented here as an Android-oriented self-custody option for users who want direct responsibility for their wallet and crypto transfers. The most important transferable skill is **understanding which signatures and spending permissions an application requests**. Your choice of wallet does not change the underlying semantics of ERC-20 allowances or EVM NFT operator approvals.

**Product-feature boundary:** This guide does *not* assert that the current Terenval Wallet release supports WalletConnect, an integrated dApp browser, ERC-20 approval revocation, Permit2 cancellation, advanced signature decoding, or NFT operator management. Verify supported chains, signing flows, and security features in the actual installed build or official product documentation before using any dApp workflow. If a needed feature is not available, use a well-established compatible wallet or read-only explorer workflow rather than improvising with private keys.

To begin with basic self-custody, [open the official Terenval Wallet application](https://wallet.terenval.com/?lang=en), verify the correct website domain, and follow the supported wallet setup instructions. Back up recovery information offline and do not paste it into permission tools. For a related primer, see [What Does “Sign Message” Mean in a Crypto Wallet, and Is It Safe?](https://wallet.terenval.com/answers/what-does-sign-message-mean-in-a-crypto-wallet-and-is-it-safe/).

## Wallet Disconnect and Approval Safety Checklist

Before you consider a former dApp relationship fully reviewed, confirm the following:

- [ ] I know the **exact website origin** and wallet account involved.
- [ ] I have **disconnected the unwanted session** in the wallet's own connection manager.
- [ ] I separately **logged out of the website**, where relevant.
- [ ] I know whether I **signed transactions, token approvals, NFT permissions, or typed-data messages**.
- [ ] I checked **the correct EVM networks**, not only Ethereum Mainnet.
- [ ] I verified **token contracts and spender/operator addresses**, not merely labels.
- [ ] I have revoked or reduced **unneeded risky on-chain permissions** and verified their confirmed state.
- [ ] I reviewed possible **EIP-2612, Permit2, NFT-order, or custom signature** exposure.
- [ ] I understand that **prior on-chain transfers and disclosed addresses are not erased**.
- [ ] If a key or seed phrase was exposed, I have a **fresh, uncompromised wallet recovery plan**, not only disconnected the old site.
- [ ] I did not enter my seed phrase into a dApp, explorer, approval checker, or support chat.

## Analytical Model: How Much Token Value Can a Standing Allowance Expose?

A spender's nominal ERC-20 allowance is not the same thing as an immediate guaranteed loss. The amount transferable through an ordinary allowance is constrained by at least **the remaining allowance, the owner's current token balance, and the token/contract execution rules**. If the spender has a route to exercise its authority and the token behaves conventionally, a simplified upper bound for an immediate transfer is:

**Immediately transferable amount ≤ minimum(current token balance, remaining spender allowance).**

This bound is deliberately narrow: it does not account for protocol-specific limits, transfer restrictions, transaction ordering, or rights outside an ordinary ERC-20 allowance. It also says nothing about the probability that the spender will misuse the authorization. Future token deposits can increase the amount exposed if an allowance remains unused.

### Three hypothetical allowance profiles

| Wallet token balance | Remaining allowance | Simple immediate upper bound | Important future implication |
|---|---:|---:|---|
| 100 tokens | 25 tokens | 25 tokens | Permission ends once consumed, absent new approval |
| 100 tokens | 1,000 tokens | 100 tokens | Additional incoming tokens may also be exposed until allowance exhausted |
| 0 tokens | Effectively unlimited | 0 tokens right now | Future deposits may be at risk while authorization remains |

**Example:** A user disconnects from a contract that has a 1,000-token allowance. Their current balance is 100 tokens. The permission could allow at most 100 of those tokens to be transferred immediately under a simple ERC-20 model. If 500 additional tokens arrive and the original allowance has not been consumed, potential exposure can rise. The fact that the wallet was disconnected has no mathematical effect on the allowance or balance.

For an NFT `setApprovalForAll` grant, this arithmetic does **not** apply. Authority may extend across the collection rather than up to a fungible-token amount. For Permit2 and custom accounts, an independent allowance layer, signed quantity, expiry, nonce, and valid execution path may all matter. The useful question is not **“Did I disconnect?”**, but **“What can this verified spender or signer still do right now?”**

## Frequently Asked Questions

### What happens to my crypto when I disconnect my wallet from a dApp?

Your crypto stays recorded at the same blockchain addresses; disconnecting does not transfer, delete, freeze, or return it. The change usually affects the website's wallet connection and permission to request account information or new signing actions. Any previously granted smart-contract or signature-based authority must be evaluated separately.

### Does disconnecting a wallet revoke token approvals?

**No.** Disconnecting a dApp usually does not change ERC-20 token allowances stored in token contracts. Use a trusted approval-management workflow to reduce or revoke a specific token/spender pair, and confirm the result on the relevant blockchain. MetaMask explicitly distinguishes these procedures in its official documentation.

### Is disconnecting from a dApp the same as revoking smart contract access?

Not generally. “Smart contract access” is an imprecise expression that can mean an ERC-20 allowance, NFT operator permission, signed permit, account delegation or even a website connection. Identify which specific authorization exists before choosing an action. The wallet's Disconnect button normally addresses only the connection layer.

### Can a dApp still take my tokens after I disconnect?

Potentially **yes**, if a spender still has valid authority to move those tokens, such as a usable ERC-20 allowance or NFT operator approval. A malicious party cannot necessarily exercise every allowance just because it exists; the real spender's contract code and access rules matter. Nevertheless, a surviving dangerous allowance remains a risk after disconnect.

### Can a dApp see my wallet balance after I disconnect?

If the site already knows your public address, it or anyone else can query public-chain balances and historical transfers. Disconnecting may prevent the app from requesting your current account through the wallet provider, but it cannot make public blockchain information private or erase previously recorded identifiers.

### Does disconnecting a wallet remove transaction history?

No. Blockchain transaction history is public and persistent on ordinary public chains. The wallet or dApp may hide a personalized activity panel after disconnection, but this is a change in presentation rather than deletion of on-chain records.

### Does a dApp know my seed phrase when I connect?

Ordinary wallet connection does **not** reveal a recovery phrase or private key. The wallet mediates addresses, signatures and transaction requests. A site that asks you to type, upload or paste a seed phrase as a prerequisite to connecting, disconnecting, checking approvals or collecting rewards is unsafe.

### Do I have to pay gas to disconnect my crypto wallet?

Usually no. A connection/session termination is generally off-chain. Gas is commonly required when you broadcast a separate transaction to revoke or modify a smart-contract permission. A Disconnect button that unexpectedly requests a token-transfer or approval signature should be treated cautiously.

### Do I have to pay gas to revoke an ERC-20 approval?

In ordinary EVM token contracts, yes: changing a live allowance requires a transaction that consumes network resources. The exact cost depends on chain conditions and the particular call. Reading an allowance through a block explorer normally does not require paying gas.

### How do I revoke a token approval after disconnecting?

Identify the chain and public owner address, open a verified chain-specific approval checker, find the token contract and spender, choose the intended allowance reduction or revocation, inspect the transaction in your wallet, and confirm it. Then check the actual allowance state after inclusion. Avoid URLs sent by unknown “security support” contacts.

### Does revoking an allowance remove my tokens from a DeFi protocol?

Usually not by itself. Revoking a token allowance normally changes whether a spender can make **future token transfers from your address** through that permission. It does not automatically unwind a deposit, repay a loan, withdraw staked assets, redeem pool tokens or close a position. Review each protocol's withdrawal and position-management steps separately.

### Can I revoke one dApp without affecting other dApps?

Generally yes when the authorization is scoped to an individual spender/operator and token or collection. However, shared approval systems, routers, proxies and Permit2 may serve multiple application flows. Verify the actual contract and downstream relationships before assuming a single human-readable dApp corresponds to one on-chain spender.

### Does clearing my browser history or cache revoke approvals?

No. Browser history, cache, cookies and local storage do not control the allowance state already recorded on a blockchain. Clearing cookies may affect website login sessions, and clearing site data may reset a local connection indicator, but token permissions need the appropriate on-chain or protocol-specific action.

### If I disconnect a WalletConnect session, is it fully terminated?

A correctly processed session disconnect removes that session's communication channel according to the wallet's WalletConnect implementation. Verify that the session disappears from the wallet's active-session list. **It still does not revoke ERC-20 allowances or cancel previously signed permits.** A separate website login session might also remain active.

### Can WalletConnect stay connected after I close a tab?

Yes. WalletConnect sessions can persist beyond a browser tab's lifetime. Use the wallet's session manager to inspect and explicitly end unused connections. Closing a tab, minimizing the app or switching networks is not a reliable substitute for disconnecting a session.

### Does Disconnect cancel an NFT approval for all tokens?

No. A collection-wide NFT operator approval typically persists until the applicable NFT contract's permission state is changed. For standard ERC-721 or ERC-1155 operator approvals, review `setApprovalForAll` and, when appropriate, submit a `false` revocation. Separately check any outstanding signed marketplace orders.

### What does `setApprovalForAll` mean?

For supported NFT contracts, it authorizes an operator to manage the owner's NFTs covered by that token contract. The scope can be much broader than approving one NFT. The exact operator address, collection contract and chain matter; it is not equivalent to simply sharing an address with a marketplace.

### Is an unlimited token approval always a scam?

No. Some legitimate dApps request large or unlimited allowances for convenience and repeated transactions. The security trade-off is that more value can remain authorized longer than necessary. Evaluate the spender's identity and contract behavior, product need, potential upgrade rights and your asset exposure rather than deciding solely from the word “unlimited.”

### Is there a way to set a smaller token spending limit?

Often yes, if the wallet interface and token/protocol permit it. ERC-20 allowances are amounts, not merely yes/no switches, and some wallets display a customizable cap. Other systems implement signed amounts and expiration dates. Confirm the final authorized amount on-chain and do not assume every token or wallet offers the same controls.

### Does a signed message remain valid after disconnecting?

It can. Message validity follows its signing domain, nonce, expiry and application or smart-contract verification rules—not the wallet's current website connection. A harmless login message and a financial permit have different consequences, so review the actual message content and signing method before assessing exposure.

### Can a signed EIP-2612 permit be cancelled?

Sometimes through a token-specific nonce-changing mechanism or by waiting for its deadline, provided it has not already been exercised. There is no universal reversal that works for every token's implementation. A simple visible allowance of zero does not prove an old, unsubmitted permit has been invalidated. Investigate the particular token's rules and trustworthy tooling.

### What is the difference between Permit2 and a normal ERC-20 approval?

A normal ERC-20 approval authorizes a spender directly in the token contract. Permit2 commonly begins with a token-level approval to the Permit2 contract and then manages additional spender-specific allowances or signed transfer authorizations. These layers have distinct limits, nonces and expiration behavior, so one dashboard entry may not tell the complete story.

### Does a Permit2 signature always allow repeated transfers?

No. Uniswap documents separate modules: `SignatureTransfer` supports nonce-scoped single-use authorizations, while `AllowanceTransfer` supports standing, time-limited allowances. The risk depends on the actual signed operation and contract state. Disconnecting does not invalidate either type merely by ending the UI session.

### What is the difference between Sign-In with Ethereum and a token permit?

SIWE (ERC-4361) is designed for authenticating account ownership to a service using a structured login message. A token permit authorizes token spending under a token or approval contract. Both involve signatures, but their economic scope differs. Read the domain, contract, spender, value, chain and deadline fields when applicable, and reject unexpected signing requests.

### What if a revocation transaction is pending while an attacker has an approval?

Treat the old authorization as potentially active until the on-chain state changes successfully. Transactions can be included in an order you cannot control, and already executed transfers cannot be rolled back. Monitor the correct chain and transaction status. If the situation involves substantial funds, prioritize proven incident-response procedures rather than blindly increasing gas fees or signing unknown “recovery” transactions.

### If my recovery phrase was stolen, should I just revoke everything?

No. Someone with the seed or private key may be able to produce new valid signatures and transactions. Revoking particular allowances cannot invalidate that stolen signing authority. The priority is to secure remaining assets with newly generated uncompromised keys, subject to chain fees, operational risks and the possibility that an attacker is monitoring the old account.

### Can revoking approvals return crypto already stolen?

No. Revocation is generally preventive, not restorative. A confirmed unauthorized transfer cannot usually be reversed by disconnecting or setting an allowance to zero. Preserve evidence and report the incident; be suspicious of anyone promising guaranteed recovery for a fee.

### Can I disconnect from dApps on Ethereum, Base and Arbitrum at once?

Some wallets support disconnecting an entire site or multichain WalletConnect session, which may stop multiple network communication channels together. That does **not** merge blockchain authorization state. Token/NFT approvals on Ethereum, Base and Arbitrum still need separate verification on their respective networks.

### Can I use the same wallet address on several EVM networks?

Often yes for a conventional externally owned account, which can produce the same `0x` address on multiple compatible chains. However, tokens and allowances are stored in distinct contracts on each chain. The shared address does not imply that disconnecting or revoking a contract on one chain changes any permissions on another.

### Is disconnecting a suspicious dApp enough if I only connected once?

If you genuinely only granted basic wallet account access and never signed a relevant transaction or permit, disconnecting may be the principal wallet-related remedy. Still review account activity and any website session if the dApp was clearly malicious, because users can overlook an earlier confirmation or another connected account.

### Can a hardware wallet protect against malicious approvals?

A hardware wallet can help prevent private-key theft and require review of signing requests. But if you deliberately authorize an unsafe spender or sign a dangerous permit, that authorization may still be valid on-chain or cryptographically. Hardware custody reduces some risks; it does not replace understanding transaction details.

### Can I manage dApp permissions inside Terenval Wallet?

Do not assume an integrated permissions manager, WalletConnect session screen or token-approval revoke feature is present in every Terenval Wallet release. Check the version you installed and its documented functionality. The general guidance in this article remains applicable to compatible wallets that do support those actions, and public-chain approvals can be inspected through verified external explorers when appropriate.

## Key Terms

- **dApp (decentralized application):** An application whose operations may call blockchain smart contracts through a wallet-controlled interface.
- **Wallet connection:** A permission or session that lets a dApp request account information, signatures, or transaction proposals through a wallet.
- **Disconnect:** Removing or ending an active wallet-to-application connection or account-sharing grant.
- **ERC-20 allowance:** A token contract's recorded maximum amount a designated spender may transfer on behalf of an owner, subject to its rules.
- **Spender:** The address authorized by a token owner to call token-spending functionality under a specific contract.
- **`approve`:** A typical ERC-20 function for setting an allowance, including a zero-value revocation.
- **`transferFrom`:** A token function allowing an authorized spender to transfer tokens subject to its existing allowance and balance constraints.
- **NFT operator:** An address authorized by an NFT contract owner for transfers under permissions such as `setApprovalForAll`.
- **`setApprovalForAll`:** An NFT approval function controlling whether an operator can manage applicable tokens held by the owner.
- **WalletConnect session:** A persistent communication authorization between a wallet and dApp, with a defined set of accounts, networks and methods depending on implementation.
- **Sign-In with Ethereum (SIWE):** A structured message authentication standard defined by ERC-4361.
- **Permit:** A signed authorization that can grant token spending rights according to the verifying contract's nonce, deadline and other rules.
- **EIP-2612:** A standard defining signed ERC-20 token allowance updates through `permit`.
- **Permit2:** A Uniswap-developed token permission system with standing allowance and one-time signature-transfer paths.
- **Nonce:** A value used by protocols to track or invalidate signed authorizations and prevent unauthorized replay under defined rules.
- **On-chain revocation:** A confirmed transaction that modifies permission state in a smart contract.
- **Off-chain signature:** Signed data that may be stored away from the blockchain and later presented to a verifier or contract.
- **Gas:** Network execution cost generally payable when changing smart contract state on EVM networks.
- **[Wallet address](https://wallet.terenval.com/glossary/wallet-address/):** A public destination identifier that can often be queried on a blockchain explorer.
- **[Non-custodial wallet](https://wallet.terenval.com/glossary/non-custodial-wallet/):** A wallet arrangement where the user remains responsible for signing-key control and recovery information.

## Related Terenval Answers

- [What Does “Sign Message” Mean in a Crypto Wallet, and Is It Safe?](https://wallet.terenval.com/answers/what-does-sign-message-mean-in-a-crypto-wallet-and-is-it-safe/)
- [What Is a Crypto Wallet and What Does It Store?](https://wallet.terenval.com/answers/what-is-a-crypto-wallet-and-what-does-it-store/)
- [What Is a Wallet Derivation Path and Why Does It Matter for Recovery?](https://wallet.terenval.com/answers/what-is-a-wallet-derivation-path-and-why-does-it-matter-for-recovery/)
- [What Is a Crypto Exchange Withdrawal Address Whitelist?](https://wallet.terenval.com/answers/what-is-a-crypto-exchange-withdrawal-address-whitelist/)
- [How to Recover Crypto Sent to the Wrong Network](https://wallet.terenval.com/answers/how-to-recover-crypto-sent-to-the-wrong-network/)

For more wallet-security explainers, explore [Terenval Answers](https://wallet.terenval.com/answers/). To learn about self-custody and current availability, visit the [official Terenval Wallet application](https://wallet.terenval.com/?lang=en).

## Primary and Authoritative Sources

- [MetaMask — How to Disconnect a Wallet from a dApp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp)
- [MetaMask — How to Manage dApp Permissions](https://support.metamask.io/more-web3/dapps/manage-dapp-permissions)
- [MetaMask — How to Revoke Smart Contract Allowances](https://support.metamask.io/more-web3/learn/how-to-revoke-smart-contract-allowances-token-approvals/)
- [MetaMask — Managing Spending Caps](https://support.metamask.io/metamask-portfolio/overview/spending-caps-portfolio/)
- [EIP-1193 — Ethereum Provider API](https://eips.ethereum.org/EIPS/eip-1193)
- [EIP-2255 — Wallet Permissions System](https://eips.ethereum.org/EIPS/eip-2255)
- [ERC-20 — Token Standard](https://eips.ethereum.org/EIPS/eip-20)
- [ERC-721 — NFT Standard](https://eips.ethereum.org/EIPS/eip-721)
- [ERC-1155 — Multi Token Standard](https://eips.ethereum.org/EIPS/eip-1155)
- [ERC-2612 — Permit Extension for Signed Token Approvals](https://eips.ethereum.org/EIPS/eip-2612)
- [ERC-4361 — Sign-In with Ethereum](https://eips.ethereum.org/EIPS/eip-4361)
- [Uniswap Developers — Permit2 Overview](https://developers.uniswap.org/docs/protocols/permit2/overview)
- [WalletConnect — Session Disconnect Documentation](https://github.com/WalletConnect/walletconnect-docs/blob/main/docs/walletkit/react-native/usage.mdx)
- [Revoke.cash — Frequently Asked Questions](https://revoke.cash/learn/faq)
- [Revoke.cash — Permit Signature Cancellation](https://revoke.cash/learn/approvals/what-are-eip2612-permit-signatures)
- [Revoke.cash — Permit2 Permissions](https://revoke.cash/learn/approvals/what-is-permit2)
- [Ethereum.org — Scam Help and Reporting](https://ethereum.org/community/support/scams/)
- [Terenval Wallet — Official Application](https://wallet.terenval.com/)

*Editorial note (27 October 2026): This guide separates protocol-defined behavior from wallet-interface behavior and illustrative risk analysis. Exact menus, networks, connection methods and revocation tools may change. A successful disconnect is not evidence of a successful on-chain revocation. All hypothetical balances and gas calculations are educational and are not measurements from real Terenval transactions. Product mentions are not claims that Terenval Wallet currently exposes a particular dApp connection, permission scanning, NFT approval, Permit2 or WalletConnect feature. The article does not request seed phrases, private keys or signatures, and is not personalized legal, security or financial advice.*

## Editorial & technical review

- Published by: Terenval
- Technical review: Terenval Wallet team
- Last reviewed: 2026-10-27

## Sources

- [MetaMask Help Center — How to Disconnect a Wallet from a dApp](https://support.metamask.io/more-web3/dapps/disconnect-wallet-from-a-dapp)
- [MetaMask Help Center — How to Manage dApp Permissions](https://support.metamask.io/more-web3/dapps/manage-dapp-permissions)
- [MetaMask Help Center — How to Revoke Smart Contract Allowances](https://support.metamask.io/more-web3/learn/how-to-revoke-smart-contract-allowances-token-approvals/)
- [MetaMask Help Center — Managing Spending Caps](https://support.metamask.io/metamask-portfolio/overview/spending-caps-portfolio/)
- [EIP-1193 — Ethereum Provider JavaScript API](https://eips.ethereum.org/EIPS/eip-1193)
- [EIP-2255 — Wallet Permissions System](https://eips.ethereum.org/EIPS/eip-2255)
- [ERC-20 — Token Standard](https://eips.ethereum.org/EIPS/eip-20)
- [ERC-721 — Non-Fungible Token Standard](https://eips.ethereum.org/EIPS/eip-721)
- [ERC-1155 — Multi Token Standard](https://eips.ethereum.org/EIPS/eip-1155)
- [ERC-2612 — Permit Extension for EIP-20 Signed Approvals](https://eips.ethereum.org/EIPS/eip-2612)
- [ERC-4361 — Sign-In with Ethereum](https://eips.ethereum.org/EIPS/eip-4361)
- [Uniswap Developers — Permit2 Overview](https://developers.uniswap.org/docs/protocols/permit2/overview)
- [WalletConnect — Session Disconnect and Session Delete Documentation](https://github.com/WalletConnect/walletconnect-docs/blob/main/docs/walletkit/react-native/usage.mdx)
- [Revoke.cash — Frequently Asked Questions](https://revoke.cash/learn/faq)
- [Revoke.cash — EIP-2612 Permit Signatures and Cancellation](https://revoke.cash/learn/approvals/what-are-eip2612-permit-signatures)
- [Revoke.cash — What Is Permit2?](https://revoke.cash/learn/approvals/what-is-permit2)
- [Ethereum.org — Scam Help and Reporting](https://ethereum.org/community/support/scams/)
- [Terenval Wallet — Official Application](https://wallet.terenval.com/)

Official article: https://wallet.terenval.com/answers/what-happens-when-you-disconnect-your-wallet-from-a-dapp/

[Machine-oriented Terenval index](https://wallet.terenval.com/llms.txt)
