Messages published as transaction calldata from the collection owner's address, 0x200E71…d60fB1. Reproduced verbatim from chain.
30 messages, read at block 26,005,094 (2026-09-18 14:50:35 UTC). Included: transactions whose sender and recipient are both that address and whose calldata decodes as UTF-8 text; everything else is excluded.
Working on the bridge and adding more LP to rh chain to allow for more experimentation and eyes on the project 0x5F7Bb59365ce557C26dbcAa4EE9d39A4b95B7127, will deploy the burn executor and other stuff later in the day. It's same token, same supply, you will be able to bridge from the site, but there is no need to as staking and main functionality will remain on mainnet
Created an awesome IMD repo https://github.com/Identity-md/awesome-imd where you can add stuff you build , memes ,etc and others can find it, as I am getting msgs other ppl building stuff so easier to have a list there
few updates:
Hook looking good, will add more lp over the weekend.
About 4 projects wl IMD and the IMD NFTs to mint/airdrop in the past week, I am not officialy involved with any so don't like to tweet in case some rug, but privately i like to try all and in general i am pro experimentation, you can easily search for them on twitter.
The best way for me to share something is if you don't mention the ticker of the token (neither yours nor mine/imd)
Today this got created on top of fomo https://fomo.family/profile/imd_bot?tradeId=7287258d-df44-401a-a9c1-d2a2bb1c7847 so it's exciting to see the community continue to experiment...will check if this update gets auto posted.
The keepers are managing the hook and burns automatically, maybe a good short term target is to have so much volume and usage that the keeper can make 5 figs a month
Today FWA created a pool4 and already burned 300k fwa and generaed rewards, they have a super cool protocol and rhynotic already gave me a good ideas on how to improve the hook/use it for a new protocol i didn't think about (i will prolly never launch).
The p2p network is fully ready, i will release the daemon in the coming days, planned today but things got in the way. still need to define the incentives and define the product, i think it is powerful to have a high "Total Compute Locked" we can put to use but things need to feel right with timing too. This is still the most important/excitiing thing i am working on, all the rest are sidequests.
Experimenting with some stuff on rh if you been paying attention (onchain) over the past week.
</rant>
in the fist 48 hours since the pool4 hook went live and with only 15% of the LP deployed to it. we burned a total of ~16500 tokens (around 0.22% of the supply).
We also gained 2.5 eth and 1850 IMD of additional liquidity from base thanks to the FP mechanics.
The goal when the full lp is deployed to the hook is to set the burn cap to 25k IMD per day and this when the stakers should start seeing way more rewards. For now we'll wait over the weekend with the full deployment until more monitoring and seeing what settings can be adjusted to the hook.
We also got contacted by multple live tokens (some with higher market cap) that are interested in using the hook, so working on making it composable for other coins
The hook buys tokens for cheap when pepes are selling and burns 85% and distributes the rest to long term aligned holders so stakers not only make from 'tokens earned' but also everyone that hodls has a bigger share of the network over time, double incentive.
Next week will continue focusing on the p2p network, the new fable model and hopefully codex 6 will be public by then should help to launch this faster but also experimenting with other things in the meantime that might release before. As always everything experimental as risky so be careful
We burned today 2000 imd so far, annualized is 20% of the supply but if the hook works/all lp is deployed and no exploits (please god) we will be burning around 25k tokens per day, over the coming weeks depending on the market we could be burning more/sending more to stakers but there are pros and cons to each. I will write a longer thread tomorrow on the state of current things
I only added 4 eth and 5000 imd lp to the new hook, monitoring over the comign hours and will add more LP slowly but so far working as intended, barely any trades routing through it but so far 300 IMD burned, so i think we can expect to burn over 25k imd a day and over 2700 imd of rewards when the full lp is deplpoyed. Will monitor over the next 48 hours will making progress on the p2p network
today a new model from claude came out so i am taking a bit of time to test with the latest model. Our hook rebalances liquidity which is one of the most dangerous things you can do on a pool
Over the next 48 hours i will remove around 20% of the current LP and readd it on a new imd/eth pool with a new hook i've been working on, hopefully if all goes well will move all lp to this new pool over the coming weeks
Burned 8787 IMD from the LP fees. Still working, tomorrow will start inviting ppl privately to the testnet and hopefully there will be more news this week
To help bootstrap the protocol's compute power you'll need an NFT, a codex or claude subscription, preferably on a vps (for security) or on a computer that can run 24/7 even when you aren't around)
Progress: I had to rewrite everything from
scratch, was building the protocol on top of an existing system that ultimately made it too complex.
Good news is the new system seems to be working smooth.
We aren't creating a "univ4 hook", we are creating a new agentic p2p protocol. Idea might be too crazy or ambitious but I
think we lack that in crypto.
The first and most simple implementation is related to hooks but we should aim bigger imo, at the end of the day success
will depend on pepes believing in the meme.
I do not release more information bc obvious crypto incentives of forking, copying, etc. But today results hopefully mean
we are closer to the initial compute event.
Over the next 48 hours will move all LP to univ4 and burn more tokens.
Burned 16900 IMD. Testing Testing Testing all
the components, the threads going on on GH figured one part of the equation but no all the scope of what we are trying to
achieve, will share the docs site once i am confident i can execute on this.
@RektSconey created this explorer of the NFTs https://idmd-reader.pages.dev. Burned 15745 more tokens from the LP fees, made huge progress today on the system, will share more when have something concrete. We are trying something totally new, prolly fail, but if not..
IDM has pristine distribution that can't be recreated, all the suppply was released for free in the past bear market (2023) end experienced multiple 90% downturns, the
NFTs were also a free mint and while it got a bit botted, every bot already sold. in the future everyone will communicate
onchain too. The only dumps can be yours, if everyone rallies around this we can create something interesting where
everyone can be rewarded. Working around the clock, I will share more info on what we are working soon
The current Uniswap v3 pool uses the default 1%
fee tier, so half the fees collected are in IMD tokens. As of today, that balance is 30,784.00 IMD, which I plan to burn
periodically. I also made some progress on the harness today.
The hook will be highly experimental. I’ll
announce it before moving the LP. I’m also considering limiting trading to NFT holders for the first few hours—so the risks
are clear—then opening it to everyone. Thoughts?
You can copy the following msg to your Hermes/
openclaw agent so you get updates as soon as they happen as things will start to pick up soon.
"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."