A liquidity provider should not have to bridge and swap assets manually before funding a position. The destination may require a particular asset on a particular chain, while the capital is held elsewhere. Aqua0 has brought that funding path into its application through Trustware. Users can start from supported holdings and settle directly into an Aqua0 asset vault, with routing, conversion and the destination deposit handled within the funding flow.
What Aqua0 built
Aqua0 builds liquidity infrastructure for stablecoin and RWA issuers, and for the providers, strategists and traders working around them. An issuer can launch with sound mechanics and still have nowhere to trade at depth, because liquidity has to be assembled venue by venue and pool by pool, with capital committed separately to each one. Aqua0 approaches that from the supply side: make one pool of committed capital serve many places.
The unit is an AssetVault, one per asset on each chain. A provider who locks liquidity is credited with principal, a claim denominated in the underlying asset rather than a tradeable share token, and it sits in the vault's shared idle pool until the provider consents to back a specific strategy. That backing is a non-transferable, read-only position, not a circulating token. A provider's stake stays measured in the asset they locked, and capital is committed deliberately rather than swept into whatever the vault is running.
The payoff is capital that is available rather than parked. Rather than funding a separate position in every pool a strategy might quote on, Aqua0 keeps the backing in one place and draws on it when a trade needs it. Its adapters do that across two systems on EVM chains. On 1inch Aqua, virtual balances describe the liquidity available to a strategy without a funded pool behind it, and Aqua0's AquaAdapter pulls and pushes tokens against the vault mid-swap. On Uniswap v4, Aqua0's V4Adapter is the pool's hook, adding a temporary range at beforeSwap and settling the net movements back to the vault at afterSwap. The same committed balance backs both at once, so nothing is split or locked per venue.
On Solana, the same model reaches Orca and Raydium with one adapter for each venue. The program places the committed collateral in the pool as a position on each provider's own range. The trader swaps through the pool, and the position is withdrawn with its fees before the transaction ends. Both asset vaults then settle on the balances they actually measure. The position never outlives the swap, and the vault owns it the whole time.
Trustware addresses the other side of the system: how capital gets in.
A vault accepts a specific asset on a specific chain and a provider holding something else, or holding it somewhere else, has to close that gap before any capital arrives. The user starts with a supported asset on a supported chain and authorizes the wallet actions the route calls for.
Trustware routes and converts into what the vault accepts, and settles into the Aqua0 vault as part of the same flow.
Delivering the right token to the right chain is only part of the funding journey. Trustware carries the flow through the destination deposit, so the outcome is a credited balance in an Aqua0 vault rather than a wallet balance awaiting another action.
Trustware also changed where the flow starts: Aqua0's Provide flow reads the user's token balances through Trustware and populates what they already hold. A provider picks from their own holdings instead of searching for a token or pasting a contract address, and the funding flow takes it from there.
“Our funding flow has a lot of moving parts. A deposit has to arrive as the right asset, on the right chain, in the right asset vault, and end as a credited balance. Trustware's team made that easy. They were supportive from the start and quick to act on our requests, and changes on their end let us improve our own UX. Our Provide flow now reads a user's balances automatically, so nobody has to go looking for the right token before they fund their asset vault.”
— Yudhishthra Sugumaran (Co-Founder & CTO, Aqua0)
Keeping control with the participant
Trustware does not take custody of funds or sign on the user's behalf. Aqua0's access rules, strategy-consent requirements and withdrawal conditions still govern participation. Funding an asset vault does not replace the consent required to back a strategy, or change the risks of the underlying product.
Aqua0 defines the vaults, strategies and execution rules; Trustware supplies the non-custodial routing and settlement that lets holdings fund the vault.
The result
Aqua0 can keep the asset and network requirements of its vaults while giving participants a connected path from the supported holdings they already have. This integration carries the funding journey through to the vault rather than leaving the user to assemble the route first.
How users arrive and how liquidity operates once they are there are separate problems, and they can be solved separately. Aqua0 built a system where consented capital backs execution across venues, and this partnership makes that system reachable from any balance the users already hold.
Teams building a similar funding experience can explore Trustware's non-custodial routing and orchestration infrastructure at docs.trustware.io
Trustware is the Universal Deposit Layer for onchain applications. Accept any asset. Settle anywhere. Without ever taking custody. Visit docs.trustware.io.