Search projects, hackathons, sponsors and tech

    ← All projects

    Aqua Mux

    AquaMux atomically builds token baskets and registers shared-liquidity Aqua LP strategies.

    Demo

    About

    AquaMux is a local-first EVM liquidity-management application for 1inch Aqua shared-liquidity positions. It helps a wallet owner create, review, and manage versioned LP plans that reference inventory already held in their wallet. One wallet's inventory may back multiple strategies, so fills in one position affect the inventory available to others. The Next.js app supports Ethereum, Arbitrum, BNB Chain, and Robinhood Chain. Its managed workspace covers strategy configuration, observed positions, activity, browser-bound management runs, pause and close planning, and review history stored in local SQLite. Plans can contain one to six token pairs, pair-specific fees, reserve amounts, price denomination, ranges, and optional expiry. AquaMux separates planning, review, signing, broadcast, receipt recovery, and confirmation. The owner must explicitly confirm fund-moving actions. External-wallet execution is restricted to a named, tested adapter, while ordinary browser wallets remain manual-signing only. The project also retains a basket swap flow that can compose one input token into two to six outputs, with wrapping, token approvals, 1inch Classic Swap routing, and supported EIP-5792 wallet batches.

    How it's made

    AquaMux is built as a TypeScript monorepo with a Next.js 16 and React 19 frontend. Tailwind CSS handles styling, Base UI provides accessible primitives, Lucide supplies icons, and TanStack React Query manages client-side server state. Zod validates API input and DTOs at every trust boundary. The EVM layer uses viem, wagmi, and 1inch's Aqua SDK, SDK Core, and SwapVM SDK. The app maintains its own reviewed network and token configuration for Ethereum, Arbitrum, BNB Chain, and Robinhood Chain rather than trusting browser-provided contract addresses or metadata. It uses bigint for on-chain quantities, builds immutable transaction inputs, and separates simulation, approval, signature, submission, receipt recovery, and confirmation.