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
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Theft or permanent locking of vested funds
Unauthorized minting of ZEN tokens
Public RPC API crash
Unintended chain split (network partition)
Transient consensus failures
Out of scope
- Broken link hijacking is out of scope
Blockchain/DLT:
- Any assets under Horizen mainnet are out of scope. Only Gobi and Horizen testnets are valid.
- Any attack requiring the majority of the mining hashrate
- Attacks requiring MITM or physical access to a user's device
- Previously known vulnerable libraries without a working Proof of Concept.
- Rate limiting or bruteforce issues on non-authentication / local endpoints (e.g., RPCs, websocket)
- Application Flood Attacks on exposed ports
- Best practice critiques
Blockchain/DLT specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers