This is a single-subject field manual. The subject is Anubis Market. The contents are operational, not editorial: where to access the platform, how to verify what you have, what to do when something looks wrong.
The manual is a living document. Sections marked EXHIBIT are operational artefacts (mirror tables, fingerprints, latency measurements) and update on a 10-minute cycle from the prober. Sections marked § NN are reference text and revise on review.
Section [II] Subject Profile is the canonical reference for Anubis Market itself. Everything downstream of it is interpretation.
Three concurrent v3 onion addresses. Prober-validated on the most recent 10-minute cycle. Copy from the table; do not retype.
| Role | Onion address | Lat | |
|---|---|---|---|
| Primary | anubisq6kqiq5ttmrrnj3pyxssmnaxurl76flaegbtzbcwtes3vomiid.onion | 142 ms | |
| Backup A | anubisraftr2f2ekuml5nl453aozlgsa54gyxyeci2p2h6unsc57qqyd.onion | 178 ms | |
| Backup B | anubisgpdzwmwlo42mr7g3n75lfusb7uolh7y63ysubvdp6hrezduuad.onion | 214 ms |
Anubis Market operates on the post-Hydra darknet-market model. Three structural traits define the platform: Monero-default settlement (new accounts route to XMR; Bitcoin is supported for legacy migration only), 2-of-3 multisignature escrow as the default contract for new vendor accounts, and signed mirror rotation where the operator publishes roster changes on a multi-hour cadence. Each is operationally significant; together they distinguish Anubis from the single-signature, BTC-default, single-mirror peers it has displaced.
The Monero default is not ideological. Bitcoin’s transaction graph is fully public and has been ingested, indexed, and clustered by every commercial blockchain analytics firm currently operating; Monero’s transaction graph is, in the strict sense, not public at all. The asymmetry matters operationally: a Bitcoin deposit can in principle be retrospectively linked to your funding KYC exchange months or years later. A Monero deposit cannot.
The multisig posture matters for a different reason. The 2-of-3 contract distributes the funding key across buyer, vendor, and platform. A platform attempting an exit-scam under multisig would have to convince a majority of vendors to actively co-sign their own losses — which has not happened in the post-Hydra era and would be visible on-chain within minutes of the attempt.
Vendor selection, individual product availability, current pricing, dispute outcomes on individual orders. The manual is operational reference for accessing Anubis Market itself; on-platform decisions are out of scope. The dispute panel SLA is in [VII]; vendor program structure is in [VI].
The dominant threat against Anubis Market users is phishing — cloned storefronts on near-identical onion addresses harvesting credentials from users who arrive via mistyped links or third-party Telegram pins.
The clones are pixel-perfect by construction. Phishing operators clone the visual layout of a login page in an afternoon and register a one-character-off v3 onion in a few hours. The defence is simple in form, demanding in habit: copy from a verified directory like this manual; never retype an onion by hand; verify the URL one last time before submitting credentials.
Common patterns observed in the field: typo-squat onions one or two characters from a legitimate address; lookalike Telegram channels pushing addresses; Discord pins from compromised accounts. The defence in all three cases is the same.
Specific clone onions are not republished here — doing so amplifies their reach. Examples of pattern: anubisXXXXXXXXXXXXXXXXXXXXXXXXXXX, anubisYYYYYYYYYYYYYYYYYYYYYYYYY. The class of mimicry rather than the specific instance is the operationally useful signal.
Mirror table, fingerprints, vendor count, volume.
Verified onion addresses, prober-checked.
Mirror roles, guard pools, fail-over patterns.
How the multisig escrow works in practice.
Why XMR is the default for new accounts.
Vetting, reputation, dispute outcomes.
Third multisig signer arbitration.
Vendor commission, listing fees, buyer cost.
Two-factor login on Anubis Market.
Six-step Tor flow to a verified login.
What “working” means operationally.
The verified production list.
Clone patterns, defence habits.
Right configuration before you start.