Reentrancy guard on external-calling functions

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

Evidence summary #

No static analysis output available. Reentrancy guard coverage cannot be confirmed without tool run. OverseerV1 interacts with HyperCore via L1 read/write addresses — cross-layer call surface is a potential reentrancy concern.

Sources #

URL
OverseerV1 implementation — verified source, needs tool runhyperevmscan.io/address/0xaC43e7a1467bf6a4db24bf1f121fb59be6c9f831#coderetrieved 2026-05-17

Methodology #

Determine whether all state-mutating functions that perform external calls carry `nonReentrant` or an equivalent reentrancy guard.

See the full factor methodology and distribution across all protocols →

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