CertiK LogoCertiK Logo
Tradefi.bot logo
Tradefi.bot
DeFi
Yield Farming
Tools
Max Payout
$20,000
Project Overview

Tradefi introduces the first on-chain tokenized AI trading agents designed to generate passive income for holders. Powered by $TDFI, a hyper-deflationary utility token, the ecosystem delivers bi-weekly USDT dividends—with no staking or lockups required. Simply hold to benefit from autonomous AI-driven trading and income generation.

Committed to the highest standards of security, TDFI safeguards its smart contracts, dApps, user data, and third-party integrations to ensure a secure and reliable experience across its entire ecosystem.

Rewards by Severity

Program Overview Tradefi.bot is committed to maintaining the highest level of security across all components of its ecosystem, including smart contracts, decentralized applications, user data systems, and third-party integrations. Through this Bug Bounty Program, we aim to proactively identify vulnerabilities and reward ethical hackers who contribute to a safer environment for our users.

Reward Structure Bounties follow a 4-tier severity model, scaled based on the criticality of the issue and the affected system. Rewards for critical smart contract vulnerabilities are capped at 10% of economic damage, accounting for the funds impacted, as well as potential PR and brand concerns at the discretion of the Tradefi.bot team. High-severity issues may receive rewards up to 100% of the affected funds, with calculations based on the risk level at the time of submission.

Submission Requirements To be considered for a reward, bug reports must include a functioning Proof of Concept (PoC) and detailed reproduction steps demonstrating the end-effect on an in-scope asset. Reports without working code will not be accepted.

Payouts All eligible rewards will be issued in TDFI, distributed by the Tradefi.bot team after successful verification of the vulnerability.

Smart Contract
The bounty will be paid out in TDFI
Assets In-Scope
Target
Severity
Name
Smart Contract
TDFI Token contract
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
Permanent freezing of funds
Unauthorized mint/burn/transfer of crypto assets
Bad randomness leading to predictable results with serious financial impact
Governance voting result manipulation
Protocol insolvency
MiniApp database manipulation (e.g. tampering with trading history and user access or configuration files)
Telegram MiniApp (TON) takeover or hijack
Web application root access or backdoor vulnerability
Unauthorized access to backend servers or cloud infrastructure
Manipulation or leak of private API keys or access tokens
Full compromise of user authentication system (SSO and login bypass)
Access to or manipulation of USDT dividend distribution logic
Community-targeted exploits that redirect users to phishing versions of the app or dApp
Smart contract deployment or ownership takeover via misconfiguration or exploit
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
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.
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 SinceApr 7, 2025
Last Updated4mo 28d ago
Funds Reserved$500,000
Max Payout$20,000
Skynet Score
72.36
BBB
KYC
Not Required
PoC
Required