Skip to main content
Pharos

A protocol claim on positions, not direct cash ownership

Bridge, vault and module liabilities retain local accounting, custody and recovery risk even when the underlying asset is a stablecoin.

Protocol-position tokens rely on assets held through bridge managers, vault receipts or issuance modules. Their holder claim comes from the exact deployed code and current bindings. They are not necessarily borrower CDPs, direct fund shares or fiat cash claims, and not every member is bridged.

The underlying stablecoin's reserve quality remains upstream. The local position still needs its own liability reconciliation, custody continuity, allocation and default procedure. A high-quality parent cannot erase those local risks, and a receipt and its underlying assets must not both be counted as backing.

An exact deployed bridge or module issues STBL; managers hold underlying vault or protocol positions; holders withdraw through the operational path, while local custody, liability conservation, encumbrance and default recovery remain distinct from the underlying stablecoin's reserves.01Bridge / moduleexact deployed issuance02Managed positionsreceipts counted once03STBL liabilityprotocol withdrawal claim

How it works

The flow, step by step

  1. Deposit or module issuance

    A bridge deposit or an enabled protocol module creates a token liability. Identity review binds the holder claim to the exact token, manager, provider and module deployment.

  2. Assets through protocol positions

    Managers and vaults hold or deploy assets into underlying positions. A complete inventory must distinguish external assets, receipts, own-token lending, LP exposure and residual modules without counting circular claims as new backing.

  3. Withdraw through the protocol

    Holders use the code-defined withdrawal or swap path. Pending withdrawals, liquidity limits, manager continuity and stress recovery remain separate from an internal conversion rate or a nominal parity quote.

Tracked examples

Tracked coins using this design

Where the design fails

Known failure modes

Circular or residual exposure
Own-token lending and LP claims need a complete assets-and-liabilities valuation before their economic value is established. Unpriced residuals remain charged as bounded conservation and allocation facts, never assumed zero.
Position custody and control
A known manager address does not prove continuity, independent governance or insolvency priority. Module or bridge upgrades can change the operational claim, and mint authority remains a separate Control question.
Withdrawal and recovery mismatch
An ERC-4626 conversion, bridge withdrawal interface or open swap module does not establish executable capacity at an arbitrary notional or funded default recovery.

Variations

Sub-flavors within the archetype

Bridge-position liabilities
A bridged token's liability lives on a different layer from the underlying position. The bridge, position custodian and outstanding withdrawal book each need exact scope.
Mixed issuance modules
External swap modules can coexist with lending and LP modules. Tiny external positions do not certify the full book, stablecoin parity or the value of endogenous claims.

What to watch on Pharos

Signals that matter most

  1. 01

    Exact current manager, vault, bridge and module bindings.

  2. 02

    Liability conservation and encumbrance/allocation unknowns remain visible and priced.

  3. 03

    Underlying reserve inheritance only prices the reserve group, not local mechanism components.

  4. 04

    Operational redemption evidence is not legal default priority or measured exit depth.

  5. 05

    Internal pricing and unrestricted mint controls remain independent risks.

Tracked universe

42 tracked stablecoins in this archetype

Continue reading