With $IMD and the NFTs hitting new ATH, I wanted to break down the project for new holders. IdentityMD is building a system where AI creates products, NFTs identify participants in the contributor network, and the $IMD economy is meant to fund its operations. Let’s walk through it from a potential customer’s perspective. >> Someone comes in with an idea Say they ask “Build me a token and a market with specific trading rules” It is important to separate two things: > Community Coins: a separate coin launcher that already exists. It has a form with a name, ticker and launch button. > The core IdentityMD project: a broader concept involving an AI coordinator and a network of nodes. A simple launcher being live does not prove that this network is operational. The system may primarily work on its own projects rather than orders from external customers. The docs discuss launching ideas and running the lead AI coordinator, but do not yet describe a ready-to-use marketplace for services. >> Who coordinates the work? The docs mention a lead orchestrator, the main AI coordinator. In simple terms, this is the central agent around which a network of other participants is planned. It is reasonable to expect it to turn ideas into tasks and coordinate their execution. >> Who does the work, and why do they need an NFT? Based on Adam’s previously uncovered messages, the expected participant setup looks like this: one Identity.md NFT > one daemon > access to Codex or Claude > an always-on computer or VPS A daemon is a continuously running program. The operator runs and maintains it. In this model, the NFT serves as an access pass and an identifier for a specific network participant. The program is expected to interact with AI and carry out assigned tasks. This means the operator does not necessarily need to write code themselves. 4. How does the system check whether the AI did the work correctly? The expected workflow: task > code generation > independent verification > result acceptance > test deployment and an onchain record The public test repo is designed for end-to-end testing of the contributor network. The contract template requires reproducible builds and restricts changes to files that could let a worker tamper with verification. The Sepolia executor and registry uncovered earlier add another piece to the picture: execution results can be recorded onchain. >> Where does IMD fit in? The most likely role for IMD is to become the financial backbone of IdentityMD’s AI network, helping the system accumulate resources for compute and participant rewards. Part of this mechanism already works. POOL4 withdraws surplus IMD from the trading pool, sends the bulk of it to burn, and distributes the rest between stakers and reserves for AI and NFT nodes. Stakers receive existing tokens, with no additional emissions. The next planned step is bonding: selling reserve IMD for ETH at a discount with gradual vesting, to fund compute for the lead AI coordinator. A separate reserve is earmarked for future NFT-node rewards. This connects trading activity, staking and network funding through IMD. But mandatory IMD payments for customer orders, operator collateral and the exact payout rules remain unconfirmed. >> How does the IMD reserve turn into compute funding? the protocol accumulates IMD > sells part of the reserve for ETH at a discount with gradual vesting > spends the ETH on compute for the AI coordinator The bond buyer gets tokens on specified terms, while the protocol gets funds to run the AI. The docs say bonding will open at $4 per IMD. For now, though, the reserve is live, not the bond market itself. >> Who benefits, and how? An IMD staker deposits tokens and receives sIMD, representing their share of the vault. Rewards increase the amount of IMD backing that share. An NFT-node operator is expected to participate in the network’s work. A dedicated reward reserve is already in place for these participants. A bond buyer will eventually be able to provide ETH to the protocol in exchange for reserve IMD on specified terms. In short: > the NFT is meant to identify a participant in the contributor network > IMD plays a role in its economy > sIMD represents a share of staking rewards > bonding is meant to turn accumulated IMD into compute funding

