re.al docs
  • Introduction
    • Get to Know re.al
    • Relationship to Arbitrum
    • Tokenized RWAs on re.al
  • re.al Chain
    • Arbitrum Orbit Overview
    • Block Explorer
    • Run a Node
    • Governance
    • Security
    • Contracts & Addresses
  • Get Started
    • reETH: Native Token
    • Get Started
    • Asset Bridging
    • Network Guides and Videos
      • How to Bridge to re.al
      • How to Lock $RWA
      • How to Bridge from re.al (to Ethereum and L2s)
  • RWA Token
    • Overview
    • RWA Tokenomics
      • Reporting veRWA APY
    • Managing veRWA
    • stRWA and wstRWA
    • RWA Rewards Program
      • Overview and Goals
      • Program Specifics
      • Referrals
      • Calculating Points
    • Migration
    • Contracts
      • RWA Technical
      • stRWA Technical
  • Build on re.al
    • Start Building
    • Faucet
    • Smart Contracts
      • Write a Contract
      • Deploy Using Hardhat
      • Verify Contracts
  • Services
    • Services
    • Account Abstraction
      • Safe Account Abstraction
    • Automation & Off-chain Data
      • Gelato Web3 Functions
    • Bridges
      • Layer Zero
    • Indexers
      • Goldsky
    • Oracles
      • Redstone on re.al
    • Relay
      • Gelato Relay
    • VRF
      • Gelato VRF
    • Wallet as a Service
      • Privy
      • Web3Auth
Powered by GitBook
On this page
  1. RWA Token
  2. RWA Tokenomics

Reporting veRWA APY

PreviousRWA TokenomicsNextManaging veRWA

Last updated 7 months ago

The RWA App includes a that gives users the opportunity to look at veRWA yield sources and current/historical veRWA APYs.

veRWA APYs are presented in a rolling seven-day average to reduce noise.

The APY figure assumes the veRWA yields are compounded back into veRWA, hence the utilization of APY vs APR.

Lastly, we’ve maintained the historical APY at the time it was accrued vs the data adjusting for the current price of RWA. For example, the same amount of accrued yield with RWA at $1 and RWA at $10 is going to show a much different APY. Our data preserves the APY as it was experienced with the RWA price at that time yield was distributed.

APY methodology

re.al pulls the individual revenue streams for a time period, and voting power at time of each revenue event, computes returns based on that, and compounds them. We then annualize based on the length of the selected time period.

In most cases this period is seven days. However the re.al enables users to see compounded annualized returns across multiple time periods. For example, if the user selects a one month period the data within the yield chart will update to show the compounded annualized returns for the previous month.

How it works:

  1. re.al pulls the individual revenue streams for a time period

    1. Let's assume this is 30 days, and there are 100 revenue events each day, so 3,000 in total

  2. re.al applies the current price and total voting power for each timestamp

    1. With 3,000 revenue events, there are potentially 3,000 different prices of RWA, and 3,000 different total voting power numbers

    2. In this case, 3,000 different returns are calculated

  3. Returns are compound them for that time period

    1. For example: (1 + ret1)(1 + ret2) ... (1 + retn) - 1

  4. Lastly, returns are annualized i.e. (1 + return) ^ (365 / period) - 1

dashboard