IMD by @surfcoderepeat wants an idea to become a working financial application through a network of AI agents. Its bigger ambition is for those agents to earn enough to keep building, eventually supporting companies managed entirely by the network. That starts with two connected pieces: Identity MD NFTs organise the workforce, while the $IMD token connects payments and incentives. Each of the 2,000 NFTs represents one swarm seat* Holders connect a machine running the IMD daemon and supply AI inference, the computation behind answers and code. The NFT lets an agent contribute to the network, although owning one doesn’t guarantee profitable work. Customers bring that workforce an objective, such as building a vault and its website. The system checks the request and breaks it into implementation, testing, review and delivery with pricing is 0.5 IMD per request, paid on @Ethereum through x402. When that work produces a token-bearing launch, the agents can participate in its economics. - 2% of the new token’s supply goes to wallets with accepted launch work, - 8% is allocated per connected seat at admission. The requester controls the remaining 90% with their value depends on what gets built and whether anyone wants it. The same workforce can also answer oracle questions for applications. With chain evidence, agents propose calculations at fixed blocks, and the deployer reruns the agreed calculation before signing. A contract can verify that signature and the agreement count. POOL4 connects its trading activity to funding. When selling pushes IMD inventory above the protocol-owned pool’s cap, excess tokens and proportional ETH are removed. - 85% of that IMD is earmarked for burning - 4.5% for stakers - 6% for orchestrator bonding - 4.5% for NFT inference nodes Stakers receive sIMD shares with growing IMD backing. Bonding would convert reserved tokens into ETH for computation, but bonding and node payouts remain unfinished. As of October 5, swarm deployment remains Sepolia-only, while published work includes imdUSD documentation and Ember World audits. However, there are some concerns like shared AI mistakes, deployer-dependent signing and unaudited POOL4 contracts remain substantial risks, including documented owner powers to withdraw liquidity and sweep staked IMD. The encouraging part is that each useful application can give people another reason to use IMD and bring more work to the swarm. If that demand becomes recurring, it could help fund the agents that build the next application. There’s still execution ahead, but the foundation is taking shape: a workforce, a payment token and a growing set of experiments. Turning those experiments into products people keep using would bring IMD closer to its ambition of an economy that sustains its own builders. NFA. DYOR.