audits.htm - OHMVAULT 95_✕
Start OHMV.exe bonds.htm staking.htm loans.htm rewards.htm stats.htm how-to-buy.htm audits.htm @OHMVault Telegram
OHMVAULT Open ohmvault.xyz
Ethereum mainnet · $OHMV · audits & reviews

Audits

Every outside audit of the OHMVAULT contracts is published here, newest first, with each finding explained in plain words and a link to the auditor's own report.

Latest Safe · Serialized, 11 Oct 2026 Contracts verified on Etherscan Admin keys none
Read the latest report ↗ Check it yourself

External audits

Newest first. Each entry says who checked what, what kind of review it was, the verdict, and every finding with what is actually true about it.

Internal reviews

Our own testing and the pre-launch reviews run before each deploy. None of these is a published external audit, and the reviews were not published as separate reports. The full detail is in the whitepaper; each card links to its section.

OHMVAULT core Internal
39 unit & fuzz tests, 3 fork tests

Fork tests run the full launch, a stake's whole life and a router round trip against the real mainnet PoolManager, OHM and Chainlink feeds. Fuzzing covers: a bond never lowers backing per token, and a mint never leaves live backing under the mark.

Whitepaper §1 →
Private payouts (VaultBox) Internal
VaultBox 10 tests, VaultBox2 14 tests

Each also has a mainnet-fork test against the live contracts and the real RAILGUN proxy; VaultBox2's includes a fully relayed bond and a relayed shield. The whitepaper calls this code new and unaudited.

Whitepaper §15 →
Auto-stake & OHMV loans Internal
20 tests: auto-stake 7, loans 13 incl. 1,500-run fuzz

In the fuzz test lenders never lose and the books always balance through random borrowing, repaying, dumps and liquidations.

Whitepaper §16 →
Cerberus & the Kennel Internal
153 tests, two review rounds

Two pre-launch review rounds; every issue they found was fixed before deploy and has a regression test. Rehearsed on a mainnet fork, then for real on mainnet with a throwaway deployment.

Whitepaper §17 →
Kennel Pad Internal
Two pre-launch reviews

No critical or high issues found. The jackpot findings they raised were fixed before deploy, and the fixes also went into the Cerberus Kennel.

Whitepaper §18 →
Cerberus loans Internal
25 tests + 13 regression tests

Fuzzing and attacks on the price record, plus regression tests from a pre-deploy review. One risk is accepted and pinned by a test. The whitepaper calls this code new and unaudited.

Whitepaper §19 →
i

What the external audit covers. The Serialized audit above covers the token and the five contracts in its scope. The other core contracts (VaultStaker, OhmUsdOracle, VaultLens, VaultSwap) and the add-ons (private payouts, auto-stake, loans, Cerberus, Kennel Pad and Cerberus loans) have only the internal work on this page so far. Future audits of those contracts will be added here.

How to check yourself

An audit is someone else's reading. Every contract's source is verified on Etherscan, so you can read the same code and the same on-chain state.

  1. Open the contractsEvery address is in the whitepaper's registry (§14), each linked to its verified source on Etherscan. The core OHMV contracts are also listed on how-to-buy.
  2. Check who can mintOn the token's Read Contract tab, read minter: it is VaultMinter. Open it and read ratchet and bond. Simulate setMinter from any wallet: it reverts "frozen".
  3. Check the emission capThe Ratchet's verified source shows MAX_EPOCH_BPS = 200 (2% of supply per 6-hour epoch) as a constant. Constants can't be changed after deploy.
  4. Check the liquidityThe protocol positions belong to VaultLauncher and the hook. Neither has a function that removes liquidity.
  5. Re-run the scanOpen the Serialized report for the live result, or read every scanner warning, explained.