Frequently Asked
Questions

ZendIQ Lite is available on the Chrome Web Store and Brave Browser.

1. Visit the Chrome Web Store and search for "ZendIQ Lite"
2. Click "Add to Chrome"
3. Confirm the permission request
4. That's it! ZendIQ is now active on Jupiter, Raydium, and Pump.fun

No wallet connection, no account signup, no fees to install.

No account signup or wallet connection is required. ZendIQ can read your public wallet address (needed for the Wallet Security scan), but we never have access to:

• Your balances
• Your transaction history
• Your private keys (we never ask for them)

Your public address is only used locally to scan for token approvals. We only analyze on-chain data — we cannot move funds or sign anything on your behalf.

Yes. ZendIQ Lite is:

• ✅ Open source — auditable code on GitHub
• ✅ Non-custodial — we never touch your funds
• ✅ Read-only — we only analyze on-chain data
• ✅ No personal data — we don't track you or collect private info
• ✅ No fees — completely free

You stay in full control. We just warn you before you sign.

• ✅ Chrome (Chromium-based)
• ✅ Brave
• 🔄 Edge (coming soon)
• 🔄 Opera (coming soon)

Firefox support coming later.

ZendIQ is compatible with any Solana wallet. It works at the DEX page level — analysing the swap and showing you a risk score before your wallet is ever asked to sign. ZendIQ does not install into, modify, or interact with your wallet extension in any way.

When you click Swap on a supported DEX, ZendIQ intercepts the trade on the page and runs its analysis. If everything looks good, the transaction is passed to your wallet to sign exactly as normal. Your wallet experience is completely unchanged.

Tested and verified:

• ✅ Phantom
• ✅ Backpack
• ✅ Solflare
• ✅ Brave Wallet (built-in)
• ✅ Jupiter Wallet
• ✅ Glow
• ✅ Coin98
• ✅ Any Wallet Standard compatible wallet

If your wallet connects to a supported DEX, ZendIQ will protect your swaps on it — no wallet setup or configuration required.

ZendIQ assigns a 0–100 Risk Score based on 16 on-chain signals:

Score	Level	What It Means
0–24	🟢 LOW	Token looks clean
25–49	🟡 MEDIUM	Some risk signals
50–74	🟠 HIGH	Multiple red flags — review carefully
75–100	🔴 CRITICAL	Severe warnings — likely rug/scam

The score is not a guarantee — it's a risk indicator. You always decide whether to proceed.

Before your wallet opens, ZendIQ runs 16 on-chain checks across five categories: token authority, holder concentration, external data & launch integrity, creator history, and price & liquidity.

Signals include mint/freeze authority, top-holder concentration, RugCheck flags, LP lock, bundle launch detection, serial deployer history, token age, and price/liquidity metrics.

For a full signal-by-signal breakdown see the Token Analysis section.

The Risk Score is a warning system, not a guarantee. It catches ~70% of actual rugs in testing. It's designed to:

• ✅ Flag obvious scams
• ✅ Warn about new/risky tokens
• ✅ Identify suspicious patterns

It won't catch:

• ❌ Slow-bleed rugs (takes weeks)
• ❌ Private team rugs (no on-chain signature)
• ❌ Regulatory bans (unpredictable)

Always DYOR. Check community, team, and fundamentals.

The Wallet Security tab guides you through checking your connected wallet for common vulnerabilities. It shows you what to look for and where:

• Unlimited Token Approvals — step-by-step instructions to find and review contracts you've given unlimited permission to transfer your tokens
• Known Drainer Contracts — a check against addresses flagged for stealing funds, so you know if any are lurking in your approval history

ZendIQ doesn't access your wallet settings directly — it reads public on-chain data and tells you exactly what to check and how to fix it. You stay in control at every step.

Click the "Revoke on revoke.cash" button in ZendIQ's security tab:

1. ZendIQ finds unlimited approvals in your wallet
2. Click the link to revoke.cash
3. Sign the revocation transaction
4. Pay a small gas fee (~$0.50–2)
5. Done — that contract can no longer access your tokens

Revoke regularly, especially before holding high-value tokens.

Yes, small gas fees apply (usually $0.50–2 on Solana). But consider the trade-off:

• Cost of security: ~$1–2
• Risk of not revoking: Entire wallet drained (potentially thousands)

Good trade-off.

ZendIQ sends anonymous usage events to our backend. Every event carries an anonymous install_id (a UUID generated once per install — see below). Here are all seven event types and exactly what each sends:

Install — fired once on first install or extension update

