Panoptic

Panoptic is an options protocol designed around liquidity positions in supported Uniswap pools. Its current V2 core repository describes perpetual options over Uniswap V3 and V4, with collateral vaults and a risk engine. Panoptic uses concentrated-liquidity mechanics as part of its option positions; it is not simply a label applied to every Uniswap LP position.

Key Facts

  • Option style: Perpetual positions without a standard fixed expiry, subject to the release’s rules.
  • Market base: Supported Uniswap V3 or V4 pools, depending on the deployment.
  • Premiums: Position premiums accumulate over time; prior Panoptic material used the term “streamia” for this model.
  • Collateral: The V2 repository describes ERC-4626 collateral trackers and a risk engine that checks solvency.

How Panoptic Uses Concentrated Liquidity

Uniswap concentrated-liquidity providers choose a price range in which their capital is active. Panoptic builds option positions from such liquidity chunks, allowing users to assemble long and short legs with different ranges and sizes. The analogy between an LP range and option exposure is useful, but an LP position is not legally or mechanically identical to a standardized listed option.

Panoptic’s documentation describes perpetual options whose premium accrues during the position rather than being only an upfront payment tied to a calendar expiry. The V2 contracts track premiums, collateral, and position health through the Panoptic pool, collateral trackers, and risk engine. The exact fee, collateral, exercise, and liquidation rules depend on the specific release and pool.

The V2 repository lists separate infrastructure for Uniswap V3 and V4. That matters because pool architecture and supported deployments differ by version. Do not assume that any token pair with a Uniswap pool automatically has a live Panoptic market.

Version and Risk Checks

Earlier Panoptic explanations emphasized oracle-free pricing and called ongoing premium “streamia.” The current V2 core repository describes an internal pricing and risk system with volatility safeguards. These details show why an older article should not be used as a complete description of a newer release. Check the relevant deployment, audit scope, parameters, and interface before using a pool.

Option buyers can face ongoing premium costs, while sellers and passive liquidity providers face collateral, utilization, liquidation, and market-movement risks. Concentrated liquidity can also become inactive when prices move outside a selected range. Permissionless pool creation does not mean each pool has deep liquidity or identical risk controls.

Risks and Limitations

  • Smart-contract, market, collateral, and liquidation risks remain, including for audited code. Audit scope must match the deployed release.
  • Premiums and pool exposure can change with trading activity, price movement, utilization, and protocol parameters.
  • A perpetual option has no ordinary expiry date, but that does not mean it can be held without cost or closed under all market conditions.

Social Media Sentiment

A 2025 r/quant thread about pricing perpetual options includes Panoptic’s creator explaining the idea and asking how it compares with dated options. The replies and question focus on path-dependent realized volatility, premium uncertainty, and how to compare the instrument with standard options. This is a focused technical discussion, not broad market sentiment or an independent performance review. Read the discussion.

Last updated: 2026-10

Related Terms

See Also

Sources

  • Panoptic V2 core repository — The current core repository documents the V2 architecture, supported Uniswap versions, collateral vaults, premium tracking, and risk engine.
  • Panoptic documentation — The project documentation introduces Panoptic’s options model and provides version-specific guides; check the active release before applying an older explanation.
  • OpenZeppelin Panoptic audit — This published audit describes an earlier Panoptic design; it is evidence of a specific review scope, not proof that every later release has the same audit coverage.