A source map for official docs, developer references, live APIs, historical records, external analytics, and community channels. Pick sources by the kind of claim you need to make.
What Are You Trying To Prove?
Fast Source Triage
Start with the source family that matches the claim. A good source for one claim can still be weak evidence for another.
Source retrieved 2026-07-05Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Do not claim: Durable uptime, safety, or future availability from a single current-only response.
Evidence packet
Start source: Current Protocol State
Source posture: official
Checked / review due: 2026-07-13 / 2026-08-13
Primary source: Liquify THORNode Mimir endpoint
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-13
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.
Claim Type
A memo, fee, asset notation, endpoint, or integration behavior works a certain way.
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.
Do not claim: That static docs prove the feature is live, unpaused, or correctly implemented by every interface.
Evidence packet
Start source: Build And Query Guide
Source posture: official
Checked / review due: 2026-07-14 / 2026-08-14
Primary source: Connecting to THORChain
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-14
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#glossary-definition-map)
Do not claim from this alone: That static docs prove the feature is live, unpaused, or correctly implemented by every interface.
Claim Type
A swap fee, affiliate fee, outbound fee, slip fee, or quote minimum explains a user-facing result.
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.
Do not claim: That one fee field proves route competitiveness, interface quality, revenue lift, or future quote cost.
Evidence packet
Start source: Swap Refund And Fee Triage
Source posture: official
Checked / review due: 2026-07-14 / 2026-08-14
Primary source: Connecting to THORChain
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-14
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.
Claim Type
An App Layer contract, secured asset, trade account, or app route is usable now.
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.
Do not claim: Current solvency, product availability, safety, or recovery completion beyond the dated evidence.
Evidence packet
Start source: Historical Features And Recovery
Source posture: historical
Checked / review due: 2026-07-14 / 2026-08-14
Primary source: Archived Savers docs
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-14
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.
Claim Type
A wallet, explorer, app, or integration surface is the right place to inspect.
Do not claim: Wallet safety, download integrity, quote quality, endorsement, or transaction suitability.
Evidence packet
Start source: Third-Party Interfaces And Wallets
Source posture: curated
Checked / review due: 2026-07-13 / 2026-08-13
Primary source: THORChain Ecosystem
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-13
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.
Claim Type
ADR-026 dynamic fees changed a fee floor, partner record, or revenue signal.
Do not claim: Durable revenue lift, route competitiveness, or partner-attribution quality from current records alone.
Evidence packet
Start source: Dynamic Fee Experiment
Source posture: curated
Checked / review due: 2026-07-13 / 2026-08-13
Primary source: ADR-026 dynamic L1 fee model
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-13
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.
Claim Type
A RUNE number, supply figure, security constant, price, or value claim needs a source.
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.
Do not claim: Price targets, fair value, market cap, exchange float, investment suitability, guaranteed yield, or live security constants from dated tokenomics text alone.
Evidence packet
Start source: RUNE Tokenomics And Value
Source posture: curated
Checked / review due: 2026-07-14 / 2026-08-14
Primary source: RUNE and TCY tokenomics
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-14
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.
Claim Type
People are debating, prioritizing, or interpreting something a certain way.
Do not claim: Final governance status, official incident truth, current availability, or representative sentiment without dated sampling.
Evidence packet
Start source: Community Channels
Source posture: curated
Checked / review due: 2026-07-14 / 2026-08-14
Primary source: Discord
Carry forward: cite the start source, run the next checks that match the claim, and keep the non-claim boundary attached.
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-08-14
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.
Source retrieved 2026-07-13Current-only Liquify Midgard provider health, sync state, and lag for rendered live metrics; regional provider freshness still needs checking.
Source retrieved 2026-07-13Current-only Liquify earnings intervals as returned by Midgard; not protocol revenue attribution or cross-region freshness proof.
Use THORNode evidence for live operational checks such as halts, signing, quotes, Mimir values, and inbound fields. Use Midgard for indexed dashboard metrics such as pools, network totals, and earnings intervals.
Live API responses are current-only snapshots. Midgard metrics are useful dashboard context, but they are not by themselves route-availability proof.
Use For Claims
Current halt, pause, signing, LP, TCY, trade-account, secured-asset, app-layer, or chain-observation state from THORNode.
Current inbound-address, router, gas-rate, Mimir, quote, node/version, or dynamic-fee snapshot.
Current halt, inbound, or quote evidence for a catalog-listed or queried supported chain after the separate static catalog lookup.
Current Midgard pool, network, reserve, bond, node-count, earnings, or APY-style dashboard metric with source freshness attached.
Whether a rendered live value is available, unavailable, degraded, or warning-backed at check time.
Do Not Use Alone To Claim
Durable historical uptime or availability.
Protocol design intent or governance approval.
Revenue lift, safety, route quality, or route availability beyond the checked snapshot.
That a Midgard pool or network metric proves a specific swap, LP action, secured-asset flow, or app-layer action is usable now.
Source retrieved 2026-07-14Current-only RUNEPool accounting endpoint; production evidence pins it to the same Liquify provider and THORChain height as Mimir before interpreting global, provider, reserve, value, PnL, or deposit fields.
Source retrieved 2026-07-14Official RUNEPool overview for aggregate POL participation, units, deposits, withdrawals, and PnL fields; its fixed pool-count prose is not current POL-scope proof.
Source retrieved 2026-07-02Official halt-control reference; live Mimir and inbound-address reads still own current availability.
Use the live RUNEPool/POL snapshot for same-provider, height-pinned THORNode `/runepool` accounting, POL-enabled pool Mimirs, and RUNEPool caveat keys. Pair it with Network diagnostics when the claim is about whether deposits or withdrawals are usable now.
RUNEPool accounting is a current-only snapshot. Fixed pool counts in overview prose are not current POL scope, and valid PnL or current-deposit fields can be negative. The snapshot does not prove future yield, profitability, route health, action support, or user-specific outcomes.
Use For Claims
Current global RUNEPool value, PnL, provider, reserve, and current-deposit fields from THORNode.
Current POL-enabled pool scope from `POL-<Asset>` Mimir keys.
Whether a RUNEPool dashboard value is available, unavailable, degraded, or warning-backed at check time.
Which separate live controls need review before claiming RUNEPool deposits or withdrawals are open.
Do Not Use Alone To Claim
Future yield, profitability, impermanent-loss outcome, or investment suitability.
That every POL-enabled pool is liquid, routeable, safe, or competitive.
That a clean accounting snapshot proves RUNEPool deposits or withdrawals are currently usable.
A user-specific RUNEPool balance or payout without a provider-specific endpoint and intentional address context.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-14Official Incentive Pendulum, emission, and reserve-flow design; its original 500M maximum-supply framing must not be presented as the newer tokenomics page's current approximate supply.
Source retrieved 2026-07-02Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-04Current-only operational controls; malformed values must not be treated as inactive.
Use official tokenomics and protocol docs for dated RUNE supply and role framing, Stats for current Midgard network metrics, and THORNode/Mimir evidence for current security constants such as minimum bond or slash settings.
The newer tokenomics page gives approximate `425M and burning` supply framing while the economic-model page still presents the original `500M` maximum and genesis distribution. Keep those dated source contexts, live metrics, and market analysis separate; the wiki does not provide price targets, fair-value models, market-cap proof, exchange float, or guaranteed-yield conclusions.
Use For Claims
Dated RUNE supply, reserve, circulating-supply, burn, or TCY-context framing from the tokenomics source.
Which live dashboard surface owns pooled RUNE, reserve, bond, node-count, earnings, or APY-style metrics.
Which THORNode or Mimir source family should be checked before quoting minimum bond, slash settings, or current security constants.
Which external evidence would be needed before making price, fair-value, market-cap, or investment-suitability claims.
Do Not Use Alone To Claim
Current RUNE price, fair value, market cap, exchange float, or investment suitability.
Live circulating supply, reserve balance, bond posture, minimum bond, or slash settings from dated tokenomics text alone.
Future yield, protocol revenue lift, recovery value, or guaranteed return.
That one RUNE number can be reused across settlement, security, liquidity, tokenomics, and market-value claims.
Source retrieved 2026-07-14Current-only endpoint for chain presence, current vault addresses, routers, gas rates, dust thresholds, and halt fields; never a static transaction template.
Source retrieved 2026-07-04Official asset-notation reference for chain and asset identifiers used in docs, quotes, pools, and memos.
Choose the source family that owns the claim: Midgard for indexed consumer data, THORNode for current protocol state, Cosmos or Tendermint RPC for their respective data families, and gRPC clients for protobuf access.
Developer docs describe interfaces, not live transaction inputs. Refresh quotes, inbound addresses, routers, gas rates, dust thresholds, and halt fields before signing; public providers require rate-limit and failure handling.
Implementation Workflow
Need a step-by-step query plan? Use the build/query guide for endpoint choice, inbound-address checks, quotes, units, source warnings, and failover posture before wiring a product flow.
Source retrieved 2026-07-02Official halt-control reference; live Mimir and inbound-address reads still own current availability.
Use these sources to identify known interfaces, wallets, explorers, and developer tools, then pair them with live THORNode checks before assuming protocol availability.
Ecosystem references are not wallet-security audits, URL-integrity guarantees, app-uptime monitors, quote-quality proof, compliance-policy proof, or endorsements.
Use For Claims
That a project is a source-listed ecosystem reference as of the wiki review date.
Which chains, category, and source labels this wiki associates with a project.
Which live protocol checks should be reviewed before using a transaction surface.
Source retrieved 2026-07-04Official fee reference for fee categories and quote fields; exact values remain live/current-only.
Use these for ADR-026 design context, live dynamic L1 fee Mimirs, sealed records, and current-epoch accumulators.
ADR text is design/governance context. THORNode endpoints are current-only snapshots and do not prove durable revenue lift, route competitiveness, or partner attribution quality.
Use For Claims
ADR-026 design intent, whitelist states, pair scope, and controller mechanics.
Current dynamic-fee Mimirs, sealed records, and current-epoch accumulators exposed by THORNode.
Whether the dashboard has samples, warnings, or insufficient evidence for a particular pair.
Do Not Use Alone To Claim
Durable revenue lift or route competitiveness.
Partner attribution quality or off-chain affiliate correctness.
A final governance outcome beyond the dated ADR and current THORNode state.
Source retrieved 2026-07-02Official documentation root used for curated protocol background; it still describes GG20 at review time, but current safety and migration state require dated incident and release sources.
Source retrieved 2026-07-05Official RUNE and TCY tokenomics overview, including TCY supply, revenue share, and no-governance-rights caveat; current amounts and distributions still require live evidence.
Source retrieved 2026-07-14Official app-layer technology reference for the permissioned mainnet model and contract sandbox boundary; current contract availability still depends on live scoped controls.
Use for high-level protocol architecture, tokenomics, node concepts, RUNE, TCY, and canonical educational context.
Static docs can lag live protocol state. Prefer dated language when describing fast-moving operational controls.
Use For Claims
Protocol architecture, tokenomics framing, node concepts, and educational mechanism summaries.
Officially documented halt key families, RUNE/TCY framing, and app-layer concepts.
Canonical background for pages that also expose current-only live checks.
Do Not Use Alone To Claim
Exact current Mimir values, constants, pool state, or chain availability.
Post-incident operational safety unless the source is a dated incident or upgrade report.
Third-party interface status, wallet safety, or market conclusions.
Source retrieved 2026-07-14Official historical Savers mechanics and explicit permanent-deprecation date of 2025-01-04; not current deposit, yield, synth, or redemption instructions.
Source retrieved 2026-07-14Official historical Lending mechanics and explicit permanent-deprecation date of 2025-01-04; not current borrow, repay, collateral, or TOR instructions.
Source retrieved 2026-07-05Developer-facing TCY mechanics, claim, staking, and recovery caveats, including the explicit warning that full debt recovery is market dependent and not guaranteed.
Source retrieved 2026-07-05Dated THORFi unwind postmortem with January-February 2025 liability, pause, and Proposal 6 milestones; its implementation-status section is historical, not current TCY availability proof.
Source retrieved 2026-07-05Official initial May 2026 exploit timeline and then-pending ADR-028 recovery framing; use Report #2 and the accepted ADR for later root-cause and conciliation status.
Source retrieved 2026-07-04Official root-cause report for the May 2026 GG20/TSS vault exploit, patched v3.19.1 recovery, and still-planned migration away from GG20.
Source retrieved 2026-07-04Official v3.19.0 release summary for post-exploit restart controls, including TSS patches, compromised-vault exclusion, temporary KeyVerify, and pause safety.
Use for Savers/Lending deprecation, THORFi unwind, incident reports, recovery records, and source-dated historical context.
Historical records should not be converted into current availability claims without live or newly reviewed sources.
Use For Claims
Savers and Lending were permanently deprecated on 2025-01-04; archived mechanics are historical context, not reusable instructions.
Official exploit-report root cause, remediation, restart, and recovery context, with v3.19.0 restart controls kept distinct from the v3.19.1 incident-class patch.
Which current TCY controls need review before making claim, stake, distribution, unstake, claim-swap, or trading availability claims.
Dated milestones or incident lessons where the source itself supports the claim.
Do Not Use Alone To Claim
That historical products are available now.
That a memo handler still appearing in developer documentation proves the corresponding product or action is enabled.
That TCY claiming, staking, trading, distributions, user eligibility, or interface support is currently available without live controls and official-interface evidence.
Current solvency, safety, or recovery completion beyond dated sources.
Financial advice, recovery-value expectations, or investment outcomes.
Source retrieved 2026-07-14Direct source returned a Cloudflare challenge from this review environment; reconcile with THORNode and verify in a browser before relying on its indexing.
Source retrieved 2026-07-14External analytics source returned a rate-limit response from this review environment; not canonical protocol state or verified current coverage.
Source retrieved 2026-07-14Open-source organization responded during this review; code claims still need repository, branch, commit, and deployment context.
Use to inspect transactions, pools, nodes, and market or flow context outside this wiki.
Explorer and analytics data may use their own indexing rules. Treat them as references unless independently reconciled.
Use For Claims
Transaction, pool, node, market, or flow context from external indexers.
Third-party research summaries when labeled as curated or needs-review.
Pointers for readers who want to inspect evidence outside this wiki.
Do Not Use Alone To Claim
Canonical protocol state or official THORChain policy.
Reconciled accounting, tax, or solvency proof.
Endorsement, safety review, or complete interface coverage.
Source retrieved 2026-07-14Open-source organization responded during this review; code claims still need repository, branch, commit, and deployment context.
Use these for community discussion, announcements, open-source repositories, and social context.
Community and social channels are not canonical protocol proof. Use official docs, live APIs, or dated incident reports for claims.
Use For Claims
Community debate, implementation discussion, ecosystem chatter, and repository context.
Signals about what people are asking, disputing, or prioritizing.
Links to places where readers can continue non-canonical research.
Do Not Use Alone To Claim
Canonical protocol proof, final governance state, or official incident truth.
Current operational availability or safety.
Representative sentiment without careful sampling and date boundaries.