81,500 wallets left $44.8M in dead protocols. I ran full withdrawal simulations. The exits still executed. A closed website and inactive social accounts do not always mean the assets are gone. At the time of my research, I confirmed: > 29 major DeFi protocols > a technically executable exit for every included position Example: Aave V1 At Ethereum block 25,730,407, I found: > 5,545 eligible positions > 5,084 EOA wallets > 20 supported routes > $3.281M in withdrawable value These assets are sitting idle and earning zero yield for their owners. You can check an old wallet and its available exit route at defireclaim.com You can also withdraw directly through the protocol’s own contracts. Most of the positions are worth tens or hundreds of dollars. A user may have tested a new farm, left behind a small balance and completely forgotten about it years later. But some of the confirmed positions are much larger: > Balancer V1 > 0x7...6FE > $622K > Badger Legacy > 0xb...491 > $458K > PoolTogether V3 > 0x1...221 > $448K > Aave V1 > 0xB...42D > $401K > Kernel BNB > 0xa...825 > $371K > Ribbon Legacy > 0x8...b48 > $369K I hope they are doing well. Maybe they are just very rich. Other protocol examples: > dYdX v3 > $24M > Aave V1 > $3.3M > Ribbon Legacy > $3.2M > Badger Legacy > $2.7M > Balancer V1 > $2.2M > Stader BNBx > $2M > Kernel BNB > $1.3M How I calculated the numbers For each protocol, I: > identified legacy contracts and possible exit routes > reconstructed holders and full position balances at a fixed block > separated standard EOA wallets from smart contracts and delegated accounts > checked underlying asset prices and available liquidity > performed a full eth_call for the entire position > confirmed the route through a state-changing fork > excluded dust, illiquid, unpriced and reverting positions But contract state changes. Liquidity can decrease, a route can be paused, or an individual position may already have been withdrawn by its owner. That is why DeFiReclaim checks current availability separately for each wallet immediately before creating a transaction: > whether the position still exists > its full current balance > whether the route is active > whether sufficient liquidity is available > which asset the user will receive > how much they will receive > whether the full withdrawal passes simulation > whether the target and calldata match the verified route If any mandatory check fails, DeFiReclaim does not offer the transaction. Check your old wallets If you farmed, provided liquidity or tested new DeFi protocols between 2020 and 2026, your old wallets may be worth checking. I built DeFiReclaim to find legacy positions and verify exit routes that may still be available. All you need is a public wallet address. If you have any issues with the website or a withdrawal, you can always DM me. I also welcome any feedback.

What has been happening with $IMD since the network launched On September 20, the IdentityMD AI agent testnet was opened to NFT operators I compiled the key points: results, demand and potential earnings For anyone unfamiliar with the project, an NFT holder connects a computer or VPS and their own Codex or Claude. The customer pays in IMD, while the network distributes the work among agents and verifies the result What is already live: > around 590 connected agents > 1,136 customer payments from 163 wallets > 63 wallets have paid more than once > 166 contract deployments on Sepolia marked as live since the network opened > 102 completed contract - website workflows A total of 576.5 IMD has been paid for requests Automatic deployment of generated contracts is currently limited to Sepolia Users can now do more than just request a new project: > continue and improve previous work > schedule recurring tasks > request an AI review of existing code > deploy contracts without launching a token > receive a website, research, media or a signed oracle response The task history includes more than successful generations. It also shows review feedback, fixes, repeated testing and work being reassigned to other agents after failures In a thread, Adam also highlighted several community projects: > Pepe2Pepe: a prediction market using an IMD oracle > Pepes family: a token launch platform using IMD in trading pairs and the swarm to review its contracts > Swarm Pepe: an NFT collection created using the network > HIVE and IMD Strategy: projects accumulating NFT slots to organize agent work There are also earlier concepts such as INFER, a stablecoin whose economy is proposed to be linked to AI compute What about NFT earnings? Since Oct 1, tokenized launches have used the following distribution: > 2% goes to those who worked directly on the project. The allocation is split equally between wallets whose work was accepted by the system, for example development or review > 8% is split equally among eligible connected NFT nodes, even if they did not perform tasks for that specific project. The allocation is calculated per NFT node, not per wallet The recipient list is fixed when the project is approved for launch Simply holding an NFT in a wallet is not enough The node must be connected and meet the network’s requirements There is also a separate reserve of approximately 1,762 IMD for NFT nodes, including rewards accumulated before the network opened Essentially, you assign a task to an entire AI team. The network selects agents for the required work and assigns verification to other agents The result can be used in an application, passed to a smart contract or sent through another round of improvements This allows a single request to become the beginning of a project that can continue evolving within the same network Now we wait for the beta to end and for generated projects to be deployable on mainnet

What is @CatalystMkts_? Based on the site’s public JS code, event schemas and demo scenarios, it appears to be a hybrid between a prediction market and an automated token-buying mechanism Two networks are already included in the configuration: > Robinhood Chain with USDG > Base with USDC Markets can be built around three types of actions on X: > an account posts a specific phrase > follows another account > replies to another account For posts, the system can track either an exact match or a mention of the specified phrase It can monitor tweets, replies or both The likely flow: > users buy the token of a specific market in advance > the specified event happens on x > the market’s capital is used to buy a selected asset > the purchased asset is distributed among holders In the code, the event outcome is described as a buy action with a token address and network Even more interesting, the asset being purchased can remain hidden The outcomeHidden and revealMc fields, along with the demo scenarios, suggest that the target asset may only be revealed once a certain market cap is reached This means users could trade the expectation of an event without knowing which token the system will buy once it happens

The potential earning model for NFT operators is becoming clearer Previously, we saw a shared $IMD reward fund for network participants Now, personal allocations have appeared in the data for test launch #37, Bazaar Out of the 1 billion BZR supply, 100 million tokens were allocated to rewards, representing 10% of the total supply: > agent #10259: 58.34M BZR, or 58.34% of the reward pool > agent #10303: 41.66M BZR, or 41.66% of the reward pool Agent #10259 handled development and launch preparation Agent #10303 performed the review The allocations are tied to specific agents and wallets This is already a concrete example of a project distributing its own tokens among the participants who helped launch it The second potential source of rewards is the IMD reserve According to the POOL4 documentation, out of every 100 IMD removed through the pool inventory reduction mechanism, 4.5 IMD is reserved for NFT nodes The rules for distributing this reserve among active operators have not been revealed yet Two potential reward streams are now taking shape: > IMD from the protocol reserve > tokens from projects the agent helps create

Adam shared a bit more about his plans for IdentityMD According to him, agents running on VPSs will be able to connect to the network as early as tomorrow Adam also described the goal of IdentityMD: > someone proposes a new financial instrument > the system builds and launches it > attracts funding and liquidity > then maintains and improves the product IdentityMD is designed to automate the entire journey from an idea to a working financial application However, the capital formation mechanism has not been revealed yet A token and pool can be created automatically, but the ETH for liquidity still has to come from participants or the treasury The tests are already covering a longer workflow The new task #44, VolatilityGuard Lab, includes a protective Uniswap v4 hook, a test VGL token and a complete ETH/VGL swap website with wallet connection and live pool state tracking > development > testing and review > deployment > frontend integration > website publication This cycle has not been completed yet The next step is to bring it all the way to a working application with independent NFT operators participating in the process

I put together a list for anyone planning to trade from day one on Arc > Bridges Circle USDC Bridge: the official bridge bridge.usdc.com Across: a backup option app.across.to > Wallets supporting Arc OKX Wallet: announced day-one support Features include a scanner, wallet tracking, market and limit orders, copy trading and deposits web3.okx.com Bitget Wallet: announced day-one support for Arc mainnet web3.bitget.com > Token discovery and analytics RadarDEX: pairs, liquidity, volume, token age, trades and holders Includes contract address search and token filtering radardex.pro ArcTools: a general launch feed, wallet analytics and trading tools arctools.fun > Terminals and swaps TOLLY: trading terminal, charts, trades and token information tollylabs.com GMGN: token discovery, analytics and trading Arc is already listed in the official documentation for market data, swaps and orders gmgn.ai FOMO: Arc mainnet integration has appeared in the latest client fomo.family > Launchpads ArcPad: new token launches that go directly to Uniswap v3 arcpad.meme Warp: launch feed and bonding curve trading circlewarp.fun/terminal DYORSwap dyorswap.org Archemist: launches through v3 and v4 archemist.fun > Explorers Arc Mainnet Explorer: the address is already listed in app configurations, but it is currently behind Circle authentication explorer.arc.io ExploreMe: an explorer by STAKEME Currently paused until the public launch arc.exploreme.pro

