Approved workflow

Release Match (ERC-20 symbol MTCH) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Match (MTCH), total supply 1,000,000,000 MTCH with 18 decimals, minted once to the deployer. Application contract: QuadraticFunding. Currency: MTCH is the app's working currency. QuadraticFunding takes the MTCH address as its only constructor argument (constructorArgs ["$token"]), stores it immutable, exposes it as token(), and holds no MTCH at deploy; contributors get MTCH by swapping Sepolia ETH in the launch pool the factory seeds. Every payment in is approve + SafeERC20.safeTransferFrom (permit not required). QuadraticFunding has no payable function and no receive/fallback, so it never holds ETH. Payouts are pull-based (the recipient calls to collect; nothing is pushed to third parties), follow checks-effects-interactions and are nonReentrant. No owner, admin, pause or upgrade path. Quadratic funding rounds in MTCH. createRound(start, end): anyone; start >= block.timestamp, end - start between 1 day and 30 days. fund(roundId, amount): anyone adds to the matching pool until end; funders are recorded. register(roundId, payout): the round's creator only (rounds are curated, so strangers cannot fill the cap), before end, at most 50 projects per round, payout != address(0). contribute(roundId, projectId, amount): only in [start, end), amount >= 1 MTCH; each contributor's total per project accumulates, and the contract keeps sumSqrt[p] = sum over contributors of sqrt(total), updated incrementally (sumSqrt += sqrt(new) - sqrt(old)) with OpenZeppelin Math.sqrt (floor) on base units. After end, finalize(roundId) (anyone, once) computes q_p = sumSqrt[p]^2 and Q = sum q_p over the round's projects; match_p = Math.mulDiv(pool, q_p, Q) (floor); the rounding remainder goes to the project with the largest q_p (lowest id on ties), so the whole pool is always distributed. If Q == 0 (no contributions), each funder can reclaim their own funding. claim(roundId, projectId): only the project's payout address, once, after finalize; transfers contributions + match to it. The README says the round creator curates the project list and that QF is sybil-able (splitting contributions across addresses raises the match) and that no identity check exists on Sepolia. Views: round(id), project(roundId, pid), contributionOf(roundId, pid, account), estimateMatch(roundId, pid) (live estimate), token(). Events: RoundCreated, Funded, Registered, Contributed, Finalized, Claimed, Reclaimed. Tests (Foundry) must cover: integer square root edge cases, incremental sumSqrt matching a from-scratch recomputation, the whole pool distributed exactly (sum of matches == pool) under fuzzed contributions, Q == 0 reclaims, the 50-project cap, register by a non-creator reverting, double claim, and time-window boundaries. The independent adversarial review must attack: match arithmetic overflow (sumSqrt^2 times pool), registration by anyone but the round creator, rounding that leaves or over-spends pool dust, claiming before finalize or twice, contributions outside the window, and the sybil and creator-curation trade-offs being stated. Deploy through the project factory, then publish a one-page website to create a round, register a project (round creator), contribute, fund the pool, finalize, claim and reclaim, and show each project's contributions and live match estimate. The page reads the MTCH address from QuadraticFunding.token(), shows the connected wallet's MTCH balance and allowance, has an Approve step before every paying action, and says that MTCH comes from swapping Sepolia ETH in the launch pool (no in-page swap). Lists come from contract views and events only (no backend, no indexer). Keep it to one small page; the static export has index.html in dist/.

Sepolia (11155111) only. GitHub publication and IPFS hosting are approved. Launch token: a separate fixed-supply ERC-20, 18 decimals, no constructor arguments, exactly 1,000,000,000 minted to msg.sender, no mint or admin functions. The factory sends that supply to LP and rewards, so no application contract may need a launch-token balance at deploy. Application contracts are fully configured in nonpayable constructors using only address, uint, bool or bytes32 arguments (no strings, arrays, proxies, delegatecall or selfdestruct); anything else is set at runtime. No owner unless the request names one, and then it is $owner. No external oracles, VRF or keepers: randomness is commit-reveal or a future blockhash read within 256 blocks with a refund path. foundry.toml sets bytecode_hash = "none". The website is a static export with index.html in dist/. Site label lab-quadratic-funding.

Build MTCH and QuadraticFunding (QuadraticFunding takes constructorArgs ["$token"]; contributions and matching pools are MTCH) with Foundry tests and an independent adversarial review, deploy them through the project factory, then build the one-page website against the live deployment.

One static page, no framework beyond what the skill needs, reading the live deployment's ABI and address. Approve MTCH before paying; show MTCH balance and allowance.