IMD FLOWPrepare my job
← All documentation

Project brief

English · Project documentationDownload .md ↓

The idea

Make IMD easier to use. Someone arrives with ETH and wants to perform an IdentityMD action. IMD Flow is designed to acquire exactly the IMD missing from that person's wallet, then hand back to IdentityMD's normal payment process.

The product targets a specific onboarding interruption: needing to leave an application, buy a token, and return before completing a paid action. This is a product hypothesis, not a measured conversion improvement.

Who it serves

  • Users starting jobs, workflows, and oracle requests through IdentityMD.
  • Developers who want a clear acquisition step before an IMD payment.

The public website offers a read-only demonstration: it retrieves current requirements from the official API and calculates a shortfall using an illustrative balance entered by the visitor. No wallet is connected and no action is purchased by the demo.

What exists today

An ownerless ETH-to-IMD exact-output router MVP, Ethereum mainnet-fork tests, spending/refund checks, payment integration code, a presentation website, and English technical documentation. The recorded contract suite passed 49 aggregate tests. This is tested software, not an independently audited mainnet deployment. There is no public usage, revenue, market-size, or conversion metric asserted here.

V1 adds no router fee. It is focused on one route: ETH through the official POOL4 IMD market, with IMD delivered to the wallet. The same wallet then authorizes IdentityMD's existing x402 payment. The project does not replace IdentityMD, its token, its market, or its settlement process.

Planned Stockereum launch

The project owner intends to launch the product and a separate project token through Stockereum. The website presents this as a plan, not a completed listing, confirmed partnership, or active sale.

The project token is not IMD and is not required by the current router. Its name/ticker, role, pairing asset, trading-fee configuration, allocation implications, launch timing, and project listing are not finalized in this repository. No token price, return, fee entitlement, governance right, or holder reward is promised.

A useful token design must identify a concrete function and the contracts or processes that enforce it. The presentation website does not establish those rights. Product demand and the value of a token should not be treated as the same claim.

Two markets, two purposes

The existing product uses POOL4 to acquire exact IMD output. Stockereum's current documentation, reviewed on 2026-10-05, describes exact-input swaps and fixed launch settings. A future project-token market there is separate from the current payment-acquisition route; it must not silently replace POOL4 or change the router's exact-output requirement.

Platform documentation is not an on-chain verification of a proposed launch. Its contracts, quote-asset availability, fees, and immutable choices must be reviewed again before any launch parameters are approved. No token launch or real transaction was performed for this website iteration.

Delivery milestones

  1. MVP and mainnet-fork evidence: available.
  2. Independent review and remediation: pending.
  3. Approved, verified production deployment: pending.
  4. Full live payment acceptance with a controlled wallet: pending.
  5. Public release, operational monitoring, and user feedback: follow the acceptance steps.

The token-design and launch track proceeds separately and requires its own finalized parameters. No launch date is promised. A future funding plan can be tied to engineering, independent review, integration validation, and deployment operations; no funding target or budget allocation is asserted here.

Official references

IMD Flow is presented as an independent project. No endorsement by IdentityMD or Stockereum is claimed.