CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Ready To Fight logo
Ready To Fight
Blockchain Commerce
Web3
Marketplace
Max Payout
$1,000
Project Overview

Ready to Fight is a blockchain-powered social network designed to connect fighters with professionals such as promoters, coaches, and nutritionists. Serving as a trusted intermediary, the platform enables athletes to advance their careers, enhance collaboration, and increase their earnings within a decentralized ecosystem.

Rewards by Severity

Program Overview The Ready to Fight (RTF) Bug Bounty Program is a proactive security initiative designed to enhance the resilience of the RTF ecosystem. By inviting ethical hackers, security researchers, and the global cybersecurity community to identify potential vulnerabilities, RTF reinforces its commitment to safeguarding user data, platform integrity, and system performance.

Reward Structure All valid submissions are evaluated using a 4-tier severity model, with reward amounts based on the criticality of the vulnerability and the affected component. Issues that pose significant financial or systemic risk qualify for higher-tier rewards. Final rewards may also include public acknowledgment of contributors in addition to monetary compensation.

Submission Requirements To qualify for a reward, reports must include a working proof of concept (PoC) and detailed reproduction steps that clearly demonstrate the impact of the vulnerability on an in-scope asset. Submissions without executable code or measurable real-world consequences will not be eligible for reward consideration.

Payouts Bounties are denominated in USD and paid in USDT, issued directly by the RTF team upon successful validation of the report and KYC compliance.

Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://github.com/Rtfight/rtf-token
Smart Contract
RTF Token
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
Major
Theft or permanent freezing of unclaimed yield
Medium
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Low
Missing events for functions that change critical parameters
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)
Best practice critiques
Sybil attacks
Centralization risks
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 26, 2024
Last Updated1y 7mo 22d ago
Funds Reserved$10,000
Max Payout$1,000
Skynet Score
84.61
A
KYC
Required
PoC
Required
View on Skynet