> For the complete documentation index, see [llms.txt](https://docs.tapir.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tapir.money/what-is-tapir/why-tapir-is-different.md).

# Why Tapir Is Different

## Protection funded by the underlying asset

Tapir creates DP and YB from the same deposited asset. The pool retains that asset's yield-bearing economics while the two tokens allocate losses differently: DP is the risk-protected claim and YB the first-loss claim. Whatever causes the underlying asset to lose oracle-measured value, YB supplies the collateral that increases DP's redemption rate when a qualifying depeg is recorded.

This avoids requiring a separate reserve asset for the DP/YB split. It also means protection depends on the underlying collateral remaining available: Tapir does not replace missing assets with an external guarantee.

## A market price for risk

DP and YB trade against each other. Participants choose how much exposure to hold, and supply and demand determine the exchange rate. The protection premium is reflected in the price paid or received; swap fees, slippage, pool exit fees, and network fees also affect the result.

Both sides retain exposure to the underlying asset's performance. This can make protection useful for yield-bearing assets without requiring the seller to forgo all underlying yield. Affordability and realized returns depend on the particular market.

## Settlement follows a defined formula

| Stage          | How it works                                                                                                                           |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Observation    | Authorised operators record source data and checkpoints for the configured oracle                                                      |
| Final data     | The oracle submits a high watermark and resolution price; VRP and PTRW variants add asset-specific measurements and admin backup paths |
| Waiting period | The pool enforces expiry, cooldown, and minimum price age                                                                              |
| Resolution     | Anyone can call the pool's resolution function once the conditions are satisfied; the resulting redemption rates are fixed             |
| Redemption     | Holders burn DP or YB for the calculated amount of the pool's base asset, less the applicable fee                                      |

Users do not submit individual insurance claims. The calculation is deterministic once the pool accepts its final inputs, but obtaining those inputs and operating the contracts involves authorised roles. Admins can change certain settings, pause operations, and propose an oracle replacement with a seven-day timelock.

## Defined limits, shared dependencies

DP's redemption rate is capped at twice its base rate. That provides a structural buffer for up to a 50% oracle-measured depeg before fees and premiums. YB can lose its full redemption value, and DP can still lose value in a larger decline.

Assess Tapir's contracts alongside the underlying protocol, price sources, vault accounting or redemption witness, chain, liquidity, and administrative controls. The [Quantstamp and Hashlock audits](https://docs.tapir.money/security/security-and-audits.md) and [Core V1 access-control documentation](https://github.com/tapir-protocol/public-tapir-core-v1/blob/main/docs/tapir_access_control.md) help make that review reproducible.
