{"workflow":null,"planning":null,"id":"ea03cadf-2bb9-47b5-8393-057877c62f58","state":"blocked","template":"skill:build-contract-project","objective":"Continue 7e9ad980-ce4e-4f84-93a5-0f347e228237.\nChain: Ethereum mainnet only (chainId 1). Kind: univ4_hook. Name SwarmGuard, symbol SWARM.\nDrop the ERC-8004 whitelist, EIP-712 swap gate, and emergency pause. No human admin and no agent admin in this version. Swaps are permissionless.\nHook: beforeSwap/afterSwap fee only. 1.25% on buys and sells in the pool, split 1.00% to remainderTo and 0.25% to LPs. No separate IMD protocol fee.\nEconomics: poolBps 8000, remainderTo the paying wallet. Do not deploy a Node Vault; the swarm 10% is the launch Merkle distributor.\nDo not set a 10 ETH cap; open at the chain policy cap. No stand-in addresses.\nFrontend after contracts are accepted: pool metrics, fee, swap, add/remove liquidity. No live quorum log, because there is no quorum in v1.","blockedReason":"node build_contract_project: needs_input: The paying wallet's Ethereum address for remainderTo and the Ethereum mainnet launch policy cap are absent from the brief and supplied files. The workspace contains only the pinned reads, with no network.json or existing project configuration providing these values. With no human or agent admin and no authorized placeholder, the recipient cannot be guessed or deferred to an owner setter; the chain policy cap cannot be invented. — What are the paying wallet's Ethereum address to use as remainderTo and the authoritative Ethereum mainnet launch policy cap, expressed in wei?","createdAt":"2026-10-08T20:46:37.019Z","updatedAt":"2026-10-08T20:47:59.466Z","paidBy":"0xbbf17c1376eb60bdb4a5821042e4ea1bc9aab21e","parentJobId":"7e9ad980-ce4e-4f84-93a5-0f347e228237","project":{"id":"7e9ad980-ce4e-4f84-93a5-0f347e228237","head":"ea03cadf-2bb9-47b5-8393-057877c62f58","running":null,"versions":[{"jobId":"7e9ad980-ce4e-4f84-93a5-0f347e228237","workflowId":null,"objective":"[SYSTEM / HIGH PRIORITY EXECUTION]\nPROJECT NAME: SwarmGuard\nTOKEN TICKER: SWARM\nTARGET EVM: Ethereum / Base\nPURPOSE: IMD Hackathon Submission (Oct 7 - Oct 21)\n\n---\n\n### FRONTEND INTERFACE SPECIFICATIONS:\n\n- WHAT THE SITE SHOWS: A real-time dashboard displaying the SWARM Uniswap V4 pool metrics, live ERC-8004 agent consensus verification logs, dynamic fee status, and interactive MEV shield activity.\n- WHAT A CONNECTED WALLET CAN DO: Swap SWARM tokens, deposit/withdraw liquidity into the V4 pool, track volume metrics, and claim accumulated trading fee dividends in real-time.\n\n---\n\n### TOKENOMICS & DEPLOYMENT PARAMETERS:\n\n1. TOKEN SPECIFICATIONS:\n   - Name: SwarmGuard\n   - Symbol: SWARM\n   - Total Supply: 1,000,000,000 (18 decimals, fixed single mint, zero minting/pausing/limits after deployment).\n\n2. ALLOCATION & DISTRIBUTION:\n   - 10% Allocated to the IMD Swarm Node Vault.\n   - 10% Allocated to Creator Wallet.\n   - 80% Paired with ETH to seed initial Uniswap Liquidity Pool (Target Opening Market Cap: 10 ETH).\n\n3. TRADING FEE STRUCTURE:\n   - Base Trading Fee: 1.25% on transfers/swaps.\n   - Fee Split: 1.00% Claimable by Creator, 0.25% Protocol Fee to IMD.\n\n---\n\n### CORE SMART CONTRACT & HOOK ARCHITECTURE:\n\n1. HOOK INTEGRATION (`SwarmGuardHook.sol`):\n   - Implement Uniswap V4 `IHooks` interface (`beforeSwap`, `beforeInitialize`).\n   - Integrate ERC-8004 signature validation directly into swap execution routines.\n\n2. SWARM CONSENSUS & DYNAMIC PROTECTION:\n   - Require EIP-712 / ECDSA cryptographic signatures signed by authorized IMD Swarm Agent nodes for high-volatility swap validations.\n   - Dynamic Fee Shield: Allow Swarm agents to temporarily scale pool protection fees up to a capped rate when toxic order flow or MEV sandwich attacks are detected on-chain, mitigating Loss-Versus-Rebalancing (LVR) for LPs.\n   - Circuit Breaker: Emergency pause functionality callable exclusively through IMD Swarm Agent quorum consensus (zero human admin keys).\n\n---\n\n### REQUIRED OUTPUT DELIVERABLES:\n\n1. Complete, gas-optimized Solidity contracts for SWARM token and SwarmGuardHook.sol.\n2. Automated Foundry test suite (`SwarmGuardHook.t.sol`) validating ERC-8004 signatures, fee routing, and attack resistance.\n3. Automated deployment sequence to initialize the pool at a 10 ETH market cap.\n4. Generated web frontend reflecting the interface specifications above.\n5. Technical `README.md` documenting the zero-human governance architecture for IMD Radar indexing.\n\nEXECUTE SPECIFICATION, GENERATE FRONTEND, AND PREPARE ON-CHAIN DEPLOYMENT NOW.","baseCommit":"0243d7da4a4337ae8b16bcdf15bb4ead736fd68f","state":"blocked","createdAt":"2026-10-08T19:42:39.610Z"},{"jobId":"ea03cadf-2bb9-47b5-8393-057877c62f58","workflowId":null,"objective":"Continue 7e9ad980-ce4e-4f84-93a5-0f347e228237.\nChain: Ethereum mainnet only (chainId 1). Kind: univ4_hook. Name SwarmGuard, symbol SWARM.\nDrop the ERC-8004 whitelist, EIP-712 swap gate, and emergency pause. No human admin and no agent admin in this version. Swaps are permissionless.\nHook: beforeSwap/afterSwap fee only. 1.25% on buys and sells in the pool, split 1.00% to remainderTo and 0.25% to LPs. No separate IMD protocol fee.\nEconomics: poolBps 8000, remainderTo the paying wallet. Do not deploy a Node Vault; the swarm 10% is the launch Merkle distributor.\nDo not set a 10 ETH cap; open at the chain policy cap. No stand-in addresses.\nFrontend after contracts are accepted: pool metrics, fee, swap, add/remove liquidity. No live quorum log, because there is no quorum in v1.","baseCommit":"0243d7da4a4337ae8b16bcdf15bb4ead736fd68f","state":"blocked","createdAt":"2026-10-08T20:46:37.019Z"}]},"deliver":true,"host":false,"site":null,"launch":{"requested":false,"kind":null,"id":null,"status":null,"chainId":null},"oracleRequestId":null,"delivery":null,"media":null,"nodes":[{"key":"build_contract_project","role":"implement","state":"failed","attempt":1,"revisions":0,"judgeRevisions":0,"dependsOn":[],"allowedPaths":[],"failureReason":"needs_input: The paying wallet's Ethereum address for remainderTo and the Ethereum mainnet launch policy cap are absent from the brief and supplied files. The workspace contains only the pinned reads, with no network.json or existing project configuration providing these values. With no human or agent admin and no authorized placeholder, the recipient cannot be guessed or deferred to an owner setter; the chain policy cap cannot be invented. — What are the paying wallet's Ethereum address to use as remainderTo and the authoritative Ethereum mainnet launch policy cap, expressed in wei?","dispatchNote":null,"dispatchNoteAt":null,"updatedAt":"2026-10-08T20:47:59.466Z","verdict":null,"seat":null,"live":null}],"reviews":[{"status":"queued","chainId":1,"txHash":null,"blockNumber":null,"sentAt":null,"entries":[]}]}