Implemented the MAD website and static export with verified contract integrations.

Build/typecheck passed, plus 58 browser checks, 34 live checks, 44 contract tests and 16 design checks. Submission content is 5.66 MiB; dependencies and caches are excluded.

Trading remains closed with no active liquidity. No real transactions were sent. WebKit testing was unavailable.

See README, DESIGN.md and validation.

I found one high bug: the Trade page refuses to quote a buy against the live pool's actual state. Besides that there are three low findings. All four are in .imd-findings.json, and I changed no tracked files.

Requirements

• "Explain the project's actual purpose, rules and risks": met. The How it works page (Protocol.tsx) covers freeze cost, burns, the 24-hour lock, round rules and the oracle. It also warns that freeze has no maximum-cost parameter.
• "Use the verified addresses and exact units/decimals": met. The addresses come from web/src/deployment.json. chain.ts:111-130 checks the hook's links (bound, mad, rewards, receiver, hub, projectId, project) against them before showing anything.
• "Confirm this is the registered receiver": met. chain.ts:118-130 reads receiver.playground(), receiver.projectId() and hub.projects(1).receiver.
• Supported actions only (freeze, round closure, oracle, award, NFT acquisition, claim, payout, flushBurn): met (Freeze.tsx, Rounds.tsx, Protocol.tsx).
• "Support buying and selling against its actual base currency": broken. The quote is blocked whenever in-range liquidity is zero, which is the live pool's state (Trade.tsx:52, trading.ts:91).
• "Native ETH only when a verified route supports it": met. There is no ETH route, and the page says so (Trade.tsx:390).
• "User-selected slippage, nonzero minimum output, unexpired deadline": met. Both start empty, and minimumOutput rejects a zero minimum.
• "Show the precise spender and amounts before approval": met. Both the Permit2 and router spenders are shown in full.
• "Handle stale quotes and insufficient liquidity": stale quotes are met (they expire after 30 seconds). Insufficient liquidity is broken: it is decided by the wrong signal (see the high finding).
• "Live public state", connected-wallet positions, and "recent verified events with transaction links": met (Freeze, Rounds, and Activity paged by block range).
• "Distinguish loading, empty, stale and RPC-error states": met (main.tsx:139-197). A balance whose read failed shows "Unavailable", never 0.
• "Read current permissions onchain before showing controls": met. Manage.tsx reads the hook and rewards owners, and states that the project creator and Playground owner get no admin rights by default.
• "Read-only browsing, connect/disconnect, correct network": met. There is a wrong-network notice (main.tsx:173) and writes are disabled off chain 1.
• "Simulate, explicit confirmation, no duplicate sends": met in its structure (transactions.tsx). Nothing past a signature could be tested without a wallet.
• "Distinguish held funds from claimable": met. Receiver-held FWA and ETH are listed separately from claims (Protocol.tsx:237-247).
• Hub and receiver fee flow (depositETH, swapToETH, the split): met as explanation, with no payment UI added (Protocol.tsx:277-298).
• "Accessible, mobile-friendly navigation": met. The site has a skip link, two-row mobile navigation, and focus moves on route change.
• "Do not redeploy … create new fees": met.
• Hosting and deploy: after review.

The idea: a dark ledger-style dapp for a token game where one snowflake mark and an orange freeze action carry the whole site. I found no competing visual devices.

Findings

1. High. bug: the Trade page blocks every quote while the launch pool's liquidity sits just above the current price (web/src/Trade.tsx:52, `web/src/trading.ts:

All four findings reproduced and are fixed. The changes stay small and the rest of the accepted work is untouched.

High: buy quotes were blocked when in-range liquidity was zero. The report was right. I read the pool on the live chain:

• The price sits at tick -62150.
• getLiquidity returns 0.
• Tick -62100 carries about 4.03e25 of liquidity, which is the launch MAD position just above the price. A buy crosses into it and fills.

The fix:

• Trade.tsx: removed the "no active liquidity" notice and the check that disabled the quote button.
• trading.ts: quote() no longer refuses on zero in-range liquidity. It still refuses an uninitialized pool.
• validateQuote(): this pre-write check had the same gate and would have blocked the approvals and the swap even after a quote, so I removed it there too.
• Error message: the Quoter simulation now decides. If it reverts, the page says "Not enough liquidity in the pool for this amount." I match on the contract-revert error type, so an RPC or network failure isn't reported as a liquidity problem.
• Transaction code: the swap, approval and router calls are unchanged.

Low findings:

• Missing space above "Frozen wallets cannot sell." The cause was a CSS rule with three values where only two are valid (margin-block: 28px 0 12px in styles.css), so the browser ignored it. It is now 28px 12px, and the rendered gap is 28px. Only that one heading uses the rule, so nothing else moves.
• Block window: both block numbers now have thousands separators ("26,248,829 to open"), like the header.
• MAD supply: the exact figure only appears as a second line when it differs from the rounded one, so it no longer repeats.

Checks (all passing):

• Typecheck and production build.
• 59 browser checks. I added one for quoting with zero in-range liquidity and for the Quoter-revert message, and changed the closed-trading check so it no longer expects the old notice.
• The design probe: 16 of 16.
• A render against the live chain at 390 wide confirmed all four fixes.

Limitations:

• Trading is still closed onchain, so a real buy quote can't be shown until the owner calls enableTrading(). The new quote behaviour is tested only with mocked chain data.
• WebKit could not launch on this machine because system libraries are missing.

I rebuilt dist/, which renamed the asset files. I also updated README.md, artifacts/validation.md, and the recorded check results in artifacts/. Answers to all four findings are in .imd-responses.json. I didn't commit anything.

All four findings are resolved. .imd-findings.json contains {"findings":[]}. No application files were changed.

Validation passed: 59/59 Chromium checks, including another run with zero liquidity throughout the trading fixtures; 34/34 live deployment checks; and 16/16 taste checks. Chromium and WebKit passed the targeted interactions at 390px and 1440px. At 390×844, the primary action ends at 750.64px, inside the first screen.

Live reads confirmed tick −62150, zero in-range liquidity and positive liquidity beginning at −62100. Trading remains closed. Successful transaction checks used isolated fixtures; no mainnet transaction was sent.

The site is an Ethereum freeze-and-reward application carried by a snowflake motif, pale surfaces and an orange primary action.

The requirement checklist below groups related clauses without treating unavailable external prerequisites as website defects.