How does it work?

RUNEBond runs on public THORChain transactions. Every node listing, whitelist request and operator answer is a transaction with a memo, sent to the official RUNEBond address, so anyone can read and verify it on-chain. RUNEBond indexes those transactions and shows them in a friendly interface. It never takes custody of the RUNE you bond.

Who takes part

• Bond providers hold RUNE and want to earn a share of a node’s rewards without running infrastructure.
• Node operators run THORChain nodes and need enough bonded RUNE to stay in the active set.

Bonding on THORChain is permissioned: an operator has to whitelist a provider’s address before the protocol accepts their bond. RUNEBond exists to make that connection simple and transparent. If you are new to THORChain, start with THORChain 101.

The flow, step by step

1. An operator lists their node. The listing is an on-chain transaction with a RUNEBond memo that publishes the node’s terms. See list your node.
2. A bond provider finds a node. The app shows listed nodes with their fee, minimum bond, capacity and status side by side. See find nodes.
3. The provider requests a whitelist. A 0.1 RUNE transaction whose memo names the node, the provider’s wallet and the amount they intend to bond. See how to request whitelist.
4. The operator answers. Approving the request whitelists the provider’s address on the node; the answer is also recorded on-chain. Providers can follow the status in my requests.
5. The provider bonds. Once whitelisted, the provider sends the bond transaction from that same address. The RUNE goes from their wallet to the node, never through RUNEBond.
6. Both sides track the position. Rewards, node status, slash points and the estimated maximum time to leave are visible in the app, and notifications can alert you to changes.

Everything is public

The listing, each whitelist request and the status of every request are public in the transaction history of the official RUNEBond address:

• thor1xazgmh7sv0p393t9ntj6q9p52ahycc8jjlaap9 on thorchain.net

The memo formats are a RUNEBond convention, not part of the THORChain protocol, but the transactions themselves are ordinary THORChain transactions. That has two consequences:

• Both sides build a verifiable history. Operators can show how they have treated providers, and providers can check it before bonding.
• Any interface can use the same data. RUNEBond only indexes these transactions, so other wallets or dashboards can read and display them too.

To avoid spam, RUNEBond ignores any transaction worth less than 0.1 RUNE.

What RUNEBond does and does not do

RUNEBond does:

• index listings, requests and answers and present them in one place,
• build the bond and whitelist transactions for you, which reduces delegation errors,
• provide tools to evaluate operators, such as node profiles and on-chain chat.

RUNEBond does not:

• custody your bond: it moves from your wallet to the node and back,
• control nodes, their keys or when they leave the active set,
• change any THORChain protocol logic.

The one optional exception to the non-custodial flow is the experimental claim your rewards feature, which briefly routes claimed rewards through a RUNEBond vault. It is documented with its risks on its own page.

Build on it

If you want to offer the same functionality in your own interface, get in touch. Our DMs are open on X.