New findings around $IMD and IdentityMD’s core direction On sepolia, test NFT №1 has already been linked to a specific AI agent, №10259 The agent now has a public profile showing its network registration status A FeedbackBatcher has also been deployed, a contract designed to record contributor reputation: > who completed the work > their role: development, testing or review > the score they received > where the proof of the result is stored The system is expected to recognize verified work even if the entire project never reaches an onchain launch This points to a much broader model than simply creating tokens Task №36 has appeared on GitHub: create and independently verify a fixed-supply token and a record registry What Adam says: > an API is planned for external tasks > the coordinator will split tasks into subtasks and distribute them across nodes > a basic explorer interface already exists > he planned to publish the daemon to npm over the weekend for the first testers > a new protocol built on top of POOL4 is being considered, but the details remain undisclosed > staking and the core functionality will remain on Ethereum > for Robinhood Chain, he is working on the bridge and liquidity, while the burn executor will be deployed separately Alongside the test project launches, we now have a specific NFT-based agent identity and reputation infrastructure Now we wait for the confirmed public release of the daemon and the full end-to-end cycle

A list of Ethereum launchpads in the style of robinhood:0x39dbed3a2bd333467115de45665cc57f813c4571 @fusi_ng Permissionless pairs on Ethereum. Live today: TSLA , GOOGL, SPCX, COPX and AAPL @senderdotfamily Launches tokens paired with stocks and ETFs The list already includes NVDAon, AAPLon, TSLAon and COINon @strawdotfamily A Uniswap v4 launchpad. Pairs with ETH and Ondo tokens. Dual pairs are already enabled @spir8l_com For now, pools are paired with the network’s native token. RWA pairs with $NVDA , $GOOGL and $TSLA have been announced for the coming days @NysePAD At launch, you choose the stock collateral and a hook: buyback and burn, ETH dividends, fee splitting, staking or a lottery @0xprogrammable A stock-paired model on Ethereum: NVDAon, TSLAon, AAPLon and other Ondo assets

Sent my ducks out to farm $SHELL Let’s see how this goes

Two notable $IMD updates IdentityMD has now deployed a game on Sepolia. Project #35, Duel Arena: rock-paper-scissors with bets placed in the DUEL token. > DUEL token created > game contract deployed > reward distributor created > pool launched The distribution is once again 10/80/10: > 10% to the contributor reward fund > 80% to liquidity > 10% to the treasury This is another confirmation of a mechanism through which IdentityMD contributors could receive tokens from the projects they help create. Another well-known Adam @Rhynotic is testing POOL4. He deposited 10 ETH to test the mechanics and is ready to add more liquidity if everything goes well. We’re getting closer to launch

Two days ago, Identity.md NFT holders made the wl for @FlockFall , a game launching on Robinhood Chain. I broke down the game mechanics and potential ways to earn. The core idea: ducks farm $SHELL, while foxes can steal both the rewards and the NFT itself. The outcome depends on the character, location and expedition duration. 1. Two types of characters All 6000 Genesis NFTs have already been minted. After the reveal, they will turn into 5400 ducks and 600 foxes. Ducks produce SHELL: 80% of the rewards accumulate on the character, while 20% goes into the shared fox pool. Carried rewards remain at risk until the character returns home. Foxes receive a share of the common pool based on their weight. Active foxes can also be automatically selected for attacks. 2. Choose a route and duration You send a character on an expedition, and everything else is calculated automatically. There are five expedition durations: 1.5 / 4 / 12 / 36 / 84 hours Three locations offer different duck production multipliers: > Pond ×0.65 rewards, lower encounter risk > Marsh ×1 rewards, standard risk > Wilds ×1.35 rewards, higher encounter risk For foxes, the location affects their chances of being selected as an attacker, but does not increase their share of the common pool. Longer expeditions allow more SHELL to accumulate, but also increase the chance of an attack. After the expedition, the character takes a safe journey home lasting 2 to 24 hours. There is also a paid early exit called Rush, which comes with another encounter risk. 3. You can lose more than just tokens A robbery takes 25% to 75% of the carried SHELL. If a character is captured, the attacking fox owner receives the NFT itself and all the SHELL it was carrying. Foxes can also become victims. 4. Rarity affects the mechanics Characters come in four tiers: T1 to T4. For ducks, the tier affects production. For foxes, it affects their reward weight and their chances of being selected as an attacker. Capture protection is: 0% / 35% / 65% / 85% Genesis status also cuts the remaining capture probability in half. 5. SHELL is required to mint new NFTs The Hatchery will release four Gen1 batches of 1000 characters each. Mint prices increase with every batch: 100 > 250 > 500 > 1000 SHELL SHELL spent on minting is burned. Batches unlock gradually. The second and subsequent batches require the previous 1,000 NFTs to be revealed and at least five days to pass since the previous batch opened. 6. Production gradually decreases As in-game emissions increase, the production multiplier declines: ×1 > ×0.5 > ×0.375 > ×0.25 > ×0.125 The first reduction happens after 2.25m SHELL in game emissions. The entire game is built around one choice: how much SHELL you are willing to accumulate in a single run and how much risk you are willing to take with your character. For now, I’m watching the launch and choosing the best strategy to start with.

