XMR-default escrow market with multisig settlement and signed mirrors
Three concurrent v3 onion addresses, prober-validated. The Primary handles the bulk of buyer traffic. Backups absorb spillover and act as the DDoS-challenge fail-over. Copy from the table.
| Role | Onion address | Lat | |
|---|---|---|---|
| Primary | anubisq6kqiq5ttmrrnj3pyxssmnaxurl76flaegbtzbcwtes3vomiid.onion | 142 ms | |
| Backup A | anubisraftr2f2ekuml5nl453aozlgsa54gyxyeci2p2h6unsc57qqyd.onion | 178 ms | |
| Backup B | anubisgpdzwmwlo42mr7g3n75lfusb7uolh7y63ysubvdp6hrezduuad.onion | 214 ms |
Anubis Market is the only market this chamber catalogues. The prober checks the platform’s production v3 onions every 10 minutes: it resolves the address, completes any anti-DDoS challenge presented, fetches a representative page, and confirms the response carries the platform’s expected page fingerprint. Mirrors that miss three consecutive checks drop from the table above and only return after a clean cycle.
The chamber does not republish addresses that fail this check. If an onion you have on a third-party Telegram pin or a forum quote does not appear in the table, treat it as expired or hostile.
Anubis Market runs 2-of-3 multisignature escrow as the default settlement contract for new vendor accounts. The contract distributes the funding key across buyer, vendor, and platform; funds cannot move without two of the three signing. This is the structural feature that makes a unilateral exit-scam architecturally impractical — a platform attempting an exit would have to convince a majority of vendors to actively co-sign their own losses, which has not happened in the post-Hydra era.
The full reference is in Chamber: Escrow. Buyer-side, the contract is opaque — you place orders normally, the multisig is in the background. The protection it offers is real and matters most precisely when a platform’s health is least visible.
Anubis Market defaults new accounts to Monero. Bitcoin is supported for legacy migration but actively de-emphasised through UI nudges and slower confirmation thresholds. The case for funding in XMR rather than BTC is in Chamber: Currency.
Yes. Mirrors that miss three consecutive prober cycles drop from the table automatically; the entries above passed their most recent check.
The Primary handles the bulk of buyer traffic. Backup A absorbs spillover during traffic peaks. Backup B is the explicit failover. There is no universal best — copy the Primary first and switch only if the challenge layer times out.
BTC and XMR. Monero is the default for new accounts; Bitcoin is supported but de-emphasised.
Yes — 2-of-3 multisignature escrow with buyer/vendor/platform keys is the default for new vendor accounts.
Use the Copy button on the mirror table above. Never retype a 56-character v3 onion. Bookmark this directory rather than any single onion; the rotation is re-validated every 10 minutes.