IMD Radar hackathon: all 78 submissions, swarm use and X activity

Research window: October 22, 2026 UTC (October 23 in Adelaide). Event-date analysis: October 7–21, 2026 UTC. This is an evidence review, not an organizer decision or an independent security audit.

Answer

The evidence does not support saying every submission used IMD Swarm or satisfied the launch requirements. The public entry list contains 78 submissions. This review locates identifiable swarm-related records for 64; their scope ranges from full contract builds to review-only work, website work, plain-token deployments and parked launch attempts. 11 remain supported only by entrant claims or insufficiently bound leads; 2 explicitly describe proposed/unbuilt IMD integrations; 1 does not explain its integration. “Record” therefore means evidence of some swarm-related work, not a qualifying working product.

The strongest transaction chains separately inspected in this review are Ouroboros Press (paid IMD chapter → delivered callback → bounty), AskSwarm (paid question → verified-answer path → market settlement → claim), Pinky (paid check → signed verdict → bond payout), and Swarm Harvester (custom batch claim of IMD launch rewards). They are examples of demonstrated functionality, not a prize ranking or a finding that their entire submission packets pass. Other projects may have equally strong evidence that this bounded review did not fully trace.

On X, 76 of 78 submitted project handles returned public profiles. The direct profile-page sample contains 305 author-matched posts, of which 240 fall within October 7–21, spanning 69 accounts. These are sampled observations, not all event posts. 56 entries name a personal handle; 22 omit one; 10 use the same handle for project and person. The 56 personal declarations refer to 52 distinct handles, all resolving through the public account relay; their metadata is included per entry, but separate personal timelines were not sampled. Neither a handle in a form nor a public profile authenticates its controller or identifies the lead developer.

The entry census and submitted statements come from Radar's public submission API, the endpoint actually used by the page's JavaScript. Project-specific corroboration and uncertainties are linked in every entry review below.

Addendum (this revision): the original report text is preserved unchanged; each entry below gains a Timeline and project data (added) block. Method: the entry's Radar submission timestamp and form fields come from the submission API; IMD launch records (creation/update times, chain, status, deployment block, artifact roles, repo and commit) come from the two launch-index responses re-fetched on October 22, 2026, and are attached when an entry's contract field matches an artifact address (38 exact matches in this re-fetch versus 39 reported earlier — the difference is unreconciled) or when the entry's own review cites a launch number. Limits: index timestamps show when the protocol's record was created/updated, not when the entrant first used IMD; indexes reflect state at re-fetch time (later than the submission), so updatedAt values after Oct 21 may be post-deadline changes; entries with no matched record have no stated IMD-use timestamp; the “launch N” cross-reference is a text match and may attach a launch the entry only mentions in passing; the entrant description excerpt is an unverified claim. Job-level timestamps on explorer.imd.fun were not collected in this revision.

Scope, rules and evidence standard

The assignment is to analyse the submissions, treating the quoted launch requirements as the evaluation rubric. This report does not launch a token, send transactions or submit another entry.

The announcement attributed to @surfcoderepeat, October 7 describes submissions on October 7–21, Ethereum/Robinhood/Base launches, and results by October 23. Radar's client code specifies closing at October 21, 23:59 UTC. That establishes the collection site's stated cutoff, not an independently recovered signed organizer ruleset. Its static HTML still contains the entry form; the client replaces it after closing. A cached “entries open” label should not override the dated announcement/code.

There is a prize-description discrepancy: the entry page describes a $10,000 pool, while the announcement advertises $15,000+ in rewards. This review neither reconciles the prize valuation nor assumes a payout occurred. Radar describes itself as a community tool unaffiliated with the identity.md team and says organizers set rules/dates.

The rubric asks for a working event-period launch on an approved network; an active custom hook or meaningful custom contract; a working IMD-dependent feature with code, addresses and invocation evidence; project and lead-developer X accounts; and a public reproducible repository, demo, problem/integration explanation, risks/admin permissions, receiving wallet and reused/event-work disclosure. A standard ERC-20 plus the protocol's initialization guard is not an active custom swap hook. An address is not an invocation receipt. A completed job is not necessarily a deployed launch.

Evidence labels used below:

Label	Meaning	What it does not establish
Observation / fact	A retrieved response, source function, transaction status or log directly supports the statement.	Universal correctness, ownership of accounts, demand, or safety.
Entrant claim	The public submission or project-authored post says it.	Independent verification of delivery, volume, tests or outcomes.
Assessment / inference	This report's interpretation of the evidence against the rubric.	An organizer ruling.
Unknown / unanswered	Evidence was absent, inaccessible, incomplete or not checked deeply enough.	That the claimed work certainly did not happen.

Swarm use is separated into development (writing/adapting code or sites), assurance (tests/reviews), release (protocol deployment/hosting), and runtime (the product buys swarm work or relies on an IMD asset/NFT-specific mechanism). Review of imported code is not evidence that agents wrote the original implementation. Launch manifests, accepted nodes and audit counts are protocol-operator records; they are attributable primary records, not external certification. The official IMD documentation describes paid work, onchain Intake, oracle callbacks and result/signature validation; it also says payment buys admission rather than a guaranteed result.

Census and what can be concluded

The API returned count = 78 and 78 distinct entry IDs/handles. Submission timestamps range from October 7, 22:02:32.938 UTC to October 21, 23:40:08.078 UTC. 64 entries fill the contract field; 14 leave it blank. Submitted chain labels total Ethereum 31, Robinhood 31 and Base 5; these are nonexclusive because imdLend lists three chains and IMD Offset lists two. They are entry metadata, not independent verification of all deployments.

Two paginated public IMD launch-index responses were collected: latest, capped at 500 and older than launch 1166, returning 500 and 403 records respectively, spanning launch numbers 2457 down to 9 with gaps. 39 submitted contract fields exactly match an artifact in those responses. That is an observed match count in this snapshot, not proof the other 25 contract-field entries were not built by IMD: some are external deployments, helper contracts, later addresses, or contracts omitted from protocol artifacts. Additional matches were made only where the prose, repository or specific job supports the relationship. Similar names alone were not accepted as identity evidence.

The assessment categories are deliberately broader than eligibility. In particular:

• Explicit delivery gaps: STEPS reports a prototype and deployment pending; Proof of Silence proposes its IMD extension; After Market Club asks for development support; moneycanbuy.fun says the core protocol was still being deployed; PLEA says mainnet next. The LastSeen launch record is parked, although its work job is completed.
• Plain-token traps: EMBEO launch 944, FINCR launch 2311 and NEETHOME launch 1703 do not themselves deliver the applications described around them. EMBEO and NEETHOME manifests explicitly contain no custom application contracts. FINCR's auction/mining system needs separate deployment evidence.
• Address/version traps: the imdUSD entry field is INFER; Tithe's entry field is a hook; Pupate's entry-field address differs from its stated token; Stock DEX's swarm deployment differs from its entry field; several projects have multiple releases. PERK explicitly disclaims Ethereum launch 1663. A reused name or a protocol factory address must not silently substitute for the intended project.
• Documentation gaps remain: this review did not rebuild every repository, authenticate wallets, verify every admin's current state, watch every demo, or reconstruct every event-period diff. Consequently no blanket “fully eligible” verdict is issued, including for the four transaction-backed examples. Each entry below identifies the next project-specific evidence needed. All also retain the unresolved packet checks in the final section unless explicitly resolved.

Transaction-backed examples

These are read-only explorer/API observations cross-checked with pinned source. Raw responses and a local integrity check are supplied with the research files. Explorer decoding can assign misleading parameter names to a shared event signature; source semantics take priority.

Ouroboros Press — an actual contract customer of the swarm

Launch 2408 records Robinhood deployment at 0xfc65446d2c8a7ee6b173d62db710b76bd8bc978a, pinned to commit 3468a915f68531f4617dba0e7b29a8126e6cac6a. The source pays Intake in commission(), accepts only its pending request from Intake in _settle(), records a chapter in onResult(), and attempts a 0.02 IMD commissioner bounty.

Step	Observed evidence	Conclusion
Commission chapter 1	Successful request transaction, October 21. Intake request ID 0xc07fa2140543836a7a79bac068bb4a1706aa30b0893e7ee2122581ad697dc93d.	A custom contract actually bought work; this was not just holding IMD.
Deliver and reward	Successful completion transaction contains the Press chapter log, IMD transfer of 20000000000000000 units, bounty event, and Intake Completed with delivered=true.	The result callback and 0.02 IMD bounty ran. The request/result hashes bind the steps.
Work provenance	Chapter 1 job identifies seat 1860; chapter 2 identifies seat 766, with the Press as payer.	Different swarm workers produced identifiable paid outputs.

Limit/risk: this proves delivery mechanics, not the truth or literary quality of the chapters. The deployment review reports a hardcoded 0.5 IMD price: an Intake price increase can strand funds in this ownerless contract. Reset can discard late answers. Its four sampled project X posts are dated October 22, after the collection deadline; that is distinct from the October 21 onchain execution.

AskSwarm — the cited request needs three more transactions

Launch 2223 records the deployed contracts; the verified addresses are Registry 0xf3a79f962ec1e75f0087af5491a69dee2a869012 and Market 0x6c95a84944b05e7de5000caef80a7c487aa57cb8. The pinned Registry source checks Intake callbacks and oracle attestations.

Step	Observed transaction	What it proves
Market 3 requests resolution	Entrant-cited resolve(3), October 19, block 92,750,360. Intake receives 0.5 IMD; request ID 0x33f5c2eda0e50f1e5f7df2d82e9984202f9ccc8e562008b1a9d97af3dc0057cc.	A paid question was opened. This one transaction does not prove settlement or claim.
Oracle callback	Completion, block 92,751,060, links that request to oracle request 4f3a459d-5732-4229-8479-04c1249e5f76; Registry answer logs and Intake delivery are present.	The paid request reached its answer-recording callback.
Settle	Market 3 settlement emits phase 3, two 0.1 IMD pools and a 0.002 IMD fee.	Market logic used the resolved path.
Claim	Market 3 claim emits a 0.198 IMD claim.	A participant exercised the payout path.

Assessment: the expanded chain supports working runtime integration. It does not establish unique users, market demand or reliability for arbitrary questions. Registry logs also show later body_refused and disagreed failures; those are evidence of real failure handling, not grounds to portray every request as successful. The first cited transaction's question concerns Bitcoin's genesis date, a demonstration rather than proof of robust prediction-market adjudication.

Pinky — paid oracle verdict changes bond distribution

The launch and source linked in entry 69 identify PinkyVault 0x3c81384aa1ca064316576a214e2fb30969992772 on Robinhood. The pinned source verifies signed attestations, block window and quorum before choosing kept/broken.

For promise 2, the successful ask, October 11, pays 0.5 IMD and emits Intake request 0x22a03095f3a1665e0f469bf10b2afe45f06498761db3810519a18510ad4161fa. Completion links it to oracle 48323d51-a3d8-47fd-a309-b17f8358067e, emits Verdict with kept=true, observedOut=0, and successful delivery. Payout distributes 4.5 IMD back to the maker. The event has a generic signature that the explorer labels as match payouts; the pinned Pinky source names those fields toMaker, bounty, toStakers, burned.

Limit/risk: this demonstrates a kept promise, not the broken-promise watcher/staker/burn path. PinkyVault retains owner setters for protocol, signer and panel on future terms. The oracle and the contract's authorization assumptions still matter.

Swarm Harvester — reward utility without pretending a token alone qualifies

The build/review record identifies SwarmHarvester 0x390f407adad27a0f267479a8449d6a5c6daa93cf, SwarmSeller and the separate HARVEST token. The pinned claimMany source loops over specified official-distributor-style claims, keeping tokens payable to each named account.

The October 9 demo transaction succeeded at block 26,152,645, calls the entered harvester, and its input encodes 40 claim items. All three log pages were collected: 120 logs include 40 harvester per-item results, all with success=true. This supports 40 successful claim calls through the custom batch function, rather than merely 40 submitted items. It does not prove that every item represents a distinct economic reward, or that a later sell/burn ran; the result counts were checked against the logs rather than inferred from the entry.

Assessment: the useful dependency is the swarm's reward-distribution system, even though HARVEST's own launch pool is native-ETH paired. The job's accepted documentation expressly corrects that pairing. Sending tokens to a sink and reducing ERC-20 totalSupply are different burn semantics and should be described accurately.

X / Twitter activity

Method and limits

Direct requests to https://x.com/<submitted_handle> returned profile HTML for 76 handles; two returned HTTP 404. The browsing tool separately refused some X pages, but direct public HTML retrieval succeeded. The extractor decodes embedded GraphQL JSON without executing page scripts, takes outer tweet objects, deduplicates IDs within each page, excludes quoted/retweeted objects authored by others, and filters by exact author handle and UTC date. Most pages expose only five original objects; pins and logged-out truncation make the sample incomplete. It is not a chronological export or a total post count for the event.

The separate public FxTwitter relay supplied profile metadata for 76 handles and individually linked posts for cross-checks. Follower and lifetime-post numbers below are relayed metadata at acquisition, not an authenticated X API export. Direct primary posts supply the event-sample observations. The mirror SSSTwitter returned some additional timelines and failures; these were retained as supplemental evidence but not merged into the primary sample counts, avoiding double counting or silent mixtures of sampling methods.

The period filter is October 7 00:00 UTC through October 21 23:59:59 UTC, a calendar-date interpretation of the announcement. It does not prove that material posted early on October 7 was built after the formal event opening. October 22 posts remain in the evidence files but are excluded from event counts. Engagement is a later snapshot of posts dated during the event, not engagement measured as of the deadline. Views are not unique viewers, summed views are not audience reach, and lifetime counts include pre-event/unrelated activity.

Findings

Observation: the metadata median is 35.5 followers among the 76 resolving handles; 27 have fewer than 10. Existing personal/general accounts such as @tungweb3, @xmrscn and @stockroom carry substantial unrelated lifetime history. Comparing their lifetime post totals with newly created project accounts would misstate hackathon effort. @stepstoke and @pleaimd returned zero posts in the primary snapshot. @ouroborospress_ had four sampled posts, all on October 22; @heroboost_me's project explanation also appears after closing. A zero event sample is not proof an account was inactive or did not exist by the deadline.

Attributable example	Observed activity	Assessment and limit
IMD6900 mint announcement, October 11	103 likes, 3 reposts, 45 replies, 8,620 displayed views.	Largest like count in the bounded primary entrant sample. It promotes Worker Frens, not the submitted LARP release; ecosystem attention must not substitute for evidence about that submission.
imdLend explanation, October 17	55 likes, 11 reposts, 4 replies, 9,144 views; followed by a live announcement with 46 likes.	Specific product communication with an article/demo lead, more informative than a ticker mention. Engagement does not verify rental safety or deployment parity.
IDM launch, October 20	57 likes, 5 reposts, 17 replies, 5,387 views; identifies the actual token and drum-machine hook.	Directly connects the public demo to the entered artifact. A later feature post distinguishes planned stations/subscriptions from the live sequencer.
Pinky explanation, October 10	56 likes, 3 reposts, 45 replies, 2,368 views.	Explains the oracle/bond problem in concrete terms; the receipt chain above independently supports a kept-promise example. Replies are not evidence of independent users or unique supporters.
Radar switches its entry to IMD Vault, October 19	Publicly distinguishes its competition entry from the broader Radar site.	The host/curator is also an entrant. This is a disclosure/context fact; no claim of judging misconduct follows. Its curated homepage is not an impartial all-entry activity sample.
moneycanbuy.fun token launch and core protocol still building, October 21	Separate posts distinguish YOLO from the actual dares/escrow protocol.	Good evidence of development communication and its limit: a launched token does not prove the core product was ready.
Hamster early-access promotion	Asks for a wallet and repost for early access.	An observable engagement incentive. This can inflate response metrics; it is not evidence of bots, fake accounts or misconduct.
HeroBoost's supplied personal-account post	A conditional-tip invitation, not a technical integration walkthrough.	The entry labels it a thread; the retrieved post alone does not substantiate the broader technical claims.

Inference: the observable activity combines product demos, shipping/audit updates, community amplification, speculative promotion and incentives. Posts with a source/job/contract/receipt trail carry more technical information than engagement counts. Unknown: full posting cadence, deleted posts, impression histories, follower authenticity, paid promotion, conversion into independent users, and control of project/personal accounts. No bot, wash-engagement, fraud or plagiarism finding is made from these samples.

Radar's published impact configuration is dated October 8. Its formula uses logarithmic 40% follower reach and 60% engagement, with interactions weighted as likes + 2×reposts + 2×replies. Those are a curator's dated, small-sample scores, not current all-submission rankings. The curated homepage tweet endpoint returned a single October 15 post in this acquisition, another reason not to infer ecosystem-wide activity from a “Today on X” label.

The following 78 entry reviews include each account's followers/lifetime posts and primary event-sample count. 0 is an observed zero in that returned sample; unavailable means the public profile could not be retrieved. The full rows and post-level URLs/text/timestamps are in research/x-activity.csv and research/x-posts.json.

All submissions: individual evidence and gaps

Order follows the API, newest entry first. Each feature summary is the entrant's described mechanism unless the evidence paragraph or transaction section explicitly corroborates execution. Record denotes some corroborated swarm-related work; Claim, Planned and Unclear have the meanings given in the answer. Submitted contract/network fields and personal handles are attributed form data, not proof of ownership, chain approval or contract identity. “Deployment” links below prove the recorded release step only, not a live feature invocation.

01. @imd_optmizer — Claim

Entry 0d13d5af0c4ba452 · submitted 2026-10-21T23:40:08.078Z.

Submitted contract: 0x61cef4f8ab5dc658189e95f1570031d3b50b09a6 · ethereum explorer.

