About DrugHub Watch — Methodology & Sourcing
DrugHub Watch is an independent editorial resource that documents publicly observable verification information for one specific onion service. The site is not affiliated with the service it documents; it is a third-party research project that records addresses, signing chains, and publicly available user feedback for educational and security-research purposes. This About page describes the editorial methodology behind the records published elsewhere on the site, the boundaries of what DrugHub Watch will and will not document, and the principles that govern the site's relationship with its readers.
Editorial Methodology
The records published by DrugHub Watch are sourced through three categories of input, each subject to its own verification discipline. Each entry on the site can be traced to one or more of these source types.
Source type 1: Direct observation
Direct observation entries are produced through verification probes that DrugHub Watch runs against the documented onion service. A probe attempts to complete a Tor circuit to the service, retrieves the operator's signed canary message, and verifies the signature against a saved fingerprint. The result of each probe — responsive, unreachable, partial, or anomalous — is logged with its ISO-8601 timestamp. Direct observation is the primary source for the uptime log and the verification timestamps in the address record. Where a record entry rests on direct observation, the timestamp of the observation is published alongside the entry so the reader can apply the appropriate temporal weighting.
Source type 2: Operator-signed announcements
Operator-signed announcements are PGP-signed messages published by the service's operator through their established communication channels. An announcement enters the record only after its signature has been verified against the operator's known signing key. Operator-signed announcements are the source for canonical address rotations, mirror additions, and operator-side context. DrugHub Watch does not relay an announcement that fails signature verification; the failure itself is logged in the failed-verification record with the reason for rejection.
Source type 3: Published reporting and primary documents
Published reporting and primary documents are external sources that DrugHub Watch cites and quotes with attribution. This category includes academic research (USENIX, Privacy Enhancing Technologies Symposium), reputable security journalism (Wired, Motherboard, Krebs on Security), official documentation from project authorities (the Tor Project, the Electronic Frontier Foundation), and primary legal documents (DOJ press releases, court filings on PACER). Forum-aggregated user feedback collected for the review database is sourced from publicly readable threads with attribution to the source forum, the source thread, and the posting date.
What DrugHub Watch Is Not
DrugHub Watch is not a registered organization. The site does not claim corporate identity, does not invite contact, and does not represent any legal entity. References to "DrugHub Watch" on the site refer to the editorial brand under which the records are published, not to a company.
DrugHub Watch is not authored by a named individual. The site does not publish biographical author profiles, photographs of staff, or named-employee titles, because no such people exist behind the site. Modern editorial-quality signals on the open web depend on documented sourcing and verifiable citations, not on fabricated personas; this site relies on the former and explicitly avoids the latter. Fabricated authorship would be a misleading signal, not a neutral one.
DrugHub Watch is not a continuously updated dashboard. The site publishes records at the times the records are produced, and each record carries the timestamp of its production. Readers should treat the most recent entry as the most recent observation, not as a real-time indicator of current state. Records remain on the site as historical entries even after they are superseded.
DrugHub Watch does not endorse the service it documents. The verification record establishes that an address chain is signed by a specific key on a specific date; it does not establish that the underlying service is reliable, safe, or appropriate for any particular use. A reader who treats verification as endorsement is misreading the record.
Editorial Boundaries
The site does not solicit, generate, or fabricate user reviews. Reviews entered into the review database are sourced from public forum threads with attribution; reviews that cannot be sourced are not included.
The site does not invent statistics. Numbers reported on the site (probe counts, observation timestamps, version numbers, dates of historical events) are either directly observed or sourced from external publications with citations. Round-number summaries are avoided in favor of specific values where the underlying data permits.
The site does not invent monitoring frequencies. The probe cadence behind the verification records is whatever the cadence actually is at the time the probes are run; the site does not claim a continuous monitoring infrastructure that does not exist. Each verification entry's timestamp is the truthful record of when that specific verification occurred.
Reaching DrugHub Watch
DrugHub Watch does not maintain a contact channel. The site does not host a contact form, does not publish an email address, and does not accept correspondence. This is a deliberate methodological choice: a publicly maintained contact channel for a research site that documents adversarial subjects produces solicited input that would distort the editorial record. Readers who identify factual errors in published records are invited to verify the same primary sources directly; the records are reproducible from those sources without involvement from the site.