WiSP for Chrome
Every chart is a private buy button.
WiSP in Chrome's side panel, and its buy and sell buttons on the token pages you trade from. Your keys are made and kept on your device. The only WiSP extension is the one linked here.
Check your copy
The store's build, file by file, against the release we published.
Every release lists the SHA-256 of every file it ships. The check downloads the build Chrome's store serves today and compares each file. The store adds two things of its own, and only those are set aside: its signed hashes (the _metadata folder) and the update_url and key lines in the manifest.
1. The file list
0.4.1.files.json, digest 22bd0fadca2d9779b79c5e40b2852d98d179ff30f1fc4141cf897492ebb50110.
2. The check
Save the verify script (Node 20 or later, no dependencies), then run:
node verify-0.4.1.mjs 0.4.1.files.json --id pcniebcihchdcjbiooboecpoclcijjbh
IDENTICAL means the store serves exactly this release. Anything else, tell us at once (the address is on the Security page).
What it asks for
Access to a site only when you switch that site on.
At install, Chrome names WiSP's own API and the two RPC providers the wallet reads the chain through. Nothing else. The sites where WiSP shows its buttons (X, DexScreener, pump.fun, GMGN, Axiom, Photon, Terminal, BullX, Birdeye, Solscan, Jupiter, fomo, Telegram, Discord) are each asked for when you switch them on, and can be switched off again in WiSP or in Chrome. It never asks for all sites, your tabs or your history.