Security & Trust
Verify the site, then verify every transaction.
Revoke.PLS is intentionally narrow: it helps you review wallet approvals, understand what can still spend assets, and prepare revoke transactions that you must confirm in your own wallet.
What Revoke.PLS can do
- Scan public approval history for the supported EVM networks currently wired into the app.
- Re-check discovered allowances and NFT operator permissions live before showing them as active.
- Prepare standard revoke transactions for approvals you choose to clear.
- Link tokens, spenders, and transaction hashes to the relevant block explorer for independent review.
- Scan a pasted EVM address without connecting a wallet, then keep revoke unavailable until a matching wallet is connected.
What Revoke.PLS cannot do
- Move, bridge, swap, stake, or custody tokens.
- Recover stolen assets or reverse transactions that are already on-chain.
- Guarantee that every explorer, RPC, wallet, browser, CDN, or hosting provider keeps no logs.
- Guarantee a spender or protocol is safe just because a label is shown.
- Reduce or bypass network gas fees required for on-chain revoke transactions.
- Support Solana revoke flows in the current EVM approval scanner design.
Official site warning
The official site is pulserevoke.com. Bookmark it and be careful with links from DMs, Telegram, Discord, fake ads, search ads, and misspelled domains. Revoke.PLS will never ask for a seed phrase or private key.
What connect wallet means
Connecting lets the app see your public address and current chain through your wallet provider. It does not give Revoke.PLS custody of funds, private keys, or permission to move assets. A write request appears only after you choose a revoke action.
What a revoke transaction does
A standard token revoke usually calls approve(spender, 0). NFT revokes usually clear an operator with setApprovalForAll(operator, false) or clear a per-token approval with approve(0x0, tokenId).
Before signing
Your wallet prompt is the final checkpoint.
Revoke.PLS prepares a transaction, but your wallet decides what you actually sign. Cancel if the prompt shows a transfer, swap, bridge, unknown approval, unexpected function, or unreasonable fee.
Revoke.PLS does not add an app-level fee. Your wallet should show the network gas cost before confirmation, and you can reject the transaction if the cost or call data looks wrong.
Transaction hashes should remain independently auditable. After a revoke confirms, use the chain explorer link or your wallet history to inspect the on-chain transaction yourself.
- 01Official domain is pulserevoke.com with no misspellings or extra words.
- 02Connected chain matches the approval you are reviewing.
- 03Token or NFT collection address matches the asset you expect.
- 04Spender or operator address is the exact contract you intend to clear.
- 05Function name is approve(spender, 0), setApprovalForAll(operator, false), or approve(0x0, tokenId).
- 06Wallet prompt does not show a token transfer, swap, bridge, or unknown approval.
- 07Gas fee is reasonable for the selected chain before you confirm.
Wallet safety recommendations
- Bookmark pulserevoke.com and open it from your bookmark instead of from chat links or ads.
- Use hardware wallets for long-term holdings when possible.
- Consider a separate hot wallet for frequent DeFi interactions.
- Disconnect from sites you no longer use and periodically review active approvals.
- Treat unknown spenders and unlimited approvals as reasons to slow down and verify on-chain.
Data minimization and privacy
Revoke.PLS does not maintain an app-level database of scanned wallets or approval history. Scans use public chain data and configured RPC, explorer, API, wallet, browser, hosting, and network providers may still process normal request metadata.
The app avoids seed phrase entry, private key handling, app-level approval history accounts, and custom custody services. Public blockchain data is still public, and normal infrastructure metadata can exist outside the app.
Supported chains and current status
Current production scope, not future promises.
The matrix reflects the scanner and revoke paths present in the app today. It does not enable any new network, mark any spender as safe, or imply support for chains that need separate approval mechanics.
| Chain | Chain ID | Scan | Revoke | Status | Current reality |
|---|---|---|---|---|---|
| PulseChain | 369 | Yes | Yes | Live | Shared scanner and wallet-side revoke flow for PRC-20, ERC-721, and ERC-1155-style approvals. |
| Ethereum Mainnet | 1 | Yes | Yes, for live-verified rows | Live | Uses the Ethereum read-only API plus live RPC validation. Revoke is wallet-side and available only after row verification, matching wallet, and correct chain checks pass. |
| BNB Smart Chain | 56 | Yes | Yes | Live | Shared scanner and wallet-side revoke flow with BSC-specific gas cap and high-gas warnings preserved. |
| Base | 8453 | Yes | Yes | Live | Shared scanner and wallet-side revoke flow using Base explorer discovery and live verification. |
| Arbitrum | 42161 | No | No | Not enabled | Not wired into the production scanner or wallet write paths. |
| Solana | N/A | No | No | Not supported | Solana approval mechanics need a separate design and are not supported by the current EVM revoke flow. |
Address-only scan
Scan first, connect only when you are ready to revoke.
Approval state is public blockchain data, so Revoke.PLS can scan a pasted EVM address without a wallet connection. That mode is useful for review, triage, and comparing chains before you expose a wallet connection to any site.
Revoke stays unavailable until the connected wallet exactly matches the scanned address and is on the required chain. This preserves the same wallet-side ownership and network checks as connected scanning.