CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
STON.fi logo
STON.fi
DeFi
Web3
Token
Max Payout
$100,000
Project Overview

STON.fi is a decentralized Automated Market Maker (AMM) built natively on the TON blockchain, offering near-zero fees, minimal slippage, and seamless integration with TON wallets. Designed for simplicity and efficiency, STON.fi delivers a smooth and accessible DeFi experience through an intuitive interface and optimized on-chain performance.

Rewards by Severity
Smart Contract
The bounty will be paid out in STON
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 user funds
other than unclaimed rewards.
Permanent freezing of funds.
Protocol insolvency
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
Griefing attacks that can damage users or the protocol without profiting the attacker
Low
Important gas optimizations
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
Not following best practices
with no security risk.
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.
  • 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.
  • 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:
  • 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.
  • Any testing with mainnet.
  • Any testing with pricing oracles or third party Smart Contracts.
  • Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks).
  • Any denial of service attacks.
  • Router address - EQAFpeGFJQA9KqiCxXZ8J4l__vSYAxFSirSOvPHn6SSX44Dt.
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 Scope5
Live SinceApr 1, 2025
Last Updated3mo 10d ago
Funds Reserved$500,000
Max Payout$100,000
Skynet Score
89.55
AA
KYC
Not Required
PoC
Not Required
View on Skynet