Wand
  • ⚖️Background
  • Products
    • IP-Vault
      • Principal Token
      • Yield Token
      • Dutch-VAMM
      • Points Tracking
    • Yield-Vault V2
      • Glossary
      • Innovations
      • User Interaction
      • Product Description
        • Single-Asset Liquidity Pool
        • Liquidity Provision
        • Pricing Mechanism
        • Implied APY
      • Renewable Liquidity
      • Zero Liquidity Bootstrap
    • Collateral-Vault
      • Core Concept
        • USB-Stablecoin
        • xToken-Margin Token
      • Vault
        • AAR--Asset Adequacy Ratio
        • V-Vault
          • Deposit for minting
          • Withdraw for redemption
        • S-Vault
      • Earn
        • Interest Settlement
        • PTY--Price Trigger Yield
      • Discount Offer
      • Revenue Flow
      • Parameters
      • RedStone Oracles
      • Audit Report
      • Addresses
      • Migration to V2
      • Guide 101
        • What can I do with Wand?
        • How to obtain xToken and USB?
        • FAQ
  • 🪙TOKENOMIC
    • Coming soon
  • --------Archived--------
    • Blast Campaign
      • Basic Rules
      • Blast Points
      • Blast Gold
Powered by GitBook
On this page
  • Mechanism
  • Points Tracking Method
  1. Products
  2. IP-Vault

Points Tracking

For regular on-chain reward claims, IP-Vault can handle them automatically. However, for rewards in the form of Points calculated off-chain, the following method is required for integration.

Mechanism

IP-Vault comprises PT and YT. PT represents users’ shares of the underlying assets, while all additional rewards generated by these assets, such as profits or points, are fully distributed to YT users. Unlike Pendle’s mechanism, in IP-Vault, YT users’ rewards are determined by their YT share proportion, not the quantity.

Points Tracking Method

This method applies to continuous point issuance, such as protocols that distribute points based on TVL daily or per hour/block. IP-Vault’s TVL earns points in the protocol’s system, and these points should be passed through to users, not retained by IP-Vault. The implementation is as follows:

  • Wand provides a JSON file

https://story-api.wandfi.io/api/third/points/:vaultaddress/:block

  • Inputs the relevant parameter to query the JSON file for the user list and their YT balances at that block. The data structure is as follows:

{ data: { address: string, balance: string }[], timestamp: number}

Abnormal state description:

400: Vault not started

404: Vault has not been created in this block yet

500: Needs to wait for server indexing data

  • Sum all YT balances to calculate the total YT Amount.

  • Calculate a user’s YT Share:

YT Share = User’s YT Balance / YT Amount

  • Determine the Total Points allocated to IP-Vault for the period.

  • Calculate points for each user:

User Points = Total Points × YT Share

  • Repeat these steps for each point issuance period, accumulating user points over time.

Example

A protocol distributes points daily at 12:00 UTC.

  • Day 1: IP-Vault is allocated 1,000 points.

  • Input the block parameter to query the JSON file, retrieving YT balances for all users, including Alice.

  • Calculate Alice’s YT Share, e.g., 1%.

  • Allocate 10 points (1,000 × 1%) to Alice for Day 1.

  • Day 2: More users buy YT, diluting Alice’s YT Share to 0.5%.

  • IP-Vault is allocated 1,200 points for Day 2.

  • Alice earns 6 points (1,200 × 0.5%) for Day 2.

  • By the end of Day 2, Alice has accumulated 16 points.

PreviousDutch-VAMMNextYield-Vault V2

Last updated 3 days ago