What people actually ask

No. Paste a public Solana address. VEIL Scan never uses a wallet adapter, never asks for a signature, and never requests a private key. If a page claiming to be this product asks you to approve a transaction, leave.

No. There is no token, ticker, airdrop, or on-chain governance coin. The basic scan is free. A later paid developer API can be billed in ordinary currency. A token is not required for that model.

No. ZK VEIL is an independent design concept. It is not a product of Zcash, the Electric Coin Company, or the Solana Foundation. Zcash appears here as an educational contrast: shielded transfers can hide sender, recipient, and amount. We are not a Zcash wallet and we do not submit shielded transactions. Start at z.cash/learn.

It restates what the public ledger already stores. It does not attach a legal name, KYC file, IP address, phone, or device. A transfer is evidence of interaction, not of a shared owner. Treat the report as literacy about public fields, not as a identity dossier.

The address you paste appears in the URL (/scan/…) and is sent to this application's server, which then queries Solana RPC. The host, any reverse proxy, and the RPC operator can see that public-key lookup. Browser history and shared links also leak the address. Do not treat a scan URL as a secret. There is no account and no wallet connect. Details are on Privacy.

This MVP has no user database. Reports are computed on demand. Typical PaaS disks are ephemeral. Hosting access logs may still record request paths, including addresses in the URL. We do not sell a dossier product on top of those scans.

The MVP window is the last 100 confirmed signatures from getSignaturesForAddress. Busy wallets have more history on-chain; this report does not claim to show it. Quiet wallets show fewer. Unused wallets show none — which is not a privacy guarantee.

Yes. POST /api/scan with { "address": "<base58 or demo>" }. No API key. Invalid addresses return HTTP 400. RPC failures return HTTP 502. The same JSON powers the on-page report. Intended later: paid higher limits and CI checks — still without inventing a token. See Developers.

Invalid base58 is rejected before RPC. Live scans fail when every configured endpoint rate-limits or times out. The scanner retries and walks public fallbacks. Set SOLANA_RPC_URL to a dedicated mainnet endpoint if you need a quota. The sample report stays available.

No. A line means value or a token-account balance moved between two public keys in the parsed window. CEX deposits, program PDAs, and other people's wallets all show up as counterparties. The map is interaction, not clustering.

No. It does not hide transfers, break links, or route funds. It shows what a transparent transfer already published. Hygiene (split keys, keep memos empty, stay off logs) is not the same as a shielded value transfer.

Confidential transfer extensions exist and are not the default. They are not Zcash. VEIL Scan reports what RPC actually returned — not amounts a future program might have hidden. If a body has no cleartext amount, we do not invent one.

You can paste any valid base58 address. Program accounts and PDAs often look different from a personal hot wallet. The report still describes public fields in the last-100 window; it does not special-case “this is definitely a person.”

A 0–100 reading aid built from signature count, counterparties, memos, token mints, recognized apps, failed transactions, noisy logs, fee-payer share, and time clustering. It is a heuristic, not a risk rating, legal conclusion, or credit score. The formula is written out on Methodology.

Not in this slice. Mainnet Solana only. Other transparent ledgers have the same class of problem; they are not implemented here.