Horizen
Horizen technology offerings and crypto advisory services help organizations leverage the blockchain to solve a broad range of complex use cases. With deep experience in the crypto space, our passionate and committed team of blockchain experts, solution architects, product managers, and developers are accelerating the adoption of blockchain technology by focusing on the critical components of security, confidentiality, speed, and innovation. With unprecedented successes—including the ApeCoin launch—Horizen delivers value at scale.
PoC required
KYC required
Resources & Documentation
Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.
Blockchain/DLT
- Blockchain/DLT - PoC, Blockchain/DLT bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
- For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.
Dev Environment and Documentation
Horizen Labs has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:
- https://eon.horizen.io/docs/
- https://faucet.horizen.io/
- https://chrome.google.com/webstore/detail/cobalt/hekbjgfncacdinlajhgiakpaieajpfph
- https://www.horizen.io/wallets/spherebyhorizen/
- https://gobi-explorer.horizen.io/
- https://eon.horizen.io/docs/
- https://eon.horizen.io/status/gobi
Impacts to other assets
Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.
If whitehats can demonstrate a critical impact on code in production for an asset not in scope, Horizen Labs encourages you to submit your bug report using the “primacy of impact exception” asset.
Impacts in Scope
(For Blockchain/DLTR and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.
Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.
At Immunefi, we classify bugs on a simplified 5-level scale:
- Critical
- High
- Medium
- Low
- None
Only the following impacts are accepted within this bug bounty program. All other impacts are considered out-of-scope and ineligible for payout.