# IMD and SIMD: bullish and bearish cases

Research cut-off: 5 October 2026, Asia/Taipei (live SIMD snapshot: 4 October 2026, 19:07 UTC).

**Assessment:** IMD has the more direct utility case: it is the payment asset for the agent network. SIMD offers a speculative, fee-funded distribution channel for that network. Subsidizing useful work could help adoption, but neither subsidized activity nor token trading establishes sustainable business demand or a fair token valuation. I would require stronger evidence of repeat customers for IMD and enforceable token value capture for SIMD before forming a valuation-based bullish view.

## What the assets are

| Asset | Attributable identification | Implication |
|---|---|---|
| IMD | The IMD payment API names Ethereum token `0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7`. Its live capabilities response prices job opening at 0.5 IMD. [Payment API](https://api.imd.fun/requests/capabilities), [API documentation](https://imd.fun/docs/#paid-requests) | Direct use in purchasing network services; use alone does not establish appreciation. |
| SIMD | The linked X account and website identify `0xbb0c1f82a2ea0253ea3d91c2f05caded82133415`. [Launch post](https://x.com/SuperIMD_eth/status/2106788356973637684), [SIMD website](https://si-md.xyz/) | Separate token claiming to fund IMD jobs with fees. Association with IMD does not prove official endorsement. |
| sIMD | IMD's staking vault share. [POOL4 documentation](https://pool4.imd.fun/docs#staking) | **Not SIMD.** Do not apply IMD staking yields or redemption rights to SIMD. |

## Evidence and its limits

**Observed facts about published material, not independently proven contract behavior:**

1. The launch post says fees are claimed every five minutes to cover 50% of IMD job costs. A subsequent post says the vault received 70% of protocol fees in IMD and coverage increased to 100%. The later wallet-free hiring announcement describes paying through the vault. These are issuer claims, with the newer posts superseding the earlier coverage claim. [Launch](https://x.com/SuperIMD_eth/status/2106788356973637684), [coverage update](https://x.com/SuperIMD_eth/status/2106792390157803948), [hiring announcement](https://x.com/SuperIMD_eth/status/2106820488307835361).
2. The SIMD API snapshot reports vault `0xd60483Eb8004e3DE3e283b3efF0e67FBb57f9B21`, 101.424318 IMD, 100% coverage, and a 0.5 IMD payout. It reports 5.75 IMD distributed across 12 transfers to seven recipients, including eleven 0.5 IMD transfers and one 0.25 IMD transfer. Its own note defines these as outgoing transfers. **Transfer counts are not proof of completed jobs, unique customers, or revenue.** [Live state](https://si-md.xyz/api/state); frozen response in `evidence/simd-state.json`.
3. The first job linked by X is marked completed in the IMD API. Its objective is a promotional visual for SIMD, and still describes approximately 50% subsidies. This supports a concrete example of execution, but it is project marketing, not evidence of independent commercial demand. The response lists a paying wallet; I did not independently establish its relationship to the SIMD vault. [Job record](https://api.imd.fun/jobs/b6246ba3-6571-4c45-9730-ff835277b8b4), [explorer](https://explorer.imd.fun/jobs/b6246ba3-6571-4c45-9730-ff835277b8b4).
4. POOL4 describes excess-inventory trims: 85% burned, 4.5% for stakers, 6% for bonding, and 4.5% for nodes. It describes an ETH buy wall and no inflation. It also discloses unaudited contracts, owner withdrawal powers, and planned bonding/node payouts. Its factory-status passages conflict. These are design disclosures, not a verified deployment-state audit. [POOL4 documentation](https://pool4.imd.fun/docs).

## IMD bullish case — inference

- **Service demand can create token demand.** If independent users repeatedly purchase valuable jobs, IMD becomes a working payment asset. SIMD's wallet-free subsidy could reduce onboarding friction and introduce users who later pay themselves. The supporting evidence is the payment API and hiring announcement above; customer conversion remains unmeasured.
- **Scarcity may strengthen the economics.** If the documented burn mechanism operates safely and sustained demand meets declining supply, holders could benefit. This is conditional: destroying tokens does not by itself increase total network value.
- **A visible execution record is more useful than a roadmap alone.** A completed promotional job offers an initial example. The stronger catalyst would be reproducible, useful outputs for unrelated customers and repeat paid orders rather than more launch content.

## IMD bearish case — inference

- **Subsidized usage can overstate demand.** Free requests may attract low-value or abusive work. The first linked job promotes SIMD itself; it cannot establish customers' willingness to pay.
- **Payment utility may produce little holding demand.** Customers can acquire IMD immediately before paying, while recipients may sell. Revenue destination, retention, and compute costs determine whether activity supports holders.
- **Technical and governance losses can overwhelm utility.** The documented escape hatches and unaudited status weaken the scarcity thesis. Current ownership, renunciation, bridge configuration, and actual liquidity were not verified.
- **Burns and a buy wall offer no guaranteed price floor.** Market demand can fall faster than supply. I have no verified current price, capitalization, holder concentration, or executable depth with which to judge whether the opportunity is already priced in.

## SIMD bullish case — inference

- **A useful acquisition loop is plausible:** token activity generates fees; fees fund IMD work; useful results attract users and attention; continued activity replenishes the vault. X describes this funding proposition, and the state API reports payouts. Each causal step beyond those observations remains a hypothesis.
- **Wallet-free hiring improves accessibility.** Users may care about receiving a report, image, or application more than managing crypto payments. Durable repeat use would make this a stronger distribution channel.
- **Transparent reserves could make the subsidy measurable.** Using the reported balance and current task price, `101.424318 / 0.5 = 202.85`: approximately **202 whole requests**, assuming all reserves are spendable, no replenishment, and no other costs. This is a capacity estimate, not a runway in days or a service guarantee.

## SIMD bearish case — inference

- **Trading-funded subsidies can be circular.** If speculative trading generates the fees, falling activity removes the budget precisely when attention weakens. Useful jobs must eventually justify continued funding independently of launch excitement.
- **Value to IMD users is not automatically value to SIMD holders.** No verified holder entitlement to dividends, redemption, buybacks, or protocol cash flows was established. SIMD could successfully subsidize IMD while its own price falls.
- **A 100% subsidy does not prove 100% of operating costs are funded.** Paying the 0.5 IMD request price does not establish coverage of inference subscriptions, servers, gas, maintenance, or contributor compensation.
- **Free access needs controls.** Without adequate eligibility, quotas, or abuse prevention, a small reserve could be exhausted quickly. Wallet-free access alone does not establish anonymous, unlimited, or guaranteed access.
- **Execution and token risk remain unresolved.** Fee routing, the remaining 30%, owner powers, automation failures, contract security, supply distribution, and liquidity have not been independently verified.

## What would change the assessment

| Unanswered question | Evidence needed | Effect on the thesis |
|---|---|---|
| Is demand independent and recurring? | Completed outputs, repeat customers, paid versus subsidized requests, and customer concentration over several weeks | Repeat unsubsidized use strengthens IMD; predominantly self-promotion weakens both. |
| Can SIMD sustain subsidies? | Verified fee inflows, allocation rules, full expenses, payout-to-job reconciliation, and replenishment history | Positive net funding through quiet markets strengthens SIMD; reserve depletion weakens it. |
| Do SIMD holders capture value? | Verified contract rules and enforceable holder rights | Clarifies whether adoption benefits the token or only service users. |
| Can administrators redirect assets? | Verified source, current owners, upgrade rights, timelocks/multisigs, and independent audit | Reduces or confirms governance and loss risks. |
| Are either tokens attractively valued? | Timestamped prices, supply, concentrations, vesting, pool depth, and trade-size slippage | Necessary for an entry-price judgment; absent here. |
| Is SIMD officially recognized by IMD? | Confirmation from IMD's own channels | Resolves an affiliation claim that the linked account alone cannot establish. |

## Method and uncertainty

The X research browser initially failed, but a direct HTTPS fetch recovered the public profile and five visible posts. This is a partial account sample, not a complete history. Direct post links above identify the exact claims; saved HTML preserves the retrieved page. The linked site, its read-only state endpoint, and IMD's read-only APIs were inspected without submitting jobs or making payments.

The state responses are operator-provided, not independent chain verification. The reported 92 IMD in an earlier X post differs from the later 101.424318 IMD snapshot; changing balances are plausible, but the intervening inflows were not reconciled. Etherscan contract pages were blocked by the research browser. The payout transaction linked by X is [here](https://etherscan.io/tx/0xd4319dee167471a5f522759b0af26703670e07c3e819377ef8aba1fdf9e0aba4), but its success, logs, and fee provenance were not independently confirmed.

The report makes no price target or verified audit claim. Its strongest conclusion is the distinction between IMD service utility and SIMD's still-unproven subsidy sustainability and holder value capture.