CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Haven1 logo
Haven1
Layer 1
Web3
Infrastructure
Max Payout
$100,000
Project Overview

Haven1 is a security-first EVM Layer 1 blockchain purpose-built to prevent on-chain exploits, scams, and rug pulls. By implementing network-level safeguards and requiring user and builder verification, Haven1 fosters a trusted environment where participants can interact safely and transparently across the decentralized ecosystem.

Rewards by Severity

Program Overview Haven1 offers a structured bug bounty program to proactively identify and resolve security vulnerabilities across its smart contracts and application layers. This initiative reflects the platform’s commitment to maintaining a secure and transparent on-chain environment for all users.

Reward Structure The program adopts a 4-tier severity model, with rewards adjusted based on both the criticality of the vulnerability and the type of system component affected (smart contracts or web applications). Higher-impact issues receive higher-tier payouts in alignment with industry standards.

Submission Requirements All submissions must include a working proof of concept (PoC) that clearly demonstrates an exploit’s impact on an in-scope target. Reports that lack actionable code or fail to show end-effect will not be considered.

Payouts Rewards are denominated in USD but paid out in USDC, processed directly by the Haven1 team upon successful validation and completion of KYC.

Smart Contract
Blockchain
The bounty will be paid out in USDC
Assets In-Scope
Target
Severity
Name
https://github.com/haven1network/contracts-go-quorum
Blockchain
HAVEN1 Permissioned Contracts Suite for Go Quorum – a comprehensive set of smart contracts (including PermissionsImplementation, PermissionsInterface, AccountManager, NodeManager, OrgManager, RoleManager, and VoterManager) that manage network permissions, roles, accounts, and nodes with a single Network Admin structure for secure and transparent on-chain governance.
https://github.com/haven1network/contracts-core-bug-bounty
Smart Contract
This repository houses the Solidity smart contracts essential for the core infrastructure of Haven1. The contracts encapsulate critical functionalities required for the seamless operation and governance of the Haven1 ecosystem. We've included Bridge, Fee, Governance, Staking, and Network Guardian contracts that ensure secure asset transfers, fee management, identity verification, and on-chain governance, all structured for streamlined deployment and testing.
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of project funds other than unclaimed rewards
Direct theft of user funds other than unclaimed rewards
Unauthorized mint/burn/transfer of crypto assets
Bad randomness leading to predictable results with serious financial impact
Governance voting result manipulation
Protocol insolvency
Major
Issues leading to temporary freezing of funds for a limited amount of time
Theft or permanent freezing of unclaimed yield and rewards
Temporary denial of services
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration.
Griefing attacks that can damage users or the protocol without profiting the attacker
Block stuffing for profit.
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation.
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Blockchain
Critical
Network not being able to confirm new transactions (Total network shutdown)
Unintended permanent chain split requiring hard fork
Permanent freezing of funds(fix requires hard fork)
Transaction/consensus manipulation
Unauthorized token minting
Major
Unintended chain split (fix not requiring hard fork)
Transient consensus failures
Validator selection set manipulation
Medium
High compute consumption by validator/mining nodes
Vulnerability in RPC API (except via DDoS attack)
Low
Underpricing transaction fees relative to computation time
Griefing (e.g. triggering abnormally high gas fees for everyone or abnormal cpu consumption for validator/mining nodes)
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Not following best practices with no security risk
Sybil attacks
Centralization risks
Issues with no security or financial impact
Blockchain
Centralization risks
Best practice critiques
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope2
Live SinceApr 28, 2025
Last Updated4mo 28d ago
Funds Reserved$100,000
Max Payout$100,000
Skynet Score
89.95
AA
KYC
Required
PoC
Required
View on Skynet