Crescendo
Bounty Program
Help Secure the Biggest Flow Upgrade Since Launch
What is in the scope of this bounty program?
This bug bounty program seeks exploitable weaknesses in smart contract code, transactions, or scripts that could destabilize the Flow network, such as crashing or significantly slowing down network nodes.
The goal is to safeguard the Cadence and EVM runtime environment from unauthorized control and protect the non-public state of accounts from privilege escalation. Your expertise could earn substantial rewards and contribute to a more secure Flow network!
The bounty program welcomes any bug reports that clearly demonstrate unintended behavior and significantly impact Flow builders or users.
Bounty Tiers
Where are potential bugs?
The Crescendo upgrade introduces major performance upgrades and full EVM equivalence. Here are the key areas that underwent significant changes, and potential bugs that could arise.
- New and updated functionality
- Circumvention of resource semantics, such as unauthorized construction, duplication, or use-after-destruction.
- Type confusion, such as using functionality designed for a certain type (parameter) with a value of another type.
Discover Cadence source code and Flow node software source code.
Privilege elevation/bypassing sandbox protections for file system access controls, services/processes, and restricted memory access.
For example:
- Gaining control of the machine hosting the Cadence & EVM runtime environment (e.g., the node’s private keys) via adversarial transactions and/or smart contracts.
- Accessing private keys of a node hosting the Cadence & EVM runtime.
- Gaining access to the Random Number Generator's internal state, leading to reliable prediction of future outcomes of on-chain randomness (see Flow’s VRF for more details).
Discover Cadence source code and Flow node software source code.
- Withdrawing from a FT vault without proper access.
- Hijacking another user's account.
- Accessing private data belonging to other users.
- Gaining inappropriate access to sensitive and/or private information, such as a contract accessing private fields of another contract.
- Making unauthorized changes to the application or its data.
- Bypassing business logic rules around account changes.
- Bypassing authorization and authentication mechanisms.
- Bugs or vulnerabilities in exposed API endpoints.
- Data corruption or loss.
- Unreachable data due to data migration or transaction/script execution.
What is outside the scope of this program?
All vulnerabilities must be reported in accordance with the Flow Responsible Disclosure Process.
For a list of Flow protocol and web application exclusions (i.e. non-qualifying vulnerabilities), refer to the Flow Responsible Disclosure.
Start building on Flow
Developer-friendly layer 1 blockchain with EVM equivalence enabling seamless user experiences, secure assets, and low fees.