New findings have surfaced around $IMD Two new projects have been published on GitHub, and a Sepolia deployment helps show how network participants could potentially earn. Yesterday, Identitymd was tested on a specific task: building a price oracle for Uniswap v4. The result has already been deployed on Sepolia, and the onchain record is linked to the source code on GitHub. In a single successful transaction: > the TOS token was created > a hook and reward distributor were deployed > liquidity was added > the result was recorded onchain The onchain record points to a specific commit in the public repo. The most interesting part is the token distribution for this test project: > 10% to the participant reward pool > 80% to liquidity > 10% to the treasury The distributor received 100M test TOS. This launch has a one-hour lock, after which recipients from a predefined list can claim their share. This reveals another possible source of rewards: Identitymd participants could receive a share of the tokens from projects they help build, rather than only IMD. Project No. 34 also appeared today: a separate lottery with ETH tickets, rounds, prize claims and refunds. Most likely, Adam is using it as another Identitymd test task: can the system build not only a hook, but also a complete app with game logic, tests and deployment preparation? Project creation, contract deployment, result recording and a reward pool are already coming together in the test environment. Now we’re waiting for proof of the next step: independent NFT operators completing this cycle, with clarity on how much they earn and for what work. Watching what comes next

The new Kraken validator on @HyperliquidX was funded by the same wallet that funded the active operational address of Backed/xStocks, a company within the Payward group, the owner of Kraken. The authority of the xStocks address is confirmed by the official contracts. Common funding source Wallet: 0x8e34dfb6b5af9ae7baf421f5c67e2ce2fa964170 On August 19, it sent 17 HYPE to the Backed Deployer address: 0x5f7a4c11bde4f218f0025ef444c369d838ffa2ad On August 28, the same funder sent 10,079 HYPE to the future Kraken validator: 0xddc5a378be9276069f7a3fa7d84fbe55fb74874b Backed’s official API lists the HyperEVM contracts for NVDAx and BDXx. Calling multiplierUpdater() on both returns the exact Backed address above. On September 8, it successfully executed updateMultiplierValue on BDXx. This is a permissioned function, so the wallet is actively servicing the contract. Payward’s acquisition of Backed was completed in January 2026, as confirmed by Kraken itself. The funder’s verified history as of September 9 contains 10 regular outgoing HYPE transfers on HyperEVM to three addresses: the validator, the Backed operator and one unattributed recipient. The funds for the future self-stake reached the validator on August 28, before Bloomberg reported that Hyperliquid was in talks with Payward. On September 9 , the address registered Kraken / Kraken Exchange Validator with a 10 000 HYPE self-stake and a 5% commission. The Kraken-branded validator and the confirmed Backed/xStocks operator share the same funding source.

Calculated the creator/LP fees from the original pools of the top memecoins on @RobinhoodCrypto $AI 2 131 NVDA = $481k $MICRODUCK 1 906 NVDA = $430k $PONS 135 WETH = $335k $ANSEM 3 174 SOL = $328k $AITAX 618 NVDA = $140k $MEME 19 853 AMC = $50k $GAGE 19.80 ETH = $49k $BONER 751 HIMS = $21k $CASHCAT 0.561 WETH = $1.4k $BRUNO 0.0535 WETH = $133 Doesn’t quite line up with today’s stories about $1k in fees in 10 minutes

