Methodology and route-review changelog
The Trust Mixer methodology and route-review changelog records changes that affect evidence, coverage, or reader decisions. Cosmetic typography fixes are left out.
- v1.4
Cluster ownership and reproducible review protocol
Added a route-review protocol that keeps catalog observations, network facts, issuer controls, and quote-time values in separate findings.
- Scope
- Editorial policy, the help desk, the USDT hub, and the route evidence pages.
- Review result
- Reconciled the reviewed Xuanxi route catalog with the local route record and rechecked the 19 canonical pages for indexability and source boundaries.
- v1.3
Catalog provenance and route-specific reviews
Added a dated Xuanxi catalog source, limited verified wording to observed route codes and availability flags, and rebuilt the five network pages around distinct route decisions.
- Scope
- The public USDT and USDC catalog layers, plus five detailed network reviews.
- Review result
- The catalog snapshot is checked by route code and send/receive flag; an absent fee, minimum, delay, or production override remains explicitly unpublished.
- v1.2
Evidence model published
Every operational claim now carries a status, scope, date, and source. Removed all numeric grades and seals in favour of re-checkable verdicts.
- Scope
- Claim tables, status badges, source citations, and route comparison language.
- Review result
- A result can now be traced to a public ledger, issuer document, provider statement, direct observation, reasoning, or an explicit absence of evidence.
- v1.1
Legal timeline re-cited
Re-reviewed the 2024-2026 legal events and attached primary records or reputable reporting to each entry.
- Scope
- The legal-risk timeline and the distinction between using a service and operating one.
- Review result
- Each dated event is labelled by evidence strength; unresolved legal questions are kept as partial or claimed rather than presented as settled law.
- v1.0
USDC issuer-control hub added
Separated USDC from USDT with a dedicated issuer-control hub covering Circle's blacklist authority and the native-vs-bridged distinction on Base.
- Scope
- USDC route coverage, Circle contract references, and native-versus-bridged Base terminology.
- Review result
- The hub keeps Circle's issuer terms separate from Base ledger facts and does not treat a ticker or route listing as proof of the active production contract.
How to use this history
Read the newest entry first when a route page shows a changed date. The current method is v1.4; its status vocabulary and review sequence are defined on the evidence framework, publication decisions are documented in the editorial policy, and material changes follow the corrections record.
Sources for the current route layer
These are the primary or first-party references used when the route layer is reconciled. They support individual fields; they do not prove a live quote, settlement, or destination outcome.
- Source: Public enabled-route catalog, Xuanxi
- Source: Tether Token Terms: freezing and address blacklisting, Tether
- Source: Official USDC contract addresses by blockchain, Circle Developers
- Source: Binance-Peg BSC-USD token contract, BscScan
Maintained by the Trust Mixer editorial team.