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.

defiyieldpendlept-ytstructured-financefixed-rateregulatory-gap
Filter by shape:
|
D5 · DEFIPendle yield tokenization·5 stations(1 compliance, 4 infra)·pendle
S1INTENTS2S3DISCOVERYS4NEGOTIATIONS5S6AUTHORIZATIONS7FACILITATIONS801Smart Wallet02Yield Split03Swap04State Update05Settlement
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the Pendle yield tokenization path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
5 stations across 5 of 8 segments. 1 are compliance checkpoints, 4 are infrastructure.
4 code-enforced1 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET

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

"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.

Counterparty
Self (user holds keys, no KYC counterparty)
Latency
Instant · no on-chain tx yet
Finality
N/A — deposit not yet initiated
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTSETTLEMENT
L3 EXECUTIONSETTLEMENT
L2 CONSENSUSSETTLEMENT
◆ Enforcement Line — code-enforced at this layer

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

"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 Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTAMM
L3 EXECUTIONAMM
◆ Enforcement Line — code-enforced at this layer

Step 3 · PT/YT Trading on Pendle AMMCode-Enforced

"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 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONMATURITY
L2 CONSENSUSMATURITY
◆ Enforcement Line — code-enforced at this layer

Step 4 · Maturity Monitoring & YT ExpirationCode-EnforcedINGESTDETECTALERT

"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.

Counterparty
Pendle Protocol (time-decay oracle)
Latency
N/A — autonomous countdown
Finality
Maturity triggers redemption automatically
Vendors
Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONSETTLEMENT
L4 ACCOUNTSETTLEMENT
◆ Enforcement Line — code-enforced at this layer

Step 5 · Redemption & FinalityCode-Enforced

"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.

Counterparty
Self (user self-custodied, redemption code-enforced)
Latency
1–15 seconds (Ethereum L1)
Finality
Finalized on block confirmation
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

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.

Other DeFi Protocols Paths

SETTLEMENT CHAINS