First-depositor / share-inflation guard

stHYPE (Valantis Labs)'s assessment for RD-F-075 — scored not_assessed on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Same constraints as F074. wstHYPE uses a custom share accounting model (stHYPE balance-based). No documentation of seed-deposit, virtual-share offset, or floor-check guard against first-depositor inflation. 6 audit engagements (most recent Obsidian Apr 2026) cover the architecture but findings not accessible (PDF binary format on GitHub). Contract source not publicly confirmed. wstHYPE proxy 0x94e8396e0869c9F2200760aF0621aFd240E1CF38 on hyperevmscan.io inaccessible via WebFetch (403). First-depositor guard status unverifiable without contract source inspection. Note: multiple audit engagements make it less likely a critical share-inflation vulnerability was missed, but this inference cannot substitute for evidence.

Sources #

URL
wstHYPE — Valantis DocsValantis docs wstHYPE — share accounting model (reads balances from stHYPE contract)retrieved 2026-05-17
URL
ValantisLabs audits repo (audit engagements list)ValantisLabs audits repo — 6 engagements listed but PDFs not machine-readableretrieved 2026-05-17
Internal
stHYPE protocol profile §8.research/protocols/staked-hype/00-profile.md §8 audit firms — 6 engagements including Obsidian Apr 2026retrieved 2026-05-17

Methodology #

Determine whether the vault has a first-depositor guard (seed deposit on deploy, virtual-share offset, or floor-check).

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol staked-hype factor RD-F-075 score not_assessed collected_at 2026-05-17 13:02:38