Skip to content
⬡
THORChain Wiki

THORChain Wiki

Community-maintained encyclopedia of the THORChain protocol: architecture, economics, governance, ecosystem, and source-backed live network data.

Check live operationsBrowse guided answersFollow learning paths
Curated·Last verified 2026-07-08· 8 sources
CuratedChecked 2026-07-08·
THORChain Docs
retrieval details
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.
+7 sources
THORChain Dev Docs
retrieval details
Source retrieved 2026-07-02Official developer documentation root used for API and integration concepts; pair with live endpoints for current state.
THORNode inbound_addresses
retrieval details
Source retrieved 2026-07-04Current-only chain availability, router, halt, and inbound-address snapshot; not durable uptime proof.
THORNode Mimir endpoint
retrieval details
Source retrieved 2026-07-04Current-only operational controls; malformed values must not be treated as inactive.
Midgard v2 Health
retrieval details
Source retrieved 2026-07-04Current-only Midgard provider health, sync state, and lag for rendered live metrics.
Midgard v2 Network
retrieval details
Source retrieved 2026-07-05Current-only network totals; pair with visible source freshness before treating values as live.
Midgard v2 Pools
retrieval details
Source retrieved 2026-07-05Current-only available-pool snapshot; not durable pool uptime proof.
THORChain Network Halts
retrieval details
Source retrieved 2026-07-02Official halt-control reference; live Mimir and inbound-address reads still own current availability.

Use this page for

  • Choosing the right first proof path for live operations, metrics, guided answers, learning paths, ecosystem pointers, and source maps.
  • Knowing which sources back the homepage before following current-only or dated-context links.

Verify elsewhere before claiming

  • Current swaps, route availability, signing, LP actions, TCY actions, RUNEPool availability, or data-source health.
  • Third-party interface safety, future uptime, investment value, recovery completion, or protocol behavior after the checked snapshot.

Live Operations Snapshot

Current THORNode evidence belongs before present-tense claims about swaps, LP actions, signing, TCY, or route availability.

Open diagnostics →

Checking live network status

Fetching THORNode Mimir, inbound-address, version, and block evidence.

Loading live source...

Look here first

Ordinary swaps

Checking

Limited chains

Unavailable

Other operations

Unavailable

Data quality

Pending

Compact view hides raw Mimir keys. Use Network diagnostics for exact evidence and grouped controls.Open diagnostics

Learn in Sequence

Guided reading paths keep explanatory articles separate from current-state proof.

View all paths →

New to THORChain

Start with RUNE settlement, pool mechanics, live-data source boundaries, chain observation, and vault signing before using dashboard numbers.

Start with RUNE as the Universal Settlement AssetVerify before claiming: Current supported chains, halts, or inbound-address availability.

Swap Economics

Read settlement, CLP mechanics, source-bound dashboard evidence, RUNEPool/POL accounting boundaries, and refund/streaming evidence first, then connect incentives and security costs before interpreting fee dashboards.

Start with RUNE as the Universal Settlement AssetVerify before claiming: Current liquidity depth, APY, and earnings coverage from live Midgard snapshots.

Liquidity Actions

Start with the liquidity-action evidence ladder, then use RUNEPool/POL boundaries, live network diagnostics, and Midgard stats before interpreting CLP mechanics, APY, or transaction evidence.

Start with Liquidity ActionsVerify before claiming: Current LP action, pool-deposit, asymmetric-withdrawal, RUNEPool, and source-warning state.

Build And Query

Start with the build/query plan, then connect source-family boundaries, halt controls, quote/refund behavior, and interface checks before shipping a data or transaction workflow.

Start with Build And Query THORChain DataVerify before claiming: Current quoteability, chain availability, inbound-address freshness, Mimir state, and source-warning posture.

Network Security

Use this path when a security or availability claim depends on halt controls, TSS, Bifrost observations, churn, or bonded-node incentives.

Start with Mimir And Halt ControlsVerify before claiming: Current signing, observation, trading, or chain-specific Mimir state.

App Layer And Integrations

Start with the App Layer model, then read halt-control scope before connecting it back to pools, observation, and current network diagnostics.

Start with App Layer, CosmWasm, and Secured AssetsVerify before claiming: Current secured-asset, trade-account, oracle, WASM, signing, trading, and chain-specific Mimir state.

Historical Recovery

Start with the TCY recovery timeline, then read historical Savers/Lending mechanics and the security mechanics that shaped later incident-recovery claims.

Start with TCY Recovery TimelineVerify before claiming: Current TCY operations, balances, distributions, or recovery progress.
Pooled RUNE

Loading

Bonding APY

Loading

Active Nodes

Loading

Midgard Pool Rows

Loading

Network metrics source

Loading live source...

Pool rows source

Loading live source...

Counts Midgard /pools?status=available rows. This is pool-list context, not proof that a route will quote or settle.

THORChain DocsDeveloper DocsMidgard APIRuneScan Explorer