Field	Why
OS (windows / mac / linux)	Understand platform distribution
Browser (brave / chrome)	Understand browser distribution
Locale (e.g. "en-US")	Aggregate language distribution — no sub-region precision
Country (2-char ISO from browser locale)	Derived by the browser, not geolocation — understand global reach
Reason (install / update) + previous version	Track upgrade paths

Session — fired when a wallet is detected on page load and on page close

Field	Why
Type (start / end)	Measure session duration
Wallet adapter name (e.g. "phantom")	Which wallets are most used — never the public key
DEX (jup.ag / raydium.io)	Which DEX the session was on

Trade — fired after the user makes a swap decision (optimise, proceed, or cancel)

Field	Why
dex	Which DEX executed the trade
input_mint	Token sold — needed to measure routing gain accuracy
output_mint	Token bought — needed for risk signal accuracy
trade_usd	Trade size in USD — capped at $50k (Lite) / $500k (Pro)
user_action	What the user chose: optimised / proceeded / cancelled
success	Whether the transaction landed on-chain
tx_sig	Transaction signature — deduplication + on-chain verification. Publicly visible on Solana.
risk_score	Overall risk score (0–100) at time of decision
bot_risk_score	MEV / sandwich risk score (0–100)
token_risk_score	Output-token risk score (0–100)
net_benefit_usd	Estimated routing gain minus fees at time of sign
routing_gain_usd	Raw routing gain vs Jupiter's concurrent quote
mev_value_usd	Statistical MEV protection value from Jito tip
fees_usd	Priority fee + Jito tip cost
jito_tip_lamports	Jito tip used — verifiable on-chain
profile	Which protection profile was active
auto_sign	Whether auto-accept fired
exec_path	Which route was used: zendiq / jupiter / raydium
route_chosen	Route type: AMM / RFQ / gasless / bundle
failure_reason	Human-readable failure description (≤80 chars) when success=false
data_json	Extra fields not in fixed columns — future-proofs schema (≤4KB)

Not collected: wallet public key, full transaction bytes, counterparty wallet.

MEV detection — fired when a sandwich attack is identified around a swap

Field	Why
tx_sig	Transaction signature of the user swap being attacked — deduplication; publicly visible on Solana
detected	Whether an attack was confirmed
loss_usd	Estimated USD loss from the attack — measures real-world impact
loss_bps	Attack severity in basis points
attacker_hash	SHA-256 of attacker wallet, truncated to 12 hex chars — not sufficient to reconstruct the full address
method	Detection method: vault_neighbor / bonding_curve_pda / front_run_only
time_to_detect_s	How quickly ZendIQ identified the attack — measures detection latency
prevented_count	Attacks in the same block that Jito tips blocked

Not collected: user wallet address, transaction bytes, victim identity beyond the public tx signature.

Error — fired when an internal failure degrades protection (e.g. wallet hook failure)

Field	Why
category	Error class (e.g. wallet_hook, rpc, injection) — routes alerts to the right fix
detail	Human-readable description (≤120 chars) — no stack traces, no user data
rpc_endpoint	Which RPC endpoint failed — diagnoses provider reliability
latency_ms	RPC latency — diagnoses slow-provider issues
dex	Which DEX context the error occurred in

Funnel — key UX steps in the widget flow

Field	Why
event	widget_shown / quote_fetched / sign_clicked / cancel_clicked / auto_signed
dex	Which DEX
widget_render_ms	Widget render latency — UX performance metric

Measures where users drop off between "widget appears" and "trade optimised" without any user-identifying data.

Heartbeat — once per UTC calendar day on service-worker wake

Field	Why
day	Calendar date (YYYY-MM-DD) — deduplication key: one install = one heartbeat/day
site	Which DEX site triggered the wake

Powers DAU/WAU/MAU metrics without any persistent user identifier.

Never collected — in any event type:

• ❌ Wallet public key or address
• ❌ Private keys or seed phrases
• ❌ Token balances or portfolio data
• ❌ Full transaction bytes or content
• ❌ Browser history or URLs outside jup.ag / raydium.io
• ❌ IP address (used for rate-limiting only, never stored in our database)
• ❌ Any personal or identifying information

Every event carries an install_id — a UUID-v4 generated once on fresh install and stored in chrome.storage.local. It is:

• ✅ Not tied to any account, wallet, or identity
• ✅ Not transmitted off-device other than in event payloads to our backend
• ✅ Reset on extension uninstall — a reinstall is a new install_id
• ✅ Not exposed to any website — it lives only in extension storage

Its sole purpose is to group events from the same installation for aggregate analytics (e.g. "how many installs have made ≥3 trades?"). It cannot be linked to your wallet, browser fingerprint, or any personal identity.

Absolutely not. We:

