fluid ⌘K

Liquidity Layer

Risks

Learn about the risks associated with Fluid

Fluid is a cutting-edge lending protocol designed with robust security measures to offer a secure and efficient experience for users. However, it's crucial for all users to understand the risks associated with lending protocols like Fluid. By using the platform, you assume all risks, including potential loss of funds. Fluid shares many similar risks with established protocols like AAVE and Compound but includes several advancements that enhance and makes it more secure than previous protocols.

What Makes Fluid More Secure?

Automated Limits: Fluid employs Automated Limits that expand continuously per block, restricting the maximum withdrawal and borrowing within any 12-hour period. This mechanism, known as Expand Percentage, is available on the Stats page. Automated Limits protect the protocol from sudden black swan events, making it highly unlikely for all liquidity to exit Fluid in a short period. For instance, it would take approximately four days for all liquidity to exit.

Simple Liquidity Layer: The core of Fluid is a simple liquidity contract, the Liquidity Layer. This layer ensures all Fluid liquidity is maintained in a straightforward contract, does not involve end-user borrowing functions, and minimizing attack surfaces.

Efficient Liquidation Mechanism: Fluid's advanced liquidation mechanism ensures the cheapest and most gas efficient liquidations. Thousands of positions can be liquidated in one transaction, allowing the protocol to liquidate debt quickly and effectively. This efficiency enables Fluid to offer higher Loan-to-Value (LTV) ratios for user assets.

Advanced Oracle System: Fluid uses a combination of Uniswap and Chainlink oracles for accurate and reliable pricing data, reducing the risk of price manipulation. A recent update enables multi-use oracles for different operations, adding extra security measures.

Risk Considerations

Smart Contract Bugs

Fluid has been audited by Statemind and Mixbytes, but unforeseen bugs or errors may occur, potentially causing users to lose funds or face issues interacting with the protocol. Fluid encourages community involvement and offers a $500k bug bounty through Immunefi to identify and mitigate these risks.

Instadapp Bug Bountyimmunefi

Click here to view our 500k Bug Bounty!

Price Oracles

Fluid utilizes multiple price oracles, including Chainlink and Uniswap TWAP (Time Weighted Average Price) checks, to verify prices during transactions. This dual-check system minimizes the risk of price manipulation, ensuring more reliable and secure operations.

Protocols such as the Vaults protocol can utilize multiple oracles like Chainlink and Uniswap and do utilize them in combination to protect users and the protocol from bad debt.

  1. Pulls on chain Uniswap TWAP price (on-chain price)
  2. Checks this price against the Chainlink (difference check)
  3. If the TWAP is within parameters it will use on-chain otherwise it will use the Chainlink price. (determines oracle to utilize)

In essence, this means the uniV3 price (on-chain pricing) will be utilized in most cases. However, if there is a significant market fluctuation, we will revert to using the Chainlink price. Our goal is to ensure that liquidations on the Vault protocol can occur whenever necessary, relying on the most accurate information available. This approach safeguards the protocol from incurring bad debt.

Contract Pricing

Certain Vaults within the Vaults protocol, such as weETH/wstETH, employ enhanced security measures through contract pricing to prevent user liquidations during short-term price depegs. By querying the backing contract for assets, we can verify that they are fully backed, ensuring accurate asset pricing even with low on-chain liquidity. This approach effectively prevents baseless liquidations due to temporary price fluctuations. Contract pricing in Fluid has some similarities to Fundamental Pricing on AAVE, providing a robust mechanism to maintain stability.

Liquidity and Automated Limits

Fluid's innovative Automated Limits system ensures a secure and stable environment for users by continuously adjusting per block to restrict maximum withdrawals and borrowing within any 12-hour period. This dynamic mechanism, known as Expand Percentage, is prominently featured on the Stats page, providing transparency and confidence to users. By preventing the sudden removal of large amounts of funds, Automated Limits safeguard against black swan events and ensure that it would take approximately four days for all liquidity to exit the protocol. This design allows the protocol to unwind safely within five days, maintaining stability while still accommodating user needs effectively.

Undercollaterized fToken

As a liquidity layer, all protocols built on Fluid draw liquidity from the same pool. Excessive access to liquidity or significant asset devaluation can affect the liquidity layer, causing depositors to become under-collateralized. This is managed by governance and how much each protocol can tap into the liquidity layer, if an asset becomes undercollaterized or an asset is frozen it may impacts all asset holders until the specific vault or protocol's debt is neutralized, returning the fToken to parity.

Liquidation Risks

Liquidations on Fluid operate neutrally, allowing anyone to execute and call liquidations. Vaults can be liquidated via an indirect swap, buying the debt at a slight discount while liquidating the position in the process. Liquidations require accurate price oracles and sufficient on-chain liquidity and are actively monitored by the team. Delayed liquidations can exacerbate losses. Fluid employs a two-tier liquidation system:

  1. Liquidation Threshold: This is the point at which a position becomes eligible for liquidation.
  2. Max Liquidation Threshold: This is a higher threshold at which the entire 100% of the position can be liquidated to repay outstanding debt.

Oracle Usage Risks

Oracles are a crucial point of DeFi infrastructure. If an oracle reports incorrect data, it may cause liquidations or incorrect protocol operations, resulting in bad debt and loss of user funds. Fluid can utilize a variety of oracles and can specify oracles for different operations ensuring the protocol can mitigate risk while serving users.

Interface Web UI

Fluid is a collection of smart contracts deployed on the Ethereum network, accessible through multiple UIs. Users must ensure their computers and browsers are secure to avoid hacks. Malicious actors can spoof or scam users, leading to potential loss of funds.

Governance and DAO Risks

Fluid's governance involves DAO decisions that affect protocol operations and risk management. Proper alignment and management are crucial to maintaining protocol stability and user satisfaction.

Phishing and Hacks

Fluid implements security measures against breaches, including hacks and cyber-attacks. Users must also take precautions to secure their assets and interactions with the protocol.

Individual Asset Risk

Fluid onboards various assets, each with different risks. For example, weETH is available as collateral but not for borrowing. Users must understand the risks associated with each asset, including pricing methodologies and oracle use.

LRTs and Stablecoins

Liquid Restaking Tokens (LRTs) and stablecoins like USDC and USDT have specific risks. Users must rely on providers for restaking and be aware of centralized institutions' potential actions that could affect Fluid.

By using Fluid, you acknowledge and accept these risks. It is crucial to stay informed and exercise caution when interacting with the protocol.