LINK TO POINTS TRACKING SCRIPT: https://github.com/Pendle-Finance-Periphery/pendle-generic-balance-fetcher/tree/main

<aside> 💡

In the future if you would like to have your pool’s LP as collateral, you must use this script for your points tracking as it will help us to autoforward LP rewards to these users accurately

</aside>

Things that the script has taken into account:

• Pendle’s treasury for YT fees and post-maturity PT fees

1. Mechanism on Pendle

• Tracking points on Pendle is slightly more complicated since you will need to take into account YT holders and LP holders for points.
• Pendle consists of 3 main components - PT, YT, LP:
  • Principle Token (PT) - users receive a fixed yield in exchange for foregoing all floating yields and points
  • Yield Token (YT) - users receive underlying floating yields and points. For example, holding 10 YT-eETH will give you 200,000 (20,000 a day * 10 eETH) ETHFI points a day vs 20,000 ETHFI points a day if you hold 1 eETH.
  • Liquidity Providers (LP) - users receives additional yields from swap fees and Pendle incentives while retaining some points exposure. Since LP is made up of SY + PT, users will also receive some points exposure from the SY proportion in the LP.

<aside> 💡

TLDR: PT forgoes all points, YT and LP earns points. To learn more about the mechanism of Pendle, refer to this page. Pools will stop earning points upon maturity, so YT and LP users will not earn additional points after maturity of a pool.

</aside>

2. Methodology of the Script

• This script enables you to fetch YT and LP balances (in SY terms) across blocks, which you can allocate the points accrued from our SY contract proportionally to these users based on their balances.
• To do so:
  • In the configuration script below, Pendle will provide the relevant information in the table below to be updated in the script. The addresses need to be in lowercase.
    • Link to update information in the script
  • To find the relevant contract addresses for the script:

    • Head to the market page of the relevant pool

    • Click on Specs

      

    • Copy and paste the LP, YT, and SY addresses into the script accordingly

      

<aside> 💡

You can test out the script by using any of the pools available on Pendle.

</aside>

• Protocols will then query the holdings of the underlying token in our SY contract then allocate the points based on the balance queried from the script.
• In our script, we will also allocate 5% of points earned from YT to our treasury wallet, which may be distributed to vePENDLE holders in the future. There are no additional actions required from your end for this, since it’s already available in the script.

<aside> 💡

5% of the points earned from YT to our treasury wallet will be taken from existing users. So if a user was supposed to earn 100 points, 95 points will be allocated to them and 5 points will be allocated to treasury.

</aside>

3. How to Fill Up the Script? Using Ethena USDe 31July2025 as Example:

1. Go to https://github.com/Pendle-Finance-Periphery/pendle-generic-balance-fetcher/tree/main and fork the code.

2. In the fork, configure the contract addresses in https://github.com/Pendle-Finance-Periphery/pendle-generic-balance-fetcher/blob/main/src/configuration.ts

   

3. You need to update the SY, YT and LP addresses. To find the relevant contract addresses, go to your pool’s market page → click on specs which is next to the pool’s name. You could then find the relevant addresses from the table.

   

4. Given the information from USDe 31Jul2025, Update the following information from Step 2 to:

   import { CHAINS, PoolConfiguration } from './types';
   
   export const CHAIN = CHAINS.ETHEREUM;
   
   export const POOL_INFO: PoolConfiguration = {
     SY: '0xb47cbf6697a6518222c7af4098a43aefe2739c8c',
     YT: '0x733ee9ba88f16023146ebc965b7a1da18a322464',
     LPs: [
       {
         address: '0x9df192d13d61609d1852461c4850595e1f56e714',
         deployedBlock: 21920466
       }