• ❌ Never ask for keys or seed phrase
• ❌ Never have access to them
• ❌ Can't sign transactions on your behalf

We only analyze public blockchain data. You stay in control. Always.

The transaction signature (tx_sig) is a public on-chain identifier — already visible to anyone on Solana block explorers like Solscan. It does not contain your wallet address, amount, or any personal data on its own.

We use it for two purposes:

1. Deduplication — prevents the same trade from being counted twice if the extension fires the event more than once
2. Quote accuracy — ZendIQ Pro polls the transaction after confirmation to compare the quoted output vs what actually landed on-chain; this makes the "Quote Accuracy" metric trustworthy

We do not store the full transaction bytes, the signer's wallet address, or any counterparty information.

No, never. We:

• ❌ Don't sell or share data
• ❌ Don't have ads
• ❌ Don't use third-party analytics services (no Google Analytics, no Mixpanel)

Data flows only from your browser to our own backend. Nothing goes to any third-party analytics platform.

Currently live:

• ✅ Jupiter (jup.ag) — Solana's #1 DEX aggregator
• ✅ Raydium (raydium.io) — Solana AMM
• ✅ Pump.fun (pump.fun) — Memecoin launcher

Coming soon:

• 🔄 Magic Eden (NFT swaps)
• 🔄 Orca (DEX)
• 🔄 Other Solana DEXs

Not yet. ZendIQ is Solana-focused because:

• Solana has the highest MEV/rug risk
• Pump.fun is Solana-only (highest volume memecoins)
• Token programs differ per chain (need different scoring)

Multi-chain support coming in 2026 (Ethereum L2s, Base, Arbitrum).

No. ZendIQ:

• Runs in the background with no visible slowdown
• Only activates on supported DEXs (Jupiter, Raydium, Pump.fun)
• Makes API calls that complete in <1 second
• Has a minimal memory footprint

Most users notice zero performance impact.

ZendIQ still works. Risk scoring happens locally in your browser; on-chain data fetches directly from Solana RPC (public network). We only use our backend for analytics, which is non-critical.

If our backend is down:

• ✅ Risk scores — still work
• ✅ Token analysis — still works
• ❌ Analytics logging — fails silently

No data loss, no broken swaps.

Typical causes:

• Solana RPC is slow (network congestion) — wait 5–10 seconds
• Your internet is slow — check connection
• Token mint is new/unusual — takes longer to validate all sources
• Browser extension lag — rare, try refreshing the page

If stuck >30 seconds: refresh and try again.

ZendIQ analyzes across five categories:

Token Authority — Can devs rug you?

1. Mint authority (can devs print unlimited tokens?)
2. Freeze authority (can devs lock your wallet?)

Holder Concentration — Is it centralized?

3. Top-1 holder % of supply
4. Top-5 holder % of supply

External Data & Launch Integrity — Third-party risk checks

5. RugCheck danger flags
6. RugCheck warning flags
7. LP lock status
8. Bundle launch detection — coordinated bundle activity at token creation

Token & Creator History

9. Token age (<24h, <7d, <30d?)
10. Speculative/memecoin keywords detected
11. Serial deployer detection — how many tokens the creator wallet launched in 30 days

Price & Liquidity — Can you actually exit?

12. 3-month price change
13. Long-term price change (6 months)
14. 7-day vs 90-day volume trend
15. Liquidity depth ($X before Y% slippage)
16. Market cap

Common reasons:

• New token (<7 days old) — higher risk by default
• Centralized supply — top holder has >30%
• Liquidity concern — can't sell without massive slippage
• Authority flags — mint/freeze authority still active
• RugCheck warnings — detected on external risk database
• Price volatility — wild price swings signal pump-and-dump
• Bundle launch detected — coordinated buying in the creation slot
• Serial deployer — creator wallet launched multiple tokens recently

High score ≠ automatic rug. Some new legitimate tokens score high. You decide.

When a new token launches, coordinated insiders sometimes bundle multiple transactions into the same slot to buy a large share of the supply before anyone else can react — then dump on retail buyers.

ZendIQ checks the number of transactions in the token's creation slot (the very first block the token appeared in) using standard Solana RPC. A high count suggests a coordinated launch:

Txs in creation slot	Signal	Score impact
1–2	🟢 LOW	No penalty
3–4	🟠 HIGH	+20
5+	🔴 CRITICAL	+40

Detection is inconclusive for established tokens with more than 2,000 total transactions — at that scale the creation slot can no longer be reliably identified. No penalty is applied in those cases.

ZendIQ traces the wallet that deployed the token and counts how many other tokens the same wallet launched in the last 30 days. Serial deployers are a strong signal of rug-factory behaviour.

