Skip to main content

Responsible Disclosure

Full policy lives at SECURITY.md in the contracts repo.

Summaryโ€‹

  • Found a vulnerability? Report it privately โ€” do not open a public issue.
  • Scope: DHPFactory, DHPImplementation (vaults), DHPFeeCollector, and the deployed bytecode on all five chains.
  • Out of scope: the underlying tokens wrapped by vaults (their own bugs are theirs), UI-only issues without contract impact, and the already-documented risks.

How findings are handledโ€‹

  1. Private triage โ€” acknowledged, severity-rated against the same Crit/High/Med scale used in the seven self-audit passes.
  2. Fix + regression โ€” fixes ship with a permanent regression test; the v1.4.0 reentrancy fix (same-day, PoC-converted-to-regression) is the template.
  3. Public report โ€” findings and fixes are published in-repo once resolved, with PoCs preserved in git history.

Publication trailโ€‹

ArtifactWhere
Self-audit reports (v1.0 โ†’ v1.4.0)SELF_AUDIT*.md in the contracts repo
Latest audit PDFSELF_AUDIT_V1.4.0.pdf in the contracts repo
PoC codePreserved in git history
Verification ledgerdeployments.json โ†’ verificationLedger
note

There is no bug bounty pool at this time; the protocol has no treasury-controlled upgrade surface to indemnify. Reports are still honoured and credited.