How this beat gets reported
Coverage of these markets is unreliable in patterned ways. Knowing the patterns lets you read around them.
This page is about the reporting rather than the markets. It is worth its own space because the failure modes are consistent enough to be predicted, which means a reader who knows them can extract signal from stories that are mostly noise.
Four failure modes
Sourcing from the wrong place. Most reporting is built on forum posts, and forum posts are where rumours live. A story sourced to a forum is a story about what people are saying, which is a legitimate thing to report if labelled as such and almost never is.
Numbers with no provenance. Volumes, user counts, uptime percentages, and vendor totals get printed with no indication of how they were derived. Most of these figures originate as an estimate in one article and become fact through repetition. Trace one back far enough and you usually find a single unsourced sentence.
Confusing the market with the beat. A story about a law enforcement operation against one platform gets written as though it applies to all of them. The categories are not interchangeable and treating them as one produces reporting that is technically true and practically misleading.
Incentives nobody discloses. A large share of sites covering this subject take money from the platforms they cover. Readers have no way to tell which from the outside, and the sites that do it never say. Disclosure is rare enough that its absence carries no information either way, which is the worst possible state for a reader.
Questions that filter most of it
- Where did the number come from, and does the piece say? If not, treat it as decoration rather than data.
- Is the source a document or a person saying a thing? Signed documents are checkable. Assertions are not.
- Does the piece distinguish what it observed from what it inferred? Good reporting on this beat is heavy on inference and says so.
- What does the site earn from? If it is not obvious, assume the answer is the thing being covered.
The pattern in seizure coverage
Worth naming separately because it recurs. A platform is seized, coverage describes it as a decisive blow, and within months the displaced users have distributed across other platforms. The reporting is accurate about the event and wrong about the consequence, every time, because it treats the market as an institution rather than as demand that will route around an obstacle.
The useful read of a seizure is not that the ecosystem shrank. It is that a particular set of users lost funds and had to move, which is a real and specific harm that gets lost inside the larger claim.
Our own position
This site covers one platform in depth and the wider beat only where it touches that platform. That is a narrow scope and it is a limitation, not a virtue. We are not a general source on this subject and readers looking for one should be aware that we are not trying to be.
Verified working Nexus Market mirrors
Three v3 onion addresses currently serving the production market, signed under PGP fingerprint 0x7F2A0A9D. Use the Copy buttons.