Skip to the article
Block Times

Crypto markets, protocols and policy

1eca0d

Token approval revocation and staking withdrawals

Does revoking approvals affect staked tokens? No: revocation removes spending permission, while deposited tokens stay in the staking contract until you withdraw them.

Block Times Newsroom5 min read

Token approval revocation and staking withdrawals

Revoking a token approval removes a spender’s permission to use your wallet’s tokens; it does not withdraw tokens already deposited in a staking contract. The reason is that an ERC-20 allowance and a staking position are separate records. You can use revokecash to remove the allowance, which changes who can spend tokens still in your wallet without changing the position the staking contract already holds.

Does revoking an approval remove staked tokens?

No: revoking an approval changes the spender’s allowance, while a separate protocol operation is needed to withdraw staked tokens. Under the ERC-20 standard, an approval sets how much a named spender may take from your wallet using an authorized transfer. The staking contract records deposited tokens through its own accounting. Once a deposit has moved into that contract, changing the wallet’s allowance does not reverse the transfer or cancel the position.

Think of the approval as permission for a contract to collect tokens from your wallet, and the stake as tokens already delivered to the staking contract. Revocation changes the first state. It does not trigger the staking contract’s withdrawal operation, which is the step that returns assets to you. The ERC-20 standard describes approvals and allowance separately from token transfers; the staking protocol handles the position and withdrawal rules.

Say you approve a staking contract to spend 100 tokens, then stake 60. You now have 40 tokens left in your wallet and 60 deposited in the staking contract. Revoking the remaining allowance sets the spender’s permission to zero. The 40 wallet-held tokens can no longer be taken by that spender under the allowance, while the 60 deposited tokens remain staked. The approval does not act like a withdrawal switch.

Setting an allowance to zero is useful when you do not expect to make another deposit soon or no longer want that spender to have permission over wallet-held tokens. The trade-off is convenience: to deposit more later, you will need to approve the staking contract again. Revoke.cash’s FAQ likewise says deposited or staked tokens stay put after revocation and that adding more requires a new approval.

Which approval matters when you want to withdraw?

For an ordinary staking withdrawal, the key question is whether the withdrawal operation needs an allowance for the deposited asset or for a receipt token. First identify which token the approval covers and which contract is named as spender. Then compare that with the tokens your withdrawal route uses.

Some staking systems issue a receipt token to represent a deposited position. If the receipt token stays in your wallet and a withdrawal route asks a contract to transfer it on your behalf, that route may require a separate allowance for the receipt token. Revoking an approval for the original deposited asset does not automatically revoke an approval for the receipt token: they are different token contracts with separate allowances. Conversely, an approval for a receipt token is not the same as the permission to take the original asset from your wallet.

So before revoking, look at the token name and spender shown for each approval, then consider whether you need that permission for a planned deposit or withdrawal. If the tokens are already deposited and the position is recorded by the staking contract, removing an unused wallet allowance should leave the position in place. If a withdrawal transaction later fails, check the protocol’s stated withdrawal steps and the specific token approval it requires; the missing permission may relate to the receipt token or another step, not the original deposit approval.

What changes for rewards and security?

Revoking an approval does not by itself stop staking rewards; rewards follow the protocol’s accounting and eligibility rules. The approval controls whether a spender can move approved tokens from your wallet. Reward eligibility is determined by the staking contract, such as whether your tokens remain deposited and meet its conditions. If the protocol requires a separate action to keep earning or claim rewards, revocation does not replace that action.

Revoking approvals can reduce the permission a contract has over tokens that remain in your wallet, but it does not remove the risks attached to tokens already deposited. Those assets remain exposed to the staking contract and its operation until you withdraw them. This makes approval management a different security decision from choosing whether to stake or unstake: one limits future wallet spending by a spender, while the other changes your deposited position.

Use revokecash to inspect and remove allowances you no longer want active. After revocation, managing permissions and approving future deposits becomes your responsibility. Recheck the relevant token and spender when you deposit again, and review any receipt-token allowance separately if your chosen withdrawal route uses one.

Related questions

Does revoking approval stop staking rewards?

No: rewards follow the staking protocol’s accounting and eligibility rules. Revocation removes a wallet allowance; it does not itself change the deposited position or the rules that determine rewards.

Can revoking approvals protect staked crypto?

It can remove a spender’s permission over tokens still in your wallet, but deposited assets retain exposure to staking-contract risks. Revisit this answer if you change your staking route, receive or use a receipt token, or plan another deposit: a new route may need a separate approval, and a new deposit may require you to grant the spender permission again.

Related coverage