IMD · explained
reading chain…
imd.fun pool4 github

IMD, explained.

A token, a Uniswap v4 hook that only ever shrinks its supply, 2,000 on-chain identities meant to become compute nodes, a launchpad priced in the token, and an AI agent that ships smart contracts. One machine, built by one developer.

How it fits, assuming you know nothing. Unofficial. Numbers read from chain every ten minutes.

Price
·
market cap ·
Supply on Ethereum
·
IMD · only goes down
Destroyed so far
·
burned on Base since May
identity.md floor
·
2,000 minted
Staked
·
of supply, as sIMD
Community coins
·
launched
1

The short version

Four sentences.

IMD is a token on Ethereum. Around it sits a Uniswap v4 pool the protocol owns outright, with a hook that destroys IMD whenever people sell into it: 85% of every batch it retires is burned, and 15% goes to stakers, to a fund for an AI agent, and to a reserve for a planned network of NFT-holding compute nodes. Supply only shrinks. Everything else on imd.fun is a wire back into that one pool.

It is built and run by Adam (@surfcoderepeat), who calls it experimental and posts updates as text inside Ethereum transactions.

2

One token, three names

IMD is Fren Pet, renamed twice. Scanners get this wrong, so start here.

Fren Pet was a tamagotchi game on Base (Aug 2023) whose token, FP, was given away through play. In Oct 2025 Adam bridged it to Ethereum through a LayerZero contract with a rename switch. It became VIBE in Jan 2026 and Identity.md / IMD in May 2026, the day the NFTs minted. Same supply, both chains, bridgeable 1:1 either way. Burns go back to Base and are destroyed there. "Mintable" on scanners means the bridge, nothing else.

Where the supply isbridge ↗
  1. 31 Aug 2023Fren Pet launches on Base.
  2. 4 Oct 2025FP bridged to Ethereum, renameable.
  3. 14 May 2026identity.md mints: 2,000 free, one per wallet. Updates move on-chain.
  4. 17 Aug 2026All liquidity moved to Uniswap v4. Community Coins two days later.
  5. 2 Sep 2026POOL4 hook goes live with 4 ETH and 5,000 IMD.
  6. 10 Sep 2026FWA opens the first POOL4 market for another token.
  7. 11 Sep 2026"The p2p network is fully ready, I will release the daemon in the coming days."
3

The engine: POOL4

A pool the protocol owns, with a hook that turns selling into burning.

  1. The hook is the only liquidity provider in a full-range ETH/IMD pool with a 1% fee. Any router can trade it. The hook runs after a swap settles, so it never changes your quote.
  2. The pool has an inventory cap. Sells push IMD in; anything above the cap is removed as liquidity, not sold, so the trim does not move the price.
  3. 85% of the trimmed IMD is destroyed. The ETH that came back with it becomes a standing bid under the market. A keeper re-places it after every rebalance.
  4. The cap ratchets down as people buy, at most 1,000 IMD a day, never below 1,000 IMD. The plan: 25,000 IMD burned a day once all liquidity is in the hook.
85 burned
85% burned. Every holder owns more of what is left.
4.5% to stakers (sIMD vault, live).
6% to the agent. Bonding reserve, opens at $4 per IMD.
4.5% to nodes. Reserve for NFT compute nodes, not live.
IMD destroyed on Base, per dayburn receiver ↗

Before 2 Sep the burns were pool fees Adam sent by hand. Since then the hook trims and anyone can bridge the batch. Trims land here a little after they happen.

The market, livepool4.imd.fun ↗
ETH in the pool
·
IMD in the pool · cap
·
Buy wall
·
Retired by trims
·
Staked in sIMD
·
1 sIMD redeems for
·

Staking: deposit IMD, get sIMD, a vault share that redeems for more IMD as rewards drip in. No lock, no claim. The APR on the stake page is a launch rate until the full pool is deployed.

4

The NFT: identity.md

2,000 free-mint identities drawn entirely on-chain. Meant to be nodes, not profile pictures.

identity.md, rendered from the contract
read from the contract

identity.md

OpenSea ↗

Each token can hold a markdown file by IPFS hash, lockable forever (the Memory State and Memory Lock traits). An identity.md is the file an agent reads to know who it is; each NFT is a slot for one. To run a node you will need one NFT, a Claude or Codex subscription, and a machine that runs 24/7. One NFT per daemon. The daemon has not shipped; the 4.5% node reserve is earning now, and compute rewards "won't be in IMD as no inflation."

The collection, liveOpenSea ↗
Floor
·
Owners
·
Volume, all time
·
Node reserve waiting
·
5

Community coins

Anyone can launch a coin for gas. Every coin is priced in IMD.

Each coin sits on a bonding curve denominated in IMD, not ETH. You pay ETH, the hook swaps it to IMD through the main pool, keeps that IMD as the coin's backing, and 0.5% of it is burned. So the coins move together: buying any coin lifts IMD and every other coin; selling marks them all down. And every exit is paid from backing through that one pool, which is usually far below the headline market cap. Names are free text; several coins call themselves IMD.

Top coins by IMD backinglaunchpad ↗
Coins launched
·
Trades
·
Volume
·
IMD burned by it
·
6

The agent

An orchestrator that writes, tests and deploys contracts. Already running in public.

The 6% bonding slice pays for a lead orchestrator: one AI agent that turns a spec into a finished, reviewed, deployed project. Its output is the GitHub org Identity-md: an empty base, a launch.json, then commits by "IdentityMD Worker" with Adam reviewing. A verifier rebuilds every job offline and checks the agent only touched the files it was allowed to. Deploys are on Sepolia so far.

  1. Jobs 30, 31SwapCounterHook, the smallest useful v4 hook. It counts swaps.
  2. Job 33TickOracleHook and its token TOS: a v3-style price oracle for any v4 pool.
  3. Job 34A lottery with bounded rounds, pull-based prizes, timeout refunds.
  4. Job 35Duel Arena, commit-reveal rock-paper-scissors with token escrow.

The metric Adam says he cares about is Total Compute Locked. NFT nodes fill it, bonding pays the orchestrator that hands them jobs, and the p2p daemon tying the two together is the piece still to ship. Other tokens can use the hook too: a launcher opens a capped market for any token in one transaction. FWA (Fake World Assets) was first, on 10 Sep; it has retired · FWA so far. Adam's research skill lets any coding agent read any POOL4 market.

7

Where the dev talks

Transactions to himself, with the update in the calldata. Latest one, read from chain.

Have your own agent watch for new posts 
Please monitor Ethereum mainnet for new onchain messages sent as self-transactions by this address:

0x200E710aCAA6A93bbc77146026328C40F1d60fB1

Only alert me for transactions where:
- from = 0x200E710aCAA6A93bbc77146026328C40F1d60fB1
- to = 0x200E710aCAA6A93bbc77146026328C40F1d60fB1

Check at least once per minute. Decode the transaction input/data field as UTF-8 text when possible, and notify me immediately when a new matching transaction/message appears.

Do not alert me for old transactions that already existed when you set this up. Keep a seen-hashes state file/list so I only get notified once per new tx.

Each alert should include:
- decoded message text, if readable
- tx hash
- timestamp/block time
- Ethereum mainnet explorer link

Use Ethereum mainnet only.