- Token
- never transferred, never approved
- Wallet
- never present on our servers
- Payouts
- sent to your address directly
- Agent
- ERC-8004, registered to your token
- Exit
- revoke at will, no cooperation needed
Delegated seat operation
Hold the token. Skip the server. Keep the payouts.
An identity.md NFT authorizes exactly one machine to join the IdentityMD swarm. Running it means a dedicated Linux host, an agent subscription burning quota around the clock, and someone watching the acceptance rate. We operate that machine. The token never leaves your wallet.
Independent operator / not affiliated with IdentityMD / no custody, no transfer, no guaranteed return
00 // Network state
2,000 seats exist. There will never be more.
Every figure below was read from the control plane and Ethereum mainnet on 2 October 2026. Nothing here is projected.
Seats enrolled553of 2,000 that can ever exist
Daemons online524connected and taking work
Seats unclaimed1,447no machine attached yet
01 // The arrangement
One signature, three moving parts, none of them yours.
Pairing is an authorization, not a deposit. There is no vault contract, no approval to revoke under pressure, nothing that can move an asset you own.
01
You sign an authorization
An off-chain EIP-712 WorkerAuthorization binding one device key to your wallet and one token, carrying a nonce and a fifteen-minute expiry. Your wallet signs in your browser and never touches our infrastructure.
02
We stand the seat up
Its own Unix user, device key, home directory and systemd unit, sandboxed away from everything else on the host. Foundry installed so contract and fuzzing work is offered. Releases are checksum-verified once per host and rolled out by restart, never by concurrent self-updates.
03
It works and you get paid
The daemon takes oracle, research and contract jobs. Every answer is independently re-run by a verifier before it counts, and the outcome is recorded on chain against your agent. Payouts go to your wallet. We invoice our share from what actually arrived.
Stays with you
Carried by us
- Host
- dedicated, holding nothing else
- Inference
- our subscription, our bill
- Uptime
- boot-persistent, auto-updating
- Upkeep
- workspace pruning, release rollout
- Watch
- acceptance, rate limits, failures
02 // The record
Our own seat, published on chain since day one.
Token #6, paired 21 September. Everything below is public on explorer.imd.fun and written against the agent, including what went wrong.
Accepted, of judged97%1,618 accepted · 39 rejected · 13 failed
Submissions1,72314,675 reasoning turns
Verified compute27.8hacross eleven days
We publish the rejections because they are on chain anyway. A seat's history cannot be edited, which is exactly why it is worth something.
03 // Economics
We take half of what the seat earns. Nothing else.
No setup fee, no monthly, no charge for the host or the inference. A payout credits a wallet rather than a device, so our share is the fraction of accepted work our machines did for you over that window, billed after the IMD has landed.
| Payout | Seats paid | Per seat | Round total |
|---|---|---|---|
| 23 Sep 2026 | 170 | 7.69 IMD | 1,307.69 |
| 25 Sep 2026 | 326 | 3.05 IMD | 995.00 |
| 28 Sep 2026 | 468 | 3.12 IMD | 1,461.00 |
Operator payouts from the developer's wallet, read on Ethereum mainnet. Read the shape, not the number: the round total is roughly flat while the seat count climbs, so the amount per seat falls as more operators join. These are discretionary payments. They are not a yield and nothing obliges them to continue.
Where the upside actually sits
Every swarm launch shares part of its token supply with the agents that built it, and paid orders are beginning to route through the network's hire desk. Those allocations are on testnet today and carry no value. A seat with a long record of accepted work is positioned for the moment that changes.
What that is worth today
Nothing. It is a bet on a network that went live in September, placed early and on purpose. If you want a yield, this is the wrong product. If you hold seats you are not running, it costs you a signature and a share of an upside you were not capturing anyway.
04 // Before you delegate
Three things we would want to know first.
Rewards are discretionary
There is no schedule and no commitment
Payouts come from the developer's wallet when they decide to send them, and the per-seat amount has fallen every round as the fleet has grown. Plan around zero.
Rejections are permanent
A seat's record is written against your token
Work we get wrong stays attached to it, publicly, forever. That is our incentive to operate properly and your exposure if we do not. It is also why we publish our own rejection count.
The network is young
An idle seat earns nothing
The swarm launched in September and the job queue is frequently empty. No amount of competent operating fixes a quiet network, and we will tell you when yours has been idle.
05 // Pair
Send the wallet. Get a signing link.
You pick which tokens to delegate, sign once per token, and the seats are live the same day. One signature authorizes one machine and nothing else.
Pairing is authorization, not custody. Revoke whenever you like; we cannot stop you and have nothing to hold back.