Markets - Napier AMM
What Are Markets in Napier?
A Napier Market consists of a trading pool and an execution system that pairs a single underlying yield-bearing asset with its Principal Token (PT).
Pools currently support both the Napier AMM and the Curve AMM, structured as PT/underlying pairs (e.g., PT-sUSDe / sUSDe
).
The execution system functions as a router that atomically handles PT, YT, and underlying actions—including issuance, redemption, swaps, and liquidity operations—within a single transaction.
Each Napier Market is curated and customized to the underlying asset and intended use case. Parameters are chosen at launch and remain fixed, except where certain adjustments are predefined as configurable.
Core Concepts
Napier AMM: A bespoke liquidity engine facilitating swaps between PT, YT and the underlying asset.
Execution System: A unified router that encapsulates all actions within and beyond Napier, designed to enhance the overall UX.
Key Features
Modularity: Built from interchangeable components, allowing flexible configurations.
Flash-Swap: Atomic flash swaps ensure that YT trades are executed against the same PT/YT pool, preventing liquidity fragmentation and improving capital efficiency.
Rehypothecation + JIT: LP capital can be deployed into ERC-4626 vaults. Dynamic AMM↔Vault rebalancing during PT/YT trades enables just-in-time (JIT) liquidity, reduces idle reserves, and delivers dual yields (vault returns + trading fees).
Concentrated Liquidity: Liquidity is concentrated into bespoke implied-APY bands to maximize efficiency and minimize price impact.
Time-Adaptive Curve: Curves evolve with time-to-maturity, aligning price with accrued yield and minimizing LP value leakage, with greater usable depth near expiry.
Curator-Set Parameters: Curators configure vault allowlists, allocation ratios, fee splits, and APY bands, enabling differentiated strategies and business models.
Uniswap v4 Compatibility: Implemented as a v4 Hook for direct router/solver integration and portable deployment across all v4 chains.
Permission-less Creation
A defining feature of Napier is permissionless market creation. Any curator may deploy an isolated market defined by a fixed set of parameters.
This design contrasts with conventional models that:
require governance or core-team approval for market listings or parameter changes, and
concentrate market control in a single entity or DAO, thereby pooling systemic risk.
In Napier, parameters are determined by each market’s curator at creation and cannot be modified thereafter (except where predefined as adjustable). The curator exercises full administrative control and receives the economic returns tied to the market’s growth.
Fees (Economics)
Similar to PTs and YTs, curators configure fee parameters based on market demand, volatility, and maturity.
Swap Fee
A fee is applied to every swap in the underlying token.
Napier charges percentage-based swap fees on the yield-receivable portion of PT whenever trades occur. This ensures that fees scale fairly across different maturities:
Longer time to maturity → higher yield receivables → higher fees (in $ terms)
Shorter time to maturity → lower yield receivables → lower fees (in $ terms)
At pool creation, the curator defines the LP vs Curator/Protocol Fee Share (
reserveFeePct
), which allocates fees between LPs and Curator/Protocol.LPs receive their portion in proportion to liquidity share.
The Curator vs Protocol split (
splitFeePct
) is subsequently adjustable by Napier Governance (currently set to 100% Curator).Curators must balance their own revenue share with LP attractiveness to ensure sustainable market growth.
Example
A $1,000 swap with a 1% Swap Fee (= $10):
With
reserveFeePct = 90/10
andsplitFeePct = 70/30
:LPs receive $9
Curator receives $0.7
Protocol receives $0.3
Roles (Governance)
Similar to PTs and YTs, roles may be delegated on a per-market basis. Curators assign roles to one or more parties.
Role Types
Curator: Market owner responsible for assigning and removing roles.
LP: Provides liquidity and receives fee allocations in proportion to share.
Fee Receiver: An individual or project designated by the curator to collect curation fees.
Protocol Pauser: An account authorized by the curator to pause a specific market in emergencies.
Developer: A role authorized to implement additional custom logic for PTs/YTs.
Governance Principle
Neither Napier Labs nor the Napier DAO holds privileged control over individual PT/YT markets. Role assignment is exclusively managed by curators.
Market Categories
Permissions evolve with DeFi and may be selectively retained to meet user demand.
Categories
Verified: Markets created by curators who complete the verification process. Displayed with a Verified badge on the Napier interface by default.
Unverified: Markets without verification. Displayed with an Unverified badge.
Unstoppable: Markets where curators renounce all permissions except Fee Receiver, rendering the market immutable. Displayed with an Unstoppable badge.
Banned: Markets deemed socially or morally inappropriate, or created with malicious intent. Displayed with a Banned badge.
Core Interactions
Buy and Sell: Trade PT/YT through Napier Markets.
Provide Liquidity: Add or remove liquidity to earn fees and rehypothecation incentives.
Build Collateralized PT Positions: Use PT as collateral in external protocols.
Rehypothecation Settings: Configure vaults and allocation ratios to unlock new strategies, such as built-in PT looping.
Claim Curation Revenue: Curators claim accrued fees, incentives, and rehypothecation revenue at any time.
Curate and Manage: Create markets, configure fees/oracles, manage roles, and administer rehypothecation and emergency actions.
Get Involved
Napier Markets are open and composable by design. Choose your path and dive deeper with the dedicated guides:
For Users → User Guide: Learn how to trade PT/YT, provide liquidity, and use PT as collateral.
For Curators → Curator Guide: Understand how to launch markets, configure parameters, and build your own onchain yield products.
For Builders → Developer Guide: Integrate Napier Markets into your protocol with SDKs and APIs.
Last updated
Was this helpful?