CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Openfabric AI logo
Openfabric AI
Infrastructure
AI
Max Payout
5000 0FN
Project Overview

Openfabric AI is a decentralized Layer 1 protocol designed to build and connect AI applications through the power of blockchain technology, advanced cryptography, and innovative infrastructure. By providing a secure and scalable foundation, Openfabric AI enables developers to create interoperable AI-powered solutions within a decentralized ecosystem.

Rewards by Severity

Program Overview Openfabric maintains a bug bounty program to support the secure development and operation of its AI-centric decentralized infrastructure. The program invites security researchers and ethical hackers to identify vulnerabilities that could affect the Openfabric blockchain client, smart contracts, or other components detailed in the program’s scope.

Reward Structure The program follows a 4-tier severity model, with reward levels determined by the criticality of the vulnerability and the type of component affected. Critical vulnerabilities, which could cause financial losses or network disruptions, may receive rewards of up to 5,000 OFN tokens. These include issues in officially deployed versions of smart contracts or core blockchain components. Non-critical vulnerabilities, while not directly causing financial or availability risks, may still affect developer or user experience and qualify for rewards of up to 500 OFN tokens. All submissions are subject to validation and final assessment by the Openfabric team to ensure accurate classification and fair compensation.

Submission Requirements All bug reports must include a complete and functioning proof of concept (PoC) with detailed steps to reproduce the vulnerability. Reports relying only on written explanations or without demonstrating real-world impact will not be eligible for rewards.

Payouts All bounties are denominated in USD-equivalent value and paid out in OFN, Openfabric’s native token. Payouts are managed directly by the Openfabric team following successful verification and KYC compliance.

Smart Contract
The bounty will be paid out in 0FN
Assets In-Scope
https://github.com/Openfabric/openfabric-token
Smart Contract
OFN 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
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 12, 2023
Last Updated9mo 8d ago
Funds Reserved50000 0FN
Max Payout5000 0FN
KYC
Required
PoC
Required
View on Skynet