Skip to content
Mixer Briefing Finish briefing

SOURCE LEDGER

Every claim needs a source.

Sources are part of the interface. The reader should be able to tell which sentence came from a dated observation, which is policy and which is still a gap.

Use a source-aware route Read the method
Reader jobSources and dates
EvidenceDated sources and open questions
Next moveVerify before relying
Decision pathDated check
01 Name the sourcePublic URL or internal policy boundary.
02 Keep the dateFreshness is manual, not assumed.
03 Match the claimNo source, no positive copy.
04 Expose the gapA source check stays visible.
Source ledger ยท 4 source classes

01 / SOURCE CLASSES

Four boundaries, one rule.

A public URL does not make every property true. The source class tells you what kind of wording is allowed.

Evidencedated observation

XuanXi first-party observation

Public interface and service wording observed on 13 Aug 2026. Used only for attributed, dated observations.

open public source
Evidenceaggregate context

Background research

Search results and published answers can reveal questions worth checking. They do not verify a provider claim.

read boundary
Evidencescope and guardrails

Project policy

Defines editorial identity, evidence boundaries and handoff rules.

read boundary
Evidencesource needed

Second provider source still needed

A named provider needs its own official public URL and check date before any changeable detail can be stated as current.

read boundary

02 / CLAIM PARITY

The claim ledger is intentionally small.

These are the service-facing observations currently supported here. They are dated, attributed and constrained.

Approved public claim set
USDC observation
USDC was visible in the dated observation.
observed
This does not establish permanent availability.
Route labels
Observed USDC route labels: ERC20, Arbitrum, AVAX C-Chain, Optimism, Solana, Base and Algorand.
observed
A label does not prove direction, current availability or terms.
Account field
The observed order form had no account or email field.
observed
Do not turn an interface observation into a universal account-requirement promise.
Timing wording
Published timing ranges are service-attributed estimates.
attributed
They are dated estimates, not technical guarantees.
Privacy wording
A positive technical property is not established.
source check
conflicting evidence
Open questions
Retention, refund workflow/SLA and a permanent support channel remain unverified.
source check
Check the current order flow or provider terms before relying on this detail.
XuanXi first-party observationAll six observations resolve to the dated first-party sourceChecked 2026-08-13open source

03 / PRIMARY CONTEXT

Read the risk context separately.

External educational sources can explain mixer terminology and regulatory risk. They do not verify a provider's current route, fee, logs or support workflow.

Chainalysis glossary

Independent background on mixer terminology and tracing limits.

open primary context

U.S. Treasury notice

Public context for sanctions risk around a specific historical action.

open primary context

04 / WHAT IS NOT HERE

Absence is deliberate.

No operator, license, audit, rating, review count, user volume, permanent network map, refund SLA or legal conclusion is stated without evidence.

Read editorial policy