Sapien Vault

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Sapien Vault is rejected under the version-1 below-materiality dossier. The live yield feed showed one SAPIEN vault on Base with about $77,000 deposited; nearly all of the displayed rate came from SAPIEN rewards rather than underlying cash flow. Sapien’s live collateral application accepts SAPIEN deposits, ages the position, and permits withdrawal after its lock; the receipt therefore represents locked exposure to the same volatile token rather than a dollar-denominated lending or savings claim. This is a protocol-specific application of a published class rule, not an unsupported claim that every contract or operator behind Sapien Vault is defective.

Kill criteria: the events that revoke this verdict
• Attributable vault capital remains above the institutional materiality threshold for 30 consecutive days
• Current contracts, privileged roles, audits, reward funding, and stressed unlock and withdrawal evidence are published and reviewed

The research file

Mechanism and applicability

Sapien’s live collateral application accepts SAPIEN deposits, ages the position, and permits withdrawal after its lock; the receipt therefore represents locked exposure to the same volatile token rather than a dollar-denominated lending or savings claim. The reviewed deployment therefore satisfies the dossier’s mechanism requirements on its own facts. The live yield feed showed one SAPIEN vault on Base with about $77,000 deposited; nearly all of the displayed rate came from SAPIEN rewards rather than underlying cash flow. A class application records enough protocol evidence to prove applicability while leaving the shared economic argument in the pinned dossier rather than pretending this is a separate flagship review.

Control and incident boundary

The official surface identifies the live Base vault and lock lifecycle but does not publish enough operator, reward-funding, audit, or loss-history evidence on that page to support an individual institutional review. Those controls and the available incident record may change operational risk, but they do not remove the property that triggers this disposition. No clean-record claim is used as proof of safety: a young deployment can have little adversarial history, and an established deployment can execute its intended economics without an exploit while still remaining unsuitable for the advised sleeve.

Exit and current measurement

A holder must wait for the position to unlock before withdrawal, and the roughly $77,000 measured pool is far smaller than a plausible advised sleeve or practice-wide allocation. Aggregate TVL is an accounting measure rather than a promise that the exact client position can be unwound at the displayed value. The disposition remains a zero allocation until a stated reopen condition is observed and a new review measures the proposed-size exit instead of inferring it from a dashboard total.

Comparison and decision

Directly holding a reviewed asset avoids the additional vault and lock, while a mature staking product would need independently reviewed reward mechanics, authorities, audits, and exit capacity. The comparison is made at the exposure level, not by brand or headline rate. The published dossier is preferable to repeating the same class judgment with slightly different wording for every venue; the protocol-specific sources retained here make the classification reproducible and the reopen criteria observable.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Sapien — live collateral vault · primary · accessed 2026-08-26
  Supports: SAPIEN deposit, Base vault, position aging, unlock-dependent withdrawal
• DefiLlama — Sapien Vault protocol data · secondary · accessed 2026-08-19
  Supports: protocol category, chain perimeter, current TVL

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.