1inch has rolled out Aqua, a shared liquidity layer protocol that lets providers allocate virtual balances from a single wallet across multiple DeFi strategies, all without actually locking their tokens. The protocol now spans roughly 13 EVM-compatible blockchains, including Ethereum, Base, Arbitrum, Optimism, and Avalanche.
How Aqua actually works
Aqua uses a registry-based architecture where virtual balances are tracked per liquidity maker, per application, per strategy hash, and per token. The core contract sits at address 0x499943e74fb0ce105688beee8ef2abec5d936d31 across supported networks, creating a unified system for managing liquidity positions.
Once a strategy is deployed on Aqua, it’s immutable. The protocol builds in flexibility through what 1inch calls “dock-and-ship mechanics,” which allow for updates and modifications without compromising the integrity of the original strategy.
The protocol also integrates with SwapVM, a complementary system designed to enhance strategic liquidity solutions.
Developer access launched on November 17, 2025, with an SDK, documentation, and a bounty program offering up to $100,000 for contributions and bug reports. A public frontend is expected to arrive in Q1 2026, with full deployment across all 13 supported networks expected by mid-2026.
Why capital efficiency matters right now
Aqua’s virtual balance system allows providers to maintain custody of their tokens in a single wallet while still accessing opportunities across all 13 supported chains. Providers never hand over their tokens to a protocol or bridge — virtual balances are accounting entries that represent liquidity commitments without requiring actual token transfers, removing bridge exploit risk from the equation.
Competitive landscape and what investors should watch
The bounty program, maxing out at $100,000, signals that 1inch is investing in developer adoption as the growth engine rather than user-facing liquidity mining campaigns. The Q1 2026 public frontend launch will be the first real test of broader demand beyond the current developer-focused audience.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.

1 hour ago
6









English (US) ·