Fluid Protocol's Invite-Only Program is a form of Audit Competition which is exclusively accessible to a select group of security researchers who have submitted at least 1 valid report during Fuel Attackathon event. These researchers will share a flat reward pool for every valid bug found.
Live
Triaged by Immunefi
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
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.
Whitehat Educational Resources & Technical Info
- https://docs.hydrogenlabs.xyz/fluid-protocol-community/
- Ottersec audit: https://drive.google.com/file/d/1qhiI26aB9MTXfo-hLW8Qy9ki2ueCudKN/view?usp=sharing
Is this an upgrade of an existing system? If so, which? And what are the main differences?
This is a rewrite of Liquity (v1) from Solidity into Sway, with numerous design changes. The main differences are the lack of recovery, multi-collateral system with single stability pool, and partial liquidations.
Where do you suspect there may be bugs? Useful aspects of this question are:
Yes, please see required functions across all the contracts. Specifically in FPT staking, there are the same assumed invariants as in this report for Liquity: https://github.com/trailofbits/publications/blob/master/reviews/LiquityProtocolandStabilityPoolFinalReport.pdf Additionally, math rounding throughout the contracts, since we are using 9 decimals of precision whereas liquity is using 18.
What ERC20 / ERC721 / ERC777 / ERC1155 token standards are supported? Which are not?
SRC-20 Token Standard
What addresses would you consider any bug report requiring their involvement to be out of scope, as long as they operate within the privileges attributed to them?
An Owner is out of scope.
What addresses would you consider any bug report requiring their involvement be out of scope, even if they exceed the privileges attributed to them?
Owner Address.
What external dependencies are there?
Fuel standard library primarily. Sway libs. Pyth, Redstone.
Are there any unusual points about your protocol that may confuse whitehats?
The Fluid Proocol docs overview covers the main design changes from Liquity. There are some other minor changes that are not documented.
What is the test suite setup information?
The tests for the smart contracts are included in the GitHub repo: https://github.com/Hydrogen-Labs/fluid-protocol
Test Structure: Unit tests for some smart contracts are located in ./contracts/[contract-name]/src/utils.sw Integration tests are located in The interfaces and setup for integration tests are in
Running the Tests: Make sure you have fuelup, fuel-core, cargo, and rust installed Use command: make build-and-test
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
Previous Audits
Fluid Proocol’s completed audit reports can be found here https://drive.google.com/file/d/1qhiI26aB9MTXfo-hLW8Qy9ki2ueCudKN/view?usp=sharing. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Theft of unclaimed yield
Theft of unclaimed royalties
Permanent freezing of unclaimed yield
Temporary freezing of funds for more than one week
Smart contract unable to operate due to lack of token funds
Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
Theft of gas
Unbounded gas consumption
Contract fails to deliver promised returns, but doesn't lose value
Out of scope
These impacts are out of scope for this bug bounty program.
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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
- 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
Blockchain/DLT & 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
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