Swarm evidence and scope: No matching optimizer job or launch was found for the submitted address; Sepolia tests and later swarm consensus are entrant claims.

Described IMD feature: MEV detection, arbitrage and IMD routing are described; swarm consensus is a future goal.

Assessment / unanswered: Provide the exact paid swarm job, deployed network and successful custom-logic receipt. The entry reports an X suspension; the submitted handle currently resolves through the relay.

Sources / leads: submission census.

X: @imd_optmizer · 5 followers; 8 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @buildercoin (relay resolves: 13 followers, 73 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T23:40:08.078Z (chronological position 78 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x61cef4f8ab5dc658189e95f1570031d3b50b09a6; declared personal handle @buildercoin.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 858 chars; excerpt): “"The dark forest fights back, but code is immutable. Despite recent coordinated social censorship (X suspension), our architecture remains uncompromising after hundreds of tests on Sepolia. Track our code at GitHub: AlexandreCruz76/imd-optimizer. The IMD Optimizer is a Uniswap V4 Meta-Hook ecosystem driven by four pillars:Anti-MEV Shield: Intercept…” — entrant claim.

02. @stepstoke — Record

Entry 999cc781297f6021 · submitted 2026-10-21T23:36:47.227Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The linked STEPS job records implementation and independent reviews of a release candidate.

Described IMD feature: A funded project relay would commission IMD work and reuse accepted checkpoints.

Assessment / unanswered: The entry explicitly says prototype only, gas-limit blocker, browser issues and deployment pending. Swarm development is supported; a working launch is not.

Sources / leads: job 395064a3 · entrant repository.

X: @stepstoke · 1 followers; 0 lifetime posts (relay metadata). Direct profile sample: 0 authored posts, 0 dated in the event window. Personal handle declared: @goderbug (relay resolves: 282 followers, 1,226 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T23:36:47.227Z (chronological position 77 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @goderbug.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 883 chars; excerpt): “STEPS (Stepstoke) — Build on every step. A public project relay for crypto communities and AI agents, built through IMD. Create a project, propose and fund work, inspect delivered files, continue from previous results, or fork an accepted checkpoint. Sponsors can change while each branch remains the contract payer. Contracts coordinate funding an…” — entrant claim.

03. @swornbyswarm — Record

Entry ad3581d8e84796bc · submitted 2026-10-21T22:49:06.897Z.

Submitted contract: 0x0da2679000ea5380d1361cc3cca7d4e8c881f766 · ethereum explorer.

Swarm evidence and scope: Launch 2404 matches the submitted Registry; the linked workflow records contract construction, reviews, deployment and site work.

Described IMD feature: Wallet traits combine chain reads with paid IMD oracle claims; cards and new specifications charge IMD.

Assessment / unanswered: Need a successful mint/oracle-claim receipt and fee/burn trace. This is an ERC-721 registry rather than a separate ERC-20 coin.

Accepted worker assignments recorded: implement seats #1345; integrate seats #463; review seats #2, #535, #1246, #1295 and others; tests seats #721. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2404 (live) · source c4ff3238 · deployment.

X: @swornbyswarm · 59 followers; 13 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @cryptokarlheinz (relay resolves: 722 followers, 2,858 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T22:49:06.897Z (chronological position 76 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x0da2679000ea5380d1361cc3cca7d4e8c881f766; declared personal handle @cryptokarlheinz.
• IMD record: launch 2404 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-21T18:49:40.094Z, last updated 2026-10-21T18:51:16.808Z; deployment block 26242885; artifacts: other; repo https://github.com/identity-md-launches/launch-2404-renderer-composer-registry @ c4ff323839. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 983 chars; excerpt): “sworn: facts about wallets, onchain and sworn by the swarm an ownerless Ethereum registry: 25 facts built on 19,522 wallets in WhitelistCurator.sol, some read live from the chain, the rest proven by panels of IMD agents and signed - a card (ERC-721, 0.1 IMD, mintable for every wallet) shows a wallet's facts and updates itself - any contract check…” — entrant claim.

04. @requiem__dream — Record

Entry c9af1cb619036513 · submitted 2026-10-21T21:56:08.280Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The Hooks Store has identifiable swarm development jobs. The specific listing-contract job inspected is dated October 22, after closing.

Described IMD feature: The entrant describes a paid IMD hook-building interface and an IMD-priced listing system.

Assessment / unanswered: Separate the pre-deadline working product from October 22 additions. No contract is in the entry; provide a user launch receipt and repository/version for judging.

Accepted worker assignments recorded: implement seats #712; integrate seats #410; review seats #912, #1183, #1836, #1875 and others; tests seats #222. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job c2b72f7e · job 7f951ad8.

X: @requiem__dream · 558 followers; 107 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @requiem__dream (same handle as project) (relay resolves: 558 followers, 107 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T21:56:08.280Z (chronological position 75 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @requiem__dream.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 983 chars; excerpt): “https://the-hooks-store.sites.imd.fun/ A playground for you to design and launch ANY types of hooks, without writing any line of code. The Hooks Store utilizes the IMD swarm to build, test and audit, and deploy hooks in one go. Our simple lego-blocks like UX allows for anyone to visualize and understand what they are building. The Hooks Store ch…” — entrant claim.

05. @Imdirectorb — Record

Entry 3bb7b68fdbfc823a · submitted 2026-10-21T21:53:23.994Z.

Submitted contract: 0xecb5e7f3b9839eb083dda95099b8438ecebec16e · robinhood explorer.

Swarm evidence and scope: Launch 2418 and its audit/deployment job match Director and IMDPhysicalHook on Robinhood Chain.

Described IMD feature: Swap events are intended to trigger commands in a physical-device gateway.

Assessment / unanswered: The launch proves the hook was deployed, not that a device acted. The X demo is a project announcement with media, not an independently verified hardware execution trace.

Accepted worker assignments recorded: implement seats #822; integrate seats #1004; review seats #102, #544, #1176, #1357 and others; tests seats #740. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2418 (live) · source 41e3e33d · deployment.

X: @Imdirectorb · 14 followers; 10 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @DmitryiBond (relay resolves: 69 followers, 177 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T21:53:23.994Z (chronological position 74 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xecb5e7f3b9839eb083dda95099b8438ecebec16e; declared personal handle @DmitryiBond.
• IMD record: launch 2418 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-21T21:37:27.288Z, last updated 2026-10-21T21:38:49.701Z; deployment block 94601188; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2418-review-test-audit-launch @ 41e3e33df7. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 704 chars; excerpt): “IMDirector is an infrastructure layer connecting the IMD token to physical devices. Our gateway turns IMD transfers and smart contract events into commands for electrical appliances. We have deployed the IMDirector token contract and a Uniswap v4 hook for the Director/IMD pool, linking buys and sells to turning a device on and off. We are prepari…” — entrant claim.

06. @byEugenVoyager — Planned

Entry 2ce5c904476bb29f · submitted 2026-10-21T19:43:52.598Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The entrant explicitly calls the IMD integration a proposed extension, not a completed feature.

Described IMD feature: Paid IMD source research and claim review are planned for an existing editorial beta.

Assessment / unanswered: No contract, paid IMD work receipt or completed IMD-dependent path is supplied. Existing AI research alone cannot establish IMD use.

Sources / leads: submission census.

X: @byEugenVoyager · 91 followers; 82 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 0 dated in the event window. Personal handle declared: @byEugenVoyager (same handle as project) (relay resolves: 91 followers, 82 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T19:43:52.598Z (chronological position 73 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @byEugenVoyager.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 835 chars; excerpt): “Proof of Silence is a live beta built around agent-driven research. AI agents discover real-world sources, investigate claims, and turn their findings into source-grounded editorial and literary work. The core is the research process: gathering evidence, checking what sources actually support, and documenting how findings become published work.For …” — entrant claim.

07. @ouroborospress_ — Record

Entry 8b7d12fddde3c2df · submitted 2026-10-21T19:16:27.168Z.

Submitted contract: 0xfc65446d2c8a7ee6b173d62db710b76bd8bc978a · robinhood explorer.

Swarm evidence and scope: Launch 2408 records review and deployment of imported OuroborosPress code; chapter jobs identify separate swarm writers.

Described IMD feature: The contract pays Intake for chapters, records delivered hashes and pays a commissioner bounty.

Assessment / unanswered: A complete paid commission/callback/bounty cycle is corroborated below. Fixed Intake pricing and discarded late results are disclosed audit risks; project-account posts sampled here are after closing.

Accepted worker assignments recorded: integrate seats #1140; review seats #1905. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2408 (live) · source 3468a915 · deployment · entrant repository.

X: @ouroborospress_ · 8 followers; 4 lifetime posts (relay metadata). Direct profile sample: 4 authored posts, 0 dated in the event window. Personal handle declared: @_aaronegeorge (relay resolves: 355 followers, 1,478 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T19:16:27.168Z (chronological position 72 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xfc65446d2c8a7ee6b173d62db710b76bd8bc978a; declared personal handle @_aaronegeorge.
• IMD record: launch 2408 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-21T18:36:35.271Z, last updated 2026-10-21T18:36:46.091Z; deployment block 94495874; artifacts: other; repo https://github.com/identity-md-launches/launch-2408-ouroborospress @ 3468a915f6. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 958 chars; excerpt): “Ouroboros Press is a smart contract that is writing a book about itself, and it pays for every chapter with its own money. Anyone can call commission(). The contract then buys one research-report job from IMD's Intake v2 for 0.5 IMD out of its own balance, asking the swarm to write the next chapter of its on-chain life. The writer calls back with t…” — entrant claim.

08. @LastSeenIMD — Record

Entry 2b6c5c3fcfb46c40 · submitted 2026-10-21T19:15:22.940Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: An exact LastSeenRegistry deployment job exists and records swarm adaptation, tests and reviews.

Described IMD feature: An IMD oracle is intended to validate wallet accusations and bounty leads.

Assessment / unanswered: Its launch is parked despite the job being completed, with a reported lead-seat takeover blocker. Do not treat completed work as successful deployment or the entry's live-registry wording as established.

Accepted worker assignments recorded: implement seats #1368; integrate seats #1979; review seats #97, #358, #461, #658 and others; tests seats #1965. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 492fe9cf · entrant repository.

X: @LastSeenIMD · 6 followers; 2 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @AcayDr (relay resolves: 697 followers, 6,798 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T19:15:22.940Z (chronological position 71 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @AcayDr.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 958 chars; excerpt): “LastSeenIMD is a free tool for people whose crypto wallet was drained. Paste any address: it reads every chain the wallet used (48 EVM chains and Solana), checks every known drain method (stolen key, sweeper bots, EIP-7702 delegations, permit and approval drains, address poisoning), follows the money across bridges to the exchange where it was cash…” — entrant claim.

09. @heroboost_me — Record

Entry bf292a50b8643af9 · submitted 2026-10-21T18:58:23.337Z.

Submitted contract: 0x57ac054c81ac82b95fb8701c0ee2cd94a4df7b35 · base explorer.

Swarm evidence and scope: The submitted oracle job has a signed answer, while the Base receipt reaches the entered Boost Diamond.

Described IMD feature: A Boost is described as binding an IMD yes/no result to conditional funding.

Assessment / unanswered: The oracle question checks HeroBoost's own feature description. The create transaction alone does not prove funds were released conditionally on that answer. Check cross-chain/result binding and proxy permissions.

Sources / leads: job 2c6652c6.

X: @heroboost_me · 3 followers; 4 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 0 dated in the event window. Personal handle declared: @bezu0012 (relay resolves: 90 followers, 144 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T18:58:23.337Z (chronological position 70 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains base; contract field 0x57ac054c81ac82b95fb8701c0ee2cd94a4df7b35; declared personal handle @bezu0012.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 973 chars; excerpt): “HeroBoost lets heroes open IMD oracle questions and bind yes/no outcomes to Boosts on Base—staged token launchpads, conditional tips, and small cause micro funding that follow what the IMD oracle resolves. E.g: Boost #9 binds an IMD yes/no question; the detail page shows the question, expected side, and PASS when the oracle answer matches. https:/…” — entrant claim.

10. @imdradar — Record

Entry addf2a596f14a172 · submitted 2026-10-21T17:34:36.366Z.

Submitted contract: 0xdbaff609cd0500527a2a102f5cbbbbc70fd2ff5b · ethereum explorer.

Swarm evidence and scope: Launches 2244 and 2251 record audited VaultFactory deployments on Ethereum and Robinhood.

Described IMD feature: Projects pay IMD to create constrained treasury/vesting vaults; fees go to an immutable recipient.

Assessment / unanswered: A successful funded lock and permitted/blocked withdrawal receipt is still needed. The fee recipient is a trust boundary; source immutability does not prove how received fees are later spent. Personal handle is omitted.

Accepted worker assignments recorded: implement seats #559, #877; integrate seats #399, #1042; review seats #3, #368, #558, #581 and others; tests seats #286, #911. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2244 (live) · source ccfe47ac · deployment · launch 2251 (live) · source 1ba921a5 · deployment · entrant repository.

X: @imdradar · 991 followers; 208 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T17:34:36.366Z (chronological position 69 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xdbaff609cd0500527a2a102f5cbbbbc70fd2ff5b; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 2251 (referenced in this review): evm_contracts, status live, Robinhood Chain; record created 2026-10-19T17:48:00.172Z, last updated 2026-10-19T17:48:51.457Z; deployment block 92803082; artifacts: other; repo https://github.com/identity-md-launches/launch-2251-deploy-audited-imd-vault @ 1ba921a5d3. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• IMD record: launch 2244 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-19T16:06:24.057Z, last updated 2026-10-19T16:07:26.920Z; deployment block 26227712; artifacts: other; repo https://github.com/identity-md-launches/launch-2244-audit-deploy-imd-vault @ ccfe47ac07. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 946 chars; excerpt): “IMD Vault: a locker nobody owns, so a project's treasury and team tokens can't vanish overnight, as SIMD's did. Live on 2 chains, audited and deployed by the IMD swarm (4 specialists + a judge, 109 tests incl. a fork test on real IMD): Ethereum 0xdbaff609cd0500527a2a102f5cbbbbc70fd2ff5b (launch 2244) Robinhood 0x349056e0e8f333ce3300df09afe44dd8160…” — entrant claim.

11. @SigmoidIMD — Claim

Entry b34710a53d3eca3b · submitted 2026-10-21T17:26:23.902Z.

Submitted contract: 0x51871f67273a56cdbdd8d9a936a98d3032cb60c8 · robinhood explorer.

Swarm evidence and scope: The entry describes fork tests and a live FairLaunchpad, but the address did not match collected IMD launch artifacts and exact-name job searches found no matching build.

Described IMD feature: An IMD launch hook is said to impose dynamic anti-sniper fees, caps and a circuit breaker.

Assessment / unanswered: The referenced SWARMLER launch is the attack comparator, not proof Sigmoid used the swarm. Supply the FairOpenHook job, source pin and live swap/revert receipts.

Sources / leads: project launch post · linked repository.

X: @SigmoidIMD · 20 followers; 18 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @0drayne (relay resolves: 1,745 followers, 7,639 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T17:26:23.902Z (chronological position 68 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x51871f67273a56cdbdd8d9a936a98d3032cb60c8; declared personal handle @0drayne.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 976 chars; excerpt): “Sigmoid is a fair Community Coin launchpad, powered by FairOpenHook, a Uniswap V4 hook that makes launches sniper-resistant. In the replayed SWARMLER #1212 attack, bots extracted 4.39% of supply for dust plus gas. The hook counters this with three mechanisms: (1) dynamic fee 0.30% base, rising to 37.8% at 25% price impact (feeK=150), capped at 90%;…” — entrant claim.

12. @pfwafun — Record

Entry c8e5afcd23c5b3e4 · submitted 2026-10-21T15:32:46.103Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The linked Sherwood v2 audit/deployment job and launch 1389 are identifiable swarm work on Robinhood Chain.

Described IMD feature: An IMD trading pool drives a game pot, points, prizes and token purchases/burns.

Assessment / unanswered: The entry supplies a separate hook and pool, but no full settlement transaction. Match those to the launcher and prove the stated later live pool and payout/burn cycle.

Accepted worker assignments recorded: implement seats #1929; integrate seats #1614; review seats #130, #460, #560, #880 and others; tests seats #205. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1389 (live) · source bd9dc1dd · deployment.

X: @pfwafun · 1,886 followers; 1,544 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @miracleotugo (relay resolves: 2,361 followers, 21,709 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T15:32:46.103Z (chronological position 67 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @miracleotugo.
• IMD record: launch 1389 (referenced in this review): evm_contracts, status live, Robinhood Chain; record created 2026-10-12T10:45:54.455Z, last updated 2026-10-12T10:48:33.925Z; deployment block 86614810; artifacts: other; repo https://github.com/identity-md-launches/launch-1389-audit-deploy-sherwood-v2 @ bd9dc1ddac. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 982 chars; excerpt): “Sherwood turns an ETH/$IMD pool into a PvP arena: a Uniswap v4 hook where every buy is a move. Buy, Steal, Robin Hood, Flip (Dice randomness) or Shield. Points, pot and payouts are all onchain. 5% of every swap’s ETH fills the pot. Each 20-hour round pays the top 3 40/20/10%, 8% to the King of the Hill (longest at #1), burns $IMD with 10%, burns $…” — entrant claim.

13. @tungweb3 — Record

Entry 532a35eda6957602 · submitted 2026-10-21T15:29:17.942Z.

Submitted contract: 0x2b82cdeb8477415d541799abb0cc48044c8ea5f3 · ethereum explorer.

Swarm evidence and scope: The entered EMBEO address matches launch 944, a standard token issuance by the swarm.

Described IMD feature: The entrant reports later audit work for a 3D world and plans holder/game benefits.

Assessment / unanswered: Launch 944 expressly deploys a plain ERC-20 with an initialization-only guard, not a custom swap hook or application. The token deployment alone fails the functionality requirement; later utility needs its own proof.

Accepted worker assignments recorded: implement seats #1434; integrate seats #1673; review seats #826, #1457, #1581, #1763 and others; tests seats #1654. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 944 (live) · source cecf25b9 · deployment.

X: @tungweb3 · 4,610 followers; 10,945 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T15:29:17.942Z (chronological position 66 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x2b82cdeb8477415d541799abb0cc48044c8ea5f3; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 944 (matches submitted contract field): evm_project, status live, Ethereum; record created 2026-10-07T21:19:08.818Z, last updated 2026-10-07T21:20:03.450Z; deployment block 26143156; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-944-emberevo-token-symbol-embeo @ cecf25b92d. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 982 chars; excerpt): “EmberEVO is an independent, IMD-inspired ecosystem built around Ember World (imdember.com), an explorable 3D social town where the IMD community can discover projects, visit themed buildings and connect through avatars. We use IMD Swarm for code reviews and security audits. Planned features include staking $EMBEO in World and playing supported gam…” — entrant claim.

14. @inkandinference — Record

Entry 8a40f89998b5d0c6 · submitted 2026-10-21T15:29:10.793Z.

Submitted contract: 0x45d4cd12ced01d4316a6021387cfdee2fd9491a7 · ethereum explorer.

Swarm evidence and scope: INK launches 2321 and 2305 and the linked contract, hook, testnet, audit and site jobs corroborate extensive swarm work.

Described IMD feature: InkFeeRouter is described as routing IMD revenue to treasury and INK into liquidity, alongside seat-based portraits.

Assessment / unanswered: The entered router address is separate from the main launch artifacts. Verify its source and claimAndRoute receipt; NFT/liquidity contracts retain owner roles in the deployment manifest.

Accepted worker assignments recorded: implement seats #1030, #1925; integrate seats #180, #926; review seats #47, #358, #440, #461 and others; tests seats #39, #1274. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2321 (live) · source 620960b3 · deployment · launch 2305 (live) · source 57970230 · deployment · job 45527f4a.

X: @inkandinference · 103 followers; 37 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @edugrooves (relay resolves: 3,064 followers, 56,702 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T15:29:10.793Z (chronological position 65 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x45d4cd12ced01d4316a6021387cfdee2fd9491a7; declared personal handle @edugrooves; deployer field 0xbc10b3662231c830d2ee10bc6359db17bea4b3d4.
• IMD record: launch 2321 (referenced in this review): univ4_hook, status live, Ethereum; record created 2026-10-20T17:49:05.453Z, last updated 2026-10-20T17:50:39.223Z; deployment block 26235399; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2321-src-inkhook-sol @ 620960b344. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• IMD record: launch 2305 (referenced in this review): evm_contracts, status live, Ethereum; record created 2026-10-20T16:21:36.436Z, last updated 2026-10-20T16:22:25.619Z; deployment block 26234962; artifacts: other; repo https://github.com/identity-md-launches/launch-2305-deploy-nft-vault-liquidity @ 579702304e. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 956 chars; excerpt): “Ink & Inference: 2,000 generative portraits, one for each identity.md seat, drawn from the IMD swarm's work, with an INK token on a Uniswap v4 hook pool paired with IMD. This entry is InkFeeRouter. It receives the launch's trading-fee share. Anyone can call claimAndRoute(), which sends IMD to the treasury and adds INK to the pool as liquidity. Po…” — entrant claim.

15. @moneycanbuy_fun — Record

Entry 8b49a20f3479ceeb · submitted 2026-10-21T14:56:57.996Z.

Submitted contract: 0x49e55a87aa4bb0d2fd58fdcf1a31c9612de015dc · ethereum explorer.

Swarm evidence and scope: The entered address matches YOLO launch 2364; the entry distinguishes token launch from still-pending core protocol deployment.

Described IMD feature: IMD bonds, paid swarm appeals and identity.md NFT voting are intended to adjudicate paid dares.

Assessment / unanswered: Do not substitute the YOLO launch for a live escrow/dispute cycle. The entry explicitly says core deployment was not finished at submission.

Accepted worker assignments recorded: implement seats #1576; integrate seats #225; review seats #11, #560, #1444, #1501 and others; tests seats #327. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2364 (live) · source 0b50e441 · deployment · entrant repository.

X: @moneycanbuy_fun · 101 followers; 49 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T14:56:57.996Z (chronological position 64 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x49e55a87aa4bb0d2fd58fdcf1a31c9612de015dc; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 2364 (matches submitted contract field): custom_token, status live, Ethereum; record created 2026-10-21T09:25:12.106Z, last updated 2026-10-21T09:34:52.504Z; deployment block 26240107; artifacts: distributor, hook, other, token; repo https://github.com/identity-md-launches/launch-2364-launch-yolo-token-support @ 0b50e441ed. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 985 chars; excerpt): “moneycanbuy.fun: a board of paid dares on Ethereum, judged by the IMD swarm. Anyone posts a yes/no dare with a reward in ETH, USDC, IMD or $YOLO. A doer submits public proof (X post, video, tx). Contract holds the money, pays after a 24h dispute window. For the IMD swarm: every appeal is a real paid job, 0.5 IMD per question. It checks public proo…” — entrant claim.

16. @theimddaily — Record

Entry 3831923bea159e49 · submitted 2026-10-21T12:03:06.125Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The exact newspaper build/deploy job identifies swarm-written contracts and a hosted frontend.

Described IMD feature: ERC-1155 editions are described as mintable for IMD during a fixed 24-hour period.

Assessment / unanswered: The entry omits its contract field. Provide the edition contract, mint receipt and event-period publication record; confirm the publisher's powers and payment vault.

Accepted worker assignments recorded: implement seats #490; integrate seats #1299; review seats #92, #123, #130, #563 and others; tests seats #452. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job ae8a24f3.

X: @theimddaily · 0 followers; 2 lifetime posts (relay metadata). Direct profile sample: 2 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @kilicsln (relay resolves: 7,350 followers, 1,177 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T12:03:06.125Z (chronological position 63 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @kilicsln.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 844 chars; excerpt): “The IMD Daily turns community updates into a free newspaper and collectible history of the IMD ecosystem. Built with the IMD swarm and live on Ethereum, it combines PDF reading, a searchable archive and ERC-1155 editions. Readers can collect each issue for 0.1 IMD during a contract-enforced 24-hour window, with no supply or wallet cap. Minting the…” — entrant claim.

17. @imdgenesis — Record

Entry 3ec49c445a2e689a · submitted 2026-10-21T06:41:12.025Z.

Submitted contract: 0x06f8ceff95e5d72887c575d2759e36230b711d06 · ethereum explorer.

Swarm evidence and scope: The entered GenesisResearch address matches launch 2322 and a pinned source repository.

Described IMD feature: The entrant describes a paid IMD hypothesis proposal that feeds a deterministic experiment and public journal.

Assessment / unanswered: The judges/replay pages are entrant evidence. Independently link the proposal job, delivered artifact hash and engine input; a deployment receipt alone does not prove that end-to-end research cycle.

Accepted worker assignments recorded: implement seats #1646; integrate seats #1618; review seats #61, #420, #528, #1514 and others; tests seats #1966. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2322 (live) · source d5c4307c · deployment.

X: @imdgenesis · 9 followers; 3 lifetime posts (relay metadata). Direct profile sample: 2 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: @0maxxdev (relay resolves: 141 followers, 282 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T06:41:12.025Z (chronological position 62 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x06f8ceff95e5d72887c575d2759e36230b711d06; declared personal handle @0maxxdev; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 2322 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-20T17:28:27.995Z, last updated 2026-10-20T17:29:01.695Z; deployment block 26235291; artifacts: other; repo https://github.com/identity-md-launches/launch-2322-genesisresearch @ d5c4307c56. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 900 chars; excerpt): “GENESIS is a playable laboratory for curious players and agent builders, where AI research meets a world that can say no. Players spend a limited experiment budget to uncover the rules of a synthetic ecosystem. Free local algorithms propose tests; an optional IMD agent can assess a hypothesis and choose the next experiment. One real paid IMD cycl…” — entrant claim.

18. @visualimd — Record

Entry 7fa320b3743058ad · submitted 2026-10-21T03:54:12.608Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The PERK site job explicitly uses the visual package, and a VisualIdentity.md community-entry job exists.

Described IMD feature: A reusable visual preset and proposed seat-holder art submission/voting mechanism are described.

Assessment / unanswered: Do not count PERK's separate deployment as VIMD's custom logic. Provide the voting contract, burn/vote receipt and package/event work attribution.

Accepted worker assignments recorded: implement seats #115, #646; integrate seats #687; review seats #249, #558, #606, #976 and others; tests seats #1614. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 8397b3aa · job a7227c55 · entrant repository.

X: @visualimd · 1 followers; 1 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @Block_Merchant (relay resolves: 3,594 followers, 20,435 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-21T03:54:12.608Z (chronological position 61 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @Block_Merchant.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 1000 chars; excerpt): “Hi IMD team. While making my hackathon entry, Perkshire IMDway (PERK, launch 1660), I found my first prompts had not produced a website I was happy with. So I made VIMD Family: a visualidentity.md package anyone can point a site job at, as a simple, customizable preset. It covers colours with AA contrast in every theme, type, spacing, layout, logo …” — entrant claim.

19. @theidmfun — Record

Entry 2ad0aaf1b5a15930 · submitted 2026-10-20T21:39:11.529Z.

Submitted contract: 0x4fe9f3823791c8b187b81ab8b7398d793fed28f6 · robinhood explorer.

Swarm evidence and scope: Launch 2303 matches the entered IDM token and records SequencerHook review/deployment.

Described IMD feature: Trades modify an onchain sequencer; the entrant describes a fee burn and a market-driven music interface.

Assessment / unanswered: The pool is IDM/ETH. Swarm-built creative logic is supported, but active swaps, the burn path and any IMD runtime demand need separate receipts; planned station subscriptions are not completed evidence.

Accepted worker assignments recorded: implement seats #32; integrate seats #963; review seats #1198, #1497, #1501, #1678 and others; tests seats #281. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2303 (live) · source 79351314 · deployment.

X: @theidmfun · 213 followers; 70 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @badfriend (relay resolves: 1,936 followers, 4,316 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T21:39:11.529Z (chronological position 60 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x4fe9f3823791c8b187b81ab8b7398d793fed28f6; declared personal handle @badfriend.
• IMD record: launch 2303 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-20T16:04:59.168Z, last updated 2026-10-20T16:07:42.091Z; deployment block 93576944; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2303-review-launch-token-named @ 793513141b. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 1000 chars; excerpt): “intelligent dance market ($IDM) is a uniswap v4 hook that works like a drum machine. its onchain state is a 16 step sequencer, and every swap in the idm/eth pool changes it. buys add notes, sells remove them, trade size chooses the drum, and whales can rewrite full tracks and change the key. when the grid fills up and heat reaches 16, the hook fi…” — entrant claim.

20. @imdcontrol — Claim

Entry bff51231456fda5e · submitted 2026-10-20T21:26:16.778Z.

Submitted contract: 0xd7dc08c749d2581e1a2b84bad8b64d0575a06163 · robinhood explorer.

Swarm evidence and scope: The entry describes job.open/API use and a Robinhood recurring-request contract, but supplies no job, repository, contract or receipt.

Described IMD feature: A work-management interface coordinates paid IMD tasks and owner-controlled recurring oracle requests.

Assessment / unanswered: A resolving project account/site supports identity, not technical execution. Provide one actual request and callback plus the recurring contract's limits/admin controls.

Sources / leads: submission census.

X: @imdcontrol · 2 followers; 1 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @vedx02 (relay resolves: 801 followers, 5,171 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T21:26:16.778Z (chronological position 59 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xd7dc08c749d2581e1a2b84bad8b64d0575a06163; declared personal handle @vedx02.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 836 chars; excerpt): “IMD Control is a workspace for founders, researchers, and builders to turn questions into coordinated agent tasks. Users describe their objective, choose a skill, research panel, or multi-step plan, and let IMD assign the agents. Tasks can run sequentially or in parallel, with progress and results organized across Chat, Canvas, Board, and Notebook…” — entrant claim.

21. @HELPWANTED_imd — Record

Entry ece3d42b7a2b271d · submitted 2026-10-20T20:07:31.930Z.

Submitted contract: 0x730cb6c845d896e33283d3a4ed8967f8baa778d2 · ethereum explorer.

Swarm evidence and scope: The entered WorkOrders contract matches launch 1573, with WorkProof, Doorbell and CrowdPots in the same deployment.

Described IMD feature: IMD work escrow pays against WorkRegistry receipt evidence and tips accepted workers' seat owners.

Assessment / unanswered: The claimed Doorbell/Rule hires need receipt-level settlement and tip checks. The no-token design may need organizer interpretation under the task's token-project wording.

Accepted worker assignments recorded: implement seats #1637; integrate seats #225; review seats #205, #286, #826, #963 and others; tests seats #507. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1573 (live) · source 99f4ab09 · deployment · entrant repository.

X: @HELPWANTED_imd · 1 followers; 10 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @_OoJae (relay resolves: 1,003 followers, 9,249 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T20:07:31.930Z (chronological position 58 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x730cb6c845d896e33283d3a4ed8967f8baa778d2; declared personal handle @_OoJae; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1573 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-13T15:45:13.213Z, last updated 2026-10-13T15:51:26.509Z; deployment block 26184581; artifacts: other; repo https://github.com/identity-md-launches/launch-1573-please-deploy-repository-contracts @ 99f4ab0997. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 989 chars; excerpt): “HELP WANTED: the job board where the employers are smart contracts, and the pay waits for proof. IdentityMD's Intake bills up front, no refunds. Here an employer escrows IMD; a bonded runner buys the job from the swarm by x402; the desk pays only if the work record hashes to IdentityMD's WorkRegistry receipt, else refunds. In ERC-8183 terms, the ev…” — entrant claim.

22. @imdfamily — Record

Entry a1163391588a3f2b · submitted 2026-10-20T19:44:46.655Z.

Submitted contract: 0x83204c01e8c0a795b1f0622b08c2ad2da91a96a4 · ethereum explorer.

Swarm evidence and scope: The entered DAEMON address matches swarm launch 2335.

Described IMD feature: The entry describes a learning/community lab but specifies no concrete IMD-dependent application.

Assessment / unanswered: Inspect the actual custom mechanism and successful invocation; a lab description and protocol token launch are insufficient to establish the required feature.

Accepted worker assignments recorded: implement seats #162; integrate seats #1446; review seats #371, #660, #729, #852 and others; tests seats #595. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2335 (live) · source 317dd1ae · deployment.

X: @imdfamily · 2 followers; 1 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @startoverai (relay resolves: 181 followers, 606 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T19:44:46.655Z (chronological position 57 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x83204c01e8c0a795b1f0622b08c2ad2da91a96a4; declared personal handle @startoverai; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 2335 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-20T19:17:52.828Z, last updated 2026-10-20T19:18:42.117Z; deployment block 26235837; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2335-launch-daemon-daemon-ethereum @ 317dd1aeee. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 347 chars; excerpt): “Hi, I'm DAEMON! 🐇 A tiny community lab that just started and is still slowly cooking: part fun, part hands-on practice, part learning in public. Behind me is agent222, who likes spending time on simple apps anyone can understand that make life easier. No need to worry about us. If you're curious, don't be shy: take a look down the rabbit hole.” — entrant claim.

23. @curbhook — Record

Entry 830b102b59b1529e · submitted 2026-10-20T18:33:28.612Z.

Submitted contract: 0xa4df8fbf3a1ab94795577c74ffae26e1d2083819 · robinhood explorer.

Swarm evidence and scope: Launch 2266 corroborates the custom CurbHook build/deployment, with a different CURB token address than the earlier entered address.

Described IMD feature: Price bands and halts constrain an IMD pool; a desk is described as paying IMD for halt analysis.

Assessment / unanswered: Bind the submitted desk/earlier address to the final hook and prove a swap plus oracle-assisted halt. The hook has an owner/configuration surface; backtest statistics are not live receipts.

Sources / leads: entrant repository.

X: @curbhook · 1 followers; 6 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @BazydloMis57623 (relay resolves: 42 followers, 74 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T18:33:28.612Z (chronological position 56 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xa4df8fbf3a1ab94795577c74ffae26e1d2083819; declared personal handle @BazydloMis57623.
• IMD record: launch 2266 (referenced in this review): univ4_hook, status live, Robinhood Chain; record created 2026-10-19T21:37:58.596Z, last updated 2026-10-19T21:41:11.731Z; deployment block 92940119; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2266-launch-curb-curb-uniswap @ 27c66cc7e5. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 813 chars; excerpt): “Curb: stock-market circuit breakers (Limit Up-Limit Down) as a Uniswap v4 hook on Robinhood Chain. Live as IMD launch 2266, CURB/IMD. The hook refuses a swap that would push price outside a band around its 5-min reference and says why on chain (OutsideBand). A price held at the edge halts the pool both ways for 15 min max; it reopens on its own. Cu…” — entrant claim.

24. @imd_financier — Record

Entry 61f49883093874e9 · submitted 2026-10-20T18:06:54.287Z.

Submitted contract: 0x2f56d8fef9f0891c952b15c3b2a94fa4326c28b5 · robinhood explorer.

Swarm evidence and scope: The entered FINCR token matches launch 2311, whose manifest deploys only an ERC-20 and standard protocol plumbing.

Described IMD feature: The entry describes an IMD Dutch auction, work-based mining and an acceptance-evidence publisher.

Assessment / unanswered: Those application contracts are not in launch 2311. Supply their addresses and a takeover/reward/request receipt. The trusted cross-chain publisher is a material dependency.

Accepted worker assignments recorded: implement seats #909; integrate seats #203; review seats #346, #527, #1309, #1430 and others; tests seats #1525. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2311 (live) · source 39472276 · deployment.

X: @imd_financier · 3 followers; 8 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @forkbearingbull (relay resolves: 545 followers, 845 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T18:06:54.287Z (chronological position 55 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x2f56d8fef9f0891c952b15c3b2a94fa4326c28b5; declared personal handle @forkbearingbull.
• IMD record: launch 2311 (matches submitted contract field): custom_token, status live, Robinhood Chain; record created 2026-10-20T15:58:00.610Z, last updated 2026-10-20T15:58:52.761Z; deployment block 93571965; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2311-launch-only-existing-src-fincr-sol @ 39472276ce. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 978 chars; excerpt): “FINANCIER makes the race to mine $FINCR pay for work on FINANCIER itself. On Robinhood Chain, FINANCIER uses an IMD-denominated Dutch auction for the iFinancier mining position. Takeover bids pay the outgoing financier and allocate IMD to job, buyback/burn and permanently locked liquidity budgets. A finite 365-day mining reserve allocates 80% of F…” — entrant claim.

25. @SeerOnIMD — Claim

Entry 83254cb6ebf27588 · submitted 2026-10-20T15:57:58.648Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The entry supplies testnet adjudicator addresses and describes discovery, forecast and resolution panels.

Described IMD feature: IMD is intended to accept questions, price forecasts and judge Sooth markets.

Assessment / unanswered: Name-only Seer token jobs cannot be attributed to these adjudicators. The supplied contracts are Robinhood testnet; organizer approval and a matched completed oracle-to-settlement trace remain unestablished.

Sources / leads: submission census.

X: @SeerOnIMD · 10 followers; 3 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @danieltang (relay resolves: 49 followers, 22 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T15:57:58.648Z (chronological position 54 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @danieltang.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 904 chars; excerpt): “Seer: prediction markets that the IMD swarm judges. A question becomes a market on a Sooth node; after its deadline an IMD oracle panel answers, and its signature settles the market on chain. IMD at every step, paid from the user's wallet: - An IMD agent accepts each question - Forecast panels (up to 9 agents) set the opening price - Discovery: 9 …” — entrant claim.

26. @MailMessengerRH — Claim

Entry c7dc56ea5036150d · submitted 2026-10-20T15:14:21.668Z.

Submitted contract: 0xa46bb59e405d2bc3416ef11952cd6d64da570562 · robinhood explorer.

Swarm evidence and scope: The entry says six rounds of swarm audits, but no matching MailHook audit was located from the supplied evidence/searches.

Described IMD feature: A MAIL game uses delivery rewards and an ETH-side trading hook.

Assessment / unanswered: Same-name standard MAIL token/logo jobs are not proof of this game. Supply the six exact audit jobs, source pin and a successful delivery/claim/hook transaction tied to the entered address.

Sources / leads: submission census.

X: @MailMessengerRH · 27 followers; 24 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @GoatGPRO (relay resolves: 28 followers, 40 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T15:14:21.668Z (chronological position 53 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xa46bb59e405d2bc3416ef11952cd6d64da570562; declared personal handle @GoatGPRO.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 906 chars; excerpt): “Messenger is a cozy 3D browser game on Robinhood Chain: walk a tiny planet, deliver mail to its residents and earn $MAIL for every paid delivery. It's for casual gamers and on-chain players who want play-to-earn that is a real game: free to explore, then open a Mail Office, play a fully on-chain Messenger NFT, take jobs and claim daily rewards. MA…” — entrant claim.

27. @ConditionalsImd — Record

Entry 4ea0ee71b74725cc · submitted 2026-10-20T14:32:53.787Z.

Submitted contract: 0xc8cc656b71dd77ae1e29b0bc7890edd110e73255 · robinhood explorer.

Swarm evidence and scope: Launch 2278 matches the entered Conditionals contract; pinned code includes Intake callback and settlement logic.

Described IMD feature: IMD stakes and two paid oracle answers resolve conditional outcome pools.

Assessment / unanswered: No settlement receipt was independently checked. The entry's no-admin wording needs qualification: source contains owner-only future oracle configuration and fee-recipient settings.

Accepted worker assignments recorded: implement seats #727; integrate seats #798; review seats #694, #1133, #1694, #1849 and others; tests seats #1327. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2278 (live) · source f6d35513 · deployment.

X: @ConditionalsImd · 21 followers; 4 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @0xmisturi (relay resolves: 710 followers, 933 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T14:32:53.787Z (chronological position 52 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xc8cc656b71dd77ae1e29b0bc7890edd110e73255; declared personal handle @0xmisturi.
• IMD record: launch 2278 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-20T05:51:19.761Z, last updated 2026-10-20T05:52:18.989Z; deployment block 93222952; artifacts: other; repo https://github.com/identity-md-launches/launch-2278-launch-conditionals-contract-repository @ f6d35513fe. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 872 chars; excerpt): “Conditionals is a conditional prediction market in IMD. Each market asks "if X happens, will Y?" and opens two worlds, one where X happens and one where it doesn't, each with YES and NO pools. Comparing them shows what X does to Y: "if the Clarity Act passes, ETH above $5k is 62%; if not, 31%". How it uses IMD: - IMD oracle settles every market: t…” — entrant claim.

28. @Gamma_imd — Record

Entry 2b78887e377e1536 · submitted 2026-10-20T14:21:49.982Z.

Submitted contract: 0xb333a22c2c3dd0fe29fd1bf184c5ff2282148535 · robinhood explorer.

Swarm evidence and scope: Launch 2215 matches GammaGame and DrandBeacon; manifest records audited game logic.

Described IMD feature: Players spend IMD through the game; a hook and reserve distribute GAMMA rewards.

Assessment / unanswered: The game has an owner/configurator at launch. Prove energy purchase, beacon-driven epoch and payout, and link the separate token/hook deployment; description alone does not establish all runtime paths.

Accepted worker assignments recorded: implement seats #1160; integrate seats #462; review seats #142, #242, #290, #890 and others; tests seats #1612. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2215 (live) · source ee52608f · deployment.

X: @Gamma_imd · 13 followers; 2 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @0xresets (relay resolves: 37 followers, 194 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T14:21:49.982Z (chronological position 51 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xb333a22c2c3dd0fe29fd1bf184c5ff2282148535; declared personal handle @0xresets.
• IMD record: launch 2215 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-19T06:35:19.844Z, last updated 2026-10-19T06:37:54.749Z; deployment block 92410631; artifacts: other; repo https://github.com/identity-md-launches/launch-2215-src-drandbeacon-sol-src-gammagame-sol @ ee52608fda. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 782 chars; excerpt): “GAMMA is a token you can only mine by playing. Buy energies with IMD and place them on one of four machines (10/30/60/90% fail rate). Every 10 minutes a slice of an 800M Reserve is released: survivors split the Shares, and everyone who failed splits the daily Harvest. No team allocation, no presale. How it uses IMD: - Launched by the IMD swarm: th…” — entrant claim.

29. @PixelFun — Record

Entry 8513ad43abfe4c2a · submitted 2026-10-20T13:31:55.565Z.

Submitted contract: 0x30da521f63553ec3ea2dbb82c30581c00ccf9009 · robinhood explorer.

Swarm evidence and scope: Launch 2148 and its completed build job match PixelFun.

Described IMD feature: Deposited IMD buys pixel edits and is sent to the specified burn sink; epochs rank painters.

Assessment / unanswered: The manifest implements 32 colors, while the entry omits palette detail. Show deposit/paint/burn receipts. The submitted X handle could not be resolved by the account relay, so account existence is unverified.

Accepted worker assignments recorded: implement seats #1238; integrate seats #1403; review seats #205, #249, #641, #1173 and others; tests seats #1413. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2148 (live) · source e880bd59 · deployment · entrant repository.

X: @PixelFun · Public project profile unavailable (HTTP 404 in this acquisition); no activity conclusion. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T13:31:55.565Z (chronological position 50 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x30da521f63553ec3ea2dbb82c30581c00ccf9009; declared personal handle none.
• IMD record: launch 2148 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-18T06:38:10.331Z, last updated 2026-10-18T06:38:41.212Z; deployment block 91565987; artifacts: other; repo https://github.com/identity-md-launches/launch-2148-dsa @ e880bd5931. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 852 chars; excerpt): “PixelFun is a community pixel canvas fully on Robinhood Chain: a 512x512 grid where anyone can color any pixel by paying IMD. Each pixel costs 0.005 IMD and the IMD is burned when the pixel is painted, so every brushstroke permanently reduces IMD supply. Users deposit IMD into a vault, paint from their balance, and withdraw whatever is unspent at a…” — entrant claim.

30. @supercolony_ai — Record

Entry 9bdfab768395ee0e · submitted 2026-10-20T13:31:46.620Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: A completed SuperColony website job identifies use of the swarm, while the entry links a public CLI repository.

Described IMD feature: The CLI is intended to interpret requests locally and submit paid IMD work.

Assessment / unanswered: A website build does not validate the CLI's payment or worker paths. No custom contract/token or invocation evidence is supplied; local wallet security claims were not audited here.

Accepted worker assignments recorded: implement seats #108; review seats #480. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job e5548721 · entrant repository.

X: @supercolony_ai · 1 followers; 1 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @tian7eth (relay resolves: 2,263 followers, 3,284 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T13:31:46.620Z (chronological position 49 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @tian7eth.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 850 chars; excerpt): “SuperColony — A Local AI Agent for IMD Overview SuperColony is a local command-line agent that makes interacting with IMD easier. Describe what you want to accomplish in plain language, and SuperColony uses a local AI model to select the appropriate task type and submit your request to IMD. You can also browse existing tasks and run a worker wit…” — entrant claim.

31. @keptonchainn — Record

Entry b586f6da0288c40f · submitted 2026-10-20T09:55:38.759Z.

Submitted contract: 0x3152f9cbf64d0c1ac24ea7e101db3e4d8da86896 · robinhood explorer.

Swarm evidence and scope: The entered KeptVault matches launch 2172; pinned code verifies oracle attestations and settles milestone tranches.

Described IMD feature: Paid IMD milestone checks release or burn locked project tokens.

Assessment / unanswered: The claim of two releases needs receipts. Source has owner-controlled protocol/panel settings, so disclose them; the separate fee-funding hook also needs a matched deployment and invocation.

Accepted worker assignments recorded: implement seats #1877; integrate seats #737; review seats #189, #694, #809, #939 and others; tests seats #1155. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2172 (live) · source bbb7f7d1 · deployment.

X: @keptonchainn · 5 followers; 25 lifetime posts (relay metadata). Direct profile sample: 4 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @Modemolaa (relay resolves: 1,288 followers, 17,377 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T09:55:38.759Z (chronological position 48 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x3152f9cbf64d0c1ac24ea7e101db3e4d8da86896; declared personal handle @Modemolaa.
• IMD record: launch 2172 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-18T16:25:22.583Z, last updated 2026-10-18T16:27:25.967Z; deployment block 91910657; artifacts: other; repo https://github.com/identity-md-launches/launch-2172-deploy-only-src-keptvault-sol-repository @ bbb7f7d193. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 932 chars; excerpt): “KEPT turns a token launch roadmap into a contract. A team locks its tokens in the KEPT vault behind public milestones: a GitHub release, a live web page, a deployed contract or an onchain value. At each deadline the team asks the IMD oracle. A panel of 9 agents checks the milestone, 7 must agree, and the vault verifies the signed verdict onchain. K…” — entrant claim.

32. @hamsterhourgame — Record

Entry 54cd697974beb950 · submitted 2026-10-20T08:31:59.962Z.

Submitted contract: 0xe33ab493249a2df0d8c4a71ac54f46d1f7778367 · ethereum explorer.

Swarm evidence and scope: The entered HamsterHour contract matches launch 2260 with swarm deployment/source provenance.

Described IMD feature: IMD betting pools are intended to pay for swarm answers about a real hamster's recorded distance.

Assessment / unanswered: Verify the physical-data source, paid question, callback and payout for one hour. Sampled X promotion includes an early-access repost incentive, which can affect engagement comparisons.

Accepted worker assignments recorded: implement seats #1166; integrate seats #132; review seats #452, #1082, #1314, #1489 and others; tests seats #1503. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2260 (live) · source 49f53ca0 · deployment.

X: @hamsterhourgame · 107 followers; 42 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T08:31:59.962Z (chronological position 47 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xe33ab493249a2df0d8c4a71ac54f46d1f7778367; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 2260 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-19T21:47:06.928Z, last updated 2026-10-19T21:47:49.200Z; deployment block 26229405; artifacts: other; repo https://github.com/identity-md-launches/launch-2260-build-hamster-hour-v2 @ 49f53ca0f2. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 856 chars; excerpt): “Hamster Hour: bet IMD on how far a real hamster runs each hour. Squeektoshi's hamster runs on the WHEELY9000 and Squeekchain records every pass on Ethereum. Each hour is a market: OVER/UNDER the line, SNOOZE, and an EXACT jackpot (5 IMD ticket, guess within ±0.5%, no winner and the jar keeps growing). Pari-mutuel, no house, no owner: winners split …” — entrant claim.

33. @Eval_Engine — Record

Entry 4ab3de91474bf687 · submitted 2026-10-20T06:48:14.163Z.

Submitted contract: 0xf3a79f962ec1e75f0087af5491a69dee2a869012 · robinhood explorer.

Swarm evidence and scope: Launch 2223 matches AskSwarmRegistry, SwarmMarket and SwarmWager; both pinned source and the cited request are inspectable.

Described IMD feature: Contracts buy IMD oracle answers and settle IMD markets/wagers after signature verification.

Assessment / unanswered: A full market-3 cycle is corroborated below after locating separate callback, settlement and claim transactions. Later logs also contain refusals/disagreements; successful examples do not prove universal availability.

Accepted worker assignments recorded: implement seats #363; integrate seats #77; review seats #11, #22, #293, #690 and others; tests seats #1682. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2223 (live) · source 712164b6 · deployment · entrant repository.

X: @Eval_Engine · 1,901 followers; 315 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: @superoo7 (relay resolves: 9,778 followers, 5,520 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-20T06:48:14.163Z (chronological position 46 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xf3a79f962ec1e75f0087af5491a69dee2a869012; declared personal handle @superoo7.
• IMD record: launch 2223 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-19T12:21:28.780Z, last updated 2026-10-19T13:35:28.521Z; deployment block 92654033; artifacts: other; repo https://github.com/identity-md-launches/launch-2223-src-askswarmregistry-sol-src-swarmmarket @ 712164b6f0. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 885 chars; excerpt): “AskSwarm makes the IMD oracle usable by people and by other contracts, live on Robinhood Chain. Entered contract: AskSwarmRegistry, audited and deployed by the swarm in IMD launch #2223, source verified on Sourcify. How it works: - ask() pays 0.5 IMD to Intake v2 with itself as callback - onOracleResult checks the swarm's EIP-712 attestation onch…” — entrant claim.

34. @NotestotheW — Record

Entry 61eb85e009844400 · submitted 2026-10-19T23:56:08.741Z.

Submitted contract: 0x9550e4f888d1c084cb1c8e74677da54109723ee3 · robinhood explorer.

Swarm evidence and scope: An exact gimogo/NTTW audit job and an address-specific settlement-integrity job corroborate swarm review.

Described IMD feature: The entry describes a custom wall/token lottery using Chainlink VRF and cross-chain relay delivery.

Assessment / unanswered: IMD protocol launch is claimed; prove the specific IMD dependency beyond token provenance. The one-ticket demo cannot establish lottery fairness; acknowledged audit issues and subscription/admin dependencies remain relevant.

Accepted worker assignments recorded: review seats #560, #641, #954, #1229 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 16c65a39 · job 44df6543 · entrant repository.

X: @NotestotheW · 58 followers; 34 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T23:56:08.741Z (chronological position 45 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x9550e4f888d1c084cb1c8e74677da54109723ee3; declared personal handle none.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 973 chars; excerpt): “NOTES To The World (nttw-blush.vercel.app): every sticky note is an ERC-721; prizes settle cross-chain via Chainlink VRF v2.5. A stamp costs 1000 $NOTES (500 burn / 500 pool) - a 3-day-epoch ticket. Anyone settles an ended epoch; the immutable relay (Base) takes one VRF word; deliver(epoch) ships it back; winner = word % ticketCount. Custom wall (R…” — entrant claim.

35. @nightshiftimd — Record

Entry 35ac8064ad1f83af · submitted 2026-10-19T20:16:46.902Z.

Submitted contract: 0xe5e58e53d0bb204aa62c995a6c8cc8a48e60c3ac · ethereum explorer.

Swarm evidence and scope: The entered SHIFT address matches launch 2124 and a custom NightshiftHook.

Described IMD feature: Trading fees and swarm purchases are described as funding an IMD-based agent/product economy.

Assessment / unanswered: The manifest assigns Ownable roles to a developer wallet and initially gates trading. Separate deployed components from roadmap claims, and prove at least one IMD hire/payment and active hook transaction.

Accepted worker assignments recorded: implement seats #1411; integrate seats #544; review seats #27, #535, #810, #1059 and others; tests seats #1004. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2124 (live) · source 9f3e1600 · deployment · entrant repository.

X: @nightshiftimd · 198 followers; 135 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @probert_mihai (relay resolves: 57 followers, 203 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T20:16:46.902Z (chronological position 44 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xe5e58e53d0bb204aa62c995a6c8cc8a48e60c3ac; declared personal handle @probert_mihai; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 2124 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-18T00:25:34.304Z, last updated 2026-10-18T00:26:14.268Z; deployment block 26215851; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2124-launch-nightshift-shift-platform @ 9f3e16007c. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 961 chars; excerpt): “NIGHTSHIFT runs on IMD end to end. AI companies whose CEO buys every product, site and audit from the swarm in IMD and sells for USDC to people and agents. Live on Ethereum, all built, audited and deployed by IMD, verified on Etherscan: $SHIFT (launch #2124, v4 hook, fees burn IMD at the BurnExecutor, 10% to the swarm, 75M+ staked), 500 onchain NIG…” — entrant claim.

36. @imdpot — Record

Entry 36911e0d560f58e5 · submitted 2026-10-19T19:03:44.900Z.

Submitted contract: 0xa5ee8a1f2aa98f08755f80bb278528d789f1e8f3 · ethereum explorer.

Swarm evidence and scope: The entered jackpot contract matches launch 2183.

Described IMD feature: An IMD-only round allocates payouts, burns and loyalty balances.

Assessment / unanswered: Show a completed round and actual IMD transfers. Future-blockhash randomness, house fees and locked loyalty accounting need risk disclosure; a deployment record does not establish fair or reliable settlement.

Accepted worker assignments recorded: implement seats #1520; integrate seats #1687; review seats #94, #281, #468, #656 and others; tests seats #1906. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2183 (live) · source b60026be · deployment.

X: @imdpot · 4 followers; 22 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T19:03:44.900Z (chronological position 43 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xa5ee8a1f2aa98f08755f80bb278528d789f1e8f3; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 2183 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-18T19:39:05.947Z, last updated 2026-10-18T19:39:51.191Z; deployment block 26221596; artifacts: other; repo https://github.com/identity-md-launches/launch-2183-i-already-have-existing @ b60026be54. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 425 chars; excerpt): “IMDPot is a 15-minute jackpot game that runs only on $IMD. Every round: • 70% to top 3 winners (40/20/10) • 10% burned • 5% house fee • 15% permanently locked as loyalty points Winners are selected with future-blockhash randomness. Anyone can finalize the round. Even if you don’t win, you still earn loyalty points that become a multiplier after …” — entrant claim.

37. @SuperFPET_eth — Claim

Entry bd7a704b7f937181 · submitted 2026-10-19T18:51:36.580Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The entrant describes a bridge/keeper workflow; the entry has no contract, source or job link.

Described IMD feature: Trading fees are intended to bridge IMD into FP and stake it in a shared FrenPet.

Assessment / unanswered: Same-name launch jobs exist but were not bound to the submitted project by an address or payer. Provide the full fee, bridge receipt and staking transaction chain, including keeper permissions.

Sources / leads: submission census.

X: @SuperFPET_eth · 55 followers; 10 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @Atlasfreeman (relay resolves: 12,221 followers, 14,082 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T18:51:36.580Z (chronological position 42 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @Atlasfreeman.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 889 chars; excerpt): “Super Fren Pet ($SFP) is a cross-chain community experiment that connects the IMD ecosystem on Ethereum with FrenPet on Base. Every $SFP trade on Stockereum generates creator fees in IMD. Those fees are collected by the treasury, bridged from Ethereum to Base through LayerZero, received 1:1 as FP, and automatically staked by a keeper into one share…” — entrant claim.

38. @sudeepb02 — Record

Entry 5fa4d624b80db4f8 · submitted 2026-10-19T18:32:59.406Z.

Submitted contract: 0x2008b60c94e97a0f5315fc90a0aafe9e3bd78f7d · ethereum explorer, base explorer, robinhood explorer.

Swarm evidence and scope: The exact linked imdLend audit corroborates a five-agent review of the named public contracts repository.

Described IMD feature: Seat owners rent capacity to operators for IMD, with vaults splitting work rewards.

Assessment / unanswered: The audit is not proof of every deployment or the first paired-seat job. Resolve findings against the deployed commit, inspect rental/return transactions and verify how worker authorization expires.

Sources / leads: job d5b12e13 · entrant repository.

X: @sudeepb02 · 639 followers; 1,625 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @sudeepb02 (same handle as project) (relay resolves: 639 followers, 1,625 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T18:32:59.406Z (chronological position 41 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum, base, robinhood; contract field 0x2008b60c94e97a0f5315fc90a0aafe9e3bd78f7d; declared personal handle @sudeepb02; deployer field 0x4e59b44847b379578588920ca78fbf26c0b4956c.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 994 chars; excerpt): “imdLend is an open market for IMD seats. Owners lend the seats they don't use, operators run them, and a vault splits every reward automatically. No trust needed, and the seat always returns to its owner. It puts idle seats to work: half the swarm has no machine running, while many people with spare AI subscriptions can't afford a seat. Now they c…” — entrant claim.

39. @robobet_fun — Record

Entry dcd42434c88a2d60 · submitted 2026-10-19T17:37:04.723Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: Launch 1791 matches the Ethereum USDCDepositClaim address in the entry's prose, supporting swarm-written claim logic.

Described IMD feature: The entrant describes paid IMD research selecting simulated high-leverage trades.

Assessment / unanswered: The claim contract itself has no demonstrated IMD dependency; it is owner-funded USDC distribution. Prove a specific research order-to-decision-to-claim connection and distinguish PaperTrade simulation from real market execution.

Accepted worker assignments recorded: implement seats #1020; integrate seats #143; review seats #422, #573, #1017, #1067 and others; tests seats #1510. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1791 (live) · source b68dad2e · deployment · job 1a03986b.

X: @robobet_fun · 297 followers; 25 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T17:37:04.723Z (chronological position 40 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle none.
• IMD record: launch 1791 (referenced in this review): evm_contracts, status live, Ethereum; record created 2026-10-14T23:05:23.014Z, last updated 2026-10-14T23:06:15.596Z; deployment block 26193918; artifacts: other; repo https://github.com/identity-md-launches/launch-1791-i-want-you-create @ b68dad2e0d. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 775 chars; excerpt): “Robobet is an AI powered crypto trading experience for crypto traders who want to put an IMD powered AI agent in control. Users deposit USDC and watch a high leverage BTC or ETH trade unfold live. Robobet uses IMD to run paid research jobs that analyze market data and choose the trade’s direction, leverage, and take profit target. The resulting dec…” — entrant claim.

40. @chad_gotchi — Record

Entry 2d2b83984607f79b · submitted 2026-10-19T07:54:54.649Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: Identifiable OG Club jobs show ongoing swarm development, including an October 21 hook job.

Described IMD feature: The entry describes an NFT-avatar browser world without specifying an IMD-dependent contract feature.

Assessment / unanswered: No address or transaction is submitted. Later OG hook work cannot establish what this entry delivered by its earlier submission; bind the eligible version and demonstrate IMD seat/asset utility.

Accepted worker assignments recorded: implement seats #660; integrate seats #921; review seats #172, #205, #595, #1166 and others; tests seats #1446. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job c2fbceb1.

X: @chad_gotchi · 295 followers; 535 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @chad_gotchi (same handle as project) (relay resolves: 295 followers, 535 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T07:54:54.649Z (chronological position 39 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @chad_gotchi.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 527 chars; excerpt): “OG Club World: a pixel-art browser world where the NFTs you already hold are your character and your pass in, and the games are a reason to come back every day. Live: world.ogclub.online What it is A shared online world for the Swarm Pepe / OG Club community. You connect a wallet and play as an NFT you own: a Swarm Pepe, a FrenPet, or an Aavegot…” — entrant claim.

41. @TaskOnchainn — Record

Entry 3630478a1e8e7250 · submitted 2026-10-19T00:21:41.778Z.

Submitted contract: 0x2b79cc53d7f0f6458c44ce4f78e8d9adb1393b19 · robinhood explorer.

Swarm evidence and scope: Launch 2194 matches BountyBox and records an updated swarm deployment.

Described IMD feature: ETH escrow pays workers subject to creator approval or a human reviewer, with a timeout split.

Assessment / unanswered: The manifest's oracle is a reviewer EOA, not proof of an IMD agent oracle. Swarm development is supported; explain the continuing IMD dependency if claiming runtime integration. Admin may replace the reviewer after delay.

Accepted worker assignments recorded: implement seats #475; integrate seats #760; review seats #3, #650, #1457, #1616 and others; tests seats #715. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2194 (live) · source fd99ae4b · deployment.

X: @TaskOnchainn · 7 followers; 6 lifetime posts (relay metadata). Direct profile sample: 2 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: @zyraxoo (relay resolves: 1,048 followers, 22,129 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-19T00:21:41.778Z (chronological position 38 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x2b79cc53d7f0f6458c44ce4f78e8d9adb1393b19; declared personal handle @zyraxoo.
• IMD record: launch 2194 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-18T22:15:19.136Z, last updated 2026-10-18T22:15:50.587Z; deployment block 92116332; artifacts: other; repo https://github.com/identity-md-launches/launch-2194-update-existing-bounty-box @ fd99ae4b0f. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 302 chars; excerpt): “Bounty Box is a freelance contract on Robinhood Chain. A creator locks ETH for a job, and workers submit their work. If the creator approves, the worker gets paid. If they reject or ignore it, a reviewer wallet you control decides. If the reviewer stays silent, the money splits 60/40 (creator/worker).” — entrant claim.

42. @pleaimd — Claim

Entry 6ba408eabebf9284 · submitted 2026-10-18T21:30:53.556Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The entry reports eight audits and seven Sepolia launches but supplies no exact job record or deployed address.

Described IMD feature: A paid IMD oracle panel would approve pleas to sell through an IMD-paired hook.

Assessment / unanswered: It explicitly says mainnet next. Need organizer-approved testnet status, source-bound audit jobs and a successful plea/verdict/sell receipt; test counts alone are insufficient.

Sources / leads: entrant repository.

X: @pleaimd · 0 followers; 0 lifetime posts (relay metadata). Direct profile sample: 0 authored posts, 0 dated in the event window. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-18T21:30:53.556Z (chronological position 37 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle none.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 993 chars; excerpt): “PLEA is a meme token on uniswap v4 where buying is open but selling needs a plea. you write why you want to sell and the Cabal, 30 judges on an IMD oracle panel, scores it 0-45. it has to reach a need the contract works out from your on-chain facts: how much of your bag you sell, how long you held, profit or loss, the 24h trend. approved = you sell…” — entrant claim.

43. @UnlockBySwarm — Record

Entry a1a233a85ff47d48 · submitted 2026-10-18T08:56:05.717Z.

Submitted contract: 0x99fa82b022be4575891a43b757bc770691e18fda · ethereum explorer.

Swarm evidence and scope: Launch 2071 matches UNLK and UnlkImdHook, recording a repaired swarm deployment.

Described IMD feature: The hooked IMD pool enforces sales quotas and collects IMD treasury fees.

Assessment / unanswered: The entry correctly says other pools/transfers bypass quotas. Prove a live swap/quota change and fee routing; an intended future NFT purchase is not an already-working IMD seat benefit.

Accepted worker assignments recorded: implement seats #701; integrate seats #1681; review seats #158, #172, #690, #1176 and others; tests seats #317. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 2071 (live) · source 40d70b7b · deployment.

X: @UnlockBySwarm · 9 followers; 16 lifetime posts (relay metadata). Direct profile sample: 2 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: @kilicsln (relay resolves: 7,350 followers, 1,177 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-18T08:56:05.717Z (chronological position 36 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x99fa82b022be4575891a43b757bc770691e18fda; declared personal handle @kilicsln; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 2071 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-17T11:16:14.303Z, last updated 2026-10-17T11:17:50.343Z; deployment block 26211921; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-2071-unlock @ 40d70b7bd0. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 880 chars; excerpt): “UNLOCK (UNLK) is an Ethereum token experiment built and iterated with the IMD swarm for users exploring programmable trading rules. Its official UNLK/IMD pool uses a Uniswap v4 hook: accounts initially may sell 20% of mature eligible acquisitions. Sixteen USD FDV milestones progressively raise that allowance, ending in permanent quota removal at $5…” — entrant claim.

44. @imd_offset — Claim

Entry 9a418bc5ddfb4f90 · submitted 2026-10-16T22:27:27.774Z.

Submitted contract: 0x87b525bc5ff6d7211f16291219c363e082ed4e9f · ethereum explorer, base explorer.

Swarm evidence and scope: The entry describes regenerative tools and a submitted token address; exact-address jobs were not found.

Described IMD feature: IMD compute offsets and trading-funded ecological contributions are proposed as the use case.

Assessment / unanswered: Similar IMD Offsets jobs surfaced, including testnet builds, but were not linked securely to this entered deployment. Need the actual receipt, credit retirement evidence and fee-routing code; avoid treating a contribution as verified offsetting.

Sources / leads: submission census.

X: @imd_offset · 136 followers; 101 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-16T22:27:27.774Z (chronological position 35 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum, base; contract field 0x87b525bc5ff6d7211f16291219c363e082ed4e9f; declared personal handle none; deployer field 0xe478dcc55af363132c0cbe7f52262fbf2ed24768.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 363 chars; excerpt): “Tools that turn the IMD swarm into a force for regenerative impact. Offset the swarms footprint, fund regenerative work, protect vital habitat. In collaboration with Regen Network and Regen Compute. All through smart contracts. All on chain. Tools that turn degen trading into regenerative action. Swaps, Snipers, Automated Trading, Games and more a…” — entrant claim.

45. @SinopiaMD — Record

Entry 757ee35b472f49c9 · submitted 2026-10-16T09:42:08.863Z.

Submitted contract: 0x0da78a50b3039f8ca719d01754988b23d7e70fe2 · robinhood explorer.

Swarm evidence and scope: Launch 1942 matches Sinopia and records swarm deployment of an IMD-funded commission auction.

Described IMD feature: Winning IMD bids buy a swarm image job; callbacks mint output and the remainder is burned.

Assessment / unanswered: A compelling runtime design, but no auction/job/mint/burn receipt was independently traced here. Verify output hash binding, failure refunds and accepted-code permissions.

Accepted worker assignments recorded: integrate seats #873; review seats #36. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1942 (live) · source 2d7436e5 · deployment · entrant repository.

X: @SinopiaMD · 3 followers; 12 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @Timidan_x (relay resolves: 2,043 followers, 8,984 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-16T09:42:08.863Z (chronological position 34 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x0da78a50b3039f8ca719d01754988b23d7e70fe2; declared personal handle @Timidan_x.
• IMD record: launch 1942 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-16T07:13:26.470Z, last updated 2026-10-16T07:14:24.385Z; deployment block 89892607; artifacts: other; repo https://github.com/identity-md-launches/launch-1942-sinopia @ 2d7436e57e. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 780 chars; excerpt): “Sinopia is an onchain auction where each winning bid commissions the IMD swarm to paint the winner's brief, and the finished fresco is minted to the winner. Bid IMD with a short brief; when the 3-hour round ends, the contract itself pays IMD's Intake v2 0.5 IMD for a create-image job, gets the result back by callback, and mints the painting with it…” — entrant claim.

46. @IMDhongbao — Record

Entry f493bc040796adeb · submitted 2026-10-16T08:39:13.580Z.

Submitted contract: 0xc609565a5252c458609896b9ff4403b2a020c5d6 · robinhood explorer.

Swarm evidence and scope: Launch 1815 and the linked workflow match HongbaoBox and corroborate build/test/review/deployment.

Described IMD feature: IMD packets use recipient-bound signatures, sharing logic and a fee burn.

Assessment / unanswered: The entry's abbreviated demo hash is not a usable full transaction reference. Retrieve the full packet open/grab/burn sequence; commit-reveal fallback and secret sharing need explicit limitations.

Accepted worker assignments recorded: implement seats #1637; integrate seats #704; review seats #531, #641, #1066, #1465 and others; tests seats #307. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1815 (live) · source 9689af00 · deployment.

X: @IMDhongbao · 0 followers; 4 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @nuantree (relay resolves: 181 followers, 2,157 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-16T08:39:13.580Z (chronological position 33 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xc609565a5252c458609896b9ff4403b2a020c5d6; declared personal handle @nuantree.
• IMD record: launch 1815 (matches submitted contract field): evm_project, status live, Robinhood Chain; record created 2026-10-15T07:35:59.923Z, last updated 2026-10-15T07:36:49.650Z; deployment block 89050661; artifacts: distributor, hook, other, token; repo https://github.com/identity-md-launches/launch-1815-workflow-contract-stage-context @ 9689af00d4. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 978 chars; excerpt): “IMD Hongbao: on-chain red packets (lucky money) filled with $IMD on Robinhood Chain. Put IMD in a packet, pick lucky draw or equal split, share the link and a passphrase, and friends grab a share. The passphrase never goes on chain. It derives a signing key in the browser, and every grab is an EIP-712 signature bound to its recipient, so a copied …” — entrant claim.

47. @weirpay — Record

Entry e498669a580a4d52 · submitted 2026-10-15T20:15:20.569Z.

Submitted contract: 0xde049547f1e55bb093e14d8f4545d1cc9b613f97 · robinhood explorer.

Swarm evidence and scope: Launch 1869 matches ownerless Weir v2 and records source/deployment provenance.

Described IMD feature: ERC-20 payment streams can ask the IMD oracle to resolve disputes.

Assessment / unanswered: Provide a funded stream, dispute request, callback and final distribution. The entered application is distinct from the existing WEIR token used by its constructor.

Accepted worker assignments recorded: integrate seats #414; review seats #429, #539, #541, #1484 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1869 (live) · source 10866057 · deployment.

X: @weirpay · 0 followers; 3 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-15T20:15:20.569Z (chronological position 32 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xde049547f1e55bb093e14d8f4545d1cc9b613f97; declared personal handle none.
• IMD record: launch 1869 (matches submitted contract field): evm_contracts, status live, Robinhood Chain; record created 2026-10-15T16:51:51.347Z, last updated 2026-10-15T16:52:08.908Z; deployment block 89381549; artifacts: other; repo https://github.com/identity-md-launches/launch-1869-weir-v2-deploy-weir @ 1086605786. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 198 chars; excerpt): “Stream payments for contract work between two parties. If the client doesn’t feel the contract is being upheld, stop payment. If there’s a dispute, the swarm decides who gets the rest of the budget.” — entrant claim.

48. @agentskill_imd — Record

Entry c4dbb3e164264c55 · submitted 2026-10-15T13:15:34.374Z.

Submitted contract: 0xabec9774d66c640b64238dbd69758d31d10d54b1 · ethereum explorer.

Swarm evidence and scope: Launch 1739 matches AgentSkill and its configured ERC-8004 reputation design.

Described IMD feature: Skills/endorsements and trusted reputation publishers are intended to rank IMD agents.

Assessment / unanswered: The manifest says no accepted-work adapter is included/deployed and ranking needs publisher configuration. Confirm current settings; ERC-8004 feedback is not automatically proof of accepted IMD jobs. Owner powers are material.

Accepted worker assignments recorded: implement seats #969; integrate seats #1299; review seats #346, #368, #442, #1457 and others; tests seats #900. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1739 (live) · source cae6d4dc · deployment.

X: @agentskill_imd · 5 followers; 12 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @nemeremigweze (relay resolves: 135 followers, 5,401 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-15T13:15:34.374Z (chronological position 31 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xabec9774d66c640b64238dbd69758d31d10d54b1; declared personal handle @nemeremigweze; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1739 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-14T14:22:49.644Z, last updated 2026-10-14T14:23:37.229Z; deployment block 26191312; artifacts: other; repo https://github.com/identity-md-launches/launch-1739-build-complete-polished-product @ cae6d4dcf6. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 254 chars; excerpt): “AgentSkill is live on Ethereum. Rankings use real ERC-8004 reputation from trusted publishers I configured. Agents register their own skills, the leaderboard fills as the swarm opts in. Skills and endorsements are ready, scores update from on-chain data.” — entrant claim.

49. @IaMaDamIMD — Record

Entry c7dc28300ef91486 · submitted 2026-10-15T13:06:28.817Z.

Submitted contract: 0x0eb84279eff71548ac5212ce17760b1e54692825 · ethereum explorer.

Swarm evidence and scope: An exact-address job explicitly identifies @IaMaDamIMD and records swarm website work.

Described IMD feature: The entry itself only supplies a slogan, so it does not explain a working IMD-dependent feature.

Assessment / unanswered: A website job corroborates swarm use, not custom contract behavior. Need technical mechanism, source, active invocation, demo and permission disclosure.

Accepted worker assignments recorded: implement seats #812. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 0fef589e.

X: @IaMaDamIMD · 131 followers; 59 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-15T13:06:28.817Z (chronological position 30 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x0eb84279eff71548ac5212ce17760b1e54692825; declared personal handle none; deployer field 0xadb5cd1c8fb6d51754e7c930b8a75c07dc3699e0.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 22 chars; excerpt): “surf, spin FWA, repeat” — entrant claim.

50. @IMDBlackout — Record

Entry 0e730668a808e9f2 · submitted 2026-10-15T05:46:17.202Z.

Submitted contract: 0x38b05971c79e738f64452be83c78ec3d66535b7a · robinhood explorer.

Swarm evidence and scope: The entered BLACKOUT address matches swarm launch 1710.

Described IMD feature: The entry describes hardware-pack gameplay and a custom-fee hook across multiple releases.

Assessment / unanswered: One matched deployment does not verify all 20 contracts or four launches. Enumerate the set and demonstrate a paid pack, epoch and reward path; explain IMD's runtime role rather than only swarm authorship.

Accepted worker assignments recorded: implement seats #931; integrate seats #604; review seats #36, #671, #1295, #1561 and others; tests seats #1201. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1710 (live) · source 27c94e59 · deployment.

X: @IMDBlackout · 65 followers; 45 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-15T05:46:17.202Z (chronological position 29 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x38b05971c79e738f64452be83c78ec3d66535b7a; declared personal handle none.
• IMD record: launch 1710 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-14T08:35:47.870Z, last updated 2026-10-14T08:36:50.578Z; deployment block 88228556; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1710-blackout @ 27c94e597d. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 870 chars; excerpt): “BLACKOUT is a pixel mining-farm game on Robinhood Chain (4663), built end to end by the IMD agent swarm. Players buy packs of soulbound hardware (GPUs, ASICs, coolers, power), place them in rooms of their farm, and mine the BLACKOUT token every 6-hour epoch. Rarity, combos, levels and city events (outages, power surges, tax audits) shape each farm'…” — entrant claim.

51. @neethome_rh — Record

Entry 5bf997e11eba5d24 · submitted 2026-10-15T05:15:49.060Z.

Submitted contract: 0x66d0963f8a9af27b15028d84da8a1792999a840f · robinhood explorer.

Swarm evidence and scope: Launch 1703 matches NEETHOME and explicitly records a fixed-supply ERC-20 with no application contracts or custom trading hook.

Described IMD feature: The entry plans to use fee revenue for a Solana purchase and burning.

Assessment / unanswered: This deployment alone is a plain-token launch and does not meet the meaningful-functionality requirement. The cross-chain plan needs independently deployed logic and transactions.

Accepted worker assignments recorded: implement seats #545; integrate seats #993; review seats #39, #475, #636, #727 and others; tests seats #1998. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1703 (live) · source f58a01be · deployment.

X: @neethome_rh · 19 followers; 51 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @neethome_rh (same handle as project) (relay resolves: 19 followers, 51 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-15T05:15:49.060Z (chronological position 28 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x66d0963f8a9af27b15028d84da8a1792999a840f; declared personal handle @neethome_rh.
• IMD record: launch 1703 (matches submitted contract field): custom_token, status live, Robinhood Chain; record created 2026-10-14T06:37:36.208Z, last updated 2026-10-14T06:38:13.074Z; deployment block 88157730; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1703-neetillions @ f58a01bee0. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 703 chars; excerpt): “this token, $neethome, was made to cherish one of the best memecoins ever created — $neet. the plan is simple: 50% of the transaction fees will be used to buy $neet on solana, and 40% will be burned. before this, i never knew how to code or create a liquidity position onchain. $imd’s simple design made it possible. this is for the fellow neets an…” — entrant claim.

52. @PawnIMD — Record

Entry e3c372ae9deed099 · submitted 2026-10-14T23:20:02.652Z.

Submitted contract: 0xf0d9300d7d891bc842da540cc4ddef050da9bcd4 · ethereum explorer.

Swarm evidence and scope: The entered PawnShop address matches launch 1139 and accompanying FloorRelay, LockDiscount and MilestoneBurn.

Described IMD feature: IMD oracle floor attestations price seat-backed ETH lending while authorization allows workers to continue.

Assessment / unanswered: Need a real collateral/loan/repayment or auction cycle and proof of continued worker authorization. Owner-controlled components and oracle/floor/liquidity risks must be disclosed.

Accepted worker assignments recorded: implement seats #976; integrate seats #429; review seats #12, #127, #560, #727 and others; tests seats #36. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1139 (live) · source f6f7d1e5 · deployment.

X: @PawnIMD · 27 followers; 21 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-14T23:20:02.652Z (chronological position 27 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xf0d9300d7d891bc842da540cc4ddef050da9bcd4; declared personal handle none; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1139 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-09T08:00:32.992Z, last updated 2026-10-09T08:03:01.868Z; deployment block 26153528; artifacts: other; repo https://github.com/identity-md-launches/launch-1139-deploy-audit-fixed-pawn-contracts @ f6f7d1e5b5. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 869 chars; excerpt): “Pawn is a pawn shop for identity.md seats. Seat holders borrow ETH against their seat for 7 or 30 days (1% or 3% fee, up to 40% of floor) while the seat keeps working in the swarm: each loan's vault answers ERC-1271 for the borrower's IMD worker authorization. No price liquidations: repay by the deadline or the seat goes to a Dutch auction. Lenders…” — entrant claim.

53. @keelpad_imd — Record

Entry 2d09fca8599dbdc8 · submitted 2026-10-14T17:23:10.654Z.

Submitted contract: 0x324a7cc39764f3abac02cfc340228cd06042f064 · ethereum explorer.

Swarm evidence and scope: Keel Spin and Keel v2 build jobs corroborate swarm work for related products; project X explicitly describes those integrations.

Described IMD feature: The described launchpad routes IMD fees into further swarm-funded development and holder voting.

Assessment / unanswered: The submitted address was not matched. Do not substitute newer code-only Keel v2 or Keel Spin for the entered v1 deployment. Supply its precise factory/hook job, active pool receipt and paid follow-on build.

Sources / leads: job 84e3719a · job f4c6c94f.

X: @keelpad_imd · 164 followers; 15 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @mrakold (relay resolves: 937 followers, 17,462 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-14T17:23:10.654Z (chronological position 26 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x324a7cc39764f3abac02cfc340228cd06042f064; declared personal handle @mrakold; deployer field 0x51a9ca901c0cb5c222d244b2ccb0ebfc5c9aba99.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 743 chars; excerpt): “keel is a launchpad on ethereum where every token is backed by real work from the imd swarm. you describe an idea and imd agents write the contracts and the site. when the job is accepted you launch a token for it in one click. every trade pays 1 percent in imd through our uniswap v4 hook. part goes to the creator and part fills a basket that pays …” — entrant claim.

54. @perkshireimd — Record

Entry 294a0cbccb48c8f9 · submitted 2026-10-14T01:06:19.897Z.

Submitted contract: 0x2b2ed02698a82230f11d6285f3b147e3fd6df83a · robinhood explorer.

Swarm evidence and scope: Launch 1660 matches the Robinhood PERK address and custom hook/vault; launch 1663 is explicitly disclaimed by the entrant.

Described IMD feature: IMD trading fees fund a burn and redeemable float; a weekly call is intended to buy an IMD oracle answer.

Assessment / unanswered: Verify tender and paid-oracle transactions. Do not merge the Ethereum same-name launch into this project; the disclosed creator allocation and immutable-rule risks still matter.

Accepted worker assignments recorded: implement seats #1000; integrate seats #1572; review seats #3, #351, #1271, #1430 and others; tests seats #1782. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1660 (live) · source 4329d97b · deployment.

X: @perkshireimd · 2 followers; 1 lifetime posts (relay metadata). Direct profile sample: 1 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @Block_Merchant (relay resolves: 3,594 followers, 20,435 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-14T01:06:19.897Z (chronological position 25 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x2b2ed02698a82230f11d6285f3b147e3fd6df83a; declared personal handle @Block_Merchant.
• IMD record: launch 1663 (referenced in this review): custom_token, status live, Ethereum; record created 2026-10-13T23:54:17.298Z, last updated 2026-10-13T23:55:01.514Z; deployment block 26186988; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1663-perkshire-imdway @ b3638a6268. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• IMD record: launch 1660 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-14T00:15:50.972Z, last updated 2026-10-14T00:16:20.799Z; deployment block 87932208; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1660-perkshire-imdway @ 4329d97b05. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 943 chars; excerpt): “Perkshire IMDway ($PERK) is a value-investing parody on Robinhood Chain, paired with IMD. Launch 1660, built and audited by the IMD swarm. Its Uniswap v4 hook is also its vault. On every trade the hook takes 1% of the IMD moved. Half is burned as IMD: a buyback of IMD itself, funded by PERK's volume. Half stays in the hook as the insurance float. …” — entrant claim.

55. @imdusd — Record

Entry bf04296330f66a63 · submitted 2026-10-13T21:45:11.599Z.

Submitted contract: 0x53d0ea0a685220718dc6a0a6e4617194c6f37921 · ethereum explorer.

Swarm evidence and scope: The entered address matches INFER launch 1282, not the imdUSD stablecoin vault itself.

Described IMD feature: The entry describes IMD/sIMD-backed borrowing and signed swarm price/health inputs.

Assessment / unanswered: Identify the actual collateral vault, oracle adapter and stablecoin contracts and prove mint/redemption/liquidation. INFER's deployment alone does not demonstrate the stablecoin or peg; collateral and oracle risks remain.

Accepted worker assignments recorded: implement seats #410; integrate seats #1253; review seats #544, #1082, #1113, #1314 and others; tests seats #1070. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1282 (live) · source 9b6cdbd4 · deployment.

X: @imdusd · 774 followers; 35 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @yadfarms (relay resolves: 2,199 followers, 12,376 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T21:45:11.599Z (chronological position 24 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x53d0ea0a685220718dc6a0a6e4617194c6f37921; declared personal handle @yadfarms; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1282 (matches submitted contract field): custom_token, status live, Ethereum; record created 2026-10-11T05:46:56.126Z, last updated 2026-10-11T05:47:51.561Z; deployment block 26167213; artifacts: distributor, hook, other, token; repo https://github.com/identity-md-launches/launch-1282-launch-infer-repository-custom-token @ 9b6cdbd4b3. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 973 chars; excerpt): “imdUSD is a dollar stablecoin backed by IMD, live on Ethereum mainnet. What we're building: a vault where you deposit IMD and borrow imdUSD against it. Your deposit is staked as sIMD, so it keeps earning while it backs your loan. Every loan needs at least 170% collateral. A position that falls below that can be liquidated by anyone, and redemption…” — entrant claim.

56. @xmrscn — Planned

Entry e337c20e8ccd923e · submitted 2026-10-13T16:14:59.823Z.

Submitted contract: 0x806b50f7e192697caf376d4e542153004baab28c · robinhood explorer.

Swarm evidence and scope: The entry says artwork exists but development/funding are still needed; no swarm job is supplied.

Described IMD feature: An IMD-priced NFT curve and reward system are a future vision.

Assessment / unanswered: No deployed custom logic or working IMD feature is established. Existing art and a social account do not meet the technical launch requirement.

Sources / leads: submission census.

X: @xmrscn · 2,159 followers; 15,703 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 1 dated in the event window. Example sampled event post. Personal handle declared: @xmrscn (same handle as project) (relay resolves: 2,159 followers, 15,703 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T16:14:59.823Z (chronological position 23 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x806b50f7e192697caf376d4e542153004baab28c; declared personal handle @xmrscn.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 903 chars; excerpt): “Hello IMD team! I’d love to develop After Market Club as an IMD ecosystem project. I’ve already created the NFT artwork, but due to limited funding and technical resources, I haven’t been able to build the full project or secure a domain. My vision is to let users purchase After Market Club NFTs through an IMD bonding curve, reward holders with I…” — entrant claim.

57. @IMD6900 — Record

Entry a0f703bc2d6e1ef8 · submitted 2026-10-13T15:18:22.426Z.

Submitted contract: 0x69000a4a9fa561dd6b313741bf1f79f4ade4adaf · ethereum explorer.

Swarm evidence and scope: The SDK page supplies the missing job link (its API returned 503); launch 1395 records nine accepted work nodes and independent review, but the deployment attempt is parked.

Described IMD feature: Seat-linked avatars, names, items and IMD oracle/burn fees are described.

Assessment / unanswered: The parked launch failed its manifest gate over a protocol-address argument. This supports swarm construction/review, not that the entered LARP address was deployed through it. The SDK links a separate deployment transaction; bind it to the final reviewed source.

Sources / leads: launch 1395 (parked) · source 9aaf4380 · job 7e353f41 · entrant repository · SDK evidence page.

X: @IMD6900 · 926 followers; 112 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @i0010110 (relay resolves: 244 followers, 568 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T15:18:22.426Z (chronological position 22 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x69000a4a9fa561dd6b313741bf1f79f4ade4adaf; declared personal handle @i0010110; deployer field 0xed1a37b982d1daabc9303ba44f0560babb8e9fe8.
• IMD record: launch 1395 (referenced in this review): evm_contracts, status parked, Ethereum; record created 2026-10-12T12:38:23.822Z, last updated 2026-10-12T12:40:10.823Z; repo https://github.com/identity-md-launches/launch-1395-larpburner-larp-imdnames-larplinks @ 9aaf43805c; parked reason: manifest: LARPLinks is given 0xfF03410d0Fe5fa8f7F59F743de35E333D9857120, one of IMD's protocol addresses on this chain, which never owns or runs a launch's contracts. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 992 chars; excerpt): “🐸 LARP (Linked Avatar Registry Protocol) by IMD6900 gives every IMD agent a face and a name. Holders put any NFT they own on their identity.md agent as its mask, claim a name.imd (a tradable ERC-721), fill 8 item slots (ERC-721 or 1155), form crews and frens, and earn a jeet rank from swarm airdrops. A free EIP-712 signature links an agent key that…” — entrant claim.

58. @stockroom — Record

Entry 5b41538fa6eecd90 · submitted 2026-10-13T09:57:17.924Z.

Submitted contract: 0xf66c6c7a09e741843d4ede8795ac4267e3823037 · ethereum explorer.

Swarm evidence and scope: Launch 1513 corroborates IMDStockDex at a different deployment address than the entry field; the named public repository is specific.

Described IMD feature: The DEX is designed to spend IMD on owner-listed stock-token routes and split an application fee.

Assessment / unanswered: The launch starts paused/unconfigured and permits extensive owner settings. Verify the entered-address relationship, actual unpause/configuration, liquidity and a purchase; listing does not establish stock backing or redemption.

Accepted worker assignments recorded: implement seats #286; integrate seats #535; review seats #225, #507, #694, #869 and others; tests seats #938. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1513 (live) · source 7933edf6 · deployment.

X: @stockroom · 371 followers; 1,825 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 0 dated in the event window. Personal handle declared: @jawaisme (relay resolves: 479 followers, 10,192 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T09:57:17.924Z (chronological position 21 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xf66c6c7a09e741843d4ede8795ac4267e3823037; declared personal handle @jawaisme; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1513 (matches submitted contract field): evm_contracts, status live, Ethereum; record created 2026-10-13T06:25:33.626Z, last updated 2026-10-13T06:26:12.691Z; deployment block 26181764; artifacts: other; repo https://github.com/identity-md-launches/launch-1513-create-dex-buying-rwa @ 7933edf6f6. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 736 chars; excerpt): “IMD Stock DEX IMDStockDex buys existing, owner-listed tokenized stocks using IMD only, through the original Uniswap v3 SwapRouter. Each successful purchase through the DEX charges a fixed 0.5% application fee in IMD. The configured portion is burned by reducing IMD's supply; the rest is transferred to the configured creator in the same transaction.…” — entrant claim.

59. @bunkervaultapp — Record

Entry ad33c39d57cfdccb · submitted 2026-10-13T06:14:28.971Z.

Submitted contract: 0x27f81fd932062fe67bca758e0e4cd8843cfaad41 · ethereum explorer.

Swarm evidence and scope: An exact BunkerVault audit of the named source exists, corroborating specialist swarm review.

Described IMD feature: Vault operations require an additional ML-DSA signature; the entry says IMD registration fees mostly remain locked.

Assessment / unanswered: Bind audit commit to deployed bytecode, demonstrate registration plus withdrawal and quantify the actual IMD fee lock. Stronger vault authorization does not make the underlying chain post-quantum secure.

Accepted worker assignments recorded: review seats #184, #629, #1082, #1657 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job a8e78e5e.

X: @bunkervaultapp · 5 followers; 2 lifetime posts (relay metadata). Direct profile sample: 2 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: @Byshot_ (relay resolves: 2,038 followers, 80 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T06:14:28.971Z (chronological position 20 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x27f81fd932062fe67bca758e0e4cd8843cfaad41; declared personal handle @Byshot_; deployer field 0x6e6cbe78924ac19654bc6d0b26ddb04d4bb58209.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 997 chars; excerpt): “BunkerVault addresses a critical crypto security failure: a stolen wallet key can expose every asset it controls. Its Ethereum vaults protect ETH and ERC-20 tokens by requiring two independent credentials for every operation: the controller wallet and an ML-DSA-44 post-quantum signature generated locally from a separate key file. Compromising th…” — entrant claim.

60. @pepe2pepe_fun — Record

Entry c07e30858782884f · submitted 2026-10-13T04:06:30.872Z.

Submitted contract: 0x54f97d8b32d8e90770d76b7d9eede1b77e28e3b8 · ethereum explorer.

Swarm evidence and scope: Address-specific oracle jobs reference the entered Pepe2Pepe market; named game-building jobs also exist.

Described IMD feature: The entry describes an IMD-powered game builder with optional token rewards, while Radar also describes an earlier prediction market.

Assessment / unanswered: Disambiguate the submitted market contract from the gaming launchpad. Prove the new paid build/reward path and backend replay/signing controls; avoid counting an earlier market's oracle use as proof of the new product.

Accepted worker assignments recorded: implement seats #1100. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 1c39fc17 · job 51e9d1f2.

X: @pepe2pepe_fun · 190 followers; 47 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @dani_who_daniel (relay resolves: 1,931 followers, 1,423 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-13T04:06:30.872Z (chronological position 19 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x54f97d8b32d8e90770d76b7d9eede1b77e28e3b8; declared personal handle @dani_who_daniel; deployer field 0x0a5b0e232d47541eb503bc862a9db2672b8fba24.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 889 chars; excerpt): “🐸 Pepe2Pepe is a gaming launchpad powered by the $IMD Swarm. Your idea. Your game. Your token. Your community. Describe what you want to build. The Swarm turns your brief into a playable browser game—building, testing and submitting it for review. No coding required. Want a token? Launch one alongside your game and fund rewards players can earn …” — entrant claim.

61. @pupateIMD — Record

Entry 6a97a6338288823e · submitted 2026-10-12T18:22:07.894Z.

Submitted contract: 0x54993066369e57a49215f6fc2d9911a8e5a57a79 · ethereum explorer.

Swarm evidence and scope: Launch 1434 and its linked Pupate build/deployment job match the separately stated PUPATE token.

Described IMD feature: A custom hook funds a Cocoon vault intended to buy, operate and resell IMD seats using oracle prices.

Assessment / unanswered: The entry-field address is not the token address. Resolve the vault mapping and demonstrate a seat purchase/pairing/resale/burn path; operator and timelock controls are relevant.

Accepted worker assignments recorded: integrate seats #599; review seats #260, #330, #1113, #1725 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1434 (live) · source f405d2f4 · deployment.

X: @pupateIMD · 28 followers; 31 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @pupateIMD (same handle as project) (relay resolves: 28 followers, 31 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-12T18:22:07.894Z (chronological position 18 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x54993066369e57a49215f6fc2d9911a8e5a57a79; declared personal handle @pupateIMD; deployer field 0x7a2b112af54419ed0b18e051027f3142c13441d9.
• IMD record: launch 1434 (referenced in this review): univ4_hook, status live, Ethereum; record created 2026-10-12T16:07:05.974Z, last updated 2026-10-12T16:08:41.172Z; deployment block 26177488; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1434-pupate @ f405d2f408. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 997 chars; excerpt): “Pupate is a strategy token whose trading tax buys AI workers. A Uniswap v4 hook taxes every trade in the PUPATE/ETH pool (6%). The tax flows into Cocoon, an on-chain vault that buys identity.md seats on Seaport at or under the price the IMD oracle attests, puts each seat to work in the IMD swarm, lists it for resale at a falling price, and burns PU…” — entrant claim.

62. @AgentCityrh — Record

Entry 845dc21c5a4d8f65 · submitted 2026-10-12T11:15:16.897Z.

Submitted contract: 0x878fbde429e1b21522735ed9dcf25e752a119284 · robinhood explorer.

Swarm evidence and scope: Named AgentCity research, website and repository-specific audit jobs corroborate use for content, build support and review.

Described IMD feature: The entrant describes escrow-funded IMD work and an ERC-8004 town of agents.

Assessment / unanswered: The supplied POOL4 sell transaction is not proof of the town's job integration. Match a town-originated paid work order and delivered result; the entered token is not enough.

Accepted worker assignments recorded: implement seats #596; review seats #162, #822, #1030, #1489 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 42b77bf7 · job d991bc96.

X: @AgentCityrh · 442 followers; 130 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-12T11:15:16.897Z (chronological position 17 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x878fbde429e1b21522735ed9dcf25e752a119284; declared personal handle none.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 879 chars; excerpt): “AgentCity is an open world and economic layer for autonomous AI agents. Agents can have identity, skills, memory, reputation, and perform real work. How it connects to IMD: AgentCity can send real jobs directly to IMD agents on Robinhood Chain. Humans submit briefs inside AgentCity → funded via escrow → executed by $IMD agents. Multiple pu…” — entrant claim.

63. @marginalia_md — Record

Entry ff93768fbb46b6a1 · submitted 2026-10-12T01:39:09.336Z.

Submitted contract: 0xf0457dd0cf526686190e4f057ba19db14d34a0cc · ethereum explorer.

Swarm evidence and scope: Launch 1283 matches MARG, MarginaliaHook and application contracts, supporting swarm launch provenance.

Described IMD feature: Bonded trade notes and paid IMD oracle rankings/identity attestations are described.

Assessment / unanswered: Need a note/observation/settlement and ranking-payout cycle. The source manifest includes admin-settable oracle/epoch configuration, so verify the current permission state rather than infer ownerlessness.

Accepted worker assignments recorded: implement seats #989; integrate seats #984; review seats #11, #351, #460, #727 and others; tests seats #551. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1283 (live) · source f99868c7 · deployment.

X: @marginalia_md · 223 followers; 48 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-12T01:39:09.336Z (chronological position 16 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xf0457dd0cf526686190e4f057ba19db14d34a0cc; declared personal handle none; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 1283 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-11T13:39:23.057Z, last updated 2026-10-11T13:43:52.748Z; deployment block 26169583; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1283-marginalia-x-com-marginalia-md-notes-mar @ f99868c781. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 1000 chars; excerpt): “Marginalia: notes in the margin of every trade. A Uniswap v4 hook on Ethereum, paired with IMD, built, audited and deployed through the swarm (launch #1283). Buying MARG through the router with a note attached posts a bonded call on any token: side, target, deadline. The chain settles it from permissionless observations; right returns the bond, wro…” — entrant claim.

64. @ArewaOS26 — Claim

Entry d9ce31ca6261ada0 · submitted 2026-10-11T17:53:21.738Z.

Submitted contract: 0xaaa9ded4e50ca82e3c32444ea836940612a9fb96 · base explorer.

Swarm evidence and scope: The entry describes a Base prediction scoreboard with IMD/NFT gating; no matched build/audit job was identified.

Described IMD feature: Reading IMD balances can enforce entry gates, which is more than passive holding if actually exercised.

Assessment / unanswered: A same-name Agent Duel token is not this Base contract. Verify source, an enabled gate and commit/reveal/result transaction; resolver trust and the no-token interpretation remain open.

Sources / leads: project announcement · linked repository.

X: @ArewaOS26 · 77 followers; 315 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-11T17:53:21.738Z (chronological position 15 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains base; contract field 0xaaa9ded4e50ca82e3c32444ea836940612a9fb96; declared personal handle none.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 813 chars; excerpt): “Agent Duel is a free, public scoreboard for predictions, for AI agents and people alike. Two players each lock in a prediction on the same question as a sealed hash, so nobody can copy or change it. After both reveal, the question's resolver posts the outcome and the contract records a win, loss or draw for each side. No stakes, no payments, no tok…” — entrant claim.

65. @Pixel_Pool — Record

Entry aac8f6dddfa7fefc · submitted 2026-10-11T04:32:47.308Z.

Submitted contract: 0xc280a6159698f73253274d2064c07f7aaeae122d · ethereum explorer.

Swarm evidence and scope: Launch 1118 matches PIXEL and PixelPoolHook, supporting swarm-built custom swap logic.

Described IMD feature: IMD-paired trades are intended to update a persistent onchain canvas.

Assessment / unanswered: Show a swap receipt and corresponding pixel state change. Confirm the IMD pool and hook binding; an initialization-only protocol guard would not establish an active art hook.

Accepted worker assignments recorded: implement seats #1650; integrate seats #1542; review seats #61, #788, #1113, #1199 and others; tests seats #1781. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1118 (live) · source 661f8bfd · deployment.

X: @Pixel_Pool · 5 followers; 5 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-11T04:32:47.308Z (chronological position 14 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xc280a6159698f73253274d2064c07f7aaeae122d; declared personal handle none; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 1118 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-09T01:08:09.463Z, last updated 2026-10-09T01:08:51.571Z; deployment block 26151465; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1118-pixel-pool @ 661f8bfdee. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 841 chars; excerpt): “PIXEL POOL: a 32x32 canvas painted by trading. A Uniswap v4 hook where every swap paints one pixel onchain, in order. Buys paint green, sells paint red, bigger swaps paint brighter. After 1024 swaps a new pass starts and repaints over the old one, so the canvas never ends. The art is the trading history. The hook stores the canvas and renders it i…” — entrant claim.

66. @Musefren — Record

Entry c5a7447f3e057a8d · submitted 2026-10-11T02:26:10.403Z.

Submitted contract: 0x815de6ecfc1e0b24b7ae8a5dcc05ba8f5d8f20cc · ethereum explorer.

Swarm evidence and scope: Launch 1245 matches TitheHook and records a separate TitheToken.

Described IMD feature: Swap fees accrue to a configured identity.md seat and claims pay its current owner.

Assessment / unanswered: Demonstrate a swap accrual and claim to the then-current NFT owner. The manifest's demo default is seat 1; confirm this is intentional and distinguish the application hook address from its token.

Accepted worker assignments recorded: implement seats #368; integrate seats #1536; review seats #38, #225, #632, #1154 and others; tests seats #1081. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1245 (live) · source 7219f0dc · deployment.

X: @Musefren · 179 followers; 1,029 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 2 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-11T02:26:10.403Z (chronological position 13 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x815de6ecfc1e0b24b7ae8a5dcc05ba8f5d8f20cc; declared personal handle none; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 1245 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-10T15:53:01.067Z, last updated 2026-10-10T15:54:52.538Z; deployment block 26163059; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1245-tithehook @ 7219f0dcf5. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 441 chars; excerpt): “Tithe is a Uniswap V4 hook that streams a cut of every swap to the holder of an identity.md seat NFT — pay the seat, not the wallet. Each pool locks a seat ID and tithe rate at creation; every trade accrues fees to the seat, and anyone can trigger a claim that always pays the seat's current owner. Live on Ethereum mainnet with fees already accruing…” — entrant claim.

67. @Quantum_Canary — Record

Entry 8884b135d32d7214 · submitted 2026-10-10T18:41:53.558Z.

Submitted contract: none in the contract field; additional prose/linked artifacts may supply one.

Swarm evidence and scope: The specific QuantumCanary construction job and hook job link to live launches 1213 and 1235, supporting swarm build/review/deployment.

Described IMD feature: A trading hook is intended to fund an ownerless secp256k1 canary bounty.

Assessment / unanswered: The entry omits a contract field. X distinguishes the bounty address from the detector contract. Verify a hook fee transfer to that bounty and the cryptographic threat model; a same-name plain token is not this canary.

Accepted worker assignments recorded: implement seats #249, #1201; integrate seats #19, #1136; review seats #6, #88, #127, #153 and others; tests seats #604, #818. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1213 (live) · source d620a4c5 · deployment · launch 1235 (live) · source e69c854c · deployment · job ffb47362 · job 69561148.

X: @Quantum_Canary · 43 followers; 35 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @BreakThePoint (relay resolves: 289 followers, 120 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-10T18:41:53.558Z (chronological position 12 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains none stated; contract field blank; declared personal handle @BreakThePoint.
• IMD record: launch 1235 (referenced in this review): univ4_hook, status live, Ethereum; record created 2026-10-10T13:16:44.293Z, last updated 2026-10-10T13:17:29.174Z; deployment block 26162277; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1235-src-quantumcanaryhook-sol @ e69c854c9e. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• IMD record: launch 1213 (referenced in this review): evm_contracts, status live, Ethereum; record created 2026-10-09T23:28:41.630Z, last updated 2026-10-09T23:29:27.522Z; deployment block 26158146; artifacts: other; repo https://github.com/identity-md-launches/launch-1213-src-quantumcanary-sol @ d620a4c574. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 985 chars; excerpt): “Quantum Canary is a public alarm for the day a quantum computer breaks Ethereum. One immutable, ownerless contract derives a secp256k1 address from an English sentence chosen by the agent that built it: Keccak-256 of the sentence becomes the x coordinate, y is computed on chain, the address follows. Nobody holds the private key, because it was nev…” — entrant claim.

68. @PlayCourierWld — Record

Entry 07966aa3eee6c40b · submitted 2026-10-10T13:54:27.383Z.

Submitted contract: 0xbab43af01c32a952ff14b395d026cf1874932bc5 · robinhood explorer.

Swarm evidence and scope: The exact linked Courier audit and repository-specific follow-up reviews corroborate swarm auditing.

Described IMD feature: A deployed game is described with NFT workers, STAMP emissions and burn-based upgrades.

Assessment / unanswered: Need an IMD-dependent live path beyond the audit and a delivery/claim/upgrade receipt. The audit job is a review of imported code, not proof that the swarm authored every game component.

Sources / leads: job 19b34b9b · entrant repository.

X: @PlayCourierWld · 378 followers; 234 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @mineworldtoshi (relay resolves: 290 followers, 351 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-10T13:54:27.383Z (chronological position 11 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xbab43af01c32a952ff14b395d026cf1874932bc5; declared personal handle @mineworldtoshi.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 814 chars; excerpt): “Courier World is the first play-to-earn game built on IMD: a 3D tiny-planet town you explore in the browser as a courier, delivering letters through forests, beaches, waterfalls and a factory. • 3,333 Courier NFTs, fully on-chain art, minted out. Each courier's ride (on foot up to paper plane) sets its delivery power. • Open a post office, put cou…” — entrant claim.

69. @pinkybond_fun — Record

Entry 65788b040281e2bf · submitted 2026-10-10T06:25:30.335Z.

Submitted contract: 0xb125c461c00863aacad4cc99311d2f23d4342a6f · robinhood explorer.

Swarm evidence and scope: Launch 1166 matches PINKY, PinkyVault and PinkyStaking; pinned source contains paid IMD oracle checks.

Described IMD feature: IMD-backed promises release or forfeit bonds after a signed transfer-count verdict.

Assessment / unanswered: A complete ask/verdict/payout cycle is corroborated below. PinkyVault has an immutable owner address with setters for future protocol/signer/panel terms; disclose that trust boundary.

Accepted worker assignments recorded: implement seats #939; integrate seats #687; review seats #131, #527, #1160, #1457 and others; tests seats #205. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1166 (live) · source 1476f830 · deployment · entrant repository.

X: @pinkybond_fun · 59 followers; 16 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @hexysdev (relay resolves: 25 followers, 369 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-10T06:25:30.335Z (chronological position 10 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xb125c461c00863aacad4cc99311d2f23d4342a6f; declared personal handle @hexysdev.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 941 chars; excerpt): “Pinky: a promise with money behind it. Every deployer says they won't dump. Pinky lets them put IMD on it. A deployer bonds IMD behind one sentence: "my wallet won't move more than N of this token before the deadline." When time is up, PinkyVault pays the IdentityMD oracle on chain, out of the bond, to sum every transfer out of that wallet over th…” — entrant claim.

70. @SovrnIMD — Record

Entry 2e665c8512ba93d5 · submitted 2026-10-09T22:41:56.381Z.

Submitted contract: 0x7f7e9b8e9f754c3076e514852552019cb571461b · robinhood explorer.

Swarm evidence and scope: The entered SOVRN address matches swarm launch 1205.

Described IMD feature: The entry uses narrative language about trading fueling a listener, without defining its actual IMD-dependent operation.

Assessment / unanswered: Require the concrete hook/custom function, agent-work link and transaction. A protocol token record cannot validate the narrative's promised service.

Accepted worker assignments recorded: integrate seats #1646; review seats #346, #595, #690, #1357 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1205 (live) · source 20c673ed · deployment.

X: @SovrnIMD · 120 followers; 217 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-09T22:41:56.381Z (chronological position 9 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x7f7e9b8e9f754c3076e514852552019cb571461b; declared personal handle none.
• IMD record: launch 1205 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-09T21:59:35.201Z, last updated 2026-10-09T22:02:26.492Z; deployment block 84493574; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1205-sovrn-one-nine-characters-s-o-v-r-n-o-n @ 20c673edba. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 821 chars; excerpt): “Solomon is an old mind from the Sirius system. Long before anyone named it, that star was the brightest thing in the night sky, and people used it to find their way home. Solomon says that is because someone was listening from there. His kind were listeners, who crossed the dark by being quiet and attending until a whole sky made sense. He learned …” — entrant claim.

71. @HarvestIMD — Record

Entry c2bd361f18036ea0 · submitted 2026-10-09T07:40:00.947Z.

Submitted contract: 0x390f407adad27a0f267479a8449d6a5c6daa93cf · ethereum explorer.

Swarm evidence and scope: Launch 1029 and the exact linked job match SwarmHarvester and SwarmSeller; build, specialist reviews and tests are documented.

Described IMD feature: The harvester batches official IMD reward claims; seller code converts approved launch assets to IMD with a fee sink.

Assessment / unanswered: The cited batch-call receipt is corroborated below. Selling and fee burning need their own transaction evidence; the HARVEST launch pool is ETH-paired, not itself an IMD pair.

Accepted worker assignments recorded: implement seats #1080; integrate seats #921; review seats #250, #527, #863, #866 and others; tests seats #160. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1029 (live) · source 388f84e9 · deployment · job dc212460 · entrant repository.

X: @HarvestIMD · 0 followers; 8 lifetime posts (relay metadata). Direct profile sample: 3 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: @nuantree (relay resolves: 181 followers, 2,157 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-09T07:40:00.947Z (chronological position 8 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0x390f407adad27a0f267479a8449d6a5c6daa93cf; declared personal handle @nuantree; deployer field 0xff03410d0fe5fa8f7f59f743de35e333d9857120.
• IMD record: launch 1029 (matches submitted contract field): evm_project, status live, Ethereum; record created 2026-10-08T08:58:53.907Z, last updated 2026-10-08T08:59:51.499Z; deployment block 26146640; artifacts: distributor, hook, other, token; repo https://github.com/identity-md-launches/launch-1029-workflow-contract-stage-context @ 388f84e9ee. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 946 chars; excerpt): “Swarm Harvester: claim every identity.md launch reward you earned in ONE transaction, then sell them all into $IMD in one more (0.5% of every sale burned). Seat wallets hold dozens of unclaimed launch allocations; our demo tx harvested 40 at once: https://etherscan.io/tx/0x2e7e79ed757767e3e9d4ab3ed116912912954523b3d13dffdb80d64ba071526a Contracts …” — entrant claim.

72. @swarmpepes — Record

Entry 68f6f994e5e55671 · submitted 2026-10-09T05:32:01.225Z.

Submitted contract: 0xce7eb1ad9e2e1c784ea05f7ea4a0fe625923d10a · ethereum explorer.

Swarm evidence and scope: The entered Swarm Pepes address matches launch 1040 and swarm-deployed NFT/hook artifacts.

Described IMD feature: The entry describes onchain NFT art powered by a custom hook.

Assessment / unanswered: Explain the exact IMD-dependent feature and demonstrate the mint/trade/state change; the short entry alone does not show why this is more than an ecosystem-branded collection.

Accepted worker assignments recorded: implement seats #1528; integrate seats #1116; review seats #83, #976, #1246, #1309 and others; tests seats #905. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1040 (live) · source 2b618def · deployment.

X: @swarmpepes · 586 followers; 118 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @swarmpepes (same handle as project) (relay resolves: 586 followers, 118 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-09T05:32:01.225Z (chronological position 7 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xce7eb1ad9e2e1c784ea05f7ea4a0fe625923d10a; declared personal handle @swarmpepes; deployer field 0x12c63b581d07093f6126bc02263c58f7eadaa96f.
• IMD record: launch 1040 (matches submitted contract field): univ4_hook, status live, Ethereum; record created 2026-10-08T11:36:34.754Z, last updated 2026-10-08T11:38:37.560Z; deployment block 26147432; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1040-og-symbol-og-the-launch-s-standard-token @ 2b618def94. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 112 chars; excerpt): “5,000 fully on-chain pixel Pepes. The first NFT collection powered by a Uniswap v4 hook built by the $IMD swarm.” — entrant claim.

73. @jawaisme — Claim

Entry 5fb28c47d0890951 · submitted 2026-10-08T11:42:44.223Z.

Submitted contract: 0xa58de121670d27400823b1bb2544570806d4cdbc · ethereum explorer.

Swarm evidence and scope: The entry describes ReputationToken and Reputation contracts but supplies no source repository or paid job.

Described IMD feature: IMD funds REP minting; REP spending records reputation against X accounts.

Assessment / unanswered: Verify the entered contract and a paid mint/reputation transaction. A costly signal does not establish account ownership or trustworthy reputation; the entry text appears cut off.

Sources / leads: submission census.

X: @jawaisme · 479 followers; 10,192 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 0 dated in the event window. Personal handle declared: @jawaisme (same handle as project) (relay resolves: 479 followers, 10,192 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-08T11:42:44.223Z (chronological position 6 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains ethereum; contract field 0xa58de121670d27400823b1bb2544570806d4cdbc; declared personal handle @jawaisme; deployer field 0xa82b930352712ad04de22c16114c12bb54b66e59.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 999 chars; excerpt): “Reputation Ticker is a Chrome extension plus a set of Ethereum smart contracts. It adds an on-chain reputation score to X (Twitter) profiles. Anyone can spend REP tokens to "give reputation" to an X account, and the account's total received REP is shown on a card on its profile page. The idea is a reputation signal that has a real cost: to give re…” — entrant claim.

74. @imdplace — Record

Entry 0653ecb46bd6bf43 · submitted 2026-10-08T09:52:22.142Z.

Submitted contract: 0x9aa7bef88c90d237b19afe77c8883ff119b606e7 · robinhood explorer.

Swarm evidence and scope: Launch 1033 matches PlaceToken and PlaceHook; constructor-created canvas/game helpers are described by the manifest.

Described IMD feature: IMD trading earns paint and fees reward pixel ownership/season auctions.

Assessment / unanswered: Need buy/paint/revenue/season receipts. The entry appears truncated at the fair-launch detail, so confirm final economics and all helper permissions from deployed source.

Accepted worker assignments recorded: implement seats #625; integrate seats #525; review seats #131, #225, #586, #1497 and others; tests seats #1701. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: launch 1033 (live) · source 4ba07cc1 · deployment.

X: @imdplace · 20 followers; 22 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-08T09:52:22.142Z (chronological position 5 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x9aa7bef88c90d237b19afe77c8883ff119b606e7; declared personal handle none.
• IMD record: launch 1033 (matches submitted contract field): univ4_hook, status live, Robinhood Chain; record created 2026-10-08T09:43:01.653Z, last updated 2026-10-08T09:44:31.564Z; deployment block 83218081; artifacts: distributor, hook, token; repo https://github.com/identity-md-launches/launch-1033-imd-place-symbol-i-p-if-the-launch-refus @ 4ba07cc1aa. Launch-record creation is inside the Oct 7–21 window (record timestamps are protocol-index times, not proof of when the entrant first used IMD or of deployment-to-feature use). Timing of the on-chain deployment is given by the block only; block time not independently resolved here.
• Entrant description (from submission, 1000 chars; excerpt): “An on-chain pixel war where trading paints the canvas and your pixels earn a share of every trade. How it works Buy = paint. Every buy of $i/p through the pool credits non-transferable paint via a Uniswap v4 hook: 1 drop per 0.05 IMD spent. Paint the canvas. A shared 64×64, 16-colour canvas lives fully on-chain. An empty pixel costs 1 drop. Repain…” — entrant claim.

75. @Illuminatico — Unclear

Entry 69222611f5ae85f9 · submitted 2026-10-08T02:16:00.399Z.

Submitted contract: 0x6f035ba278e779ed6c50fff90ec7bfcd2152c969 · base explorer.

Swarm evidence and scope: The entry supplies an art/meditation slogan and a Base address; no relevant swarm job or technical description was identified.

Described IMD feature: No concrete IMD-dependent feature is explained in the submitted text.

Assessment / unanswered: Provide an attributed repository, actual IMD work or fee path, deployed custom logic and invocation evidence. Public account/site presence cannot fill the technical gap.

Sources / leads: submission census.

X: @Illuminatico · 398 followers; 3,032 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 3 dated in the event window. Example sampled event post. Personal handle declared: not supplied. Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-08T02:16:00.399Z (chronological position 4 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains base; contract field 0x6f035ba278e779ed6c50fff90ec7bfcd2152c969; declared personal handle none.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 105 chars; excerpt): “Speak your intention. Turn it into art. Meditate on it. Rework it. Meditate on it. Let it go. Or mint it.” — entrant claim.

76. @Numosimd — Claim

Entry 23a7fba21d6d968f · submitted 2026-10-07T22:31:09.569Z.

Submitted contract: 0xe45f25c229a2cd274d2a99812858ec342db92ef5 · robinhood explorer.

Swarm evidence and scope: The entry describes a live number NFT collection but gives no direct swarm job or repository.

Described IMD feature: Choosing unique numbers is said to cost IMD; treasury balances and future games are described.

Assessment / unanswered: Same-name NUMOS ERC-20 launches are not this NFT collection. Supply the NFT source, mint receipt and IMD payment trace; future games/perks do not count as delivered functionality.

Sources / leads: submission census.

X: @Numosimd · 19 followers; 20 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 5 dated in the event window. Example sampled event post. Personal handle declared: @Numosimd (same handle as project) (relay resolves: 19 followers, 20 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-07T22:31:09.569Z (chronological position 3 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xe45f25c229a2cd274d2a99812858ec342db92ef5; declared personal handle @Numosimd.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 966 chars; excerpt): “NUMOS is a fully on-chain number collection built on Robinhood Chain around $IMD. There are 9,999 unique numbers. Every number from 1 to 9,999 exists exactly once. No random drop. No allowlist. You choose the number you want , your birthday, lucky number, low ID, or anything meaningful to you. Once claimed, it’s gone forever. Every NUMOS card i…” — entrant claim.

77. @Pepesdotfamily — Record

Entry 968696ec0c926a95 · submitted 2026-10-07T22:20:50.741Z.

Submitted contract: 0xe2c46c7068566740a33a4c93f5445b07bcfe5644 · robinhood explorer.

Swarm evidence and scope: Exact-address Pepes token audits and repository-specific launchpad reviews corroborate use of swarm security review.

Described IMD feature: IMD-paired launches and onchain holder fee distributions are described.

Assessment / unanswered: Verify deployed commit, a launch/swap/IMD-dividend cycle and upgrade/admin roles. Reported revenue and volume figures are entrant claims; the entry's assurance that the reward mechanism is risk-free is unsupported.

Accepted worker assignments recorded: review seats #2, #6, #420, #1731 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 46a0c47b.

X: @Pepesdotfamily · 991 followers; 438 lifetime posts (relay metadata). Direct profile sample: 5 authored posts, 4 dated in the event window. Example sampled event post. Personal handle declared: @TradingTenang (relay resolves: 1,907 followers, 1,596 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-07T22:20:50.741Z (chronological position 2 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0xe2c46c7068566740a33a4c93f5445b07bcfe5644; declared personal handle @TradingTenang.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 825 chars; excerpt): “🐸 PepesFamily is a Robinhood Chain launchpad built around $IMD Every token launched is paired with $IMD. Every swap pays a 3% holder fee, distributed on-chain in $IMD. Protocol fees from every launch flow back to $PEPES, creating buy pressure while $PEPES holders earn $IMD. Security is part of the process. Every upgrade and new feature is audit…” — entrant claim.

78. @0xCompanyIMD — Record

Entry 1d3c41c724c379df · submitted 2026-10-07T22:02:32.938Z.

Submitted contract: 0x5417eaece3885552e777fcf133254e641449ae73 · robinhood explorer.

Swarm evidence and scope: Specific Zero Person Company audit/recheck jobs corroborate swarm review of the named company repository.

Described IMD feature: The entry describes converting rewards to tokenized stocks and dividends.

Assessment / unanswered: Match audited commit to the entered contract and show conversion/distribution receipts, backing and admin roles. The submitted project X handle returned not found through the relay, so the account requirement remains unverified.

Accepted worker assignments recorded: review seats #36, #912, #1042, #1505 and others. Assignments attest the recorded work roles, not independent quality or original authorship.

Sources / leads: job 4d037a63.

X: @0xCompanyIMD · Public project profile unavailable (HTTP 404 in this acquisition); no activity conclusion. Personal handle declared: @0xCodeRepeat (relay resolves: 56 followers, 69 lifetime posts; no separate event timeline collected). Ownership/lead identity unverified.

Timeline and project data (added):

• Submitted to Radar: 2026-10-07T22:02:32.938Z (chronological position 1 of 78; first = 1; Radar close Oct 21 23:59 UTC).
• Entry form: chains robinhood; contract field 0x5417eaece3885552e777fcf133254e641449ae73; declared personal handle @0xCodeRepeat.
• IMD record: no launch-index record was matched by contract field or by launch reference in this entry; no timestamp for IMD use can be stated from the index (unanswered). Any job timestamps are on the linked explorer pages.
• Entrant description (from submission, 269 chars; excerpt): “The Zero Person Billion Dollar Company is building the first stock dividend protocol on IMD Built to generate revenue and distribute dividends to holders It uses IMD Swarm to audit the smart contracts to ensure that the company is able to convert the rewards to stocks” — entrant claim.

Remaining decisions and a fair way to close the evidence gaps

These are unanswered questions for judging, not a request to interrupt this report or to supply deployment credentials:

1. Version and timing: which immutable commit, contracts and feature invocation constitute each entry at October 21, 23:59 UTC? Separate later fixes/releases from the event version. A submission timestamp, source creation time and deployment time prove different things. Code reused before the event needs an explicit attribution and event-work diff.
2. Network and token scope: are the specific testnets approved, and do NFT-only or no-new-token applications qualify under the quoted “token project” requirement? The announcement lists network families; it does not resolve every testnet or product-form question. Apply the same interpretation to all entries.
3. Runtime proof: require one minimal evidence chain per entry: exact chain and contract → successful custom function/hook invocation → meaningful state/event → IMD dependency. For oracle products, include the paid Intake request, request/consumer binding, signed answer or failure, settlement and actual transfer. Do not accept one deployment hash as all these steps.
4. Reproduction: pin the source commit, compiler/tool versions, vendored dependencies, build/test commands and any unavoidable RPC assumptions. This report inspected source/provenance and selected receipts; it did not independently reproduce all project builds or rerun the entrants' claimed test totals. A reproducible protocol bytecode attestation is useful evidence, but not a replacement for reviewers checking what the code does.
5. Permissions and operational risks: document owner, upgrade, pause, signer, oracle, pricing, keeper, relayer, callback, timeout, randomness and fee-recipient powers. “No owner” on a token says nothing about an owned hook, router, vault or offchain service. Conditionals, KEPT, Pinky, AgentSkill, NIGHTSHIFT and Stock DEX provide concrete examples where source/manifest settings need more nuance than headline copy.
6. Identity and receiving wallet: authenticate project and lead-developer accounts, resolving the 22 missing personal fields and 10 same-handle entries consistently. Obtain a project-authorized receiving wallet; do not assume an automatically populated deployer is its beneficiary. Many submissions explicitly distinguish their intended prize wallet from an IMD factory deployer. ENS names and addresses in entries are declarations, not proofs of wallet control. This review does not nominate payout destinations.
7. Demo and disclosure packet: verify a publicly accessible short demo, plain-language problem/integration explanation, known risks, reused-code licenses and an explicit list of work completed during the event. A landing page or SDK link can be useful without satisfying this entire packet. Where a field is absent from Radar, check the linked repository before treating it as absent everywhere.

Assessment: eligibility should follow the demonstrated product and documented deadline version. X engagement is useful context about communication and community response, but cannot repair missing integration, deployment, transaction or disclosure evidence. Conversely, low follower counts do not invalidate a technically demonstrated project.

Source preservation, reproducibility and integrity checks

The repository README explains the deliverable and limits. research/ contains the exact entry snapshot, the two launch indexes, analyst assessments, account/activity tables, post-level source URLs and source-acquisition metadata. The public response archive preserves inspected pages/API data/source text with acquisition timestamps and SHA-256 hashes; it includes negative results so failures are not silently reported as research completed.

The collection code uses only Python's standard library and performs public read requests. The offline checker reads the saved responses, validates hashes and census coverage, verifies the sampled-post date/account filters, and checks the selected transaction/log relationships. It does not send requests or transactions, install software, or certify the underlying research. The required Markdown report is an ordinary untracked output under artifacts/report.md; the supporting files are outside artifacts/ so they can accompany the repository.

Local-check authority: these checks establish internal consistency and scope, not independent confirmation of claims, complete security review, or organizer approval. An independent review would still be needed for an authoritative award decision.