What is RUNE?

Introduction

RUNE is the token at the center of THORChain’s two hardest jobs: moving value across chains without a centralized custodian, and making the people who secure that system economically accountable. If you buy RUNE, you are buying exposure to a specific market structure in which RUNE is used as the settlement asset inside pools, the bonded collateral behind nodes, and the unit through which fees are collected, distributed, and partly burned.

THORChain is easy to misunderstand. Many readers hear “cross-chain DEX” and assume RUNE is mainly a governance token, or a gas token, or a branding layer over bridges. The closer description is narrower and more concrete: RUNE is the balance-sheet asset of the network. Usage can create demand for it because swaps and liquidity are organized around it. Security can lock it up because nodes must bond it. Fee activity can reduce supply because part of protocol income is burned.

The token makes the most sense when you follow cause and effect. What does the network actually do? Why must RUNE be in the middle? Who has to hold it, temporarily or structurally? What happens to supply when the protocol is busy, when nodes bond more, or when parts of the ecosystem fail? Those are the questions that tell you what RUNE exposure really is.

How does RUNE function as THORChain’s settlement asset?

THORChain is designed to let users swap native assets across different blockchains without wrapping everything into a single host chain first. The network therefore needs a way to price BTC against ETH, or other supported assets against each other, while keeping a unified accounting system across many external chains. RUNE is the asset THORChain uses to do that.

The key mechanism is simple: every liquidity pool pairs an external asset with RUNE. Instead of maintaining direct pools for every possible asset pair, THORChain keeps pools like BTC–RUNE and ETH–RUNE, then routes a BTC-to-ETH swap through RUNE as the intermediate settlement asset. The protocol documentation is explicit that transactions and swaps are settled in RUNE, and that RUNE is present in every liquidity pool.

That design has two economic consequences. First, trading activity depends on RUNE being available as the common denominator of liquidity, so network usage creates transactional demand for RUNE inside the system. Second, the protocol’s pricing model and pool depth depend on how much RUNE sits opposite external assets. If external-asset liquidity grows, RUNE must grow alongside it in pool inventory.

This is the compression point for the token: RUNE is not merely adjacent to liquidity on THORChain; it is the asset that standardizes liquidity. Without RUNE in the middle, THORChain would not have its current unified cross-chain pool architecture. That is why the token has a more structural role than many exchange tokens do.

Why do THORChain validators have to bond RUNE?

A cross-chain protocol has a security problem that a single-chain AMM does not. THORChain has to watch external chains, control vaults that hold pooled assets, and sign outbound transactions according to the network’s rules. It does this with validator nodes and threshold-signature vaults, so no single node can spend funds alone. But non-custodial design in the technical sense is not enough. The network still needs an economic deterrent against collusion or misconduct.

That deterrent is bonded RUNE. Nodes must post RUNE to participate in consensus and in the machinery that manages vaults and outbound transactions. The whitepaper and docs both treat this as foundational: more Bonded RUNE means more economic security, because the value at risk for misbehaving nodes rises with the bond.

THORChain’s economic model aims for more bonded RUNE than pooled capital. In the design literature, the target is roughly a 2:1 ratio of bonded capital to pooled capital, or about two-thirds bonded and one-third staked in pools. The reason is intuitive. If the bond backing the system is larger than the value a dishonest set of nodes could steal, attacking the network becomes less attractive.

RUNE therefore differs from a token whose security role is mostly symbolic. On THORChain, bond demand is part of the token thesis. If the protocol grows and supports more valuable pools, the system has to attract and retain enough bonded RUNE to underwrite that activity. If it fails to do so, the security margin weakens.

There is also a distributional consequence. Bonded RUNE is not liquid float in the same way exchange-held tokens are. When more RUNE is bonded, less is freely circulating for speculative trading. That does not guarantee price appreciation, but it does mean security demand can materially change available supply.

How do THORChain fees and burns affect RUNE’s supply and incentives?

The cleanest part of the current RUNE story is that THORChain presents its yield and rewards as fee-funded rather than emission-funded. The protocol docs state that rewards to validators and liquidity providers come from network-generated fees, not from new token issuance, and describe the system’s yield as entirely derived from protocol activity.

That changes what holders are underwriting. In many token systems, headline yield is largely inflation redistributed from passive holders to active participants. Under THORChain’s current framing, the more relevant question is whether the network generates enough actual fee income from swaps and related activity to support node incentives and liquidity depth.

