RUNE Token
RUNE is the native asset used for settlement, liquidity pairing, economic security, and protocol accounting.
Page Source Posture
retrieval details
+2 sources
retrieval details
retrieval details
Native settlement, bond, and liquidity asset for THORChain.
Use This Page For
- RUNE roles in settlement, liquidity pairing, node bonding, and protocol accounting.
- Source-backed tokenomics framing that should remain dated when figures are quoted.
Verify Elsewhere Before Claiming
- Current price, circulating balances, reserve balances, emissions, or market conclusions.
- Current minimum bond, slash parameters, Mimir overrides, or investment suitability.
What is RUNE?
Settlement Asset
Every external-asset swap routes through RUNE liquidity, for example BTC to RUNE to ETH.
Security Bond
Node operators bond RUNE to secure vaults and participate in signing. Minimums and slash settings are current-only constants/Mimir facts.
Liquidity Pair
Pools pair RUNE with external assets, creating a unified liquidity layer rather than isolated asset pairs.
Governance Context
Operational governance is primarily node/Mimir driven. ADRs and TIPs document protocol changes; avoid treating all RUNE holders as direct voters.
What Do You Want To Do With RUNE?
Route action questions before reading tokenomics. RUNE can appear in swaps, liquidity, RUNEPool, and node bonding, but each path has a different current-state check.
Swap or acquire RUNE
- Use For
- Check whether a concrete route can quote, then inspect the interface or wallet you plan to use.
- Do Not Use For
- Do not treat this page as exchange availability, route safety, wallet safety, or execution instructions.
Stake or earn with RUNE
- Use For
- Separate RUNEPool/POL accounting, LP positions, node bonding, and TCY staking before calling anything yield.
- Do Not Use For
- Do not describe RUNEPool, LP APY, or node rewards as guaranteed staking yield.
Bond RUNE for a node
- Use For
- Use node-operator sources and live controls before relying on bond, unbond, rebond, rotation, or slash settings.
- Do Not Use For
- Do not infer current node-operation availability from tokenomics or historical node docs.
Make a RUNE claim
- Use For
- Classify the claim as settlement role, live metric, security constant, dated tokenomics, or value claim.
- Do Not Use For
- Do not turn a role explanation into price, fair value, investment suitability, or future-yield proof.
Do not treat this page as exchange, wallet, staking, yield, or node-operation instructions. It is a source router for deciding which live or dated evidence to inspect next.
Which RUNE Number Do You Need?
Pick the number by the claim you are making. RUNE appears in settlement, security, liquidity, and tokenomics, but each number needs a different evidence path.
Live network metrics
- Use For
- Pooled RUNE, reserve context, active nodes, bond/liquidity posture, earnings, APY, and source-health labels.
- Do Not Use For
- Do not use live metrics as price, fair value, circulating-supply, or future-yield proof.
Security constants
- Use For
- Minimum bond, slash settings, Mimir overrides, signing state, node set, and operational controls.
- Do Not Use For
- Do not infer current bond or safety posture from the RUNE role summary or old docs.
Supply framing
- Use For
- Reduced supply framing, reserve/circulating context, burn/reduction notes, and TCY recovery context.
- Do Not Use For
- Do not treat dated tokenomics records as live supply, market cap, exchange float, or valuation evidence.
Price or value claim
- Use For
- Use the wiki to say which source family would be needed and what this page does not prove.
- Do Not Use For
- Do not claim fair value, price targets, investment suitability, guaranteed yield, or recovery value.
RUNE Claim Checks
Start by classifying the claim. This page supports protocol-role explanations; live balances, current economics, tokenomics figures, and value claims need different source paths.
Settlement role
- Use For
- RUNE as the common settlement pair, liquidity-pool side, security bond, and accounting asset.
- Verify
- Use the settlement deep dive before turning this overview into a protocol-model explanation.
- Do Not Claim
- Do not claim price, fair value, or investment upside from the settlement role alone.
Current network number
- Use For
- Pooled RUNE, reserve context, active nodes, bond/liquidity posture, earnings, and source health.
- Verify
- Use the Stats decision panel and keep source freshness or degraded-state labels attached.
- Do Not Claim
- Do not quote stale, degraded, or unavailable live snapshots as clean current facts.
Tokenomics figure
- Use For
- Supply framing, reserve/circulating context, burn/reduction notes, and TCY recovery context.
- Verify
- Use the source-labeled Token Economics section before quoting dated supply framing.
- Do Not Claim
- Do not treat dated tokenomics records as live supply, market cap, or valuation evidence.
Value or investment claim
- Use For
- Use this page to define what the wiki does not prove about RUNE value or suitability.
- Verify
- Use sources outside this overview for market analysis, then keep the wiki citation boundary explicit.
- Do Not Claim
- Do not claim fair value, price targets, investment suitability, guaranteed yield, or recovery guarantees.
Continue From Here
Move from the source-boundary router into settlement mechanics, live network numbers, or official source maps before making current RUNE claims.
Token Economics
As reviewed on 2026-07-14, the newer official tokenomics page gives approximate figures near 425M total, 350M circulating, and 75M reserve with ongoing burns. The economic-model page still shows the original 500M maximum and genesis distribution; keep that as historical cap context rather than combining it with the newer approximate snapshot. Recheck live/source data before quoting exact balances.
source retrieval details
+1 source
retrieval details
How RUNE Flows
1. Swaps
A swap routes through RUNE-paired pools. RUNE acts as the common settlement layer between native assets.
2. Liquidity
Liquidity providers supply pool depth and earn source-dependent fees and rewards according to current protocol rules.
3. Security
Node operators bond RUNE. Misbehavior can put that bond at risk through slash mechanisms and churn rules.