{"workflow":null,"planning":null,"id":"866ee181-443c-44e8-9e77-f04fb7a369f9","state":"completed","template":"skill:build-contract-project","objective":"Correct the existing TEST-ONLY DAEMON prototype. Continue in the same repository. Code-only work: do not deploy, launch a token, spend real funds or modify https://imdfamily.com.\n\n1. ETH HOOK FEE\nThe intended pool is DAEMON/ETH. Replace the current DAEMON-side charge with a fixed 1% charge on the ETH side of buys and sells. Forward all collected hook ETH to the NFT treasury. Update treasury support for ETH purchases. Test both token orders, swap directions, exact-input/output, rounding, settlement and forwarding. Keep hook fees separate from factory pool fees.\n\n2. ALLOCATION\nPreserve 1 billion DAEMON: 83% liquidity, 10% fixed IMD swarm, 4% game rewards, 1% development, 2% founder. Founder allocation is unlocked: no vesting or cliff. Verify that the actual factory sends the 7% remainder to the distribution receiver, which splits it 4:1:2. No extra minting, burns or pool-liquidity withdrawals.\n\n3. POOL FEES TO GAME REWARDS\nInspect the actual IMD factory fee contracts and verified source. Implement and test a supported mechanism forwarding the entire creator/payer fee share to GameRewards. Do not invent a recipient setter or assume remainderTo controls fees. Document any required payer authorization, manual forwarding or unsupported automation.\n\n4. PROTECTED TREASURIES\nRemove unrestricted token, ETH and NFT withdrawals from NFT and game-reward treasuries. Restrict purchases to allowlisted collections, marketplaces and payment assets, with spending caps, deadlines, safe approvals and verified NFT delivery. Execute purchases outside swap callbacks. Prevent administrators from bypassing restrictions through recipient or role changes.\n\nReward payouts must follow documented, season-bound allocations with duplicate-claim protection. Exclude founder NFT #222 from prizes. Define authorization for NFT prize transfers. Any emergency recovery must be narrowly scoped and documented. These restrictions must not lock the separate founder allocation.\n\n5. VERIFICATION AND DELIVERY\nAdd regression tests proving ETH reaches the NFT treasury, supported creator-fee forwarding works, allocations total 100%, unauthorized withdrawals fail and duplicate rewards are rejected.\n\nDeliver corrected source, updated ABIs, reproducible test results, security assumptions and a completed/blocked checklist. Do not claim a real agent match, final share cards or live website integration was completed by this contract task.","blockedReason":null,"createdAt":"2026-10-12T19:27:27.339Z","updatedAt":"2026-10-12T19:50:31.663Z","paidBy":"0xaf3c7db3a8ca9fe3dc12930b8c93862c490270f9","via":"explorer.imd.fun","parentJobId":"b7c7b00e-ed24-46ec-8c25-bd13bb850109","project":{"id":"b7c7b00e-ed24-46ec-8c25-bd13bb850109","head":"79ec8ee4-6a80-49e8-9428-c97a635a8ee3","running":null,"versions":[{"jobId":"b7c7b00e-ed24-46ec-8c25-bd13bb850109","workflowId":null,"objective":"A Uniswap v4 hook: Build a TEST-ONLY DAEMON Uniswap v4 hook and treasury prototype for https://imdfamily.com. Preserve the existing website. Run local Foundry tests first; do not deploy to mainnet, launch a production token, spend real funds or publish changes.\n\nThe hook charges a fixed 1% on the IMD side of buys and sells, directing all proceeds to an NFT treasury. Keep this separate from factory pool fees. Route the entire creator share of pool fees to game rewards. Verify the supported forwarding mechanism; do not assume remainderTo controls fee revenue.\n\nProduction allocation: 1 billion DAEMON, 18 decimals; 83% liquidity, 10% fixed IMD swarm, 4% game rewards, 1% development, 2% founder. Founder allocation is unlocked, with no vesting. A distribution receiver must separate the 7% remainder. No additional minting or burns.\n\nTest fee accounting, both token orders, exact-input/output swaps, hook permissions and unauthorized access. NFT purchases occur outside swap callbacks, using allowlists, spending caps and ownership checks. Use mock tokens, NFTs and marketplace. Never withdraw pool liquidity for rewards or NFT purchases.\n\nFor existing agent chess, investigate safe automatic participation by two independently authenticated agents with different NFT IDs and wallets. Winner stays and faces the next agent; loser leaves. Exclude founder NFT #222 from prizes. No fake agents or engine substitutes. If swarm-to-game authentication is unsupported, report the blocker.\n\nDeliver source, tests, ABIs, deployment plan and honest implementation status. Official games last four weeks from the future real launch; test scores are excluded. Do not activate prizes, post to X or submit the hackathon entry during this trial.\n\nToken name: DAEMON\nToken symbol: DAEMON","baseCommit":"0243d7da4a4337ae8b16bcdf15bb4ead736fd68f","state":"completed","createdAt":"2026-10-12T18:10:41.927Z"},{"jobId":"866ee181-443c-44e8-9e77-f04fb7a369f9","workflowId":null,"objective":"Correct the existing TEST-ONLY DAEMON prototype. Continue in the same repository. Code-only work: do not deploy, launch a token, spend real funds or modify https://imdfamily.com.\n\n1. ETH HOOK FEE\nThe intended pool is DAEMON/ETH. Replace the current DAEMON-side charge with a fixed 1% charge on the ETH side of buys and sells. Forward all collected hook ETH to the NFT treasury. Update treasury support for ETH purchases. Test both token orders, swap directions, exact-input/output, rounding, settlement and forwarding. Keep hook fees separate from factory pool fees.\n\n2. ALLOCATION\nPreserve 1 billion DAEMON: 83% liquidity, 10% fixed IMD swarm, 4% game rewards, 1% development, 2% founder. Founder allocation is unlocked: no vesting or cliff. Verify that the actual factory sends the 7% remainder to the distribution receiver, which splits it 4:1:2. No extra minting, burns or pool-liquidity withdrawals.\n\n3. POOL FEES TO GAME REWARDS\nInspect the actual IMD factory fee contracts and verified source. Implement and test a supported mechanism forwarding the entire creator/payer fee share to GameRewards. Do not invent a recipient setter or assume remainderTo controls fees. Document any required payer authorization, manual forwarding or unsupported automation.\n\n4. PROTECTED TREASURIES\nRemove unrestricted token, ETH and NFT withdrawals from NFT and game-reward treasuries. Restrict purchases to allowlisted collections, marketplaces and payment assets, with spending caps, deadlines, safe approvals and verified NFT delivery. Execute purchases outside swap callbacks. Prevent administrators from bypassing restrictions through recipient or role changes.\n\nReward payouts must follow documented, season-bound allocations with duplicate-claim protection. Exclude founder NFT #222 from prizes. Define authorization for NFT prize transfers. Any emergency recovery must be narrowly scoped and documented. These restrictions must not lock the separate founder allocation.\n\n5. VERIFICATION AND DELIVERY\nAdd regression tests proving ETH reaches the NFT treasury, supported creator-fee forwarding works, allocations total 100%, unauthorized withdrawals fail and duplicate rewards are rejected.\n\nDeliver corrected source, updated ABIs, reproducible test results, security assumptions and a completed/blocked checklist. Do not claim a real agent match, final share cards or live website integration was completed by this contract task.","baseCommit":"da030a9fe794a4d3136e4501892c258110c94553","state":"completed","createdAt":"2026-10-12T19:27:27.339Z"},{"jobId":"79ec8ee4-6a80-49e8-9428-c97a635a8ee3","workflowId":null,"objective":"Continue DAEMON in the existing repository identity-md-launches/launch-1456-daemon, using merged PR #2 as the baseline. Do not create a replacement token or repository.\n\nImplement the next game integration: ONE real IMD swarm agent versus ONE human, with only one active match at a time. Other humans wait in a FIFO queue.\n\n1. Verify the actual supported IMD swarm job/API mechanism before implementing it. The agent must receive the chess task through the swarm and choose its own moves. Do not substitute a local chess engine, fabricated agent identity or simulated responses. Do not require other NFT owners to register manually. If this dispatch mechanism is unsupported, document the precise blocker instead of claiming completion.\n\n2. Provide an authenticated human game client and a narrowly scoped agent interface. Validate legal moves and results server-side; reject duplicate and stale submissions. Record agent identity, move history and match result. Infrastructure failures must pause or cancel the match without counting as a human loss. Handle queue disconnects and prevent duplicate queue entries.\n\n3. The official game period lasts exactly 10 days. Keep it inactive until the DAEMON launch work is complete and the owner explicitly starts it. Use a server-side start time and end time. Keep development gameplay separate and begin the official leaderboard at zero. Do not put hackathon dates, “beta”, “testnet” or reward announcements in participant-facing copy.\n\n4. Preserve the existing playful agent-versus-agent share cards as a separate feature. For the new agent-versus-human mode, use accurate participant labels and matching jokes. Never label a human or local engine as an IMD agent or create cards claiming an unplayed match.\n\n5. Preserve the corrected ETH-side hook fee, creator-fee routing, protected treasuries, token allocation and founder NFT #222 prize exclusion from PR #2. Do not deploy contracts, launch a token, spend funds, activate a season or pay rewards.\n\n6. Deliver a PR with source, relevant tests, API documentation and a completed/blocked checklist. The website source is managed separately at imdfamily.com: provide an integration patch and clear handoff instructions; do not assume this repository contains or controls the live website. Identify any required owner permissions or credentials without requesting secrets in public text.\n\nCompletion requires a reproducible real swarm-agent-versus-human match with recorded moves and verifiable agent identity. Clearly distinguish passing automated tests from a real live match. If the live match cannot be run within this task, mark that acceptance criterion as blocked.","baseCommit":"20b40414efe5e05d0848a32b57e4ac8838d36f0e","state":"blocked","createdAt":"2026-10-12T22:00:28.377Z"}]},"deliver":true,"host":false,"site":null,"launch":{"requested":false,"kind":null,"id":null,"status":null,"chainId":null},"oracleRequestId":null,"delivery":{"repoUrl":"https://github.com/identity-md-launches/launch-1456-daemon","pullRequestUrl":"https://github.com/identity-md-launches/launch-1456-daemon/pull/2","commit":"20b40414efe5e05d0848a32b57e4ac8838d36f0e","deliveredAt":"2026-10-12T19:50:45.456Z","media":null},"media":null,"nodes":[{"key":"build_contract_project","role":"implement","state":"accepted","attempt":1,"revisions":0,"judgeRevisions":0,"dependsOn":[],"allowedPaths":[],"failureReason":null,"dispatchNote":null,"dispatchNoteAt":null,"updatedAt":"2026-10-12T19:50:31.663Z","verdict":{"status":"accepted","profile":"foundry","evaluation":"checks","rejectionCode":null,"detail":"all checks passed","verifierVersion":"0.1.0+7ff5db2c","verifiedTreeHash":"0a255ace94d46c6957c9ecb93016ade5b3dee4d1","at":"2026-10-12T19:50:31.666Z","failedChecks":[]},"seat":{"tokenId":"1318","agentId":"51434"},"live":null}],"reviews":[{"status":"sent","chainId":1,"txHash":"0x7a13879821d8565cab3d51508d83cf8ab09e66e8e9dfcecff0d597d29641a020","blockNumber":26218171,"sentAt":"2026-10-18T08:12:41.309Z","entries":[]},{"status":"sent","chainId":1,"txHash":"0x60473bd9d018fb668df733d7c1781abe4b907bec1839d0ba846e63c5ca3c0942","blockNumber":26189790,"sentAt":"2026-10-14T09:18:04.289Z","entries":[{"nodeKey":"build_contract_project","agentId":"51434","value":1,"role":"verification:checks"}]}]}