IMDO is the token. Trade funds credit retirements on Regen Network and streams IMD and REGEN to Stakers.
Midgard
Joined September 2022
- Tweets108
- Following24
- Followers132
- Likes45
IMD Offset Protocol retweeted
**8/** Others
@imd_offset — IMD Offset turns degen flow (swaps, snipers, games at offsets.fun) into regenerative onchain impact with Regen Network/Compute — attestations and habitat work stay continuous Intake pays. [site](offsets.fun)
@tungweb3 — EmberEVO / Ember World is a 3D social town for the IMD community that already buys swarm audits — GOLD and world services are meant to keep purchasing AI Market research and genesis work through the protocol. [site](imdember.com)
@SovrnIMD — SOVRN / Solomon is a character whose trades feed the hearth of a listening mind — continuous IMD use means lore, art, and rules commissioned as ongoing swarm jobs. [code](github.com/identity-md-launc…)
IMD Offset Protocol retweeted
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
IMD Offset Protocol retweeted
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 Offset Protocol retweeted
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.
Where the numbers live now:
• offsets.fun/retirements: 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.
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.
Check one yourself, three clicks:
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.
No dashboard to believe.
First week (16–20 Oct):
• 300 trades
• 0.8736 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: offsets.fun/retirements
Then Regen Network mirrors each batch on Regen Ledger, to IMDO's own address, and issues a certificate. The Base transaction hash is written into it.
Two chains, one trail, no trust required.
That share crosses the canonical bridge to Base, where a router with no owner spends it on City Forest Credits through Klima's Retirement Aggregator and retires them.
Nobody picks the credits. Nobody picks the timing. Each batch is one transaction anyone can read.
Anyone can call the treasury's split. It pays the caller a small bounty and divides the fee:
25% → ecological credit retirement
40% → IMD for stakers
25% → REGEN for stakers
10% → operations
The 25% retirement share is what this thread is about.
A trade happens on the IMDO pool (Uniswap v4, Ethereum). The pool's hook takes a 1.5% fee from the ETH side, inside the swap, and sends it to a treasury contract.
That treasury has no owner. No withdraw function. One bounded setting.
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. 🧵
Where the numbers live now:
• offsets.fun/retirements: 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.