Monero (XMR): default on BlackOps Darknet
Why Monero is mandatory-grade privacy
Monero hides sender, receiver and amount with ring signatures, stealth addresses and confidential transactions. That is why BlackOps Market prices, bonds and escrow default to XMR. Practical rules: churn once after exchange withdrawal, never reuse a subaddress across identities, and wait for 10+ confirmations before treating a deposit as final during congestion.
Bitcoin (BTC): legacy support with warnings
Bitcoin remains accepted for buyers without Monero access, but it is transparent by design. Never send directly from a KYC exchange to market escrow. Swap to XMR or CoinJoin first, use a fresh address per order, and assume every hop is permanently recorded.
Multi-Sig escrow: 2-of-3 explained
Three keys are generated — buyer, vendor, market — and any two can authorize release. Happy path: buyer and vendor co-sign on delivery. Dispute path: the prevailing party co-signs with the market key. No single party, including the market, can move funds alone. Always verify cosigner fingerprints over PGP before funding.
Warrant Canary linkage and fee discipline
Escrow parameters and fee changes are announced alongside the signed canary. If terms change without a signed update, pause funding and request clarification via internal tickets. Cross-check mirror authenticity in /mirror/ and session rules in /opsec/.