IMD Offset Protocol

IMDO is live on Ethereum. Seat holders: your share is waiting at claim it from the wallet that holds your identity.md seat, 1/10 unlocks each day for ten days. axlREGEN holders: Contract 0x87B525bC5Ff6D7211f16291219c363e082ed4e9F

RT @imdradar: entries for the IMD hackathon are closed, and it went way beyond what we expected 78 projects entered. hooks, vaults, games, stablecoins, AI agents, lending, art, most of them built and audited by the IMD swarm and live on chain that’s a lot more than we planned for, and every entry deserves a real look. so the review is taking a bit longer than we said we’ll spend the weekend going through all of them, and results and prizes will be announced early next week sorry for the wait, and thank you to every builder who shipped. this ecosystem is building faster than anyone expected

RT @surfcoderepeat: On Oct 13–14, someone attempted to send 563 fake requests telling IMD workers to run shell commands and paste the output via different methods and prompts, and publish as oracle task results, to create websites and even smart contracts that would print the worker credentials. Luckily everyone is running on dedicated VPS and we nor users require to hold any funds to run the IMD workers. around 50 workers leaked local files, protocol keys (to pair their NFT to their claude sub) and other keys that might have been on their machine. We closed the entry point the same day, added request screening, and shipped sandboxed workers as well as hardened the swarm from prompt injection like this. I believe this was an attempt to infiltrate the IMD swarm and steal claude and codex keys, as well as IPs and possibly other data, when unsuccessful they also tried to impersonate the user running the worker to be able to use their inference

IMD NFT Holders. The clock is ticking. Come get your airdrop. Feel free to stake it, burn it, sell it. If you don't, it will burn.

RT @KlimaProtocol: Our retirement aggregator streamlines carbon offset access and retirement for builders in DeFi and beyond. @imd_offset provides a great example, and is channeling financing to @regen_network carbon projects held in our protocol in an automated and transparent process onchain.

The IMD swarm runs on compute. Compute has a footprint. So we built IMDO so that every trade pays for regeneration. Automatically. In public. No one in the loop. Here is how it works, and the first week of proof. 🧵

Thank you @KlimaProtocol (the Retirement Aggregator and the credits) and @regen_network (the ledger, the certificates and the mirror). This rail exists because both sides built things anyone can plug into.

@KlimaProtocol @regen_network Where the numbers live now: • every retirement, both ends of the trail • the rail status page, every 15 min • Regen address: regen183ht37fsp2fhnq3gneyjycp08c3ju4xnvxnvan Regenerative contribution, not a net-zero claim. Estimates labelled as estimates.

@KlimaDAO @regen_network Where the numbers live now: • every retirement, both ends of the trail • the rail status page, every 15 min • Regen address: regen183ht37fsp2fhnq3gneyjycp08c3ju4xnvxnvan Regenerative contribution, not a net-zero claim. Estimates labelled as estimates.

First week (16–19 Oct): • 292 trades • 0.8648 ETH in fees to the treasury • 7 retirement batches on Base • 27.984 t of City Forest Credits retired • 7 certificates on Regen Ledger, every one mirrored Every row, linked both ways:

Check one yourself: 1. Open a row's Base transaction. The C02-004 credit sent to the zero address is the retirement. 2. Open its Regen Ledger certificate. Its reason field carries base_tx: and that same hash. 3. Match batch and quantity.