IOP | Fluid Protocol-logo

IOP | Fluid Protocol

|

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.

Fuel Network
Sway

Evaluating

10d: 6h remaining
Rewards Pool
$80,000
Vault TVL
To be determined
Started
14 November 2024
Ended
12 December 2024
Rewards Token
USDC
nSLOC
6,120
  • Triaged by Immunefi

  • PoC required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - 918
Added on
14 November 2024
Target
Type
Smart Contract - 686
Added on
14 November 2024
Target
Type
Smart Contract - 572
Added on
14 November 2024
Target
Type
Smart Contract - 454
Added on
14 November 2024
Target
Type
Smart Contract - 432
Added on
14 November 2024
Target
Type
Smart Contract - 325
Added on
14 November 2024
Target
Type
Smart Contract - 309
Added on
14 November 2024
Target
Type
Smart Contract - 289
Added on
14 November 2024
Target
Type
Smart Contract - 226
Added on
14 November 2024
Target
Type
Smart Contract - 180
Added on
14 November 2024
Target
Type
Smart Contract - 180
Added on
14 November 2024
Target
Type
Smart Contract - 173
Added on
14 November 2024

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

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.

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
High
Title

Theft of unclaimed yield

Severity
High
Title

Theft of unclaimed royalties

Severity
High
Title

Permanent freezing of unclaimed yield

Severity
High
Title

Temporary freezing of funds for more than one week

Severity
Medium
Title

Smart contract unable to operate due to lack of token funds

Severity
Medium
Title

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Severity
Medium
Title

Theft of gas

Severity
Medium
Title

Unbounded gas consumption

Severity
Low
Title

Contract fails to deliver promised returns, but doesn't lose value

Out of scope

Program's Out of Scope information