For the complete documentation index, see llms.txt. This page is also available as Markdown.

How the vault works

Hypurr Vault holds Hypurr NFTs and WHYPE reserves. rHYPURR is an ERC-20 token representing a share of those assets. The design is inspired by ERC-4626, with queued deposits and redemptions rather than instant settlement.

What a share is worth

Net asset value, or NAV, is the estimated value of the vault's assets. NAV per share divides that value by the outstanding rHYPURR supply.

NAV per share = total vault asset value / outstanding shares

NFTs use a collection-level estimate based on recorded sales. NAV is not a guaranteed sale price for the NFTs, and it can rise or fall. Read the valuation method.

From request to settlement

  1. You submit a deposit or redemption. The vault holds your deposit assets or redemption shares and tags the request with the current epoch.

  2. The oracle submits a signed NAV report. The contract saves that price for the epoch and advances to the next one.

  3. The keeper processes eligible requests using their saved epoch prices. Deposits mint shares to receivers. Redemptions burn shares and pay WHYPE, subject to liquidity.

An epoch is a numbered period between NAV reports. Requests in the same epoch use the same NAV per share. A request does not lock the price displayed when you submit it.

Each queue follows first in, first out order. A partially paid redemption stays at the head of its queue until completed. Later redemptions cannot skip it.

Fees and share amounts

For a deposit, the vault deducts the deposit fee before calculating shares:

Shares received = net deposit / epoch NAV per share

For a redemption, it calculates the gross payout and then deducts the redemption fee:

For example, a net deposit of 120 WHYPE at 1.2 WHYPE per share produces 100 rHYPURR, before integer rounding. Redeeming 100 shares at 1.5 WHYPE per share produces 150 WHYPE before the redemption fee.

See fees and cancellation rules.

Who does what?

Role
Responsibility

Admin

Configures limits and permissions, and can pause the vault

Oracle and keeper

Calculates and publishes NAV, then processes queues

Vault manager

Holds NFTs, buys and sells them, and manages strategy liquidity

Treasury

Receives protocol fees

The bot observes trading activity; the treasury manager executes NFT trades through the managed wallet. An automated NAV update does not mean the bot chooses or executes trades.

Limits and safeguards

The contract checks signed reports, NAV age, report expiry, and per-report drift limits. It also enforces deposit caps, minimum request sizes, and queue order. Admins can pause operations.

These controls constrain operation. They do not guarantee a profit, immediate redemptions, or protection from every exploit. Read about security and risks.

Last updated