Source Map

THORChain Wiki source-map evidence packet
Claim to check: Something is available, paused, enabled, or healthy right now.
Start with: Current Protocol State (/docs#current-protocol-state)
Source posture: official
Checked / review due: 2026-07-13 / 2026-11-17
Primary source: Liquify THORNode Mimir endpoint (https://gateway.liquify.com/chain/thorchain_api/thorchain/mimir)
Why this source path: Current availability claims need live THORNode, Midgard, Mimir, or rendered dashboard evidence from the checked snapshot.
Next checks:
- Network diagnostics: Pause, halt, signing, LP, TCY, secured-asset, WASM, and per-chain evidence. (/network#network-diagnostics)
- Stats look-first panel: Liquidity, security-set, rewards, and metric data-quality posture. (/stats#stats-look-here-first)
- RUNEPool/POL snapshot: Current RUNEPool accounting, POL-enabled pool scope, and separate RUNEPool availability caveats. (/economics#runepool-pol-live)
- Current TCY controls: Claim, stake, distribution, unstake, claim-swap, trading, and TCY source-warning posture. (/tcy#tcy-current-controls)
Do not claim from this alone: Durable uptime, safety, or future availability from a single current-only response.

THORChain Wiki source-map evidence packet
Claim to check: A memo, fee, asset notation, endpoint, or integration behavior works a certain way.
Start with: Build And Query Guide (/deep-dives/build-query-data#query-plan)
Source posture: official
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: Connecting to THORChain (https://dev.thorchain.org/concepts/connecting-to-thorchain.html)
Why this source path: Static docs explain intended/design behavior, not proof that something is unpaused now. Pair official developer docs with live endpoint and halt-state checks before readers transact or build.
Next checks:
- Developer source map: Official docs, fees, memos, asset notation, and endpoint references. (/docs#developer-integration)
- Network diagnostics: Confirm the relevant chain or action is not currently paused. (/network#network-diagnostics)
- Glossary: Short definitions for Mimir, inbound addresses, memos, fees, and related terms. (/glossary)
Do not claim from this alone: That static docs prove the feature is live, unpaused, or correctly implemented by every interface.

THORChain Wiki source-map evidence packet
Claim to check: A swap fee, affiliate fee, outbound fee, slip fee, or quote minimum explains a user-facing result.
Start with: Swap Refund And Fee Triage (/deep-dives/streaming-swaps-refunds#what-to-check-first)
Source posture: official
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: Connecting to THORChain (https://dev.thorchain.org/concepts/connecting-to-thorchain.html)
Why this source path: Ordinary fee questions usually depend on the fresh quote response, route amount, liquidity/slip math, outbound cost, affiliate fields, dust thresholds, and current halt state. ADR-026 dynamic-fee records are a separate experiment and should not be used as the default explanation for every high-fee quote.
Next checks:
- Developer fee docs: Official fee categories, quote fields, memo fields, dust thresholds, and asset notation. (/docs#developer-integration)
- CLP mechanics: Slip, liquidity fee, pool-depth, and output-mechanics explanation without live route claims. (/deep-dives/clp#what-clp-can-prove)
- Dynamic fee tracker: Use only when the claim is specifically about ADR-026 dynamic L1 fee floors or partner records. (/dynamic-fees#dynamic-fees-live)
Do not claim from this alone: That one fee field proves route competitiveness, interface quality, revenue lift, or future quote cost.

THORChain Wiki source-map evidence packet
Claim to check: An App Layer contract, secured asset, trade account, or app route is usable now.
Start with: App Layer Claim Checks (/deep-dives/app-layer#evidence-ladder)
Source posture: official
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: Connecting to THORChain (https://dev.thorchain.org/concepts/connecting-to-thorchain.html)
Why this source path: Contract, secured-asset, trade-account, and app-interface claims cross multiple proof paths. Static docs explain the model; current use needs live WASM, secured-asset, trade-account, oracle, signing, trading, chain, and interface evidence.
Next checks:
- Network diagnostics: Current WASM, secured-asset, trade-account, signing, trading, chain, and source-warning posture. (/network#network-diagnostics)
- Developer integration: Official docs for asset notation, memos, fees, quote behavior, and endpoint shape. (/docs#developer-integration)
- Interface checklist: Wallet, app, quote recipient, memo construction, and download/source-integrity checks. (/ecosystem#interface-use-checklist)
Do not claim from this alone: Contract safety, wallet support, redemption capacity, route availability, or execution success from docs or ecosystem listings alone.

THORChain Wiki source-map evidence packet
Claim to check: An incident, deprecated product, recovery mechanism, or older feature behaved a certain way.
Start with: Historical Features And Recovery (/docs#historical-features-and-recovery)
Source posture: historical
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: Archived Savers docs (https://docs.thorchain.org/thornodes/archived/savers)
Why this source path: Historical claims need dated incident reports, upgrade notes, recovery records, or explicitly historical wiki records.
Next checks:
- TCY recovery timeline: Dated THORFi unwind, TCY mechanics, and recovery non-claims. (/deep-dives/tcy-recovery-timeline#what-to-check-now)
- Current TCY controls: Use live controls for present-tense claim, stake, distribution, unstake, claim-swap, or trading availability. (/tcy#tcy-current-controls)
- Network security path: Sequence of security explainers with current-state caveats. (/deep-dives#deep-dive-path-network-security)
Do not claim from this alone: Current solvency, product availability, safety, or recovery completion beyond the dated evidence.

THORChain Wiki source-map evidence packet
Claim to check: A wallet, explorer, app, or integration surface is the right place to inspect.
Start with: Third-Party Interfaces And Wallets (/docs#third-party-interfaces-wallets)
Source posture: curated
Checked / review due: 2026-07-13 / 2026-11-17
Primary source: THORChain Ecosystem (https://docs.thorchain.org/ecosystem)
Why this source path: Third-party surfaces are pointers to inspect, not automatic endorsements, uptime monitors, or safety audits.
Next checks:
- Interface checklist: What the wiki lists, what to check, and what not to infer. (/ecosystem#interface-use-checklist)
- Network diagnostics: Confirm protocol-level availability before trusting a transaction flow. (/network#network-diagnostics)
Do not claim from this alone: Wallet safety, download integrity, quote quality, endorsement, or transaction suitability.

THORChain Wiki source-map evidence packet
Claim to check: ADR-026 dynamic fees changed a fee floor, partner record, or revenue signal.
Start with: Dynamic Fee Experiment (/docs#dynamic-fee-experiment)
Source posture: curated
Checked / review due: 2026-07-13 / 2026-11-17
Primary source: ADR-026 dynamic L1 fee model (https://gitlab.com/thorchain/thornode/-/raw/develop/docs/architecture/adr-026-dynamic-l1-min-fee-per-thorname.md)
Why this source path: ADR-026 claims need a split between proposed design text, live THORNode Mimirs, sealed records, and current accumulators.
Next checks:
- Dynamic fee tracker: Current per-thorname and per-pair live evidence with source warnings. (/dynamic-fees#dynamic-fees-live)
- Current Protocol State: Live-source boundaries before treating records as operational truth. (/docs#current-protocol-state)
Do not claim from this alone: Durable revenue lift, route competitiveness, or partner-attribution quality from current records alone.

THORChain Wiki source-map evidence packet
Claim to check: A RUNE number, supply figure, security constant, price, or value claim needs a source.
Start with: RUNE Tokenomics And Value (/docs#rune-tokenomics-and-value)
Source posture: curated
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: RUNE and TCY tokenomics (https://docs.thorchain.org/tokenomics-rune-tcy)
Why this source path: RUNE appears in settlement, liquidity, security, tokenomics, and market discussion. Those claims use different source families and should not reuse one number as proof for another.
Next checks:
- RUNE number router: Pick live metrics, security constants, dated supply framing, or value non-claims before quoting RUNE. (/rune#rune-number-router)
- Stats look-first panel: Use current Midgard/THORNode source labels for pooled RUNE, reserve, bond, nodes, earnings, or APY-style values. (/stats#stats-look-here-first)
- Network diagnostics: Check current THORNode/Mimir evidence for minimum bond, slash settings, signing state, and operational controls. (/network#network-diagnostics)
Do not claim from this alone: Price targets, fair value, market cap, exchange float, investment suitability, guaranteed yield, or live security constants from dated tokenomics text alone.

THORChain Wiki source-map evidence packet
Claim to check: People are debating, prioritizing, or interpreting something a certain way.
Start with: Community Channels (/docs#community-channels)
Source posture: curated
Checked / review due: 2026-07-14 / 2026-11-17
Primary source: Discord (https://discord.com/invite/thorchaincommunity)
Why this source path: Community material is useful context for debate and questions, but it is not canonical protocol evidence.
Next checks:
- Official Protocol Documentation: Canonical background before converting discussion into protocol claims. (/docs#official-protocol-documentation)
- Governance and history: Dated proposals, incidents, research, and milestones. (/governance)
Do not claim from this alone: Final governance status, official incident truth, current availability, or representative sentiment without dated sampling.