The PT/YT Interface Standard, anchored by EIP-5095 and extended by Pendle's mint, burn, and yield-bearing asset reference functions, defines the minimal on-chain contract surface that every Principal Token and Yield Token must expose. Without this standard, each new Pendle market deployment would present a unique interface, forcing every downstream integrator—wallets, DEX aggregators, portfolio trackers, lending protocols, and centralized exchanges—to write bespoke parsing logic for each asset and maturity. The standard collapses that complexity into a predictable set of redeem, mint, burn, and metadata functions that work identically across all PT/YT pairs, regardless of the underlying yield-bearing asset or the chain on which they are deployed.
PT and YT Token Interface Standard (EIP-5095 and Pendle Extensions)
Why the PT/YT Interface Standard Matters
A canonical token interface is the prerequisite for composable yield markets, enabling wallets, exchanges, and protocols to integrate Principal Tokens and Yield Tokens without custom logic for every maturity date.
Operationally, the standard governs how tokens behave at maturity. EIP-5095 specifies the redeem flow that allows PT holders to claim the underlying asset after maturity, while Pendle's extensions handle pre-maturity minting of PT/YT from the Standardized Yield (SY) token and the burning of PT/YT to exit positions. Integrators who fail to implement these interfaces correctly risk settlement failures: a wallet that does not recognize a matured PT may leave a user's funds unclaimed indefinitely; an exchange that does not halt trading before maturity may face reconciliation errors when the token's accounting basis changes. The standard also defines how to query the underlying yield-bearing asset reference, which is critical for oracles pricing PT/YT and for risk systems that need to trace exposure through the token stack.
For teams building on Pendle, the interface standard is the integration surface that Chainscore Labs reviews for correctness. Common failure modes include mishandling the redeem return value, mispricing YT based on stale exchange-rate queries, or failing to account for reward accrual during the mint-burn lifecycle. Chainscore can audit integration code against the canonical interface specification, verify that redemption flows handle edge cases around maturity boundaries, and assess whether oracle implementations correctly derive implied yields from AMM state rather than relying on spot prices that may be manipulated.
Interface Standard at a Glance
Operational impact of the PT/YT interface standard on integrators, wallets, exchanges, and protocols.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
EIP-5095 Redemption | Standardized redeem() interface for principal tokens at maturity | Wallet integrators, custody providers, DeFi protocols holding PT | Audit redemption flow against EIP-5095 spec; verify post-maturity state transitions |
Mint/Burn Extensions | Pendle-specific mint() and burn() functions for PT/YT creation and destruction | Yield aggregators, structured products, arbitrage bots | Review mint/burn access control; test with expired and near-maturity markets |
Yield-Bearing Asset Reference | On-chain reference to underlying SY token and its exchange rate | Oracles, lending protocols, portfolio trackers | Validate exchange-rate precision; handle reward-accrual edge cases in pricing logic |
Metadata Schema | Name, symbol, maturity date, and underlying asset metadata format | Block explorers, wallets, tax tools, analytics dashboards | Parse maturity date correctly; handle duplicate or expired market metadata without crashes |
Maturity Lifecycle | Tokens transition from active trading to redemption-only state at maturity | Centralized exchanges, custodians, institutional on-ramps | Implement delisting procedures before maturity; reconcile balances post-redemption |
Cross-Chain Representation | PT/YT deployed across multiple EVM chains with canonical market recognition | Bridge operators, multi-chain aggregators, governance participants | Verify canonical market addresses per chain; prevent duplicate-market liquidity fragmentation |
LP Token Interface | Fungible LP token representing dual PT-and-SY position with fee accrual | Yield aggregators, vaults, structured products | Test add/remove liquidity flows; verify fee-accounting correctness under extreme market conditions |
Interface Surface: EIP-5095 Core and Pendle Extensions
The canonical interface boundary for Principal Tokens (PT) and Yield Tokens (YT), defining the EIP-5095 redeem standard and Pendle's mint, burn, and yield-bearing asset reference extensions.
The PT and YT token interface standard defines the exact function signatures, events, and state-mutating methods that any smart contract, wallet, or off-chain service must call to interact with Pendle's yield-tokenized assets. At its core, the standard mandates compliance with EIP-5095, which specifies a redeem function enabling Principal Tokens to be converted to the underlying asset after maturity. Pendle extends this base with proprietary interfaces for mint (creating PT/YT pairs from the Standardized Yield token), burn (removing PT/YT to reclaim the underlying), and a getYT reference that links a PT to its corresponding Yield Token. This interface surface is the single point of integration for every protocol composing with Pendle's yield derivatives.
For integrators, the critical operational distinction is between the pre-maturity and post-maturity state of these functions. Before maturity, redeem on a PT will revert, and the value of PT and YT is determined by AMM swap logic. After maturity, the PT's redeem function becomes active, returning a fixed amount of the underlying asset, while the YT's value goes to zero and its burn function may revert or return dust. Wallets and exchanges that do not model this state transition will display incorrect balances, fail to process redemptions, or trap user funds in expired positions. The getYT reference is a Pendle-specific extension that allows a PT holder to programmatically discover the associated YT address, a necessary step for any yield-stripping or auto-compounding strategy.
A formal audit of integration code against this interface surface is the most effective way to prevent maturity-boundary bugs, redemption failures, and composability breaks. Chainscore Labs reviews PT/YT integration logic for correct handling of the pre/post-maturity state machine, validates that redeem calls are properly gated on block timestamp vs. maturity date, and ensures that off-chain indexers correctly interpret the Mint, Burn, and Redeem events. For teams building wallets, custodians, or lending protocols that accept PT as collateral, this review is the foundational step before any mainnet deployment.
Who Is Affected by This Standard
Wallet and Custody Integration
Wallets and custodians must implement the full PT/YT interface to display balances, enable transfers, and handle the critical post-maturity redemption flow. The EIP-5095 redeem function is the primary entry point for converting matured PT to the underlying asset, and failure to surface this correctly leads to stuck user funds.
Key Actions:
- Implement
balanceOf,transfer, andredeemwith correct maturity-gating logic. - Parse the Pendle metadata extension to display maturity dates, underlying asset symbols, and yield-bearing token references in the UI.
- Build explicit post-maturity UX flows that prompt users to redeem PT and claim YT yield before markets expire.
- Test against both active and expired Pendle markets to ensure state transitions are handled cleanly.
Chainscore can audit wallet redemption flows and help teams design maturity-notification UX that prevents unclaimed position risks.
Implementation Impact by System
The EIP-5095 and Pendle-specific extensions impose distinct technical requirements across wallets, exchanges, custody providers, and DeFi protocols. Each system type must handle the maturity lifecycle, redemption interface, and metadata schema correctly to avoid integration failures.
Wallet Integration
Wallets must implement the EIP-5095 redeem() interface and track maturity dates to trigger post-expiry redemption prompts. The Pendle extension requires parsing the underlying yield-bearing asset reference so users can see what asset they will receive. Failure to surface redemption windows leads to unclaimed principal. Chainscore can audit wallet redemption flows and maturity-notification UX against the canonical interface specification.
Centralized Exchange Listing
Exchanges listing PT or YT tokens must implement trading cessation before maturity, automatic redemption settlement, and delisting procedures. The EIP-5095 maturity and redeem() functions define the exact cutoff logic. Exchanges that treat PT as a perpetual token risk settling expired positions incorrectly. Chainscore can review listing and delisting procedures for maturity-related settlement risks and reconciliation errors.
Custody and Institutional Operations
Custodians must reconcile PT/YT balances against on-chain state, handle automatic redemption at maturity, and ensure post-maturity positions are not reported as active holdings. The Pendle metadata schema provides the canonical maturity date and underlying asset reference needed for accurate reporting. Chainscore can assess custody integration code for correct redemption-flow handling and balance-reconciliation logic.
DeFi Protocol Composability
Lending protocols accepting PT as collateral must integrate the EIP-5095 redeem() function to handle maturity-triggered unwinding. Yield aggregators and structured products composing with YT must account for the token's decaying value and eventual expiration. Incorrect handling of the maturity boundary can cause bad debt or locked funds. Chainscore can review protocol integration code for maturity-boundary bugs and redemption-flow correctness.
Indexers and Data Providers
Subgraphs, analytics dashboards, and portfolio trackers must parse the Pendle metadata schema to display PT/YT positions with correct maturity dates, underlying asset references, and post-expiry status. Indexers that fail to handle the Redeem event or expired market states will show stale balances. Chainscore can audit subgraph implementations for event-handling completeness and help teams reconcile on-chain state with indexed data.
Bridge and Cross-Chain Infrastructure
Bridge protocols wrapping PT or YT tokens must preserve the maturity date and underlying asset reference across chains. A bridged PT that loses its maturity metadata becomes unreedemable on the destination chain. Reward accrual during the bridging period must also be accounted for. Chainscore can review bridge-wrapper implementations for maturity-boundary bugs and reward-leakage risks in cross-chain PT/YT transfers.
Integration Risk Matrix
Operational and technical risks for systems integrating the PT and YT token interface standard, covering redemption mechanics, metadata handling, and composability with DeFi protocols.
| Area | Failure Mode | Severity | Affected Systems | Mitigation |
|---|---|---|---|---|
Redemption Flow | Integrator calls redeem() after maturity but fails to handle the underlying asset transfer, leaving funds locked in the contract. | High | Wallets, Custodians, Yield Aggregators | Audit redemption transaction lifecycle; simulate post-maturity state in testnets before mainnet deployment. |
Metadata Parsing | Off-chain indexer or wallet parses token name/symbol without maturity date, displaying an expired token as if it is still active. | Medium | Wallets, Portfolio Trackers, Tax Tools | Implement the full metadata schema including maturity timestamp; add a visual warning for tokens past their maturity date. |
Composability | A lending protocol accepts PT as collateral but uses a spot price oracle that does not converge to face value at maturity, leading to mispriced liquidations. | High | Lending Protocols, Risk Managers | Use a TWAP oracle or a custom Pendle oracle that accounts for the deterministic convergence of PT price to underlying value at maturity. |
Bridge Integration | A bridge locks a PT on the source chain without accounting for its maturity date; the token matures during the bridging period, making the wrapped asset on the destination chain unredeemable. | Critical | Bridge Protocols (Wormhole, LayerZero) | Enforce a minimum time-to-maturity for bridgeable PTs; implement a maturity-aware unwrap function on the destination chain. |
Exchange Listing | A centralized exchange lists a YT token and allows trading after the underlying asset has matured, when the YT value is zero. | High | Centralized Exchanges | Automate trading halts and delisting procedures based on the on-chain maturity timestamp; verify the token's current phase before listing. |
Custody Reconciliation | A custodian's internal ledger does not account for the automatic conversion of PT to underlying at maturity, causing a balance discrepancy. | Medium | Custodians, Institutional On-ramps | Model the PT lifecycle in the internal ledger; schedule a reconciliation job to run at the maturity block timestamp. |
Governance Upgrade | A PIP upgrades the PT/YT interface, adding a new mandatory function. Integrators who do not upgrade their interface adapter experience broken transactions. | High | All Integrators | Monitor PIPs in 'Last Call' status; Chainscore can provide an impact assessment and integration review for new interface versions. |
Event Indexing | A subgraph or data pipeline fails to index the Redeem event, causing off-chain analytics to miss matured positions and under-report user balances. | Medium | Data Providers, Analytics Dashboards | Audit subgraph handlers against the canonical event signatures; implement a reconciliation process that compares indexed data with on-chain state. |
Integration Readiness Checklist
Checklist for wallet, exchange, and custody teams integrating Principal Tokens (PT) and Yield Tokens (YT) based on EIP-5095 and Pendle's extensions. Each item identifies a critical integration point, explains the operational risk, and specifies the signal that confirms readiness.
What to check: Verify that your integration correctly calls the redeem(uint256 shares, address receiver, address owner) function and handles the returned uint256 assets value.
Why it matters: This is the canonical redemption path for PT at maturity. Incorrect implementation can result in users being unable to claim their underlying assets, or assets being sent to the wrong address. The owner parameter allows redemption on behalf of another address, which is critical for smart contract wallets and vaults.
Readiness signal: Successful integration test on a forked mainnet environment where a PT at maturity is redeemed and the correct amount of the underlying asset is received by the specified receiver from the owner's balance.
Canonical Resources
Primary references for teams implementing or reviewing PT/YT token compatibility under EIP-5095 and Pendle-specific extensions. Use these sources to verify redeem semantics, maturity handling, contract interfaces, and integration assumptions before listing, custody, wallet display, or protocol composition.
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos
Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
Frequently Asked Questions
Common questions from integrators, wallet teams, and exchange operators implementing the PT/YT token interface standard.
A wallet must implement the standard ERC-20 balanceOf, decimals, name, and symbol functions. For PT tokens, the wallet must also call EIP-5095's maturity() and redeem() functions to determine if the token has expired and to display the underlying asset claim. For YT tokens, the wallet must call PendleYT.sy() to identify the underlying Standardized Yield token and PendleYT.pyIndexStored() to display the current claim on yield. Without these calls, a wallet will show a stale balance after maturity or fail to reflect accrued yield.
Why it matters: Users holding expired PT tokens see a balance but cannot claim their underlying unless the wallet prompts redemption. YT holders may not see their yield accrual, leading to support issues.
Confirmation signal: The wallet displays a "Redeem" action for PT tokens past maturity and shows the current yield-bearing asset equivalent for YT tokens.
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.