Fluid primary sources — 2026-05-09
Classification takeaway
Fluid is best understood as a unified-liquidity control plane that lets multiple protocols share one underlying balance sheet. Its core move is not merely launching another lending market or DEX, but centralizing liquidity in one core contract and then building lending, vault borrowing, DEX, and unwind flows on top of that shared pool. That makes Fluid analytically useful when comparing monolithic apps against systems that internalize liquidity routing across multiple products.
Primary sources reviewed
-
Official site — https://fluid.io/
- Basic first-party framing of Fluid as a borrowing and lending product surface.
- Useful mainly as the public landing page and canonical URL.
-
Technical docs root / contracts overview — https://docs.fluid.instadapp.io/
- Best concise architectural source.
- Establishes that the Liquidity layer is the core contract holding funds, while Lending, Vault, DEX, and stETH redemption sit on top.
-
Technical docs markdown — https://raw.githubusercontent.com/Instadapp/fluid-contracts-public/main/docs/docs.md
- Strongest source for the internal design language.
- Important for confirming that Liquidity sits at the center, fTokens are created by
LendingFactory, vaults byVaultFactory, and that the liquidity core uses the Instadapp Infinite proxy.
-
Understanding Fluid: Key Concepts and Practices — https://docs.fluid.instadapp.io/integrate/understanding-fluid-key-concepts-and-practices.html
- Useful for token-listing flow, dynamic borrow/withdrawal limits, gas-optimization philosophy, and the protocol’s own explanation of how new fTokens and vaults are deployed.
-
Vault whitepaper — https://fluid.guides.instadapp.io/vault-protocol/protocol-details/vault-whitepaper.md
- Most useful mechanism document for the vault layer.
- Explains the Uniswap-v3-inspired tick/slot liquidation design, branch-based liquidation accounting, higher-LTV ambition, and oracle design.
-
Vault whitepaper query answer — https://fluid.guides.instadapp.io/vault-protocol/protocol-details/vault-whitepaper.md?ask=What%20is%20the%20core%20liquidation%20mechanism%20and%20why%20does%20Fluid%20claim%20it%20can%20support%20higher%20LTVs%3F
- Helpful concise confirmation that Fluid groups positions by debt-to-collateral ratio into slots/ticks, liquidates only what is needed, and ties that design to the claim that vaults can support up to 95% LTV.
-
Liquidity variables / auth model — https://docs.fluid.instadapp.io/autogenerated-docs/liquidity/common/variables.sol/abstract.Variables.html
- Important because it makes the governance surface explicit.
- Confirms governance can add/remove auths and guardians, that governance is auth/guardian by default, and that listed liquidity tokens are append-only once configured.
-
Liquidity admin module — https://docs.fluid.instadapp.io/autogenerated-docs/liquidity/adminModule/main.sol/abstract.FluidLiquidityAdminModule.html
- Useful for showing that governance, auths, and guardians can configure revenue, token configs, auths, guardians, and allowances.
-
Vault factory auth module — https://docs.fluid.instadapp.io/autogenerated-docs/protocols/vault/factory/main.sol/abstract.VaultFactoryAuth.html
- Critical for the real control surface.
- Shows owner/auth-managed allow-listed deployers, global auths, vault-specific auths, allowed deployment logic, and an arbitrary-call
spellfunction for owner/governance.
-
Protocol repository README — https://raw.githubusercontent.com/Instadapp/fluid-contracts-public/main/README.md
- Best public repo-level statement that Fluid is a combination of DeFi protocols with a liquidity layer at the core.
-
Governance repository README — https://raw.githubusercontent.com/Instadapp/fluid-governance/main/README.md
- Short but useful source showing the governance stack is forked from Compound Governance.
-
Governance forum — https://gov.fluid.io/
- Useful as evidence that Fluid has an active governance/discussion surface beyond the contracts repo.
Why it stays in the active corpus
- Strong comparison class for protocols that fuse lending, DEX routing, and collateral management through a single liquidity core.
- Useful contrast with Euler/Morpho/Silo-style modular lending because Fluid centralizes a shared balance sheet more aggressively and then reintroduces control through auth/governance, factories, allow-listed deployers, and append-only listings.
- Adds a valuable liquidation-design comparison because the vault layer borrows Uniswap-v3-style tick intuition to change how lending liquidations are batched and minimized.