Crown Market — questions & answers
Crown Market topic hub. Bespoke storefront, PGP messaging by default, BTC and XMR settlement.
Crown Market onion endpoints — verified set
Current v3 onion endpoints for Crown Market. Verify the full 56-character fingerprint against the operator’s PGP-signed announcement on Dread before logging in. Click any address to open in Tor.
- 01 crownrywlm7mnohkzntlir2tlhafq6tzphgqyag5cw5en7nprchfklad.onion
- 02 crownwpaimgizxylrvrh4u6acpvk4l757cfla7xs6zjki7tdjqbnv6qd.onion
Crown opened in 2024. The first thing you notice is the interface doesn't look like other darknet markets. Most of them use one of two template codebases that have been floating around since 2018. Crown wrote their own. Typography, layout, how vendor pages flow — it's all original. Whether that matters to you depends on how much you care about UI.
Settlement's in BTC and XMR. Monero by default. Bitcoin if you need it. Deposit addresses are fresh on every request, which is standard everywhere now. There's a PIN on withdrawals to slow down anyone who compromises your session. None of this is unique to Crown — it's the modern baseline.
Here's the detail that's easy to miss: PGP messaging is on by default for vendor threads. Every other market we cover makes you remember to turn PGP on in account settings. Most people forget. Crown skips that step. Order notes, shipping addresses, support messages — all encrypted by default. If the server ever gets seized, what's on it is encrypted blobs, not plain text you'd want kept private.
Vendors put up a bond and run escrow-only until they've earned finalize-early from the ops team. Deal count and dispute ratio at the top of the vendor page, so the pre-purchase check is fast. The endpoint set is smaller than at multi-mirror operators — two onions in rotation right now instead of three. That's the trade-off for the bespoke codebase: harder to spin up across many onions than a templated stack.
What is the Crown Market onion address?
Crown Market currently runs two v3 hidden-service endpoints. Both hit the same back-end; use whichever your Tor circuit reaches faster.
- 01 crownrywlm7mnohkzntlir2tlhafq6tzphgqyag5cw5en7nprchfklad.onion
- 02 crownwpaimgizxylrvrh4u6acpvk4l757cfla7xs6zjki7tdjqbnv6qd.onion
The smaller endpoint count relative to multi-mirror operators is a tradeoff against Crown’s bespoke front-end codebase — the same property that makes the interface distinctive also makes spinning up additional onions less trivial.
How to access Crown via Tor
Open Tor Browser, paste one of the addresses above into the URL bar, hit enter. Don't click links from search results — type or paste from this page directly. If a link from Google or another search engine takes you to a clearnet 'Crown' domain, that's a phishing clone. Crown has no clearnet presence. Bookmark the verified onions in Tor Browser if you'll be back, but never bookmark an address from a forum post or chat link without verifying the PGP signature first.
See also
Which currencies does Crown Market accept?
Crown Market settles in Bitcoin and Monero.
BTC XMR
Monero by default. Bitcoin if the vendor specifically asks for it. Deposit addresses are freshly generated per request rather than reused, which is the default everywhere — no Crown-specific quirk to remember.
Deposit confirmations and the withdrawal flow
Bitcoin credits at two confirmations. Monero takes around ten blocks, roughly twenty minutes. Crown shows the pending balance immediately and counts confirmations live as they roll in. Withdrawals require the PIN you set at registration; the operator added that gate specifically to slow down anyone who steals an active session — they still need the PIN, which is not stored in the session.
No native Litecoin or Ethereum
Crown is BTC/XMR only. If you specifically need to pay in Litecoin, that's Nexus, Anubis, or Mars. Ethereum native is only Anubis. The decision not to add more coins reads as deliberate — fewer chains to integrate, simpler ops, less attack surface around deposit watchers.
See also
Is PGP messaging mandatory on Crown Market?
Yes — vendor-buyer threads on Crown encrypt messages with PGP by default, which is unusual. On most hidden-service marketplaces PGP messaging is an opt-in feature buried in account settings.
What that changes
The marketplace operator never sees the plaintext of an encrypted message. That includes order notes, shipping addresses, support back-and-forth. If the operator’s server is ever seized or compromised, the residue of historical messages is encrypted blobs rather than plain text.
Practical effect
You will paste the vendor’s PGP public key into your client (or import it once) before placing an order. Order messages then go through the same flow as on any market — but the operator’s server logs end up holding less information about you. See PGP on Tor markets for the broader workflow.