The stated fee split is explicit. Of protocol revenue, 5% is burned, 5% goes to a developer fund, 5% to marketing, 10% to TCY holders, and 75% goes to validators and liquidity providers, with the split between those two groups adjusted by the incentive pendulum. That lets you map activity directly to token effects.

The burn is the most obvious direct effect on RUNE holders. A portion of fees collected by the network is permanently removed from supply, which gives RUNE a deflationary tendency as long as fee generation continues. Since all tokens have already been released and there are no vesting schedules or locked allocations according to the docs, ongoing supply change is less about future unlocks and more about what fees, burns, and operational lockups do to the live float.

The other direct effect is income to participants who are actually providing security or liquidity. If you are merely holding RUNE in a wallet, you get exposure to the token’s market price and to the indirect benefit of fee burns. If you are bonding or providing pool liquidity, you are taking on operational or market risk in exchange for a larger share of the fee stream.

What is the incentive pendulum and how does it change returns for RUNE holders?

THORChain does not simply pay a fixed reward rate to everyone who contributes capital. It uses what its design calls the incentive pendulum, a mechanism that shifts income between node bonders and liquidity providers depending on how much capital is bonded versus staked in pools.

The economic purpose is straightforward. The protocol wants enough pool liquidity to make swaps usable, but not so much pool capital relative to bond that the network becomes cheap to attack. So rewards move to whichever side the system needs more of. If bonded capital is too low relative to staked capital, incentives should favor bonders. If bond is abundant and liquidity is thin, incentives can tilt back toward liquidity providers.

For a RUNE holder, “yield on RUNE” is not one thing. The exposure changes with the role.

Holding RUNE outright

A simple spot holder owns the asset without protocol income rights. The upside comes from market demand for RUNE as settlement asset, collateral asset, and burned fee sink. The downside is plain price exposure, plus the risk that network usage, market access, or confidence in the protocol weakens.

Bonding RUNE as node collateral

A bonder is using RUNE as security capital. That creates stronger alignment to fee income, but it also concentrates protocol-specific risk. If THORChain’s security assumptions are stressed, or if node economics become unattractive, this form of holding can suffer in ways a casual holder does not.

The minimum bonding requirement has historically been high enough to limit who can do this directly, which means the security function can be more concentrated than the token’s broad market ownership. Decentralization and security do not come from supply alone; they come from who can actually post bond and run infrastructure.

Providing pool liquidity with RUNE

A liquidity provider holds RUNE together with an external asset in a pool. That changes the exposure most dramatically, because the holder is no longer simply long RUNE. They are now long the pool share, earning fee income but also taking on impermanent loss, which is the change in value relative to simply holding the assets outside the pool when prices move.

So a pool position is partly a yield position and partly a rebalancing position. If RUNE moves sharply against the paired asset, the LP’s token mix changes. That can help or hurt depending on the path of prices, but it is not equivalent to holding unpooled RUNE.

What is TCY and how does it affect RUNE’s revenue share?

A reader trying to value RUNE cannot ignore TCY, even though TCY is a different token. THORChain created TCY to address debt from the THORFi collapse. The documentation describes roughly $210 million of debt being converted into TCY, with 1 TCY representing $1 of debt, and with TCY holders entitled to 10% of network revenue paid in RUNE. TCY does not carry governance rights.

Economically, the important point is not the legal history. It is that 10% of system income now has another claim on it before the rest is distributed elsewhere. That reduces the share of protocol revenue available to the rest of the system compared with a world in which no such legacy claim existed.

This does not make RUNE unworkable. But it does mean part of THORChain’s fee stream has been pledged to repairing an old balance-sheet problem. For RUNE holders, that is best understood as a real revenue diversion tied to an earlier protocol failure, rather than a vague ecosystem side note.

There is a second-order effect as well. Because TCY payouts are distributed in RUNE, ongoing protocol income can translate into RUNE flows toward TCY claimants. Some of those recipients may hold; some may sell. Either way, TCY is now part of how THORChain’s revenue is transmitted into the market.

What operational and security risks threaten RUNE?

RUNE’s role only matters if THORChain can safely do what it claims to do. That is where the main risks become specific.

The first risk is security at the chain-integration layer. THORChain’s value proposition depends on software that watches many external chains, interprets deposits and memos, controls vault logic, and signs outbound transactions. That creates a larger attack surface than a single-chain AMM. The July 2021 exploit, analyzed by Halborn, showed the point sharply: an attacker exploited refund and event-handling logic around the Ethereum-side integration and removed millions of dollars of assets. The network used its halt mechanism to limit damage, but the incident made clear that cross-chain infrastructure risk is not theoretical.

