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

EgonCoin powers EgonChain, a proprietary blockchain featuring the innovative Enhanced Proof of Stake (EPoS) protocol. Designed for simplicity and accessibility, EgonCoin enables seamless NFT integration and trading within the Egonverse, a Play-to-Earn (P2E) marketplace. By combining secure infrastructure with user-friendly tools, EgonCoin lowers the barrier to entry for Web3 gaming and digital asset ownership.

Rewards by Severity

Program Overview The EgonCoin Bug Bounty Program is a key part of the project’s commitment to proactive security and community engagement. EgonCoin welcomes developers, researchers, and ethical hackers to explore its smart contracts and blockchain infrastructure to identify and responsibly disclose vulnerabilities. By helping secure the network, participants contribute to a more robust decentralized future.

Reward Structure Bug reports are evaluated using a 4-tier severity model, with rewards based on the criticality and type of vulnerability. For critical smart contract issues, rewards are capped at 10% of the potential economic damage, determined by the funds at risk and broader considerations such as reputational impact. High-severity vulnerabilities may be rewarded up to 100% of the affected funds, based on the value at the time of report submission.

Submission Requirements All submissions must include a working proof of concept (PoC) and detailed steps to reproduce the vulnerability. Reports must show how an in-scope asset is impacted. Submissions without actual code or demonstrable exploit conditions will not be eligible for rewards.

Payouts Rewards are denominated and paid in EGON, and are issued directly by the EgonCoin team following successful validation.

Blockchain
The bounty will be paid out in EGON
Assets In-Scope
https://github.com/EgonChain/Egoncoin-Core/tree/main
Blockchain
EGON/USDT
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.
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
Bad/incorrect usage of cryptography primitives
Validator selection set manipulation
Medium
High compute consumption by validator/mining nodes
Vulnerability in RPC API (except via DDoS attack)
Attacks against thin clients
Unhandled on-chain errors affecting a user corner case
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.
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:
  • "Any testing with mainnet or public testnet contracts
  • all testing should be done on private testnets.
  • 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 Scope1
Live SinceFeb 5, 2024
Last Updated8mo 23d ago
Funds Reserved$500,000
Max Payout$100,000
Skynet Score
83.24
A
KYC
Required
PoC
Required
View on Skynet