CertiK LogoCertiK Logo
Tonstakers logo
Tonstakers
DeFi
Lending & Borrowing
Yield Farming
Max Payout
$50,000
Project Overview

Tonstakers offers an innovative DeFi staking solution on the TON blockchain, allowing users to stake TON tokens and receive tsTON—a liquid staking derivative representing staked assets plus rewards. This mechanism enables users to maintain liquidity and engage in other DeFi activities without forfeiting staking benefits.

Rewards by Severity

Program Overview Tonstakers operates a dedicated bug bounty program to ensure the security and resilience of its staking infrastructure and smart contract ecosystem. The program invites ethical hackers and security researchers to responsibly disclose vulnerabilities that could impact the Tonstakers platform or its users, strengthening overall trust and technical integrity.

Reward Structure All valid submissions are assessed using a 4-tier severity model, with reward amounts determined by the criticality of the issue and the component affected. For critical smart contract vulnerabilities, rewards are capped at 2% of the economic damage, with primary consideration given to funds directly at risk. Secondary considerations such as PR or brand impact may also influence final payouts, at the discretion of the Tonstakers team. For high-severity vulnerabilities, rewards may reach up to 100% of the funds affected, with calculations based on market conditions at the time of the report submission.

Submission Requirements To qualify for a reward, bug reports must include a detailed proof of concept (PoC) in the form of executable code, along with step-by-step reproduction instructions. The report must clearly demonstrate the end-effect of the vulnerability on an in-scope asset. Submissions without code-based PoC or those based solely on written explanations will not be considered.

Payouts Rewards are denominated in USD-equivalent value and paid out in TON, Tonstakers’ native token. All bounties are processed by the Tonstakers team upon successful validation and KYC compliance.

Smart Contract
The bounty will be paid out in TON
Assets In-Scope
Target
Severity
Name
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
Unauthorized mint/burn/transfer of assets
Double spending
Protocol insolvency
Vulnerabilities that could lead to substantial financial loss; complete loss of liquidity; or highly malicious actions (e.g.theft or destruction of tsTON or breach of smart contracts)
Major
Minor price manipulation
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Issues that can cause a considerable impact on the protocol's performance or security; but less catastrophic than critical vulnerabilities
Medium
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Vulnerabilities that affect the protocol's functionality; user experience; or moderate security risks
Low
Minor issues that have a low impact on the overall security and functionality of the protocol
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
General feedback; suggestions for improvements; or potential issues that don't pose any immediate risk
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 7, 2024
Last Updated3mo 11d ago
Funds Reserved$100,000
Max Payout$50,000
Skynet Score
87.19
AA
KYC
Required
PoC
Required