Metric Docs | Bug Bounty
Learn how to approach Metric vulnerability reporting, scope verification, reproducible proof-of-concept preparation and responsible disclosure.
Learn how to approach Metric vulnerability reporting, scope verification, reproducible proof-of-concept preparation and responsible disclosure.
Metric is built around Active Pools: liquidity pools that use a Price Provider to supply bid, ask and reference prices instead of relying only on reserve ratios. This page focuses on Bug Bounty and the practical checks that matter when using or integrating the protocol.
Responsible disclosure
Metric maintains a public vulnerability-reporting program. Before testing, read the current scope, prohibited actions, proof-of-concept requirements and reward terms.
Write a useful report
| Include | Why |
|---|---|
| Affected contract/component | Defines scope |
| Impact | Explains what can go wrong |
| Reproduction steps | Makes the issue verifiable |
| Proof of concept | Demonstrates the behavior safely |
| Suggested mitigation | Helps triage and remediation |
Do not exploit users
Security research should stay within the current program rules. Do not move user funds, expose private data or test destructive scenarios against production users.
Related Metric Docs
Last updated