Risks

Risks

Audit findings, protocol risks, and user entry scenarios.

Audit findings
11
Medium severity
3
Critical or High
0
Fixed
4 / 11
Audit, Zellic 2026-01

11 audit findings

Every finding from the Zellic report (Jan 19, 2026). No Critical or High severity issues. 3 Medium, 2 Low, and 6 Informational. Click a row to expand.

Description

redeem, redeemEarly, and getBondInfo used the global terms.vestingTerm, so an owner change could retroactively shift maturity and early-exit settlement for existing bonds. Switched to per-bond vesting.

Status
Fixed
commit 7a9b7526
Category
Business Logic
F1
User scenarios

User entry risk scenarios

Concrete scenarios where user capital can shrink even when the protocol works as designed, and the guardrails for each.

S01

Spot buy followed by market converging to NAV

Trigger

You buy RBT spot while premium is large (around 3× NAV today) and BAM pulls price down to near-NAV.

Outcome

Convergence to NAV means a large loss versus your entry. NAV trends upward over time, but recovering to your entry takes a while.

Guardrail

When the Live page verdict reads bond-only or overvalued, avoid spot buys and enter through a bond instead.

S02

Market price at bond maturity below effective entry

Trigger

RBT market price falls faster than the bond's effective entry during the vesting window.

Outcome

RBT received at maturity is worth less in market price than the USDm cost at commit. NAV survives, but market price can temporarily sit near NAV.

Guardrail

Only enter when the discount is above average, and check market price weekly while the bond is open.

S03

Commit capital cannot be withdrawn during the lock

Trigger

Once sRBT is committed, you cannot pull capital out before maturity. Early exit incurs a penalty.

Outcome

If an urgent cash need shows up, you either eat the penalty or wait until maturity.

Guardrail

Only commit capital you genuinely will not need. 24 weeks is roughly 6 months, 52 weeks is 1 year.

S04

Liquidation of RBT used as lending collateral

Trigger

You post RBT as collateral on external lending and borrow USDm, then RBT market price drops sharply.

Outcome

If LTV crosses the liquidation threshold, you get auto-liquidated and lose part or all of the collateral. POL and BAM eventually defend price, but liquidation happens immediately.

Guardrail

Keep LTV conservative under 40%. If price moves alone push it to 50%, deleverage immediately.

S05

Governance parameter changes

Trigger

Parameters like the Lock distribution curve, bond discounts, or BAM slippage get changed by governance.

Outcome

Reward at maturity for existing committed capital can shrink, or new-round entry efficiency can shift. The docs state every maturity curve and cap is at governance discretion.

Guardrail

Check the governance forum quarterly. If a distribution-reduction direction is decided, pause new commits.

Protocol risks

Protocol risks

Protocol-level risks listed on docs.blackhaven.xyz, with the mitigations in place.

Smart contract risk

Every DeFi protocol carries contract vulnerability risk. Even after an external audit, undiscovered issues can remain.

Mitigations
  • Audited by Zellic in Jan 2026. Every finding is either fixed or acknowledged.
  • Admin and upgrade functions are time-locked so users can exit before any change takes effect.
  • A bug bounty program encourages responsible vulnerability disclosure.

RBT backing risk

RBT market price can dip below backing value (NAV) for periods. The docs also note that Genesis Phase 1 charges a 10% protocol fee at bond commit, so RBT backing can run lower than 1-to-1.

Mitigations
  • Treasury is verifiable on-chain.
  • Liquidity Manager holds permanent LP for the RBT/USDm pair.
  • BAM buys RBT and burns when market price drops below NAV.

Oracle risk

The protocol relies on price oracles. Oracle manipulation or stale responses can affect NAV, bond pricing, and BAM premium capture.

Mitigations
  • Multiple oracle providers used for redundancy.
  • Wrapper reverts on stale or zero responses.

Bond-product specific risk

Bonds are fixed-term products. The docs spell out the following risks.

Mitigations
  • Smart contracts are experimental software, so undiscovered vulnerabilities are possible.
  • Oracle failure or manipulation is possible.
  • MegaETH itself can halt or reorg.
  • USDm can de-peg or run out of liquidity.
  • RBT market price can be highly volatile and could go to zero.
  • Governance decisions can affect existing positions.
  • Regulatory changes can affect product availability.
  • The docs state that total loss of bond principal is possible.

This page summarizes Zellic's public report and the Risks section of docs.blackhaven.xyz. It is not a final recommendation. Please verify the docs, the original report, and the current contract state directly before allocating capital.