Napier
- Name: Napier
- URL: https://napier.finance/
- Category: yield-tokenization infrastructure / curator-owned yield-market framework / open-curation fixed-rate protocol
- Tags: ethereum-ecosystem
- Summary: Napier is PT/YT infrastructure with market-level curation. The useful distinction is not the token split; it is that curators own fee policy, allowlists, role assignments, and rehypothecation choices per market instead of waiting on one protocol-global listing desk.
- What it does:
- Splits yield-bearing assets into PTs that redeem principal and YTs that capture the yield stream through maturity
- Supports fixed-yield and variable-yield positioning through a Napier AMM and related execution system
- Lets third parties create isolated yield markets with curator-set parameters instead of routing all listings through a single protocol team
- Supports rehypothecation of LP capital into ERC-4626 vaults and time-adaptive concentrated-liquidity design around implied APY bands
- Exposes per-market roles, fee receivers, pausers, and customization hooks so markets can act like separately administered product domains
- Markets itself as infrastructure for curator-built and institution-facing yield products with optional policy layers like KYC and whitelists
- Key claims:
- The docs say Napier tokenizes yield-bearing assets into PT and YT claims, where PT redeems 1:1 for principal at maturity and YT captures accrued yield rights
- The protocol docs say open curation means any curator can deploy an isolated market, own it, and receive the economic returns from that market’s growth
- The Napier AMM docs say curators set vault allowlists, allocation ratios, fee splits, and APY bands, making market design itself a durable control surface
- The same docs say neither Napier Labs nor the Napier DAO holds privileged control over individual PT/YT markets, and that role assignment is managed by curators on a per-market basis
- The main Napier docs explicitly frame the project as an answer to Pendle’s more centralized market model and claim market-level policy control is necessary for institutional adoption
- The curation docs say curators are expected to manage parameters, thresholds, pauses, migrations, and product packaging across vertically integrated yield products, which makes Napier useful as a comparison case for the broader curator-control trend in DeFi
- There is an important implementation nuance: Napier’s docs describe permissionless or open curation at the mechanism level, but the current curator onboarding flow says account verification is required before creating a market through the supported path
Internal linkages
- Best market-center comparison: pendle.
- Best adapter-policy contrast: sense-protocol.
Control surface
-
Practical authority sits with whoever controls market curation: vault allowlists, fee policy, role assignment, rehypothecation choices, pauses, and migrations.
-
So the note should stay on market governance and product packaging, not dissolve into generic
tokenized yieldlanguage. -
Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest current primary-source chain is
../whitepapers/napier-primary-sources-2026-05-08.mdplus the official docs and public repository. -
Sources:
- https://napier.finance/
- https://docs.napier.finance/
- https://docs.napier.finance/learn/napier
- https://docs.napier.finance/learn/protocols
- https://docs.napier.finance/learn/protocols/markets-napier-amm
- https://docs.napier.finance/curate/napier-curation
- https://docs.napier.finance/npr/governance
- https://github.com/napierfi/napier-v2-public
- https://raw.githubusercontent.com/napierfi/napier-v2-public/main/README.md
-
Last reviewed: 2026-05-08 UTC