Bitflow-logo

Bitflow

Bitflow is a decentralized exchange (DEX) that enables users to trade and earn using their Bitcoin, eliminating the need for centralized intermediaries. It leverages technologies such as Partially Signed Bitcoin Transactions (PSBTs), Atomic Swaps, Layer-2 smart contracts, Stacks Bitcoin (sBTC), and decentralized liquidity pools — unlocking the full potential of Bitcoin.

Stacks
Exchange
Defi
DEX
Liquid Staking
Clarity
NextJS
Maximum Bounty
$100,000
Live Since
08 April 2024
Last Updated
20 November 2024
  • PoC required

  • Vault program

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - stableswap-stx-ststx-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - stableswap-usda-susdt-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - stableswap-aeusdc-susdt-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - stableswap-usda-aeusdc-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - stableswap-abtc-xbtc-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - earn-stx-ststx-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - earn-usda-susdt-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - earn-aeusdc-susdt-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - earn-usda-aeusdc-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - diko-emissions-usda-aeusdc-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - earn-abtc-xbtc-v-1-2
Added on
8 April 2024
Target
Type
Smart Contract - stx-ststx-lp-token-v-1-2
Added on
8 April 2024

Impacts in Scope

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Protocol insolvency

Severity
Critical
Title

Retrieve sensitive data/files from a running server, such as: /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Severity
Critical
Title

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Severity
Critical
Title

Direct theft of user funds

Severity
Critical
Title

Malicious interactions with an already-connected wallet, such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions

Severity
High
Title

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Permanent freezing of unclaimed yield

Severity
High
Title

Temporary freezing of funds

Severity
Medium
Title

Smart contract unable to operate due to lack of token funds

Out of scope

Program's Out of Scope information
  • Tokens not deployed from SPQC38PW542EQJ5M11CR25P7BS1CA6QT4TBXGB3M
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers