CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
dForce logo
dForce
DeFi
DAO
Infrastructure
Max Payout
$50,000
Project Overview

dForce is an integrated and interoperable open finance protocol matrix encompassing lending, asset issuance, and trading. Its suite includes a global liquidity pool, yield markets, stablecoins, synthetic assets, a liquidity aggregator, and AMM infrastructure.

Rewards by Severity

Program Overview The dForce Bug Bounty Program is a proactive security initiative to protect the dForce protocol’s core smart contracts and infrastructure. The program invites security researchers and ethical hackers to responsibly disclose vulnerabilities in order to safeguard funds and ensure stability across the ecosystem. Only core system contracts listed on dForce’s official GitHub repository are in scope. Vulnerabilities in third-party protocols (e.g., smart contract wallets) or issues related to admin key ownership are explicitly excluded.

Reward Structure dForce evaluates all valid submissions using a 4-tier severity model, with separate reward calculations based on the target type (smart contracts vs. frontend/apps). Rewards increase with the criticality of the vulnerability and the impact on system security. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, primarily based on the funds at risk. The dForce team may, at its discretion, increase rewards based on public relations or brand impact.

To qualify as critical, smart contract vulnerabilities must meet all of the following criteria:

The vulnerability enables the attacker to steal at least 10% of total system collateral value.

The issue is exploitable in a real-world scenario, not merely theoretical.

The issue occurs in operation mode or emergency shutdown mode, excluding deployment or pre-activation phases.

Submission Requirements All bug reports must include a functioning proof of concept (PoC) and detailed steps to reproduce the issue. Reports without executable code or with only theoretical analysis will not be considered for reward eligibility.

Payouts Bounties are denominated in USD and paid out in DF, the native token of dForce. Payouts are processed directly by the dForce team following successful validation and KYC compliance.

Smart Contract
The bounty will be paid out in DF
Assets In-Scope
Target
Severity
Name
hhttps://github.com/UnitusLabs/Contracts/wiki/Deployments#base-contracts
Smart Contract
UnitusLabs - Contract Deployments
https://github.com/dforce-network/BountyProgram/wiki
Smart Contract
dForce BountyProgram - Home
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
Any governance voting result manipulation
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
Unbounded gas consumption
Theft of gas
Block stuffing for profit
Smart contract unable to operate due to lack of token funds
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 Scope2
Live SinceSep 5, 2023
Last Updated4mo 28d ago
Funds Reserved$50,000
Max Payout$50,000
Skynet Score
86.52
AA
KYC
Not Required
PoC
Required
View on Skynet