Submission field guide
Which submission route should I use?
Anyone can send a sourced correction about a group, substance or firearm through the browser form. It requires no name, email, reader account or signing key.
A publisher seeking a continuing, attributable channel uses the inspectable signed client. Enrollment, fresh-channel proof and independent editorial review precede publication. Ordinary editorial email is a third route; it does not provide anonymous delivery or authenticate a group.
How do I request a change to a profile?
Identify one profile and field, quote the current wording, propose the replacement, and supply public sources with dates and uncertainty. The contextual correction link carries the group ID into the browser form.
An enrolled publisher may submit the same proposal as a signed statement. A published statement and an edited profile are separate decisions: neither route writes directly to a public card.
Where is the group ID, and what if a group is missing?
The exact directory ID is the final part of its /groups/ address. Names and aliases are not interchangeable with IDs. The signed client needs that exact ID.
If there is no appropriate profile, contact the editorial inbox with public sources so a new cited record can be considered. Do not impersonate another record or invent an affiliation to pass enrollment.
What is the full signed enrollment sequence?
Inspect the client, generate an Ed25519 key locally, and submit an enrollment request for an existing group ID. Keep the private key off the website.
The server returns a fresh challenge bound to the group and key. Post that exact challenge on an already-established first-party public channel, then send the signed proof request with its URL.
An editor independently checks that channel against at least two evidence domains, its continuity and possible takeover or seizure, and the exact challenge. Only an approved key can submit statements for that channel. Statements still enter private editorial review.
What does GunsDrugs actually authenticate?
A valid signature demonstrates control of a particular private key. A reviewed fresh challenge provides dated evidence of control over an independently established channel. Editorial review separately assesses the claims and evidence.
These are three distinct checks. They do not prove a legal identity, membership roster, current group leadership, ownership of a logo, or the truth of every statement.
Can someone enroll by choosing a name or uploading a logo?
No. A name, new key, logo, biography or repeated historical claim is insufficient. Enrollment requires independent channel provenance and a fresh challenge tied to that key.
The system does not auto-enroll a group or award a general verified-news badge. No media upload is part of this protocol.
Can a key or channel be compromised?
Yes. A channel or key may be stolen, transferred or seized. Continuity evidence is dated and scoped, and can be held or revoked when uncertainty appears.
Historical signed publications remain attributable records of claims. Check the public key registry for the present state and any predecessor or successor transition.
Do I have to demonstrate a criminal act to establish a channel?
No. The site requests evidence of control over an existing public channel, not a demonstration of violence, trafficking, intrusion or access to private material.
Do not commit an act, expose a person, supply stolen data or acquire private access for this workflow. Those activities are outside the purpose of this intake.
Is a submission guaranteed to be untraceable?
No. Personal identity is not requested by the correction form or signed protocol, but a website cannot promise perfect anonymity. Device, browser, network, infrastructure and posting habits can reveal information.
A signature is authentication, not end-to-end encryption. A public pseudonym deliberately creates continuity across its approved publications and proof channel.
How do I use the advertised onion service?
Read the same-origin live API information response. A valid advertised onion hostname is shown in the intake-route panel. Use Tor Browser for that origin; do not use a clearnet onion gateway.
The command-line client does not start or configure Tor. Tor Browser does not route unrelated applications. A suitably configured Tor client wrapper and the --base onion origin are required for command-line use. There is no automatic direct-network fallback in these instructions.
Who can read a private submission?
Authorized editors and administrators can inspect the private queue. Hosting and transport infrastructure can handle connection metadata even when the application does not retain a client IP.
The private intake is not an attorney-client channel, emergency service or end-to-end encrypted drop box. Keep personal addresses, victim details, secrets, credentials and attachments out of it.
What becomes public after editorial approval?
Approved signed statements expose their signed payload, signature, group pseudonym and key reference, with separate editorial commentary and evidence links. The key registry exposes channel verification and transition history.
Anonymous correction bodies are not automatically published. An accepted correction still requires a separately sourced editorial change and deployment.
What is kept, pruned or backed up?
Correction bodies and nonpublished signed statements are eligible for pruning 30 days after receipt. Nonapproved enrollments are eligible 30 days after their seven-day challenge expiry. Replay receipts last seven days and used-work records one day; cleanup is periodic.
Fourteen daily local recovery snapshots can retain private bodies beyond live-queue pruning. Approved key history, public statements and audit metadata remain. Email-provider retention is separate from the intake queue.
What makes a useful submission?
One specific, checkable claim; original proposed wording; exact public sources; their dates; and a clear account of what remains uncertain. Distinguish allegations, charges, convictions, estimates and reported associations.
For group figures, identify the definition, year, currency and scope. A seizure, asset value or case-level proceeds figure must not be presented as annual organization revenue.
What material is prohibited?
No attachments, images, encoded files, stolen records, credentials, victim information, personal addresses, threats, demands, payment instructions, recruitment or operational assistance. Plain text and public references only.
The site does not request firearm procurement or fabrication, drug manufacture or sourcing, trafficking instructions, or demonstrations of criminal activity. Technical acceptance is not an endorsement of submitted content.
Can I propose an emblem, flag or geography correction?
Supply a public source record and explain identification, creator, rights and uncertainty. Uploading an image or choosing a flag does not establish affiliation, origin or territory.
Origin and reported operations are separate fields. National flags describe a sourced geographic relationship, not ethnicity or nationality of members. No dark-web images are collected by the site, including logos.
Which evidence helps?
Prefer dated original records and precise public citations. Explain what each source establishes and whether it is reporting an allegation, court outcome, historical estimate or official claim.
Do not substitute a logo, rumor, follower count, anonymous assertion or a copied profile for independent provenance. A source mention alone does not establish involvement or causation.
When is a statement accepted or published?
Every signed statement starts pending. An authorized editor can hold, reject or publish after reviewing it. Publication includes the publisher claim label, separate editorial commentary and source context.
A valid signature is not independent corroboration. Browser corrections can be accepted for editorial work without publishing the submitted body. Neither path makes instant changes to a profile.
How do I check progress or dispute a decision?
Keep the opaque receipt. There is no public pending-queue browser or private submission-status endpoint. The approved statement feed shows publications only.
For an editorial question, use the contact route and refer to the receipt without sending private keys or prohibited material. Acceptance into the queue is different from acceptance of a claim. No response time is promised.
Does an email alert approve a submission?
No. The submission receipt concerns intake; editorial decisions concern the current private queue. An email reminder or preliminary assessment cannot authenticate a person, corroborate a factual claim or approve publication.
If an operator alert is delayed or grouped, its existence or absence does not change editorial status. Ordinary email to bang@gunsdrugs.com does not become an authenticated publisher statement.
What publication permission does a signed statement grant?
The signed statement action requires an explicit CC-BY-4.0 grant under the publisher pseudonym. Grant it only for original text and other material you are entitled to license. Publicly accessible material is not automatically yours to republish.
The correction form requests a source-backed editorial proposal; it is separate from the signed statement licensing action. A source link does not grant rights to copy a full article or image.
Does the guide provide legal clearance or source privilege?
No. This is a procedural guide, not a legal opinion, promise of privilege or assurance that a particular engagement is lawful. Pseudonyms and signatures do not remove applicable obligations.
Questions involving restricted actors, rights, preservation duties or court process require an assessment of the actual circumstances and appropriate qualified advice. The website does not promise to ignore lawful process or provide a blanket journalism exemption.
Does the proposal helper send or save my draft?
The helper below uses memory in this tab. It does not POST, sign, enroll a key, fetch reference URLs, or write draft text to browser storage.
You can download or copy the plain-text proposal after local format checks. That is an export for your own review; it does not submit the proposal. Clipboard, downloads and device behavior remain outside this page.
Can every member register a separate publishing key?
The current model is one active publishing key per group, with predecessor and successor history. It is not a member-account or team-permissions system.
A group name in the directory is not an invitation for every claimant to enroll. Each new or recovered channel requires the same independent editorial review.
How should I handle the signing key?
Generate and store it locally. Never put a private key in the correction form, a statement, a reference URL, an email or a public repository. The server receives the public key and signatures only.
The reference client creates a new key file without overwriting an existing one. Protect a separate recovery copy appropriately; a group name cannot reset a lost key.
How do key rotation and revocation work?
Rotation requires signatures from both predecessor and successor keys on the same domain-separated transition. The public registry retains the transition so readers can inspect continuity.
A signed revocation blocks future writes from that key and holds pending statements. An editor can also revoke through authorized administration. Historical publications keep their original signatures and key references.
What if a key is lost or a channel is taken over?
Do not treat a new key plus a familiar name as recovery. The editor must perform a fresh channel-continuity review and address revocation or compromise of the old key explicitly.
The guide cannot guarantee that a historic group still controls a channel. When provenance is unresolved, the enrollment or claim remains held rather than gaining assumed authenticity.
What are the anonymous correction limits?
Choose an existing group, substance or firearm profile. Write 40–4,000 characters and provide one to three HTTPS public source URLs. The form accepts no files or media.
The server permits at most 30 accepted corrections per rolling hour and up to 500 pending corrections. Proof of work and an opaque receipt nonce help bound abuse and recover ambiguous retries without requesting personal identity.
What are the signed request limits?
Signed requests have a 16 KiB JSON limit. Statement titles are 8–180 characters, bodies 40–9,000 characters, with at most eight reference URLs and explicit CC-BY-4.0 consent. The exact closed schema is in the protocol.
Limits include 20 accepted writes per key per rolling 24 hours, 240 authenticated publisher writes per rolling hour, a separate 60/hour enrollment/proof pool, 500 fresh enrollments and 1,000 pending statements. These are intake bounds, not evidence of reliability or moderation capacity.
What do common responses mean?
400 means the request was invalid; 403 can mean a key or channel is not approved; 409 can indicate replay, a nonce conflict or incompatible state; 429 means a quota or queue limit; 5xx means service trouble. Inspect the returned message without assuming publication.
For an uncertain browser network result, use Retry same request while this tab retains it. Do not alter the payload and blindly submit again: the same nonce with different content is rejected.
What does a receipt prove?
A successful receipt confirms that the service accepted that request into its workflow. It does not confirm that a claim is true, a group identity is authentic, an editor accepted it or an email reached an inbox.
The browser retains an ambiguous request only in this tab to retry the identical bytes. Closing the tab loses that local retry state. Keep any confirmed receipt separately if needed.
Does the service open submitted links?
No. The intake stores submitted reference URLs as inert labels for editorial review. It does not automatically fetch them, download attachments or execute source text.
Submitting a URL does not endorse its contents. Reviewers must assess a reference through an authorized, bounded process before relying on it.
Signed records can cite HTTPS URLs or HTTP v3 onion URLs without credentials, fragments or nonstandard ports. The separate anonymous correction form accepts HTTPS references only. Public onion references appear as Tor-only text, with no automatic gateway or browser request.
Where is the editorial contact?
The public editorial inbox is bang@gunsdrugs.com for questions, public-source leads, corrections and privacy enquiries. Use plain text and public references.
Ordinary email is hosted by Zoho and does not provide anonymous delivery or a reviewed publisher channel. Use the appropriate intake route when continuity or network privacy matters.