Skip to content
⬡
THORChain Wiki

Network Statistics

Current-only THORChain metrics from Midgard and THORNode. Unavailable upstream data is shown as degraded, not zero.

Page Source Posture

CuratedChecked 2026-07-13·Review due 2026-08-13·
Liquify Midgard v2 Health
retrieval details
Source retrieved 2026-07-13Current-only Liquify Midgard provider health, sync state, and lag for rendered live metrics; regional provider freshness still needs checking.
+5 sources
Liquify Midgard v2 Network
retrieval details
Source retrieved 2026-07-13Current-only Liquify network totals; pair with visible source freshness before treating values as live.
Liquify Midgard v2 Pools
retrieval details
Source retrieved 2026-07-13Current-only Liquify available-pool snapshot; not durable pool uptime or cross-region freshness proof.
Liquify Midgard v2 Earnings
retrieval details
Source retrieved 2026-07-13Current-only Liquify earnings intervals as returned by Midgard; not protocol revenue attribution or cross-region freshness proof.
Liquify THORNode Mimir endpoint
retrieval details
Source retrieved 2026-07-13Current-only Liquify operational controls; malformed or regionally stale values must not be treated as inactive.
THORChain Dev Docs
retrieval details
Source retrieved 2026-07-05Official developer documentation root used for API and integration concepts; pair with live endpoints for current state.

Current-only Midgard metrics and THORNode operational status.

Use This Page For

  • Current-only Midgard and THORNode metric readbacks with visible source freshness.
  • Deciding which live numbers need attention before interpreting liquidity, rewards, node, reserve, or earnings trends.

Verify Elsewhere Before Claiming

  • Durable historical revenue, route competitiveness, solvency, or attribution quality from a rendered metric alone.
  • That swaps, signing, LP actions, or a specific chain are currently available without checking network diagnostics.

Look Here First

First check whether the sources are usable, then read the metric cards as four separate signals: liquidity depth, node reward rate, active security set, and reserve context.

Headline metrics

Loading

Pooled RUNE, bonding APY, active nodes, and reserve are waiting on Midgard.

Midgard pool rows

Loading

Waiting for the current Midgard `/pools?status=available` rows.

Midgard health

Checking

Waiting for provider health before treating metric freshness as usable.

Operations

Checking

Waiting for THORNode diagnostics before separating metric health from protocol pause state.

Earnings history

Loading

Waiting for daily Midgard intervals before drawing chart conclusions.

Operational Check

Check network status before treating loaded metrics as route-ready. A healthy-looking Midgard number does not override a current THORNode pause or source warning.

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

Which Numbers Matter

Start with the number that matches the claim. Each metric is useful, but none of them alone proves route availability, future yield, or recovery state.

Liquidity depth

Pooled RUNE
Use For
Broad liquidity depth and pool-scale context.
Do Not Use For
A specific route will quote, settle, or have low slippage.
Read CLP evidence

Security set

Active nodes
Use For
Current validator-set size and security-context triage.
Do Not Use For
Vault safety, signing availability, or incident recovery proof.
Check operations

Reward signal

Bonding APY
Use For
Current node-reward direction from Midgard.
Do Not Use For
Future yield, investment return, or durable profitability.
Read incentive model

Earnings shape

Daily intervals
Use For
Recent distribution shape from loaded Midgard intervals.
Do Not Use For
Protocol revenue lift, route competitiveness, or partner attribution.
Check fee experiment

Live Metrics

These are current Midgard snapshot numbers. Use them for dashboard triage, then verify operational availability, route quality, and historical conclusions elsewhere.

Pooled RUNE

Loading

Liquidity depth signal. LP APY: unavailable.

Bonding APY

Loading

Node reward signal; current-only and source-dependent.

Active Nodes

Loading

Security-set signal. Standby nodes unavailable.

Reserve RUNE

Loading

Protocol reserve/backstop context; not a solvency guarantee by itself.

Loading live source...

Midgard Available-Pool Rows

Loading Midgard available-pool rows... This is liquidity context from Midgard, not proof that a specific route will quote or settle. Full loaded row list stays in this wiki view.

Midgard pool rows

Loading

Chains in rows

Loading

Deepest pool

Unavailable

Highest 24h RUNE volume

Unavailable

Loading live source...

Route proof is separate

Pool rows show liquidity context. A current route still needs a THORNode quote, source freshness, and network diagnostics.

Check a route
Loading Midgard available-pool rows...

Earnings History

Loading Midgard daily earnings intervals...

Usable intervals

0/0

Unavailable intervals

Loading

Latest valid-window total

Unavailable

Loading intervals

Valid loaded-interval total

Unavailable

Loading intervals

Earnings history is a Midgard-sourced current readback of available intervals. Use it to inspect recent distribution shape, not as durable revenue proof or protocol-attribution proof.

Loading live source...

Loading earnings history from Midgard...

Related Checks

Use these before turning current dashboard values into a broader claim.

current-only
Live data guideproof boundaryCheck when to use Midgard dashboard metrics versus THORNode raw protocol state.Network diagnosticsoperationsPaused trading, signing, observation, or LP controls can decide whether loaded metrics are actionable.Liquidity actionsLP evidenceSeparate LP adds, withdrawals, pool-deposit pauses, asymmetric withdrawals, and APY claims before using stats numbers.Dynamic feesfeesUse the ADR-026 tracker when fee questions are about partner-pair floors rather than ordinary earnings.Build/query pathtaskOpen the task guide for using Midgard, THORNode, inbound-address, and Mimir endpoint data.