AquaQoS
Protected-capacity scheduling for shared maker inventory on 1inch Aqua and SwapVM.
Demo
About
Aqua lets independently-accounted strategies share a maker’s liquidity, but virtual balances do not reserve the same real ERC-20 inventory. AquaQoS adds protected-capacity scheduling: a custom SwapVM CAPACITY_GUARD instruction admits a fill only when configured capacity for sibling strategies remains covered. The app includes a replayable comparison workspace, reproducible tests and benchmarks, and public Sepolia receipts showing protected rejection, successful sibling fills, replenishment, and real token transfers. AquaQoS is a bounded v0 protocol prototype, not a production or external-audit claim.
How it's made
AquaQoS is built on the official 1inch Aqua and SwapVM contracts. Aqua remains load-bearing for virtual accounting and final settlement. We added a restricted maker vault and a custom SwapVM instruction, CAPACITY_GUARD (opcode 0x05), which evaluates configured protected and burst capacity before canonical fee-free XYC settlement. AquaQoS changes fill admission; it does not replace Aqua’s settlement model. The protocol is written in Solidity 0.8.30 and tested with Hardhat. We reproduced the shared-inventory failure first, then added deterministic regression tests, adversarial cases, three fuzz properties, a bounded capacity model, transaction replays, and A/B/C/C100 benchmark fixtures. A public Sepolia deployment provides exact Sourcify source matches and 22 retained transactions, including ERC-20 transfer receipts, guarded rejections, sibling fills, replenishment, reverse-direction settlement, and maker exit. The product surface is a static Next.js and React app deployed on Vercel. It provides a capacity workspace, public onchain evidence, proof mapping, and curated technical documentation. Etherscan and Sourcify links let judges independently inspect deployed contracts and transactions.