Web3

Revoke Approval

The act of removing a previously granted token spending permission from a program or delegate, preventing it from transferring your tokens in the future. Revoking approvals is an important security practice after interacting with DeFi protocols, especially unfamiliar ones, because outstanding approvals could be exploited if the approved program is compromised. On Solana, tools like Revoke.cash and wallet-built-in features allow users to view and revoke active token approvals.

IDrevoke-approval

Plain meaning

Start with the shortest useful explanation before going deeper.

The act of removing a previously granted token spending permission from a program or delegate, preventing it from transferring your tokens in the future. Revoking approvals is an important security practice after interacting with DeFi protocols, especially unfamiliar ones, because outstanding approvals could be exploited if the approved program is compromised. On Solana, tools like Revoke.cash and wallet-built-in features allow users to view and revoke active token approvals.

Mental model

Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.

Think of it as a building block that connects one definition to the larger Solana system around it.

Technical context

Place the term inside its Solana layer so the definition is easier to reason about.

Wallets, signing flows, dApps, and key management concepts.

Why builders care

Turn the term from vocabulary into something operational for product and engineering work.

This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.

AI handoff

AI handoff

Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.

Revoke Approval (revoke-approval)
Category: Web3
Definition: The act of removing a previously granted token spending permission from a program or delegate, preventing it from transferring your tokens in the future. Revoking approvals is an important security practice after interacting with DeFi protocols, especially unfamiliar ones, because outstanding approvals could be exploited if the approved program is compromised. On Solana, tools like Revoke.cash and wallet-built-in features allow users to view and revoke active token approvals.
Related: Token Approval, Self-Custody, Smart Contract Risk
Glossary Copilot

Ask grounded Solana questions without leaving the glossary.

Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.

Explain this code

Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.

Ask a glossary-grounded question

Ask a glossary-grounded question

The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.

Concept graph

See the term as part of a network, not a dead-end definition.

These branches show which concepts this term touches directly and what sits one layer beyond them.

Branch

Token Approval

The permission granted to a program or delegate address to spend a specified amount of tokens from your account on your behalf. Token approvals are necessary for DeFi interactions like swapping or depositing into liquidity pools. On Solana, the SPL Token program's approve instruction sets a delegate and approved amount on a token account. Approvals should be set to the minimum needed and revoked when no longer required to limit exposure to potential exploits.

Branch

Self-Custody

The practice of personally controlling your cryptographic private keys rather than entrusting them to a third party (exchange, custodian). Self-custody follows the principle 'not your keys, not your coins.' Hardware wallets and properly secured seed phrases enable self-custody. Risks include key loss (no recovery) and social engineering attacks.

Branch

Smart Contract Risk

The risk that bugs, logic errors, or exploitable vulnerabilities in on-chain program code could lead to loss of user funds. Smart contract risk is inherent to all DeFi participation because programs are immutable once deployed (unless upgradeable) and handle real value. Mitigations include professional security audits, formal verification, bug bounties, timelocks on upgrades, and starting with small amounts. Even audited programs can contain undiscovered vulnerabilities.

Next concepts to explore

Keep the learning chain moving instead of stopping at one definition.

These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.

Web3

Token Approval

The permission granted to a program or delegate address to spend a specified amount of tokens from your account on your behalf. Token approvals are necessary for DeFi interactions like swapping or depositing into liquidity pools. On Solana, the SPL Token program's approve instruction sets a delegate and approved amount on a token account. Approvals should be set to the minimum needed and revoked when no longer required to limit exposure to potential exploits.

Web3

Self-Custody

The practice of personally controlling your cryptographic private keys rather than entrusting them to a third party (exchange, custodian). Self-custody follows the principle 'not your keys, not your coins.' Hardware wallets and properly secured seed phrases enable self-custody. Risks include key loss (no recovery) and social engineering attacks.

Web3

Smart Contract Risk

