A signed-mirror vault for the only market this chamber catalogues. Three production v3 onions, prober-validated, copy-ready.
Verified · LiveThree concurrent v3 onion mirrors, all part of the platform’s rotation roster. The Primary handles the bulk of buyer traffic. Backup A absorbs spillover during traffic peaks. Backup B is the explicit failover, on lower-throughput guard relays. Copy from the table; never retype.
| Role | Onion address | Latency | |
|---|---|---|---|
| Primary | anubisq6kqiq5ttmrrnj3pyxssmnaxurl76flaegbtzbcwtes3vomiid.onion |
142 ms | |
| Backup A | anubisraftr2f2ekuml5nl453aozlgsa54gyxyeci2p2h6unsc57qqyd.onion |
178 ms | |
| Backup B | anubisgpdzwmwlo42mr7g3n75lfusb7uolh7y63ysubvdp6hrezduuad.onion |
214 ms |
Anubis Vault is a single-market chamber. We do not list directories; we do not aggregate competitor markets; we do not sell ranking placement. The chamber tracks one platform — Anubis Market — and republishes only the mirror addresses that have cleared our prober on their most recent run.
The single-market posture is deliberate. Anubis Market operates on the post-Hydra darknet-market model: Monero-default settlement, 2-of-3 multisignature escrow as the default contract for new vendor accounts, and a signed mirror roster published on a multi-hour cadence. Catalogues that lump Anubis in with a dozen competitor markets dilute the operational signal; this chamber preserves it.
Three things matter when you arrive on a darknet market: that the address you have is current, that the mirror is reachable through your Tor circuit, and that the storefront you reach is genuinely the platform you intended to visit. The chamber addresses all three. The mirror table above answers the first. Latency telemetry per mirror (refreshed on a 10-minute prober cycle) addresses the second. The phishing reference in the next section addresses the third.
Every onion address listed in the mirror table is checked every 10 minutes. The check is functional, not cosmetic: the prober resolves the address, completes the platform’s anti-DDoS challenge if one is presented, fetches a representative page, and confirms that the response carries the platform’s expected page fingerprint. Mirrors that miss three consecutive checks drop from the public table automatically and only reappear after a clean run.
The cycle is tighter than the operator’s announcement cadence by design. Operators publish signed roster changes on a multi-hour rhythm; we re-validate at 10-minute resolution so the public table tracks operational reality, not the announcement schedule.
Phishing operators clone the visual layout of an Anubis Market login page in an afternoon and register a near-identical v3 onion in a few hours. The clones are pixel-perfect; the only durable defence is to copy the address from a verified directory like this chamber, never retype, and verify the URL one last time before entering credentials.
The single biggest reason this chamber catalogues Anubis Market and not its single-signature peers is the platform’s default multisig posture. The 2-of-3 multisignature escrow contract distributes the funding key across three parties: buyer, vendor, and platform. Funds cannot move without two of the three signing.
What this means in practice: a platform attempting an exit-scam under multisig has 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. Multisig is the structural feature that makes a unilateral exit-scam architecturally impractical.
Anubis routes new vendor accounts into multisig by default and gates non-multisig listings to vetted veterans. The full reference is in Chamber: Escrow.
Mirror table, fingerprints, vendor count, volume.
Verified onion addresses, prober-checked.
Roles, guard pools, fail-over patterns.
How the multisig escrow works in practice.
Why XMR is the platform default for new accounts.
Vetting, reputation, dispute outcomes.
How the third multisig signer arbitrates.
What buyers and vendors actually pay.
Two-factor login on Anubis Market.
Six-step Tor walkthrough to a verified login.
What “working” actually means.
The verified production list.
Phishing addresses and clone storefronts.
Right configuration before you start.