BlackOps telemetry
What a sample account sees in its verification dashboard.
sample account
Checks by day
Est. 2024 and already one of the largest rooms on the network — Monero-only by policy, with the strictest vendor vetting in the scene. This page keeps BlackOps's onion under a PGP check so you never log in to a pixel-perfect clone.
Jump to the FAQ ↗️8 items available · median load through Tor dropped from 2.4s 0.8s
What a sample account sees in its verification dashboard.
Same setup, four ways — before (what gets people phished) and after (what doesn't).
Ten questions that separate routine users from exit-scam statistics.
Pick how often you touch BlackOps, choose the depth of your routine, and see how fast the habit pays for itself in risk avoided.
A clone must match character by character — not "look right."
We cross-check addresses against PGP-signed posts, never DMs.
Markets rotate onions. We timestamp every check; stale is flagged.
Open the market's own signed announcement → copy the full onion → paste into Tor Browser → compare the address bar before typing a password. Any mismatch, any "new mirror" from a stranger: stop, that's a clone.
Tap a question — get the answer streamed live, all offline in your browser.
gpg --import market-signing-key.asc
gpg --verify signed-links.txt.asc signed-links.txt
# fingerprint must equal: PGPa7f3
# only .onion lines under a GOOD signature are real
curl --socks5-hostname 127.0.0.1:9050 \
--proto '=https' http://REPLACED_ONION.onion \
-o /dev/null -w '%{time_total}s\n' # via Tor only
34 live mirrors available across 13 markets — sorted by risk reduction after PGP verification.
| Market | Risk cut | Available (depth) |
|---|
Last verifications performed by the directory — addresses truncated for safety.