The risk that bugs, logic errors, or exploitable vulnerabilities in on-chain program code could lead to loss of user funds. Smart contract risk is inherent to all DeFi participation because programs are immutable once deployed (unless upgradeable) and handle real value. Mitigations include professional security audits, formal verification, bug bounties, timelocks on upgrades, and starting with small amounts. Even audited programs can contain undiscovered vulnerabilities.

Web3

RPC (Remote Procedure Call)

The API interface for interacting with a blockchain node. Clients send JSON-RPC requests to read account state, submit transactions, and subscribe to events. Solana RPC methods include getAccountInfo, getBalance, sendTransaction, and simulateTransaction. Public RPCs have rate limits; production dApps use dedicated providers (Helius, Triton, QuickNode).

Commonly confused with

Terms nearby in vocabulary, acronym, or conceptual neighborhood.

These entries are easy to mix up when you are reading quickly, prompting an LLM, or onboarding into a new layer of Solana.

Web3token-approval

Token Approval

The permission granted to a program or delegate address to spend a specified amount of tokens from your account on your behalf. Token approvals are necessary for DeFi interactions like swapping or depositing into liquidity pools. On Solana, the SPL Token program's approve instruction sets a delegate and approved amount on a token account. Approvals should be set to the minimum needed and revoked when no longer required to limit exposure to potential exploits.

Related terms

Follow the concepts that give this term its actual context.

Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.

Web3token-approval

Token Approval

The permission granted to a program or delegate address to spend a specified amount of tokens from your account on your behalf. Token approvals are necessary for DeFi interactions like swapping or depositing into liquidity pools. On Solana, the SPL Token program's approve instruction sets a delegate and approved amount on a token account. Approvals should be set to the minimum needed and revoked when no longer required to limit exposure to potential exploits.

Web3self-custody

Self-Custody

The practice of personally controlling your cryptographic private keys rather than entrusting them to a third party (exchange, custodian). Self-custody follows the principle 'not your keys, not your coins.' Hardware wallets and properly secured seed phrases enable self-custody. Risks include key loss (no recovery) and social engineering attacks.

Web3smart-contract-risk

Smart Contract Risk

The risk that bugs, logic errors, or exploitable vulnerabilities in on-chain program code could lead to loss of user funds. Smart contract risk is inherent to all DeFi participation because programs are immutable once deployed (unless upgradeable) and handle real value. Mitigations include professional security audits, formal verification, bug bounties, timelocks on upgrades, and starting with small amounts. Even audited programs can contain undiscovered vulnerabilities.

More in category

Stay in the same layer and keep building context.

These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.

Web3

Web3

The vision of a decentralized internet built on blockchain technology, where users own their data, identity, and digital assets. Web1 was read-only (static pages), Web2 is read-write (platforms like social media), Web3 is read-write-own (permissionless, user-sovereign). Web3 applications use wallets instead of logins and smart contracts instead of centralized servers.

Web3

dApp (Decentralized Application)

An application with its backend logic running on a blockchain as smart contracts rather than centralized servers. dApps typically have a traditional web frontend that interacts with on-chain programs via RPC. Users authenticate with wallets instead of username/password. Examples: Uniswap (Ethereum DEX), Jupiter (Solana DEX), Magic Eden (NFT marketplace).

Web3

Wallet

Software or hardware that manages cryptographic keys and enables users to sign transactions, view balances, and interact with dApps. Hot wallets (Phantom, Solflare, Backpack) are internet-connected for convenience. Cold wallets (Ledger, Trezor) store keys offline for security. Wallets don't actually 'hold' tokens—they hold the private keys that control on-chain accounts.

Web3

Seed Phrase (Mnemonic)

A 12 or 24-word human-readable backup of a wallet's master private key, generated using BIP-39 standard. The seed phrase can deterministically regenerate all derived keypairs (BIP-44 derivation paths). Losing the seed phrase means permanently losing access to all associated accounts. Never share, photograph, or store seed phrases digitally in plain text.