> For the complete documentation index, see [llms.txt](https://docs.rip.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rip.xyz/help/security.md).

# Security and risks

Hypurr Vault depends on contracts, signed NAV reports, a keeper, and a manager wallet. Each has permissions and failure modes to understand before depositing.

## Contract audit

Three Sigma audited the rHYPURR vault contract. [Read the audit report](https://rip.xyz/audits/hypurrvault/rHYPURR.pdf) for its scope, findings, and reviewed version.

That report covers the code identified in the report. It does not establish that every Rip contract, later change, marketplace contract, or deployment has been audited. An audit can miss bugs.

## Who has control?

| Role              | What it can do                                                         |
| ----------------- | ---------------------------------------------------------------------- |
| Admin             | Change configurable limits and permissions, and pause operations       |
| Oracle and keeper | Publish signed NAV reports and process request queues                  |
| Vault manager     | Hold portfolio assets, execute NFT trades, and move strategy liquidity |
| Treasury          | Receive protocol fees                                                  |

The manager uses an MPC wallet, which splits signing key material across participants. Wallet policies and operator access still matter. MPC alone does not prove independent approval of every trade or eliminate custody risk.

rHYPURR tokens are held by users, but the underlying NFTs are held by the manager. Share ownership does not remove reliance on the manager or prevent every form of misuse.

## Contract checks

The vault verifies authorized report signatures, report expiry, epoch versions, and NAV drift limits. Stale NAV blocks new deposit and redemption requests. Deposit caps, minimum request amounts, and first in, first out queues constrain processing.

Admins can pause the vault. A pause can interrupt requests, processing, and cancellations; it does not freeze the market value of the assets.

## Main risks

* NFT prices can fall. Holding several Hypurrs still leaves exposure to one collection.
* NAV is an estimate. Sparse or manipulated sales data can produce an estimate that differs from achievable sale prices.
* Limited WHYPE can delay or partially fulfill redemptions. A ProjectX swap also depends on pool liquidity and can trade away from NAV.
* Contract bugs, compromised permissions, custody failures, and operator mistakes can cause losses.
* Oracle or keeper outages can delay updates and settlement.

There is no guaranteed return or insurance against losses.

## Before signing

Check the website, network, [contract address](https://docs.rip.xyz/hypurr-vault/contract-addresses.md), amount, approval, and recipient. Keep HYPE for gas. Never share a recovery phrase or private key. Start with a small transaction if you are unfamiliar with the flow.

## Report a vulnerability

Email <code class="expression">space.vars.rip\_security\_email</code> with the affected component, reproduction steps, and likely impact. Keep exploit details private while the issue is investigated. For account or app questions, use <code class="expression">space.vars.rip\_support\_email</code>.
