LogoLogo
APPDISCORDDISCUSSIONDAO VOTING
  • Portal
  • Welcome to Radiant Capital
  • Introducing Radiant v2
  • ✨Project Info
    • RDNT Token
    • Deposit
      • How to Deposit
      • 1-Click Loop & Lock
      • rTokens
      • Withdraw assets
    • Borrow
      • How to Borrow
      • Health Factor
      • Loan Repayment
      • Liquidations
      • Flash Loans
      • Interest Rate Model
    • RIZ
      • How to Use RIZ
    • Riz Vault
      • How to use the RIZ Vault
    • Dashboard
      • Rewards Box
      • Lending Box
      • Deposits and Borrows
    • Dynamic Liquidity (dLP)
      • dLP Utility
      • dLP Liquidity Options
      • dLP Architecture
      • Zapping dLP
      • Maintaining Eligibility Status
      • Disqualification Bounties
      • Explainer Video
    • Manage Radiant
      • dLP stats
      • Vesting RDNT
      • Locked dLP
      • Platform Fees
      • Relock dLP
      • Auto-compound
    • RDNT OFT Bridge
    • Radiant-Stargate Bridge
  • 💫Navigation
    • Connecting to Arbitrum / BNB
    • Radiant V1 Migration
    • v1 Tutorials
  • ⚖️Governance
    • Overview
    • Key Terms
    • Proposal Criteria
    • Proposal Process
    • Specifications
  • 🔓Contracts & Security
    • Arbitrum Contracts
    • Base Contracts
    • BNB Chain Contracts
    • Ethereum Contracts
    • Scheme of Contracts
    • DAO Reserve
    • Security Timelock
    • Audits
      • v3 Audits
      • v2 Audits
      • v1 Audits
    • Immunefi
  • 💭Other Info
    • Mission & Values
    • Frequently Asked Questions
    • Integrations
    • Branding
    • Co-Marketing Guidelines
    • Terms of Service
Powered by GitBook
On this page
  1. Project Info
  2. Dynamic Liquidity (dLP)

Disqualification Bounties

PreviousMaintaining Eligibility StatusNextExplainer Video

Last updated 1 year ago

Radiant is introducing a function for users that meet the 5% dLP to disqualify ineligible users for a bounty, akin to running a liquidation bot, either directly through the UI or with searcher bots.

A “bounty” is placed on the account equal to a base bounty that eligible dLPs can claim.

Vigilant bounty hunters can monitor available disqualification bounties on the Manage Radiant page and disqualify ineligible users by selecting "claim" and confirming the transaction.

This disqualification system prevents expired dLP accounts from receiving ineligibly earned platform fees and prevents ineligible users from receiving $RDNT emissions that fall below the 5% dLP threshold.

This has the added benefit of further decentralizing actions taken on the protocol, allowing users to point and click to remove ineligible participants while benefiting the protocol (and themselves).

Additional Notes

  • Bounty hunters must maintain the 5% dLP threshold status and have deposited assets to claim bounties

  • The base bounty is dynamic, depending on searcher bot demand and the price of $RDNT

  • Bounties are prioritized so that only one bounty per account is available at a time, although up to three bounty types exist:

    1. Bounty priority is placed on expired lock treatment (remove expired locks from the pool or re-lock dLPs with auto-relock enabled) to prevent the account from continuing to receive ineligibly earned platform revenue. The bounty for removing an expired lock is the base bounty

    2. The next bounty priority is preventing accounts from continuing to receive ineligibly earned RDNT emissions that fall below the 5% eligibility threshold. The bounty for emissions ineligibility equals the base bounty

  • Self-disqualification: performing an on-chain action within the Dapp (deposit/claim/lock) will trigger a disqualification if the above parameters are detected.

Additionally, bounty hunters receive a base bounty for relocking dLP for users that have enabled "auto-relock," and for performing on behalf of users that have enabled this automation.

To minimize the chance of disqualification, by increasing your dLP threshold above 5%.

Expired locked dLP disqualifications can be prevented by toggling the “” function on the Manage page to continue receiving platform fees without interruption.

Claimed bounties are paid in

The last bounty priority is for . When an auto-compound event is triggered, the protocol outsources the execution of the transaction to bounty hunters. AutoCompound bounties are funded by the fee paid by the user that will be compounded. This amount starts small and increases over time as they accrue more pending rewards that will be compounded

✨
auto-compounds
maintain your eligibility status
auto-relock
Vesting RDNT
auto-compounding
eligibility threshold