CertiK LogoCertiK Logo
Defiway logo
Defiway
Cross-Chain Bridge
DeFi
Payment
Max Payout
$100,000
Project Overview

Defiway is a leading Decentralized Finance platform offering secure and efficient crypto payment solutions across multiple blockchain networks. Designed for both businesses and individuals, Defiway enables seamless global transactions with minimal costs. The platform supports a wide range of industries—including gaming, e-commerce, payment service providers, influencers, bloggers, streamers, online brokers, trading platforms, and gambling—empowering users to send and accept cryptocurrency payments with ease.

Rewards by Severity

Program Overview The Defiway Bug Bounty Program is designed to engage security researchers and ethical hackers in identifying potential vulnerabilities across Defiway’s smart contracts, decentralized applications, and supporting infrastructure. This initiative reinforces Defiway’s commitment to building a secure and trustworthy DeFi ecosystem for all users.

Reward Structure Rewards are structured based on a 4-tier severity model, varying by the criticality of the vulnerability and the type of target (e.g., smart contract vs. frontend application). For critical smart contract vulnerabilities, rewards are capped at 10% of the estimated economic damage, taking into account the funds at risk and any potential reputational or PR-related consequences. High-severity vulnerabilities may receive rewards of up to 100% of the affected funds, calculated at the time of report submission.

Submission Requirements To qualify for a bounty, bug reports must include a working proof of concept (PoC) and detailed steps to reproduce the issue. Submissions that consist solely of written explanations without code or demonstrable impact will be rejected.

Payouts All approved bounty rewards are paid in USDT, and are disbursed after successful review and confirmation of eligibility.

Application/Web
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
Web Application
DEFI
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.
Application/Web
Critical
Smart contract fails to deliver promised returns - but doesn’t lose value
Major
Remote code execution and code injection
SQL injection
Obtaining high-impact sensitive information from the internal system
XXE/XML injection vulnerability with high-security impact
Authentication and authorization bypass with high impact
Large scale account takeover
Leakage of a lot of source code
Medium
Account takeover; Stored XSS on general pages; CSRF involving core business; etc
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Medium impact information disclose
Low
General information leakage - such as web path traversal - system path traversal - directory browsing etc
Other vulnerabilities with low-security impact
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.
Application/Web
Clickjacking
Any activity that could lead to the disruption of our service (DoS)
Previously known vulnerable libraries without a working Proof of Concept
Issues that require unlikely user interaction
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
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., 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:
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
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 SinceJul 15, 2024
Last Updated3mo 11d ago
Funds Reserved$200,000
Max Payout$100,000
Skynet Score
76.32
BBB
KYC
Not Required
PoC
Not Required