PulseChain approval safety

Pulse Revoke

Revoke risky approvals on PulseChain with a scanner built for careful wallet review.

Review ERC-20 allowances and NFT operator approvals, then clear the permissions you do not trust. The app stays read-only until you choose a revoke action and confirm it in your own wallet.

Primary chain
PulseChain
Scanner
Live at /app
Desktop
Pending release

Always verify spender addresses on PulseScan or Etherscan before signing. Registry labels are curated, not a guarantee of safety.

Non-custodial

Pulse Revoke never holds wallet funds.

User-signed

Every revoke is confirmed in your wallet.

No hidden writes

Write transactions appear only after you click revoke.

Curated labels

Registry names help, but users should still verify.

How it works

A narrow flow for approval review

The product does three things: connect, review, and revoke. Nothing else needs custody or hidden signing.

01

Connect wallet

Use a browser wallet or WalletConnect. The scanner reads public chain data for your address.

02

Review approvals

See active ERC-20 allowances and NFT operator approvals, with risk cues and spender labels.

03

Revoke what you do not trust

Each revoke is a wallet-confirmed on-chain transaction that clears an approval.

Desktop app

A local app path for users who prefer not to rely on a hosted frontend.

The desktop build is designed to run the same scanner locally in a Tauri shell. It keeps the same wallet-confirmed revoke flow: every write still appears in your wallet before you sign.

Run the interface locally after installation.

Use WalletConnect for desktop pairing.

Same approval review and revoke model as /app.

Desktop release status

No public desktop artifact is published yet.

Coming soon

Windows

x64

Pending

Download coming soon.

Windows

ARM64

Pending

Download coming soon.

macOS

Universal

Pending

Download coming soon.

Linux

AppImage

Pending

Download coming soon.

Release guardrail

Desktop downloads remain disabled until signed release artifacts and checksums are available. Placeholder manifest values never render as download links.

Decentralized distribution

IPFS-ready distribution path.

The release manifest already models IPFS gateways and checksums so builds can be pinned after release. The final CID is pending until a real artifact is published and verified.

IPFS status

Final CID pending release.

CID pending

Content ID

No final CID has been published yet.

IPFS.ioCloudflarePinata

Gateway links stay disabled until a real CID is present. Checksums should be published with the same release.

FAQ

Short answers before you connect

Approval tools should be boring in the right places: clear permissions, clear transactions, clear limits.

Does Pulse Revoke custody funds?

No. Pulse Revoke reads public wallet and chain data. Your funds stay in your wallet at all times.

Can it move my tokens?

The app cannot move tokens by itself. It only prepares explicit revoke transactions after you click a revoke action and confirm in your wallet.

Why do I need to sign transactions?

Revoking changes approval state on-chain, so your wallet must sign and submit a transaction. Network gas applies.

What does revoking do?

For ERC-20s, revoking sets the spender allowance to zero. For NFTs, it clears the relevant operator or per-token approval.

Is the desktop app available yet?

Not yet. The Tauri desktop path is scaffolded, but public desktop artifacts are still pending release.

What chains are supported?

PulseChain mainnet (369) and Ethereum mainnet (1). Results should still be checked on PulseScan or Etherscan before signing.