Contact

How to prepare a correction or evidence dispute, why no editorial contact channel is published yet, and where mixer support belongs.

Contact / page status
Document_

01_

Status

No channel published

02_

Scope

Guide corrections only

03_

Support

Not a mixer help desk

Boundary_

The page states its current boundary instead of inventing a channel.

Illustrative render. It explains the page topic; no live service data is shown.

Cited primary sources

web.archive.orgrdap.centralnic.comrdap.identitydigital.servicesrdap.tonicregistry.toofac.treasury.govmerklescience.comtrmlabs.com

18

public pages covered_

147

claims with evidence labels_

7

primary-source domains cited_

Read the evidence before you trust a mixer

Every claim names its evidence, explains the mechanism and marks the limit. Open the question you need to settle first.

Editorial policy
There is no contact channel published here yet

3 paragraphs_ 1 claim checks_

Open this section_
What to include in a correction request

2 paragraphs_ 4 bullets_

Open this section_
What this site cannot help you with

1 paragraphs_ 6 bullets_

Open this section_
Where service support actually lives

4 paragraphs_ 1 claim checks_

Open this section_

Direct answer_

What this covers

There is no published channel for corrections, evidence disputes or takedown requests about this guide yet.

What remains true

This is not a mixer support line and cannot help with a transaction, payout or account problem.

There is no contact channel published here yet

No mailbox, form or named contact is published yet.

A guide that makes factual claims should give readers a way to challenge them. That channel does not exist yet.

When one is available, this page will name it and the last-updated date will change.

What to include in a correction request

A useful correction request has four parts.

Specificity gives an editor something to check. Saying that a page is biased does not; quoting the sentence and adding a dated counter-source does. The claim can then be checked and either changed or answered.

  • The page address and the exact sentence you dispute, quoted rather than paraphrased.
  • What you believe is wrong about it, in one line.
  • The evidence you rely on, with a date. A live block, a document or a dated page can be checked. A recollection cannot.
  • Whether you are disputing a fact, a wording or a boundary. Those three are handled differently.

What this site cannot help you with

Transaction problems belong with the mixer that handled them, not with this guide.

  • A stuck, delayed or missing payout. Nobody here holds keys to any pool.
  • A refund, a chargeback or a dispute with an operator.
  • An identity or verification problem at a service.
  • A verdict on whether a named service is safe, honest or solvent.
  • A legal opinion about your jurisdiction or about a transaction you made.
  • Recovery of funds sent to a wrong address or to a fraudulent one.

Where service support actually lives

If your problem is a transaction, the operator is the only party who can see it.

Service support lives on the service's own domain. This guide cannot escalate, verify or override anything that happens there.

That includes the two services named on the About page. Shared ownership does not turn an educational guide into a support channel.

Be wary of unsolicited messages that claim to offer help. The Reddit and GitHub page explains the impersonation pattern and what to check before replying.

The checks behind every service claim

These rows show the evidence labels attached to claims in this guide.

Compare services

Claim review path_

  1. 01_

    Claim

    What the service says

  2. 02_

    Mechanism

    How the result could occur

  3. 03_

    Boundary

    Where the claim stops

  4. 04_

    Evidence class

    What supports it

A reading path, not a score or a service rating._

claim check_

This site is an educational reference. No page on it accepts coins, holds keys or runs a pool.

confirmed_

claim check_

The editorial contact channel is not published on this site.

not measured_

This site is an educational reference. No page on it accepts coins, holds keys or runs a pool.

BTC Mixer Guide

Fact check, this page

confirmed_

Every number here is counted, not claimed

The figures below are counted from the evidence labels attached to the pages, not typed in by hand.

Evidence registry split

What the current labels establish

90_

claim checks marked confirmed_

27_

claim checks marked assumed or not measured_

External evidence is kept separate from this two-part split.

90

claim checks marked confirmed_

27

claim checks marked assumed or not measured_

Educational disclaimer

This site is an educational reference about Bitcoin mixing technology. No page on it accepts coins, holds keys or runs a pool, and nothing on it is legal, financial, or investment advice. The operator behind this domain also runs commercial mixing services: both are named in the disclosure on the About page, and an owned service is marked as owned wherever its name appears here. Mixing services are restricted or prohibited in some jurisdictions. You are responsible for complying with the laws that apply to you and for the consequences of any transaction you make.

Search demand was not measured for this topic. Every number shown here carries an evidence label: confirmed, external, assumed, or missing.

Last updated 2026-09-12_