SynFutures-logo

SynFutures

SynFutures is a decentralized perpetual futures protocol, facilitating open and transparent trading on any assets and listings instantly. The V3 Oyster AMM launched the industry first-ever unified AMM and on-chain order book model.

Blast
Defi
DEX
Perpetuals
Solidity
Maximum Bounty
$10,000
Live Since
09 May 2024
Last Updated
09 May 2024
  • Triaged by Immunefi

  • PoC required

  • Vault program

  • KYC required

VaultImmunefi vault program

Funds available

$0

30d Avg. Funds availability

$0

Assets in vault

    Public vault address

    0xAce31615e91aBBB55C993C214b03c4eCe61fEbA5

    Rewards

    SynFutures provides rewards in USDC on Ethereum, denominated in USD.

    Rewards by Threat Level

    Websites and Applications
    Critical
    USD $6,000 to USD $10,000
    High
    USD $5,000
    Medium
    USD $2,000
    Low
    USD $1,000

    Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

    Reward Calculation for Critical Level Reports

    For critical web/apps bug reports will be rewarded with USD 10 000, only if the impact leads to:

    • A loss of funds involving an attack that does not require any user action
    • Private key or private key generation leakage leading to unauthorized access to user funds

    All other impacts that would be classified as Critical would be rewarded a flat amount of USD 5 000. The rest of the severity levels are paid out according to the Impact in Scope table.

    Reward Payment Terms

    Payouts are handled by the SynFutures team directly and are denominated in USD. However, payments are done in USDC on Ethereum.

    The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.

    Program Overview

    SynFutures is a decentralized perpetual futures protocol, facilitating open and transparent trading on any assets and listings instantly. The V3 Oyster AMM launched the industry first-ever unified AMM and on-chain order book model.

    For more information about SynFutures, please visit https://www.synfutures.com/

    SynFutures provides rewards in USDC on Ethereum, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.

    KYC Requirement

    SynFutures will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

    • Full name
    • Date of birth
    • Proof of address (either a redacted bank statement with address or a recent utility bill)
    • Copy of Passport or other Government issued ID

    Eligibility Criteria

    Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

    • On OFACs SDN list
    • Official contributor, both past or present
    • Employees and/or individuals closely associated with the project
    • Security auditors that directly or indirectly participated in the audit review

    Responsible Publication

    SynFutures adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

    Primacy of Impact vs Primacy of Rules

    SynFutures adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.

    Proof of Concept (PoC) Requirements

    A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

    Known Issue Assurance

    SynFutures commits to providing Known Issue Assurance to bug submissions through their program. This means that SynFutures will either disclose known issues publicly, or at the very least, privately via a self-reported bug submission.

    In a potential scenario of a mediation, this allows for a more objective and streamlined process, in order to prove that an issue is known. Otherwise, assuming the bug report is valid, it would result in the report being considered as in-scope, and due a reward.

    Previous Audits

    SynFutures’s completed audit reports can be found at https://www.synfutures.com/Quantstamp-Audit-Report-SynFuturesV3.pdf. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

    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.

    Immunefi Standard Badge

    By adhering to Immunefi’s best practice recommendations, SynFutures has satisfied the requirements for the Immunefi Standard Badge.

    KYC required

    The submission of KYC information is a requirement for payout processing.

    Proof of Concept

    Proof of concept is always required for all severities.

    Responsible Publication

    Category 3: Approval Required

    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.