HARD GRADE this public thesis about Identity.md (IMD) and SIMD. Be brutal — inflate nothing.

THESIS: IMD prices the work. SIMD pays for a look at the work. Those are not the same job.

@SuperIMD_eth sits next to Identity.md. It does not replace it. IMD is the control plane. SIMD is an outside reader and a payer. Mixing the two is the mistake most posts make.

IMD sells labor at a fixed price. A job.open costs 0.5 IMD. Payment uses x402 and Permit2 on Ethereum. The fee is public. The job is offered to enrolled seats. It is not sent to one named agent. A seat is one of 2,000 IMD NFTs, registered under ERC-8004. The holder runs the worker on their own machine and pays for their own Claude or Codex key. After a submission, IMD checks the work. verifier-rerun rebuilds code-like jobs in a sealed container and checks that only allowed files changed. verifier-paths covers sites, images, audio, and video, and those are not re-run the same way. Other seats can review. Accepted work is logged onchain as reputation. There is a standing read per seat. That verification lives inside IMD. It is not a SIMD feature.

SIMD, on si-md.xyz, reads public IMD routes and stores cycles as observation, then inference, then proposal, then execution, then a verified result. If a field is missing, the page is supposed to say UNAVAILABLE. The observer cycle does not sign a wallet and does not pay. Hire does pay. A hot payer wallet opens real jobs at 0.5 IMD. The vault at 0xd60483Eb8004e3DE3e283b3efF0e67FBb57f9B21 is meant to refund that wallet from IMD collected around SIMD activity. The site still lists token 0xbb0c1f82a2ea0253ea3d91c2f05caded82133415. A 7 October post from the same account said vault IMD comes from fees on 0xb6026518463ec80f1cb33e4318e802487c27f995. Those are two contracts. A reader should not treat them as one token until the docs switch the published address.

The useful loop is simple. IMD sets a price for a checkable task. SIMD can buy some of those tasks and show the receipt. The account has said fees cover about 50% of job cost, and some batches were refunded in full. The docs are stricter. A standing rule of “100% of verified task price” is marked NOT IN FORCE until an on-chain release rule exists. Contest auto-payout is also not in force. Payout rows are transfers that left the vault. They are not a promise that the next job is covered. If more than five paid opens land in five minutes, Hire freezes. That burst guard is a real limit, not a slogan.

This split has one hard tradeoff. A clean 0.5 IMD fee is a signal that someone wanted the job enough to pay. If SIMD refunds half or all of that fee, the signal gets weaker. Demand can rise because the work is cheaper. The price stops proving outside commitment. Both things can be true. The test is whether paid jobs still produce files a stranger can open, or whether the vault mostly funds jobs the payer opened for itself.

What would change my mind: if the vault address stops sending IMD to the payer, the subsidy claim is false. If Hire jobs do not appear on explorer.imd.fun as paid by the SIMD payer, the “real work” claim is false. If the docs keep two different contract addresses with no migration note, the token claim is incomplete. sIMD, the staked IMD share, is a third thing and should not be called SIMD.

Impact, if the split holds: builders get a cheaper way to buy swarm labor, and everyone else gets a public window on seats, jobs, and payouts. The value is not a new chat bot. The value is a priced task, a receipt, and a subsidy that can be checked onchain. That is the whole case for IMD plus @SuperIMD_eth.

TWEET: https://x.com/AltHunter_01/status/2107902135325413803

AUTHOR: @AltHunter_01 · followers≈59 (impact measured separately; do NOT invent follower counts)

RUBRIC (quality integer 0-10 — NOT /100). Default LOW. Most posts land 2–5. 8+ is rare.

0–2 scam/spam/garbage / copy-paste

3–4 fluff, slogans, generic crypto, no mechanism, no