CertiK LogoCertiK Logo
HanChain logo
HanChain
DeFi
Smart Contract Platform
NFT
Max Payout
$2,500
Project Overview

HanChain & PayKhan is a dual-token DeFi platform designed to bridge blockchain with real-world commerce and entertainment. Its dual-structure model consists of HAN, a collateral token, and PKN, a stablecoin issued through HAN staking, to ensure transactional stability. Integrated with the PayKhan Wallet, HAN enables online and offline payments, including access to K-pop streaming and content from KHAN’s entertainment ecosystem. PKN powers electronic financial services via PayKhan Cash, bringing blockchain utility to everyday consumer experiences.

Rewards by Severity

Program Overview Hanchain operates a bug bounty program to ensure the continued security and resilience of its decentralized infrastructure. This program invites ethical hackers and security researchers to responsibly disclose vulnerabilities that could impact the platform’s smart contracts or user-facing systems, contributing to the long-term safety and trust of the Hanchain ecosystem.

Reward Structure All submissions are evaluated using a 4-tier severity model, with reward amounts based on the criticality of the vulnerability and the type of asset impacted. Higher-severity vulnerabilities, especially those with real financial or operational risk, are prioritized for higher rewards. Final reward amounts are determined by internal review and severity classification.

Submission Requirements To be eligible for a reward, all bug reports must include a functional proof of concept (PoC) and detailed, reproducible steps that demonstrate the impact of the vulnerability on an in-scope asset. Submissions consisting only of written statements or theoretical analysis without working code will not be considered.

Payouts Rewards are denominated in USD and paid out in HAN, Hanchain’s native token. Bounties are issued directly by the Hanchain team upon successful validation and KYC completion.

Smart Contract
The bounty will be paid out in HAN
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 any user funds - whether at-rest or in-motion - other than unclaimed yield
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Major
Faulty usage of proxy patterns
Minor price manipulation
Temporary denial of services
Temporary freezing of funds for any amount of time
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
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.
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 Scope4
Live SinceSep 13, 2024
Last Updated4mo 28d ago
Funds Reserved$10,000
Max Payout$2,500
Skynet Score
87.96
AA
KYC
Required
PoC
Required