Darius never touches your wallet. Here's exactly what it does instead.
We know what a lot of "helpful" Chrome extensions in this space have turned out to be. So instead of just asking you to trust us, here's precisely what Darius can and cannot do — verifiable by anyone, in a few minutes.
Not "trust us" — check it yourself.
These are the only permissions Darius requests, visible on its Chrome Web Store listing and inside chrome://extensions once installed. Nothing else exists.
| Permission | What it's for |
|---|---|
storage |
Saves your settings and a short-lived analysis cache locally in your browser. Never leaves your device. |
alarms |
Periodically clears that local cache. That's it. |
| Read-only access to public data APIs | DexScreener, GeckoTerminal, RugCheck, GoPlus Security, block explorers, and public Solana/EVM RPC nodes — to fetch public information about the token you're viewing. Every one of these is a read-only lookup, the same data anyone can query manually. |
Notably absent: clipboardRead,
clipboardWrite,
cookies, and any wallet-related permission — because Darius has no use for them.
Four ways to check, in a few minutes.
Check the permissions before installing
Chrome shows every permission an extension requests before you install it. Read it — it matches exactly what's listed above.
Inspect it after installing
Go to chrome://extensions, enable Developer mode, and view the exact manifest and permissions Darius runs with.
Watch its network activity
Open Chrome DevTools → Network tab while browsing with Darius active. Every request goes to a public data API — never to a wallet, never to sign anything.
Read our independent scan report
We already ran Darius through extensionsecurity.io, a free third-party scanner we don't control. Result: A+ rating, risk score 13/100. View the full PDF report →
Still have questions?
We're happy to answer anything directly — technical or not. Reach out before recommending us to your audience, we'd rather earn that trust properly.