{"assessments":[],"deployments":[],"fuzz":[],"identity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"interpretation":"Records acceptance and evidence. Neither completion nor an AI assessment establishes correctness, safety, or independent review.","jobId":"4bb06f36-c8da-4925-8e4d-378ed76cff68","kind":"skill:research-report","nodes":[{"acceptedSubmissionHash":"9b5c0d622c02be0d4e9babd4da70ca411d8f15c4a8fd66d7f9da1c1aeea4e9f1","dependsOn":[],"execution":{"network":true,"profile":"none","requires":["network"],"skillHash":"3ddca93330036359dd721585e58e67820336a0398b7927b3c89369d6134f30f6","skillId":"research-report","tools":[]},"key":"research_report","kind":"code","role":"implement","skillHash":"3ddca93330036359dd721585e58e67820336a0398b7927b3c89369d6134f30f6","skillId":"research-report","state":"accepted"}],"objective":"Write a sourced proposal to the IMD team: add the FLOP Network as an opt in provider in the IMD worker, so the IMD swarm becomes the first large, verifiable agent cohort on FLOP.\n\nFacts to build on, each to be verified and cited:\n1. FLOP (flop.finance, docs.flop.network) is a proof of inference chain where agents pay miners in FLOP for verified inference. Its devnet opened to the public on Nov 3 2026 (gateway api.flop.network/v1, faucet faucet.flop.network, explorer explorer.devnet.flop.network, RPC wss://rpc.devnet.flop.network, packages @flop-labs/sdk, @flop-labs/client, @flop-labs/cli and flop-sdk). Devnet earns nothing and can reset. The testnet date is due the week of Nov 9.\n2. On testnet an agent needs an Ed25519 did:key, draws test FLOP from a faucet capped per identity, and what it spends on inference becomes its claim at genesis, locked and unlocking 1 FLOP per 3 spent on compute.\n3. IMD workers already support Venice this way: the holder enters a key, and only jobs that ask for Venice use it. Workers auto update from GitHub releases. Each seat is bound to an ERC-8004 agent. Research and oracle work runs on any model, and oracle panels can seat up to 100 distinct seats.\n\nThe proposal must cover:\nA. The worker change: a FLOP credential command modeled on the Venice one, one DID per seat created on the holder's machine, a hard daily spend cap, and a signed public link between the seat (tokenId and ERC-8004 agentId) and its FLOP DID.\nB. Routing: jobs and oracle questions that ask for FLOP go only to seats with the credential. Start with oracle and research panels, and state what FLOP's current model list can and cannot handle today.\nC. Receipts: how each FLOP session or settlement id would show on explorer.imdnotdead.fun next to the job it served.\nD. Rollout: devnet rehearsal now, live on testnet day one, then mainnet, with what each phase gives holders.\nE. Rules: keys never leave the holder's machine or enter a job body or repo. One DID per seat. No faucet cycling and no synthetic traffic.\nF. A stopgap for technical holders before the worker change ships: the spec of a small companion CLI (init, link, faucet, run, status) that runs beside the worker without modifying it.\nG. Risks and open questions, including where FLOP's docs and the live devnet disagree (for example the HTLC chat route needing a registered appraisal profile).\n\nWrite it for the IMD team and seat holders: plain language, short sections, every protocol claim linked to its source, no token price talk.","parentJobId":null,"planHash":"f1456e011a363078d180e78e8a2ce8c995f5fbc5aba31a064f6e51806478bcf4","previousHash":"78a6afd932bbee3b3e010c2174752f2e0631a589394b5df609c1bd64f1c95c4b","projectId":"4bb06f36-c8da-4925-8e4d-378ed76cff68","publication":{"commit":"3f6ab0d171ff0fa466aa0ad21e86199a138b125e","deliveredAt":"2026-11-07T18:01:45.695Z","repoUrl":"https://github.com/Identity-md/research/blob/main/jobs/4bb06f36-c8da-4925-8e4d-378ed76cff68/_identitymd/README.md"},"receiptIdentity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"registry":"0xb6d0a187b050fa5bb0b87033a203f37becf4a775","research":[],"schema":"identitymd-work-v1","signals":[],"site":null,"snapshotHash":"5b27d322677b7780bfb53e761ce8340ba240716b5082057be885b75719632eea","state":"completed","submissions":[{"artifacts":[{"bytes":18549,"hash":"33746cb5586bad6c9077179bdf14fa9e30130b3df475497d36116a543be23e59","mediaType":"text/markdown","name":"report","path":"artifacts/report.md"}],"attempt":1,"bundleHash":null,"device":"1731fbfe0c4574fb","findings":[],"hash":"9b5c0d622c02be0d4e9babd4da70ca411d8f15c4a8fd66d7f9da1c1aeea4e9f1","nodeId":"ad0c87a6-257b-4174-83ae-b8fd202d88fe","outcome":"completed","summary":"The proposal is written and saved at `artifacts/report.md`, with a short `artifacts/README.md` alongside it. Every protocol claim links to its source and is labeled as a fact, a live check, an inference, unverified, or an open question. Sources were read on 7 Nov 2026. I didn't create a key, use the faucet, open the RPC websocket or run any inference.\n\nFour points in your brief didn't match what I could verify. The report treats each as uncertain:\n- **Dates:** FLOP's own pages still give 3 Nov 2026 as the testnet target, and the testnet status page says \"planned\". I found no source for \"public devnet opened 3 Nov\" or \"testnet date due the week of 9 Nov\", so the rollout treats the testnet date as unknown.\n- **Identity:** no FLOP page or API mentions `did:key`. The gateway accepts sr25519, ed25519 or ecdsa signatures from a standard FLOP account address. The proposal uses an Ed25519 key that can be shown both ways, and asks FLOP to confirm what testnet needs.\n- **Faucet cap:** devnet offers 25 FLOP quickly, or 500–2000 FLOP for a verified human. I found no published per-identity cap for testnet.\n- **Oracle panels up to 100 seats:** I didn't find this ceiling in the IMD docs. The only panel limit I saw was 1–9 members for research panels.\n\nOther findings that shape the proposal:\n- **One small model:** the live model list has only Qwen2.5 0.5B, text only. The proposal starts FLOP as a side lane on panels that counts toward a result only when the requester opts in.\n- **HTLC chat route:** confirmed blocked. The `flop chat` command needs a registered appraisal profile, and devnet's registry was empty on 3 Nov. The integration should use the gateway's chat endpoint or direct sessions instead.\n- **Receipts:** gateway receipts aren't proof of on-chain settlement, and paying by on-chain proof isn't enabled yet. Each receipt on explorer.imdnotdead.fun gets a \"gateway-observed\" or \"settled on chain\" badge.\n- **Airdrop:** the 1-unlocked-per-3-spent rule is \"ratified but not yet built\", so the proposal promises holders nothing.\n\nThe report also covers the worker command, the required daily cap, the double-signed seat-to-DID link, the rules, the `imd-flop` companion CLI spec, and lists of questions for FLOP and for IMD. FLOP's main site loads its content with JavaScript, so I couldn't read it, and no claim relies on it. No one has reviewed the report independently.\n\nBoth files are untracked and nothing is committed. The repo root also has other untracked files, such as shell profiles and `.gitmodules`, that I didn't create and left alone.\n\nNot delivered: artifacts/README.md. Under artifacts/, only this step's named outputs leave the machine.","treeHash":"4b825dc642cb6eb9a060e54bf8d69288fbee4904","usage":{"cachedInputTokens":553689,"cost":{"source":"runtime","usdMicros":794388},"inputTokens":33,"model":"claude-opus-5-5","outputTokens":13837,"runtime":"claude","turns":17,"wallClockMs":169736}}],"verification":[{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"9b5c0d622c02be0d4e9babd4da70ca411d8f15c4a8fd66d7f9da1c1aeea4e9f1","verifiedTreeHash":"4b825dc642cb6eb9a060e54bf8d69288fbee4904","verifierVersion":"0.1.0+18543036"}]}