Deep Dive
1. Purpose & Core Mechanics
Liquity is a decentralized borrowing protocol. Users deposit collateral—Ethereum (ETH) or liquid staking tokens like wstETH and rETH—to mint stablecoins. Its first version, Liquity V1, issued the LUSD stablecoin with a unique model: zero-interest loans, a one-time borrowing fee, and a minimum collateral ratio of 110%. The system is secured by a Stability Pool of LUSD and by borrowers collectively acting as guarantors.
The upgraded Liquity V2 introduces the BOLD stablecoin and key innovations. Borrowers can now set their own interest rates, creating a market for loan pricing. If BOLD de-pegs, the protocol redeems debt from the troves with the lowest borrow rates first, a mechanism known as "friendly liquidations."
2. Technology & Design Philosophy
Built on Ethereum, Liquity is designed to be governance-minimized, non-custodial, and immutable. Once deployed, its smart contracts cannot be altered or upgraded by any party, including the development team (Liquity). This eliminates centralization risks like admin key abuse or arbitrary parameter changes.
The protocol encourages a network of "friendly forks" through a Business Source License, with over 15 planned deployments across chains like Arbitrum and Berachain (Gate.io). This strategy aims to expand BOLD's utility and liquidity in a decentralized manner.
3. The LQTY Token
LQTY is the secondary token of the ecosystem. Its primary utility is fee capture and governance. In V1, stakers earn rewards from loan issuance fees and liquidation proceeds. In V2, stakers gain enhanced governance: they vote weekly to allocate 25% of protocol revenue (the PIL) to liquidity initiatives across DeFi, directly influencing BOLD's adoption and stability (Liquity).
Conclusion
Liquity is fundamentally a crypto-native lending primitive that prioritizes decentralization and immutability, offering overcollateralized stablecoin loans through an automated, trust-minimized system. Will its immutable design and community-driven liquidity incentives in V2 be enough to drive widespread adoption against more flexible competitors?