CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
EDU3Labs logo
EDU3Labs
Web3
AI
NFT
Max Payout
$5,000
Project Overview

Edu3Labs is an innovative platform integrating education and blockchain technology to create a rewarding ecosystem for content creators, learners, and NFE token holders. By leveraging decentralized incentives, Edu3Labs enhances engagement and fosters a collaborative learning environment where all participants can benefit.

Rewards by Severity

Program Overview Edu3Labs, in collaboration with CertiK, has launched a bug bounty program to support the development of a secure and trustworthy Web3 educational ecosystem. As the platform approaches full launch, this initiative invites ethical hackers, researchers, and community contributors to help identify and address potential security threats. The program is a core part of Edu3Labs’ mission to empower educators, learners, and creators while ensuring platform reliability and trust.

Reward Structure The program follows a 4-tier severity model, with rewards determined by the criticality of the vulnerability and the component affected—such as smart contracts, APIs, or frontend systems. Critical and high-severity issues that could compromise user data, funds, or system availability are prioritized for higher reward tiers. All rewards are subject to internal validation by Edu3Labs and may be adjusted based on impact and reproducibility.

Submission Requirements All bug reports must include a working proof of concept (PoC) and detailed steps to reproduce the issue. Submissions that lack code-based demonstration or fail to prove real-world impact on in-scope assets will not be considered for a reward.

Payouts All rewards are denominated in USD and paid in USDT, handled directly by the Edu3Labs team upon successful validation and KYC completion.

Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://testnet.bscscan.com/address/0x15C73B5B376F8eE889BF19C15010C3D5B645F4eB#code
Smart Contract
Token Address
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
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Major
Faulty usage of proxy patterns
Minor price manipulation
Temporary denial of services
Temporary freezing of funds for any amount of time
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
Low
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
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)
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 SinceSep 18, 2023
Last Updated4mo 28d ago
Funds Reserved$20,000
Max Payout$5,000
Skynet Score
84.86
A
KYC
Required
PoC
Required
View on Skynet