Tokens launched (30d)	Signal	Score impact
1	🟢 LOW	No penalty
2–3	🟡 MEDIUM	+8
4–9	🟠 HIGH	+20
10+	🔴 CRITICAL	+35

This check uses on-chain data only — no third-party database required.

The wallet holding the most of that token. Example:

• Total BONK supply: 1 billion
• Top holder: 100 million BONK (10%)
• ZendIQ flags this as centralization risk

Why it matters: If one holder sells everything, the price crashes.

When token creators launch a token, build hype & trading volume, then dump their supply (or drain liquidity) to cash out — price crashes to zero and users lose everything.

ZendIQ detects warning signs:

• Mint authority still active (devs can print more tokens)
• Liquidity not locked
• Creator wallet has history of other rugs
• Suspicious holder concentration

How much you can sell before the price drops dramatically. Example:

• Liquidity depth: $1M → you can sell ~$1M before hitting 10% slippage
• Selling $5M would cause massive slippage (~50%+)

ZendIQ shows: "You can sell $X before Y% slippage"

New tokens are higher risk — no price history, unproven team, often used for pump-and-dumps. ZendIQ flags:

• 🔴 <24 hours — CRITICAL
• 🟠 <7 days — HIGH
• 🟡 <30 days — MEDIUM
• 🟢 30+ days — Lower risk (but still check other signals)

Try these steps in order:

1. Refresh the page (Ctrl+R or Cmd+R)
2. Click "Swap" to trigger the ZendIQ popup
3. Check if extension is enabled: chrome://extensions → ZendIQ → ON
4. Disable then re-enable the extension
5. Reinstall if still broken

If still broken: contact support

Popup blockers can interfere. Fix:

1. Chrome Settings → Privacy & Security → Site Settings → Pop-ups & redirects
2. Find jup.ag / raydium.io / pump.fun
3. Set to "Allow"
4. Refresh and try again

ZendIQ does NOT request clipboard access. If you see this permission request, it's likely a fake or malicious extension.

Download only from the official ZendIQ Lite listing on the Chrome Web Store.

Not yet. ZendIQ is a Chrome/Brave desktop extension only. There are no current plans for a mobile app. Use desktop Chrome or Brave for trading.

Yes. ZendIQ Lite will always be free — risk scoring is our core value and it's too important for trader safety. What's coming:

• 🆓 ZendIQ Lite (free forever) — what you have now
• ✦ ZendIQ Pro (live · free open beta · 0.05% at paid launch) — MEV protection, auto-optimized routing, advanced wallet protection

No. We commit to keeping token risk analysis free — it's too important for trader safety. ZendIQ Pro will be optional and advanced-use only.

Email support@zendiq.ai and include:

• What happened?
• What browser/OS?
• Screenshot if possible
• Steps to reproduce

Yes! Email support@zendiq.ai with your feature idea, why you need it, and how it would help. We read every suggestion — popular ones go on the roadmap.

Email support@zendiq.ai and include:

• The token mint address
• How it scammed you
• Any proof you have

We'll investigate and improve our detection. This helps us get better for everyone.

• ✅ Compliant with EU financial regulations
• ✅ Not a security, exchange, or custodian
• ✅ A risk analysis tool only

We don't hold funds, so we're not a "financial service" in the strict sense. But we follow best practices.

Full privacy policy: zendiq.ai/privacy

TL;DR:

• ✅ We collect minimal data
• ✅ No selling data
• ✅ No tracking across sites
• ✅ GDPR compliant
• ✅ You can request data deletion anytime

Key points:

• Use at your own risk — we're a warning tool, not financial advice
• No liability for losses
• Don't use for illegal activity
• Respect others' privacy

1. Install ZendIQ Lite from the Chrome Web Store
2. Learn Solana basics — Solana docs
3. Set up a wallet — Phantom, Magic Eden, or Solflare
4. Practice on testnet (free SOL to test with)
5. Start trading — use ZendIQ on mainnet
6. Check security — run Wallet Security scan weekly

• ✅ Always check the risk score before signing
• ✅ Read all warning signals — don't ignore them
• ✅ Check Wallet Security regularly (weekly)
• ✅ Research the team separately — ZendIQ is one tool
• ✅ Start with small trades (test new tokens with 1–5%)
• ✅ Set a stop loss — exit plan before entering
• ❌ Don't FOMO into high-risk tokens
• ❌ Don't trust ONLY the score — do your own research

Check zendiq.ai/roadmap (coming soon) for what we're building next, what users requested, and estimated timelines. Follow @ZendIQ_Official on X for real-time updates.