Skip to content
QORECHAIN
Register

Post-Quantum dApp

Qwakk DEX + Pond Vault

Simple swaps on QoreChain. The fees stay locked until ML-DSA-87 says yes.

Share on X

About

Qwakk is a simple, non-custodial DEX on QoreChain. It trades on the chain's own native AMM (x/amm), and every wallet action is signed in QoreX with a hybrid secp256k1 + ML-DSA-87 signature. Qwakk never holds keys: the server only builds and simulates each transaction, so a swap that would fail is explained before the wallet opens. Around the swap screen: on-chain quotes, a price impact guard, pool pages with candle charts from our own indexer, and liquidity tools. For Build Before Q-Day we built Pond Vault, a vault on the QoreChain EVM for the DEX's interface fees (QOR, fUSD, fETH, fBTC). Fees are exactly what an attacker with a leaked ECDSA key goes after. In Pond Vault every withdrawal and rule change needs an ML-DSA-87 approval, checked on chain by the pqcVerify precompile against the owner's key from pqcKeyStatus (with proof of possession), sent through a scoped EVM window, behind a timelock and a daily cap. A guardian can only pause or cancel. Built for QoreChain traders, and for builders who want a working pattern for post-quantum treasury control.

How it's made

BEFORE THE FEST (29 Aug to 31 Oct 2026, disclosed so the fest work can be judged on its own) Next.js on Vinext with server routes, so the browser never hits chain endpoints directly. @qorechain/sdk builds x/amm messages (swap, create pool, add and remove liquidity); the server simulates them on Diana and the browser hands them to QoreX signAndBroadcast, which adds the ML-DSA-87 layer. Quotes come from the chain's QuoteExactIn endpoint, swaps over max_swap_impact_bps are blocked. A Node indexer writes pools, swaps and candles to PostgreSQL and backfills through CometBFT tx_search when Diana prunes blocks. Assets: QOR plus fUSD, fETH, fBTC and IBC ATOM. DURING THE FEST (from 4 Nov 2026) Repository made public under MIT. Pond Vault, in contracts/: - PondVault.sol: approvals sign a domain-separated 203-byte message (chain id, vault, action, token, recipient, amount, sequential nonce, deadline), so they cannot be replayed across chains, vaults or actions. The contract reads the approver key live from pqcKeyStatus (0xA02), requires ML-DSA-87 plus proof of possession, and verifies with pqcVerify (0xA01). Both checks fail closed. - Timelock (60 s to 30 days) with a 7-day grace period, a daily cap per token, reentrancy guard, events for every action. - Foundry: 53 unit tests, 9 fuzz tests and 3 invariants, using real ML-DSA-87 vectors that we also verified against Diana's live pqcVerify. - Owner CLI (viem, @qorechain/sdk, @qorechain/evm, @qorechain/pqc): registers the PQC key, opens scoped EVM windows (allowedTargets = the vault), deploys, signs approvals and runs a live smoke test. - Read-only /vault dashboard in the app, threat model in contracts/README.md, CI job for the contracts. - Testnet deployment, live smoke run and the QCAI audit: in progress. HARD PARTS QoreX 0.3.5 refused plain signDirect, so every action moved to signAndBroadcast. Simulation runs without the ML-DSA-87 signature, which adds about 77k to 91k gas, so we add headroom. In the SDK the precompile addresses are not valid EIP-55 checksums and the pqcKeyStatus ABI misses possessionProven; we found both while testing. Scoped windows refuse contract creation, so deploy needs its own window first.

Timeline

Qwakk DEX + Pond VaultPost-Quantum dApp

Pushed 2 commits to main

  • 76313fd feat(mobile): guide phone users into QoreX and make swaps one tap · AltayDev
  • 31cefda docs(vault): record QCAI audit stage 1 and our responses · AltayDev
Qwakk DEX + Pond VaultPost-Quantum dApp

Pushed 1 commit to main

  • 0e2ce0c docs: document the live testnet launch and the Build Before Q-Day entry · AltayDev

Comments and questions

  • No comments yet.