Corrections and disclosure
Sources change and editors make mistakes. This corrections and disclosure page explains how a discrepancy is reproduced, what gets changed, and where referral and data boundaries remain.
Report a problem
The public help desk is an answer library, not a submission form: Trust Mixer does not ask for wallet addresses, amounts, or transaction details. To make a suspected error reproducible, record the page URL, the exact sentence, the date you saw it, and the public source that contradicts it. Do not send private keys or transaction data.
What counts as material
A material correction changes the meaning of a route decision or the boundary around a claim. A stale catalog flag, wrong contract identity, missing issuer limitation, or statement that turns a provider claim into a verified fact qualifies. A spelling fix or a visual adjustment does not change the evidence date by itself.
- Source moved
- The original source no longer supports the published wording, so the claim is re-labelled or removed.
- Scope was wrong
- A network-wide fact was presented as a route fact, or a reviewed default was presented as the live production value.
- Decision changed
- The correction affects which network, source, or safety step a reader should inspect next.
What happens next
- 1
The underlying source is opened again and compared with the published wording.
- 2
The finding and surrounding explanation are changed if the evidence has moved.
- 3
Material changes receive a new review date and an entry in the changelog.
What the public record contains
When a material correction is made, the affected page receives a new review date and the changelog names the changed rule or route layer. The record keeps the old wording out of the current answer, but it does not silently erase why the result moved.
The editor then checks nearby pages for the same boundary. For example, a changed USDT contract identity is checked against the USDT hub, the relevant network review, and the editorial protocol before the correction is considered complete.
Sources a correction can be tested against
A correction is reproducible when another reader can open the same public record. Catalog availability, a reviewed contract identity, and an issuer contract list require different sources and must not be collapsed into one verdict.
- Source: Public enabled-route catalog, Xuanxi
- Source: Official USDC contract addresses by blockchain, Circle Developers
- Source: Binance-Peg BSC-USD token contract, BscScan
Disclosure
- Independence
- Trust Mixer is independent and is not operated by, or affiliated with, any mixing service, exchange, or stablecoin issuer.
- Referral relationships
- A destination may have a referral relationship with Trust Mixer. That arrangement does not change the sources or conclusions published here.
- Data
- We do not ask for, collect, or store wallet addresses, amounts, or transaction details. Nothing you would enter on a mixing route is entered here.
Maintained by the Trust Mixer editorial team. Method v1.4.