Holders of identity.md, QUOTRONS and StonkBrokers NFTs have been added to the @QuoPull allowlist QuoPull: $QUOTRON raffles funded by $QPULL trading Dev @mylesdaughtry is also behind the Gloombles and On-Chain Flwrs NFT projects. The mechanics according to the docs: The WL guarantees a mint of up to 3 Art Passes at 0.0075 ETH each, followed by a chance to mint up to 8 in total before the public mint. An Art Pass lets you buy $QPULL during the first 2 hours of trading, while access remains closed to everyone else. When you buy $QPULL, you receive the token itself, XP points and roughly one ticket for every $10 spent. Each ticket enters the daily raffles for 7 days. Part of the trading tax is used to buy $QUOTRON, which is distributed in three ways: > daily raffles among ticket holders > a weekly raffle for wallets holding at least 4 Art Passes > rewards for the top 25 by XP, earned through purchases and by using losing tickets after they expire Art Passes also provide free entries into the daily raffles. The passes will have different rarity tiers. 80% of mint proceeds go to initial liquidity, 10% to the prize pool and another 10% to the team and project operations. The buy tax is 4%. The sell tax starts at 20% and gradually drops to 4% over 48 hours. Of all tax revenue, 80% goes to prizes and 20% to the team and project expenses. Next up, a wl for @standard_rsv, hopefully

Looks like Fables is preparing new markets for $AMC (the one paired with $MEME), $PONS and $CASHCAT The onchain registry now includes: > AMC/USDG > AMC/ETH > PONS/ETH > CASHCAT/USDG The protocol’s TVL reached $15.6M in just two weeks A reminder: Fables already has the $PROLOGUE token. Holding it is expected to qualify holders for an airdrop of the main $FABLES token. Under the current tokenomics, PROLOGUE holders are allocated 25M FABLES, or 2.5% of the total supply. The team includes @0xlayans and @0xcs361 Their previous project, Alphix, also focused on dynamic fees through Uniswap v4 hooks, but on Base and Arbitrum. Fables looks like a pivot of the same idea, now focused on RWAs

.@vladtenev followed $MEME Is this bullish or what?

You’re still not bullish enough on $IMD Adam is inviting projects that need automated market management, buybacks and burns for their own tokens. In the replies, he confirms that other teams using this mechanism should benefit IMD. He’s essentially building additional utility for the token outside the core product, which hasn’t even launched yet. A reminder of what’s already here: > Community Coins launchpad: 0.5% of the IMD side of each trade goes to burn. > Fren Pet game: depending on the action, tokens are locked or burned. Players receive a share of trading fees. More trading volume means more fees. > POOL4 and staking: buybacks, burns and the distribution of some IMD withdrawn from the pool to stakers are already live, with no new emissions. Reserves are also accumulating to fund AI and NFT nodes in the future. Now POOL4 for third-party projects is being added to the mix. Getting serious flashbacks to last year’s ethereum:0xc50673edb3a7b94e8cad8a7d4e0cd68864e33edf launch

I analyzed all memecoins launched on Robinhood chain and @fomo over the last 30 days The final sample included 2,847 tokens. Criteria: > at least $20K in liquidity > nonzero 24h trading volume > both buys and sells > ATH calculated using the main trading pair Duplicates, older and irrelevant tokens were excluded, along with RWAs, wrapped tokens and system assets. How many tokens reached each ATH market cap threshold: ≥ $1M: 219 tokens, or 7.69% ≥ $3M: 115 tokens, or 4.04% ≥ $5M: 74 tokens, or 2.6% ≥ $10M: 33 tokens, or 1.16% ≥ $15M: 24 tokens, or 0.84% ≥ $100M: 4 tokens, or 0.14% Only four reached $100M: > $MEME > $GOOSE > $NOVAAI > $SHRUB My main takeaway: instead of spreading entries across a bunch of early microcaps, it makes more sense to wait for a token to establish itself around $1M and trade the move toward $3M. Of the 219 tokens that reached $1M, 115 made it to $3M. That’s 52.5%. Based on this sample alone, the approach would look like this: > enter after consolidation around $1M MC or a retest of that level > hold the full core position until $3M > take profit on 80–90% at $3M > hold the rest until $5M > above $5M, keep only a small runner > trim further around $10–15M > above $15M, leave a moonbag worth 0.5–1% of the portfolio > treat $100M as a bonus scenario The idea: capture the move from $1M to $3M and leave only a small moonbag for the rare run to $100M.