runebond
  • Getting Started
    • Welcome
  • Sections
    • Node List
    • Operator dashboard
      • List your node
    • My Requests
      • Request for whitelist
  • Features
    • πŸ“©On-chain chat
    • Yield Guard System
  • πŸ™ˆHidden Nodes
  • Maximum time to leave
  • πŸ””Notifications via Email and Telegram
  • Node moderators
  • πŸ–₯️Node Profiles in RUNEBond
  • Others
    • Frequently Asked Questions (FAQs)
  • How does it work?
Powered by GitBook
On this page
  • Overview
  • πŸ” What Triggers Yield Guard?
  • ⚠️ What Happens to Overbonded Nodes?
  • πŸ’‘ Why Is This Important?
  1. Features

Yield Guard System

PreviousOn-chain chatNextHidden Nodes

Last updated 1 month ago

Overview

Yield Guard is a mechanism designed to protect bond providers from inefficient yield allocation across nodes in the THORChain network. Its main purpose is to prevent overbonded nodes from receiving additional RUNE delegations that would not generate yield effectively.


πŸ” What Triggers Yield Guard?

A node will be marked as Yield Guarded and hidden from listings when it meets any of the following conditions. All checks are only applied to nodes in Active status:

  1. Overbonded Node

    • The node’s total_bond is equal to or greater than the network-defined optimal_bond.

    • Additional RUNE bonded to this node will not generate yield.

    • This prevents inefficient delegation to already saturated nodes.

  2. Highest Slash Points in the Network

    • The node has the highest slash_points among all active nodes.

    • This node is likely to be churned out within 3 days due to poor performance or misbehavior.

  3. Lowest Total Bond in the Network

    • The node has the lowest total_bond among all active nodes.

    • Since it ranks lowest by bond weight, it is expected to be churned out in the next rotation.

  4. Oldest Active Node

    • The node has the oldest status_since timestamp among all active nodes.

    • Churns occur roughly every 3 days, and the oldest active node is rotated out.

  5. Requested to Leave

    • The node has requested_to_leave = true.

    • The operator has explicitly signaled intent to leave the network, which will happen within ~3 days.


⚠️ What Happens to Overbonded Nodes?

When Yield Guard is active on a node:

  • The node is hidden from public listings.

  • Users can still delegate, but it will be clearly marked as inefficient.

  • Once the node’s total bond drops below the optimal threshold again, it will automatically reappear in the listings.


πŸ’‘ Why Is This Important?

  • βœ… Ensures fair and efficient yield distribution across the network.

  • βœ… Helps users avoid delegating to nodes that will soon exit the network.

  • βœ… Encourages network decentralization by promoting underbonded and stable nodes.

  • βœ… Protects bond providers from bonding to nodes that will not generate returns.