Cadabra 2.0
Cadabra (EN)
Cadabra (EN)
  • Introducing Cadabra
  • Cadabra's mechanics
  • Security and Audit
  • Short Overview
  • Community
  • Roadmap
  • Cadabra v1
  • Articles
    • Cadabra 2.0 vs 1.0. Advantages and Differences
    • High yield at the launch of Cadabra 2.0
    • ABRA emission + External Yield. Complementarity
    • ABRA Locking: why it’s essential and how it increases your yield
    • ABRA locking migration vs Unlocking. What to choose?
    • Strategies boost algorithm
  • Team
  • Strategies
    • Strategies
    • Yield sources
    • Epochs
    • Voting
    • Liquidity Rebalancing
    • Strategies' APR
    • Underlying Protocol Rewards (UPR)
  • Tokenomics
    • ABRA
    • Emission
    • Locking and veABRA
    • Contracts
    • v1 -> v2
  • Earn with Cadabra
    • Yield from Strategies (ABRA)
    • Holder bonus
    • Yield for Voting (UPR)
    • Yield for Locking (Rebase)
    • Referral Program
  • Referral Program
    • Referral Rank
    • Rewards and Bonuses
      • Emission for Referral Rewards
    • Team bonus and Binary Tree
    • v1 -> v2
  • Airdrop
    • Launch Airdrop (season 2)
    • Airdrop (season 3)
Powered by GitBook
On this page
  1. Strategies

Yield sources

PreviousStrategiesNextEpochs

Last updated 6 months ago

Strategies interact with underlying yield sources. Yield sources invest and withdraw funds from underlying protocols on behalf of users and extract rewards. These rewards are distributed among those who voted for the yield source or strategy.

Yield sources for strategies include pools, gauges, and vaults on third-party protocols, such as AAVE, Curve etc. They are grouped into strategies based on similar characteristics: assets, risk profiles, and yield principles. Having multiple yield sources within a strategy allows for investment diversification and smooth out APR fluctuations in underlying protocols, with rebalancing occurring based on voting results.

Cadabra team constantly looks for new earning opportunities and monitors the emergence of promising protocols. Each underlying protocol undergoes a security assessment and expert assessment before being integrated. Once a yield source is implemented and tested, it is added to the strategy with a 3-7 day time lock, giving users time to decide whether they trust the new protocol.