SpookySwap-logo

SpookySwap

SpookySwap is an automated market-making (AMM) decentralized exchange (DEX) for the Fantom Opera network. Different from other DEXs, we're invested in building a strong foundation with our BOO token as a governance token, diverse farms, a built in bridge, built in limit orders and user-centered service. For more information about SpookySwap, please visit https://spooky.fi/

Bittorrent
Fantom
Horizen EON
Defi
NFT
AMM
Bridge
Crosschain Liquidity
DEX
Staking
Solidity
Maximum Bounty
$200,000
Live Since
21 September 2021
Last Updated
08 April 2024
  • PoC required

Submit a Bug

Rewards by Threat Level

Smart Contract
Critical
Up to USD $200,000
High
USD $10,000
Medium
USD $3,000

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

Critical severity smart contract bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, Critical and High severity bug reports will require a suggestion on how to fix the vulnerability for a reward

Critical smart contract bug reports will be rewarded with USD 200, 000 only if the impact leads to a direct loss in funds. All other impacts that would be classified as Critical would be rewarded no more than USD 35, 000

SpookySwap is aware of a bug where a pool can get added automatically even without doing add, if the pool is added on the corresponding farm contract, and someone deposits. This is under The Rewarder:

Payouts are handled by the SpookySwap team directly and are denominated in USD. However, payouts are done in a mix of USDC, ETH, BOO, and FTM, at the discretion of the team

All smart contracts of SpookySwap can be found at https://github.com/SpookySwap. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by SpookSwap that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

Program Overview

SpookySwap is an automated market-making (AMM) decentralized exchange (DEX) for the Fantom Opera network. Different from other DEXs, we're invested in building a strong foundation with our BOO token as a governance token, diverse farms, a built in bridge, built in limit orders and user-centered service. For more information about SpookySwap, please visit https://spooky.fi/

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default prohibited activities
  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • Any testing with pricing oracles or third-party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty
  • Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.