Skip to content
SRSR17.org
Contribute

Submit a tip, correction, or new source

Spotted an error? Have a new paper, regulatory update, forensic alert, or lab result we should cover? Send it here. We review every submission against our editorial principles.

Last reviewed: 2026-05-06Editorial methodology

What we accept

  • Corrections. If something on the site is factually wrong, link the page and tell us what should change.
  • Peer-reviewed literature. New papers on SR-17018, related compounds, or relevant pharmacology.
  • Regulatory updates. Scheduling changes, agency advisories, court decisions affecting legality.
  • Forensic alerts. CFSRE, EMCDDA, DEA, or similar public alerts about the orphine series in the unregulated supply.
  • Lab or analytical data. Independently verified identity confirmation, purity measurements, or adulterant findings.
  • Vendor incident reports. Documented adulteration, mislabeling, or contamination of vendor product. Include identifiable evidence (chromatogram, photo, batch).
  • Site improvements. Suggestions for clarity, accessibility, additional pages we should add.

We do not publish vendor recommendations, sourcing guides, or affiliate-style content regardless of submission. See methodology for our standards.

How submissions are handled

  • Every submission is reviewed by an editor against our hierarchy of evidence.
  • If we use your submission, we'll credit you in the page changelog (anonymously if you prefer, or by name if you provide one).
  • We may follow up by email if we need clarification or full-text access.
  • We don't publish PII from submitters. Email addresses are used only for follow-up.
  • If we decline a submission, we'll tell you why where possible.

Submit your tip

Submissions are stored on our own infrastructure (Vercel + Postgres). Email, if you provide it, is used only for editorial follow-up.

Alternative ways to reach us

If you have material that's too sensitive for a web form — for example, identifiable forensic data tied to a specific case, or a vendor-incident report involving a person still using — contact the editorial team directly. A secure inbox will be published on the methodology page on launch of the v1 byline.