Inside the Nexus dispute panel, how three-way arbitration runs
Most dispute systems on darknet markets are one moderator and a queue. Nexus runs a three-person rotating panel with signed rulings. The mechanics are unusual and worth understanding before you ever need them.
When a buyer opens a dispute on Nexus — non-arrival, mis-listed product, vendor unresponsive past the protection window — the ticket lands not in a single moderator's queue but in a three-person panel rota drawn from the platform's longstanding moderator pool. The panel rotates per ticket; the same three moderators do not pick up sequential tickets, by policy.
The composition is deliberate. One panelist is buyer-facing by background (typically a long-tenured buyer who has graduated into moderation). One is vendor-facing (typically an ex-vendor who has retired their shop). The third is what the platform calls a “protocol” panelist: someone whose job is to read the multisig state, the on-chain settlement history, and the signed feedback record, and to translate those facts for the other two.
The ruling flow
The panel reviews evidence asynchronously. Each panelist files a written ruling within the published 6-hour SLA. Rulings are signed at issuance with each panelist's individual PGP key, then aggregated; a clean two-of-three majority resolves the dispute, with the multisig contract receiving the appropriate co-signing instruction within minutes of the third ruling landing. Ruling text is logged on the vendor's profile, signed, with the panel composition publicly recorded.
Edge cases — a tied panel due to one panelist abstaining, a panelist recusing on a conflict of interest, a buyer or vendor producing late evidence — are handled by an escalation path that pulls a fourth panelist from the pool. The escalation rate sits below 4 percent of total tickets in the most recent quarterly transparency report.
“Three rulings beat one ruling because three panelists looking at the same evidence will catch each other's mistakes. The signed history catches the platform's mistakes. That is the design.” — quarterly transparency report, signed
What it means for buyers
Two practical takeaways. First, file evidence early. The panel is reviewing your ticket against the vendor's response asynchronously; new evidence after a panelist has filed a ruling does not retroactively unfile it. Second, the panel reads the multisig state. If the on-chain record shows the vendor has co-signed a settlement that didn't reach you, that record is one of the strongest pieces of evidence you can have, and it is on the chain regardless of what the platform's database says.
Working Nexus Market mirrors
Below are the three v3 onion addresses currently serving the production market, signed with the platform's PGP key (fingerprint 0x7F2A0A9D). Use the Copy button — never retype an onion by hand.