DeFi Protocols

Pendle Yield Tokenization (PT/YT)

Split yield-bearing assets into principal and yield tokens. Structured finance on-chain without the regulatory framework.

Vendors

Pendle Finance

Compliance Center

Code-enforced maturity at Authorization. Regulatory gap — replicates tranching.

D5 — Pendle yield tokenization · Rails: defi · Protocols: Pendle V2, Pendle AMM · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
D5 — PENDLE YIELD TOKENIZATIONYOU ARE HERE● User WalletPOLICY Yield Tokenizat…CODE◆ PT/YT Trading o…CODE Maturity Monito…CODE● Redemption & Fi…CODEIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3STEP 4STEP 5ETHEREUMVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 1 · User Wallet (Yield-Bearing Asset)Policy-EnforcedBlockchain-Native

The investor's custody account — holds yield-bearing asset (stETH, USDY, eETH, GLP, LST), no identity check, permissionless deposit.

User self-custody wallet on Ethereum (or Arbitrum) holds yield-bearing collateral (stETH, Lido LST, USDY, eETH, GLP, or other interest-accruing token) and prepares to deposit into Pendle for yield tokenization. The protocol is permissionless — no KYC, no whitelist, no identity layer. L4 Account (token balance, approval) and L5 Application (wallet UX, Pendle interface) are lit. HONESTY MARKER: D1 (Identity) is required by GENIUS Act and BSA, but Pendle Protocol enforcement is absent. The protocol cannot identify users, cannot freeze addresses. Compliance is structurally absent at the protocol level.

⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
Self (user holds keys, no KYC counterparty)
Latency
Instant · no on-chain tx yet
Finality
N/A — deposit not yet initiated
Vendors
MetaMask / Fireblocks · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · Yield Tokenization (PT/YT Split)Code-EnforcedBlockchain-Native

Bond tranching desk splits a bond into principal strip and interest strip — except permissionless, instant, and code-enforced.

User deposits yield-bearing asset into Pendle smart contract. The protocol splits the deposit into two synthetic tokens: PT (Principal Token) and YT (Yield Token). PT is a zero-coupon bond — it accrues no interest but matures to the underlying asset value (1 PT = 1 unit of underlying at maturity). YT is the floating-rate yield stream — it represents all future yield accruing between deposit and maturity. This split is instant and code-enforced. HONESTY MARKER: This replicates structured finance tranching (CDO waterfall, bond stripping, interest-only / principal-only strips) without any regulatory framework. In TradFi, bond tranching requires SEC registration, prospectus, suitability checks, redemption statements. On Pendle, anyone can tranche any asset permissionlessly. The maturity date is hardcoded into each PT/YT pair — it is immutable and code-enforced.

Counterparty
Pendle Protocol (algorithmic tranching, no legal entity)
Latency
1–15 seconds (Ethereum L1)
Finality
Finalized on block confirmation
Vendors
Ethereum PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2 · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 3 · PT/YT Trading on Pendle AMMCode-EnforcedBlockchain-Native

Bond trading on secondary market — PT and YT trade independently, each with market-determined price.

After split, PT and YT trade on Pendle's custom AMM. The AMM is optimized for time-decaying assets: YT loses value asymptotically as maturity approaches, converging to zero. PT converges to the underlying asset value. Users can buy PT for fixed-yield strategies (PT price at purchase determines effective yield to maturity) or buy YT for leveraged yield exposure. Sellers of PT provide leverage to buyers. YT sellers are short yield — if actual yield outpaces the priced-in yield, YT holders profit; if yield underperforms, they lose. This is permissionless trading with no restrictions on counterparties. D13 (Market Integrity) is code-enforced: price discovery is algorithm-driven, oracle-checked. D16 (Programmable Compliance) is absent — Pendle cannot restrict traders, cannot enforce country checks.

Counterparty
Pendle liquidity pools + anonymous counterparties
Latency
1–15 seconds (Ethereum L1)
Finality
Finalized on block confirmation
Vendors
Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2 · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 4 · Maturity Monitoring & YT ExpirationCode-EnforcedBlockchain-Native

Bond maturity date — as date approaches, principal and yield accrue forward. Automated redemption on maturity.

As the maturity date approaches (hardcoded in the PT/YT pair), market prices converge to their maturity values: PT → 1 unit of underlying asset, YT → 0 (since all yield has been distributed to holders). At maturity, YT expires worthless — no further yield accrues, YT cannot be redeemed. PT remains redeemable. This is all code-enforced: no human intervention, no governance override. The maturity date is immutable and non-negotiable. HONESTY MARKER: This replicates the risk profile of structured finance tranching and bond maturity. In TradFi, maturity is governed by indenture law and backed by trustee oversight. On Pendle, maturity is code-enforced but has no legal backup if the underlying protocol fails or the yield assumption breaks.

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
Counterparty
Pendle Protocol (time-decay oracle)
Latency
N/A — autonomous countdown
Finality
Maturity triggers redemption automatically
Vendors
Ethereum PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 5 · Redemption & FinalityCode-EnforcedBlockchain-Native

Bond redemption. PT holders redeem for principal; YT holders receive zero (yield already claimed).

At maturity, PT holders redeem their tokens for the underlying asset 1:1. If user bought PT for stETH at maturity date T, redemption returns exactly 1 stETH (minus any accrued fees). YT holders have already collected yield; YT expires worthless and cannot be redeemed. Redemption is permissionless and code-enforced — no discretion, no gate, no approval required. Recordkeeping is the on-chain transaction receipt and transfer events (D11); no traditional AML alert or CTR filing. HONESTY MARKER: Pendle has grown to $5B+ TVL at peak, with institutional interest in fixed-rate stablecoin yields (e.g., Pendle PT of USDY for treasury strategies). However, no entity has custody of funds during maturity — users are self-custodied throughout. If the underlying asset (e.g., stETH) faces a liquidation spiral or protocol risk, Pendle has no recovery mechanism. The maturity guarantee is only as strong as the underlying protocol.

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
Counterparty
Self (user self-custodied, redemption code-enforced)
Latency
1–15 seconds (Ethereum L1)
Finality
Finalized on block confirmation
Vendors
EOA / ERC-4337 · MetaMask / Fireblocks

Resolved 5 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.

TOOL 01 · 6 DID METHODS COMPARED

DID Method Resolver

Benchmark resolution across did:web, did:hedera, did:key, did:ion, did:pkh, and did:ethr with W3C DID Core compliance scoring.