Approved workflow

Release Piggy (ERC-20 symbol PIGY) on Sepolia as an evm_project: the fixed-supply launch token plus one application contract. Token: Piggy (PIGY), total supply 1,000,000,000 PIGY with 18 decimals, minted once to the deployer. Application contract: DonationVault4626. Currency: PIGY is the app's working currency. DonationVault4626's constructor takes one argument, the PIGY address as the asset (constructorArgs ["$token"]); it stores the token immutable, exposes it as token(), and holds no PIGY at deploy and never needs any: users get PIGY by swapping Sepolia ETH in the ETH/PIGY launch pool the factory seeds. Every payment in is approve + SafeERC20.safeTransferFrom; payouts are pull withdrawals (safeTransfer to the caller, checks-effects-interactions, nonReentrant); burns are transfers to 0x000000000000000000000000000000000000dEaD. PIGY is a plain fixed-supply ERC-20 with no transfer fee, so the amount pulled is the amount credited. DonationVault4626 has no payable function and no receive/fallback, so it never holds ETH. No owner, fees, admin, pause or upgrade path. DonationVault4626 is an OpenZeppelin ERC-4626 vault over PIGY with share name "Piggy Vault" and symbol "vPIGY" and _decimalsOffset() = 6 (virtual shares), so the first-depositor inflation attack does not pay. Yield comes only from donations, and donations stream in: donate(amount) pulls PIGY and adds it to a linear 7-day unlock (lockedAmount = unvested(now) + amount, lockEnd = now + 7 days); totalAssets() = PIGY balance - unvested(now), so a deposit placed just before a donation and redeemed just after gains almost nothing. PIGY sent straight to the vault by transfer counts immediately (it cannot be streamed); document it. Rounding follows EIP-4626 (always in the vault's favour); max*/preview* stay consistent with the overridden totalAssets(). A deposit that would mint 0 shares reverts. If every share is redeemed while donations are still vesting, the vested remainder accrues to the next depositors (document). Emit Snapshot(totalAssets, totalSupply) after every deposit, mint, withdraw, redeem and donate, plus Donated(donor, amount, lockEnd). Views: unvested(), lockEnd(), sharePrice() = convertToAssets(10^(18+6)). Tests (Foundry) must show: an attacker who deposits 1 wei and donates before a victim's deposit never profits (fuzz); a deposit-donate-redeem sandwich in one block gains at most rounding; unvested() falls linearly and overlapping donations merge correctly; previews match results; invariant totalAssets() <= PIGY balance. The independent adversarial review must attack: the totalAssets override against every 4626 entry point, rounding direction, stream arithmetic at lockEnd and with overlapping donations, the inflation attack with offset 6, and direct-transfer donations. Deploy through the project factory, then publish a one-page website to deposit, redeem and donate, showing your shares and their PIGY value, the unvested amount and lockEnd, and a share-price history chart from Snapshot events. The page reads the PIGY address from DonationVault4626.token(), shows the connected wallet's PIGY balance and allowance, has an Approve step before every paying action, and says PIGY 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; log queries are chunked from the deployment block). 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-donation-vault.

Build PIGY and DonationVault4626 (ERC-4626 over PIGY, virtual shares, donations streamed over 7 days, constructorArgs ["$token"]) with Foundry tests and an independent adversarial review, deploy them through the project factory, then build the website against the live deployment.

Deposit/redeem/donate with approve, your shares and value, unvested + lockEnd, share-price chart from Snapshot events.