The second risk is that the economic security model is only as strong as the bonded capital and the honesty assumptions behind it. THORChain’s design depends on a supermajority of nodes not colluding. Bonded RUNE is meant to make attacks uneconomic, but that protection weakens if the bonded-to-pooled ratio falls, if node participation becomes too concentrated, or if market conditions make bond less meaningful relative to assets in vaults.

The third risk is that RUNE’s centrality could be weakened by changes in market structure. If traders prefer competing cross-chain venues, if integrated chains or wallets reduce the need for THORChain’s routing layer, or if liquidity fragments elsewhere, then the demand generated by routing through RUNE can soften. A token whose core role is structural can still lose value if the structure becomes less used.

Does it matter whether I hold native RUNE or a wrapped/legacy version?

RUNE has not always been held in only one form. Historically, non-native versions existed on Ethereum and BNB Chain as redeemable IOUs. THORChain later activated a killswitch to phase out those ERC-20 and BEP-2 forms in favor of native THORChain-issued RUNE, with redemption rates linearly dropping over time.

A token ticker is not enough. The economic exposure depends on whether you hold native RUNE on THORChain or a legacy representation on another network. The old non-native forms carried extra dependency and mint-risk baggage because they relied on external-chain issuance arrangements. Moving toward native RUNE reduced those dependencies and made the token’s primary form line up with the network that actually uses it.

For most readers, the practical lesson is custody-aware rather than technical. If you hold native RUNE, you hold the asset the protocol itself uses for settlement, bonding, and fee flows. If you hold some wrapped, legacy, or exchange-specific representation, you may instead hold a claim that depends on another venue’s conversion and custody rules.

That is also why exchange and wallet support deserves scrutiny. Some platforms support native THORChain network deposits and withdrawals directly; others historically dealt with legacy representations. Before buying or transferring, the key question is not merely “Can I buy RUNE?” but “Which RUNE, on which network, with what withdrawal path?” Readers who want to buy or trade RUNE can do that on Cube Exchange, where the same account can handle an initial crypto or bank-funded USDC purchase, quick converts for a first allocation, and spot trading later if they want more control.

What drives demand for RUNE and what factors could weaken it?

RUNE demand comes from a few connected sources, but they all trace back to the token’s role at the center of the protocol.

The most direct source is settlement demand inside pools. If users keep swapping supported assets through THORChain, RUNE remains the common asset every pool needs. The next source is security demand from node bonding. If the network secures more external value, it needs more meaningful bonded collateral. Then there is treasury and fee-flow demand, since protocol income is distributed and partly burned in RUNE.

Supply pressure moves the other way through several channels. Burns reduce supply. Bonding and liquidity provision lock supply. But fee distributions to validators, LPs, and TCY claimants can also return RUNE to the market if recipients sell. So the market exposure is not “deflationary token, therefore up.” It is a live balance between usage, lockup, burns, and income distribution.

What would weaken the token thesis is equally clear. If THORChain lost trading relevance, settlement demand would fall. If security incidents or governance failures damaged trust, the willingness to bond capital could fall. If competing designs achieved cross-chain liquidity without centering one volatile intermediary asset, RUNE’s special position could be less defensible. And if legacy liabilities or treasury uses absorbed too much fee income, the amount of value accruing indirectly to ordinary RUNE holders could disappoint.

Conclusion

RUNE is best understood as THORChain’s settlement and collateral asset, rather than a generic platform token. Its value is tied to whether THORChain keeps attracting cross-chain activity, keeps enough RUNE bonded to secure that activity, and keeps turning fee flow into durable token economics through rewards and burns.

If you remember one thing, remember this: owning RUNE is owning the asset that THORChain puts in the middle of liquidity, security, and fee settlement all at once.

How do you buy THORChain?

If you want THORChain exposure, the practical Cube workflow is simple: fund the account, buy the token, and keep the same account for later adds, trims, or exits. Use a market order when speed matters and a limit order when entry price matters more.

Cube lets readers fund with crypto or a bank purchase of USDC and get into the token from one account instead of stitching together multiple apps. Cube supports a quick convert flow for a first allocation and spot orders for readers who want more control over later entries and exits.

1. Fund your Cube account with fiat or a supported crypto transfer.
2. Open the relevant market or conversion flow for THORChain and check the current spread before you place the trade.
3. Choose a market order for immediate execution or a limit order for tighter price control, then enter the size you want.
4. Review the estimated fill and fees, submit the order, and confirm the THORChain position after execution.