Who posts about Identity.md ($IMD) on X/Twitter?

Research window: 7 August–7 November 2026, ending at 17:45:31 UTC on 7 November. The start is 00:00 UTC on 7 August; these are calendar dates, not three completed calendar months.

I identified 151 accounts in 469 dated, deduplicated primary post observations: 111 with enough content to describe an observed subject, and 40 whose evidence is mainly a brief mention, reaction, or question. Coverage is partial. A complete archive of all posts and all accounts over the three months was not available. The tables give the account list actually supported by the retrieved evidence.

For protocol changes, the clearest starting points in this evidence are @surfcoderepeat and @taylor_. For explanations, see @LastToSign, @0xminion, @Bankless, and @Eli5defi. For ecosystem discovery, see @imdradar and @theimddaily. This is a guide to subjects covered, not an endorsement or ranking of accuracy; the dated evidence is in the tables below.

How to read the evidence. Attribution, dates, and the linked words/posts are observations. Each “observed focus” is my interpretation of that account's IMD-related material in this sample, not a measurement of its entire timeline. “Repeated” means at least three accepted observations across at least two dates; “limited” includes a single thread or a small sample and makes the focus tentative. No minimum posting frequency was required for inclusion. Counts are lower bounds on posts observed, not total posts published. They include replies and quote posts, but exclude native reposts. Accounts can discuss several subjects; each appears once under its most useful observed category.

Project identity. The target is the Identity.md agent-work network described in the project's documentation, with the Ethereum IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7. This distinguishes it from weather/business-school “IMD” results and unrelated same-symbol tokens. Ecosystem tokens such as IDM, IMDT, SHIFT, and SIMD are distinct from IMD. Discussing one is relevant here only where its connection to IMD is explicit or specifically documented as contextual evidence.

The supported account list

The evidence column links representative posts and their UTC dates. The complete set of accepted post IDs, short excerpts, source URLs, retrieval dates, relevance reasons, and evidence classes is in the post ledger; the account table contains every accepted ID for each account. Full post text is not redistributed.

Protocol development — 4 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@surfcoderepeat	Protocol design and releases, agent orchestration, oracle applications, ecosystem launches, and the goal of companies managed by agents.	23 posts on 12 date(s); 2026-10-02; 2026-11-04; 2026-11-06	Repeated in sample
@taylor_	User interfaces and operator apps, hands-on ecosystem demonstrations, and experiments coordinating many IMD agents toward a goal.	13 posts on 6 date(s); 2026-10-18; 2026-10-28; 2026-11-06	Repeated in sample
@builtbyimd	A publication feed for swarm outputs: newly launched tokens, games, and other delivered jobs. Feed-like behavior is observed; official ownership is not established here.	5 posts on 1 date(s); 2026-11-07; 2026-11-07	Limited / tentative
@nxt3d	Agent identity, NFT metadata, discovery, and reputation interfaces in discussion around IMD. The sampled technical statements are the author's claims.	2 posts on 2 date(s); 2026-10-15	Limited / tentative

Explanations and ecosystem news — 15 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@Bankless	An introductory analysis of IMD's workforce, token economics, and experimental risks, distributed as an X article. One observed IMD publication, not an established recurring beat.	1 posts on 1 date(s); 2026-09-28	Limited / tentative
@LastToSign	Detailed research threads following NFT/daemon utility, code and testnet discoveries, launch economics, operator rewards, and the distinction between hypotheses and shipped features.	15 posts on 12 date(s); 2026-08-10; 2026-09-02; 2026-10-05	Repeated in sample
@Eli5defi	A broad explainer connecting NFT seats, paid work, and launch rewards, with explicit discussion of execution and security risks. One observed long post.	1 posts on 1 date(s); 2026-10-07	Limited / tentative
@0xminion	Long-form synthesis and ecosystem maps: reasoning oracles, paid agent work, ownership, launchpads, and possible sources of repeat demand.	11 posts on 4 date(s); 2026-10-12; 2026-10-27; 2026-11-06	Repeated in sample
@ahboyash	An accessible explanation of the token-versus-NFT roles, Fren Pet lineage, supply accounting, and the protocol's economic loop. One observed IMD explainer.	1 posts on 1 date(s); 2026-10-05	Limited / tentative
@imdradar	Ecosystem discovery and tracking: collections, tokens, operator earnings, hackathon entries/results, and updates from projects using the swarm.	5 posts on 5 date(s); 2026-10-15; 2026-10-25; 2026-10-28	Repeated in sample
@damian_et	Community coordination: the hackathon, builder discovery, prizes, demonstrations, and encouragement to run agents and experiment with Uniswap hooks.	11 posts on 5 date(s); 2026-10-14; 2026-10-28; 2026-11-06	Repeated in sample
@theimddaily	A newspaper-style digest combining swarm releases, ecosystem projects, token/NFT market commentary, and broader crypto news.	5 posts on 5 date(s); 2026-11-02; 2026-11-05; 2026-11-06	Repeated in sample
@IMD_IdentityMD	Community promotion, project/NFT-seat explanations, Telegram discovery, memes, and amplification of swarm demonstrations. Its bio describes a community-run page; do not treat it as a verified official account.	8 posts on 3 date(s); 2026-11-01; 2026-11-01; 2026-11-06	Repeated in sample
@quang250802	A newcomer guide to using the swarm, launching projects, running workers, and exploring related tokens/NFTs. One observed guide.	1 posts on 1 date(s); 2026-10-11	Limited / tentative
@atrilep	An ecosystem-token watchlist discussing HIVE, PEPES, seat strategies, and swarm NFTs, with explicit warnings about early-stage uncertainty.	1 posts on 1 date(s); 2026-10-04	Limited / tentative
@LeoMenth	Community advocacy and builder/operator recruitment, alongside brief POOL4 and swarm-performance commentary.	5 posts on 5 date(s); 2026-09-25; 2026-10-05; 2026-11-06	Repeated in sample
@Keeperssd	Bullish community commentary and discussion of IMD ecosystem activity and influencer attention. Indexed mirrors also show broader ecosystem roundups, but those are not counted as primary posts here.	3 posts on 3 date(s); 2026-10-18; 2026-11-05; supplemental mirror	Repeated in sample
@wegocrypto88	Interprets new swarm capabilities, agent-managed companies, and competition demonstrations through a bullish adoption/value thesis.	4 posts on 4 date(s); 2026-11-05; 2026-11-06; 2026-11-07	Repeated in sample
@0xSt3w	Community promotion and short IMD/NFT remarks in the direct sample. Indexed mirrors additionally show project Spaces and NIGHTSHIFT discussion; that broader focus has weaker date-level evidence here.	4 posts on 1 date(s); 2026-11-01; 2026-11-01; supplemental mirror	Limited / tentative

Workers and tools — 12 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@BreakThePoint	Operating a worker and observing testnet output; publishes a dashboard for tasks, verdicts, token use, cost, and worker updates.	5 posts on 4 date(s); 2026-09-20; 2026-09-23	Repeated in sample
@0xfinne	Builds the IMD Terminal dashboard for supply, burns, staking, market data, and seat economics; also compares IMD with earlier AI-token narratives.	2 posts on 2 date(s); 2026-10-29	Limited / tentative
@RektSconey	Operator participation and firsthand reports of an agent contributing to the INFER launch and receiving its allocation.	2 posts on 2 date(s); 2026-09-21; 2026-10-11	Limited / tentative
@startoverai	Practical worker setup/onboarding and questions about integrating other tools with IMD.	2 posts on 2 date(s); 2026-10-03; 2026-11-03	Limited / tentative
@theneetguy	An operator-holder perspective: continuing to run agents through a drawdown and emphasizing developer activity and network usefulness.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@agentskill_imd	Agent discovery and skill rankings using reputation/work history; explains the distinction between finding talent and purchasing work from the swarm.	5 posts on 2 date(s); 2026-10-15; 2026-10-16	Repeated in sample
@Eval_Engine	An experiment operating an IMD seat and preparing an oracle-request dataset for evaluation/research.	2 posts on 2 date(s); 2026-10-12; 2026-10-13	Limited / tentative
@imdcontrol	A workspace for planning parallel agent tasks, approving spending, tracking progress, and reviewing sourced results. One observed announcement.	1 posts on 1 date(s); 2026-10-20	Limited / tentative
@imd_financier	A Robinhood Chain front end for hiring the swarm, with job-type selection, plan review, payments, and delivery tracking.	3 posts on 3 date(s); 2026-10-21; 2026-10-24	Repeated in sample
@HELPWANTED_imd	Smart contracts commissioning swarm work, escrowing IMD, and paying only against delivery receipts; shows rule-triggered hiring and verification examples.	7 posts on 2 date(s); 2026-10-20; 2026-10-20; 2026-10-23	Repeated in sample
@IMDTools	An IMD interaction/treasury project discussing product revamps, its IMDT token's attention problem, and an NFT promotion. IMDT is a separate ecosystem token.	4 posts on 3 date(s); 2026-10-16; 2026-10-21	Repeated in sample
@sudeepb02	imdLend: lending idle NFT seats to operators and splitting worker rewards; also comments on the wider swarm's potential.	2 posts on 2 date(s); 2026-10-17; 2026-11-06	Limited / tentative

Finance, seats and launch infrastructure — 16 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@HIVE_imd	Funding and operating pooled IMD seats, covering operating costs, acquiring additional seats, and reporting distributions to HIVE holders/stakers.	6 posts on 6 date(s); 2026-10-04; 2026-11-03; 2026-11-05	Repeated in sample
@PawnIMD	Loans against IMD NFT seats, lender-pool economics, and the claim that agents can keep working while their seats are pawned.	4 posts on 3 date(s); 2026-10-11; 2026-10-11; 2026-10-27	Repeated in sample
@i0010110	Seat-owning strategies and LARP/Worker Frens identity experiments: operating contract-held seats, assigning agent faces/names, and burning IMD through use.	4 posts on 3 date(s); 2026-09-25; 2026-10-02; 2026-10-13	Repeated in sample
@Pepesdotfamily	A launchpad whose ecosystem tokens pair with IMD, with trading-fee distributions and updates about rewards to holders.	3 posts on 3 date(s); 2026-10-02; 2026-10-31; 2026-11-04	Repeated in sample
@TradingTenang	The PEPES/IMD reward relationship and a reported PEPES buyback/burn. One observed post; broader posting focus is not established.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@CodemingWeb3	Promotes the IMD Optimizer project, anti-MEV claims, yield mechanics, deployment plans, and related buildercoin branding.	3 posts on 3 date(s); 2026-10-22; 2026-10-29	Repeated in sample
@Imd_Optmizer	IMD Optimizer marketing and development announcements framed around a Uniswap v4 meta-hook, MEV protection, and yield.	5 posts on 4 date(s); 2026-10-22; 2026-10-22	Repeated in sample
@keelpad_imd	A swarm-built launchpad/product suite and integrations. The single explicit IMD post limits the dominant-topic inference.	2 posts on 2 date(s); 2026-10-19	Limited / tentative
@requiem__dream	A no-code hook launchpad built with the swarm, the cost of commissioning launches, and dependence on IMD service availability.	3 posts on 1 date(s); 2026-10-23; 2026-10-23; 2026-10-23	Limited / tentative
@SigmoidIMD	Fair-launch hooks and anti-sniper mechanisms, including circuit-breaker behavior and claimed replay/fork testing.	2 posts on 2 date(s); 2026-10-21; 2026-10-25	Limited / tentative
@curbhook	Uniswap v4 circuit breakers, price-band refusals, trading halts, and paying IMD oracle panels for follow-up decisions.	5 posts on 1 date(s); 2026-10-20; 2026-10-20	Limited / tentative
@UnlockBySwarm	UNLOCK token experiments: milestone gates on selling, IMD-paired trading, V2 changes, migration, and launch progress.	8 posts on 3 date(s); 2026-11-03; 2026-11-05; 2026-11-06	Repeated in sample
@SuperIMD_eth	An ecosystem project's endorsement of paid swarm work, launch allocations, and oracle behavior. One observed substantive reply; its own launchpad focus needs more dated posts.	1 posts on 1 date(s); 2026-10-12	Limited / tentative
@Rhynotic	Token/Uniswap-hook launch infrastructure, with IMD among supported pairings. The directly observed IMD passage is one part of a broader infrastructure thread.	1 posts on 1 date(s); 2026-10-16	Limited / tentative
@JesseTRutkowski	An investment/distribution angle on HIVE: gaining exposure to IMD ecosystem launches and agent payouts without researching every small token. One observed comment.	1 posts on 1 date(s); 2026-10-12	Limited / tentative
@IMDRIP_ETH	An IMD-drip fan-token account: launch promotion followed by admissions about liquidity/scanner problems and the creator's selling. Its IMD reward premise comes from the account bio; the selected posts are contextual, not literal IMD mentions.	3 posts on 2 date(s); 2026-10-01; 2026-10-02; 2026-10-02	Repeated in sample

Oracle applications and markets — 14 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@imdusd	Infer/imdUSD: financial applications built with the swarm, using agents/oracles, and INFER BOX for learning to prompt and pay for swarm work.	3 posts on 2 date(s); 2026-11-01; 2026-11-01; 2026-10-30	Repeated in sample
@yadfarms	Commentary on the swarm's capabilities from an imdUSD-associated account. The sampled original commentary is broader than a stablecoin update; a mostly-imdUSD posting pattern is not established here.	1 posts on 1 date(s); 2026-11-05	Limited / tentative
@dani_who_daniel	Pepe2Pepe's early peer-to-peer betting/prediction-market use case and testing the IMD oracle on mainnet.	2 posts on 2 date(s); 2026-09-27; 2026-09-28	Limited / tentative
@SeerOnIMD	Prediction-market questions, agent forecasts, median opening odds, forecast scoring, and signed oracle settlement; identifies its sampled adjudicator as testnet.	4 posts on 4 date(s); 2026-10-25; 2026-10-31; 2026-11-02	Repeated in sample
@pinkybond_fun	IMD-backed promises: bonds, transfer/payment checks by oracle panels, verdicts, payouts, and transparent audit/review limitations.	6 posts on 4 date(s); 2026-10-10; 2026-10-19; 2026-10-26	Repeated in sample
@keptonchainn	Milestone-based team-token vesting: the IMD oracle checks delivery, then tokens unlock or burn, with a fund for verification costs.	7 posts on 3 date(s); 2026-10-20; 2026-10-20; 2026-10-22	Repeated in sample
@marginalia_md	Bonded trading theses, wallet-linked research records, weekly AI judging, and unusually candid updates about oracle panels failing to reach ranking consensus.	9 posts on 4 date(s); 2026-10-21; 2026-10-22; 2026-10-25	Repeated in sample
@swornbyswarm	Wallet facts and attestations: agent panels proving facts, signatures checked by a registry, community-defined rules, and wallet cards.	7 posts on 3 date(s); 2026-10-21; 2026-10-21; 2026-10-21	Repeated in sample
@ConditionalsImd	An IMD-linked markets product and its token launch, with proposed protocol-fee buybacks shared between its own token and IMD.	5 posts on 3 date(s); 2026-11-02; 2026-11-05; 2026-11-07	Repeated in sample
@Briefs_fun	Argument contests judged by swarm agents for a prize pot. The observed reply describes a mock-jury testnet stage while awaiting an IMD mainnet oracle path.	1 posts on 1 date(s); 2026-10-05	Limited / tentative
@HeroBoost_me	Using IMD yes/no oracle outcomes for conditional tips, staged launches, and small fundraising campaigns on Base. One observed announcement.	1 posts on 1 date(s); 2026-10-22	Limited / tentative
@moneycanbuy_fun	Paid real-world dares, proof and dispute resolution by NFT holders/swarm agents, plus YOLO launch and live-stream activity.	3 posts on 3 date(s); 2026-10-15; 2026-10-21; 2026-11-05	Repeated in sample
@nightshiftimd	Autonomous AI companies hiring the IMD swarm, partner recruitment, and business-accounting updates distinguishing shipped products from actual sales.	2 posts on 2 date(s); 2026-10-29; 2026-11-07	Limited / tentative
@SovrnIMD	SVO/AI-assistant and autonomous-swarm promotion. Its bio calls the token launched/audited through IMD; the selected original swarm-vision post is contextual. A dominant IMD-specific beat is not established.	1 posts on 1 date(s); 2026-11-05	Limited / tentative

Games, art and NFTs — 29 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@pepe2pepe_fun	The account's observed October focus is a swarm-built game arcade and sponsored game creation, following the project's earlier prediction-market framing.	6 posts on 3 date(s); 2026-10-11; 2026-10-12; 2026-10-16	Repeated in sample
@Gamma_imd	A Robinhood Chain proof-of-play token/game presented as built and launched by the IMD swarm. One observed launch post.	1 posts on 1 date(s); 2026-10-20	Limited / tentative
@0xresets	Announces building Gamma for the IMD hackathon. One observed project announcement; insufficient history for a dominant focus.	1 posts on 1 date(s); 2026-10-20	Limited / tentative
@hamsterhourgame	Hamster-based betting, IMD reward pools, HAMSTER staking, leaderboards, and support explanations for unmatched bets.	4 posts on 4 date(s); 2026-11-01; 2026-11-02; 2026-11-05	Repeated in sample
@ArewaOS26	Agent Duel: sealed predictions and a public scoreboard on Base, presented as a free-to-play IMD use case.	2 posts on 2 date(s); 2026-10-12; 2026-10-17	Limited / tentative
@pfwafun	Prediction markets and the Sherwood trading game, including its IMD-priced Season 2 and swarm audit/deployment trail.	5 posts on 2 date(s); 2026-10-09; 2026-10-12	Repeated in sample
@imdpot	An IMD-denominated jackpot game, framed as token utility during a drawdown, with ticket-purchase instructions.	2 posts on 2 date(s); 2026-10-19; 2026-10-21	Limited / tentative
@imdgenesis	A science/exploration game using IMD research agents to test hidden world rules; later GENS token design and launch updates.	8 posts on 5 date(s); 2026-10-21; 2026-10-23; 2026-10-29	Repeated in sample
@SinopiaMD	Auctions that commission swarm-generated art, pay IMD from a contract, and mint the delivered image as an NFT; documents the first completed fresco.	8 posts on 1 date(s); 2026-10-16; 2026-10-16; 2026-10-16	Limited / tentative
@inkandinference	Agent portraits, INK token/pool mechanics, portrait claiming and rerolling, and IMD-denominated pricing examples.	3 posts on 1 date(s); 2026-10-21; 2026-10-21	Limited / tentative
@mirrorimd	Wallet-identity MIRROR cards, IMD/NFT-holder eligibility, and mint promotion, alongside bullish IMD remarks.	5 posts on 4 date(s); 2026-10-19; 2026-10-20; 2026-10-21	Repeated in sample
@SwarmCoreIMD	An NFT mint and proposed follow-on IMD-paired token/airdrop. The observed announcements describe plans, not verified execution.	2 posts on 1 date(s); 2026-10-16; 2026-10-16	Limited / tentative
@WorkonIMD	The WORK/Workers mining collection, IMD mint and staking rewards, launch progress, and chain/balance support for users.	7 posts on 1 date(s); 2026-10-08; 2026-10-08; 2026-10-08	Limited / tentative
@pupateIMD	Metamorph MD browser mining and seat-derived cards, with mint revenue/rewards described in IMD.	2 posts on 2 date(s); 2026-10-15; 2026-10-16	Limited / tentative
@Numosimd	Onchain number NFTs claimed with IMD on Robinhood Chain; mint guidance, chain/contract clarification, and community-building updates.	4 posts on 1 date(s); 2026-10-07; 2026-10-07; 2026-10-07	Limited / tentative
@IMD6900	Worker Frens NFTs as faces/identities for IMD seats, mint terms, and agent-profile/LARP integration. Also corrects an earlier free-mint description.	4 posts on 3 date(s); 2026-10-02; 2026-10-11; 2026-10-17	Repeated in sample
@swarmpepes	Swarm Pepe NFT activation, associated OG-token use cases, and fee/reward promotion. The direct sample is small.	1 posts on 1 date(s); 2026-10-08	Limited / tentative
@theidmfun	Turning trading activity into music with a drum-machine hook; later music-label announcements. Explicitly distinguish its IDM token from IMD.	3 posts on 3 date(s); 2026-10-19; 2026-10-20; 2026-11-06	Repeated in sample
@badfriend	Design choices behind IDM's music market, especially IMD pairing, gas costs, and liquidity constraints. One direct IMD-related reply.	1 posts on 1 date(s); 2026-10-20	Limited / tentative
@Pixel_Pool	A trading chart/art experiment where PIXEL/IMD swaps generate onchain dots. One observed project post.	1 posts on 1 date(s); 2026-10-09	Limited / tentative
@Quantum_Canary	A swarm-built cryptography-risk canary/bounty demonstration. This report describes its promoted experiment, not proof that its security claims hold.	4 posts on 1 date(s); 2026-10-10	Limited / tentative
@tungweb3	EmberEVO/IMD Ember World: visualizing agents and swarm activity in a 3D world, plus game experiments and ecosystem spaces.	8 posts on 5 date(s); 2026-10-02; 2026-10-06; 2026-11-07	Repeated in sample
@Imdirectorb	Live-streaming and physical-device control using IMD transactions, agents, and hooks; reports relay/outlet tests and planned interactive shows.	6 posts on 5 date(s); 2026-10-21; 2026-10-23; 2026-10-27	Repeated in sample
@DmitryiBond	Music from IMD trading activity and a blockchain/physical-world live-show concept around the hackathon.	3 posts on 3 date(s); 2026-10-19; 2026-10-21	Repeated in sample
@SuperFPET_eth	A Fren Pet/IMD-adjacent project promoting its hackathon participation and swarm development. The posts support that affiliation claim, not verification of its mechanics.	3 posts on 2 date(s); 2026-10-19	Repeated in sample
@IMDhongbao	Sending IMD as onchain red packets, randomized/equal splits, example payouts, and the project's swarm build/audit receipts.	4 posts on 1 date(s); 2026-10-16; 2026-10-16; 2026-10-16	Limited / tentative
@ouroborospress_	A smart contract commissioning its own written biography, paying IMD for chapters, receiving callbacks, and publishing chapter hashes.	4 posts on 1 date(s); 2026-10-22; 2026-10-22	Limited / tentative
@imdplace	Small swarm experiments, especially BEG, where users ask the swarm for tokens; links the experiment to its IMD build job.	2 posts on 1 date(s); 2026-10-15; 2026-10-15	Limited / tentative
@Pleaimd	A PLEA token experiment with swarm-judged pleas, an AI-selected airdrop, public verdicts, and launch/claim documentation.	2 posts on 1 date(s); 2026-10-30; 2026-10-30	Limited / tentative

Regeneration — 1 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@imd_offset	The swarm's estimated compute footprint, regenerative-credit spending, IMDO fee allocation, and an airdrop for IMD seat holders. Offset quantities remain issuer claims here.	6 posts on 5 date(s); 2026-10-20; 2026-10-20; 2026-10-28	Repeated in sample

Token commentary and criticism — 20 accounts

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@blknoiz06	Brief bullish token calls and a statement that the author still holds IMD; the observed posts are sentiment/position signals rather than detailed protocol analysis.	3 posts on 3 date(s); 2026-09-24; 2026-10-04; 2026-11-05	Repeated in sample
@AdamOnFinance	A speculative large-upside thesis based on agents replacing oracle/data/service functions. One observed forecast, not a valuation fact.	1 posts on 1 date(s); 2026-09-25	Limited / tentative
@SamSteffanina	A holder thesis emphasizing continuity from Fren Pet and confusion over FP/VIBE/IMD metadata; combines a bullish forecast with criticism of naming.	1 posts on 1 date(s); 2026-09-25	Limited / tentative
@jaganite	Trading entries and rotation between IMD tokens and NFT seats, plus complaints about confusing token branding/metadata.	2 posts on 2 date(s); 2026-09-25; 2026-09-26	Limited / tentative
@jawaisme	Price/demand skepticism and increasingly bearish forecasts, despite earlier interest in prediction-market utility. Predictions and demand assertions are the author's views.	6 posts on 6 date(s); 2026-10-19; 2026-10-30; 2026-11-06	Repeated in sample
@mun1aa	POOL4 burns, staking/seat participation, and comparative token economics; a burn-comparison thread explicitly acknowledges mismatched periods and supply assumptions.	7 posts on 3 date(s); 2026-10-31; 2026-11-05; 2026-11-05	Repeated in sample
@Tittomikhati	Buying/holding conviction and a thesis that autonomous agents increase demand for crypto payments.	2 posts on 2 date(s); 2026-10-17; 2026-11-07	Limited / tentative
@EtanBoss	Bullish comparisons between reported network output and token valuation, plus calls for conviction through price weakness.	2 posts on 2 date(s); 2026-10-27; 2026-11-07	Limited / tentative
@Farby07	Bullish price/bottom commentary and amplification of network-output statistics. Repeated promotional framing rather than independent measurement.	4 posts on 4 date(s); 2026-10-23; 2026-10-27; 2026-11-04	Repeated in sample
@G_waap	Repeated promotional price-target posts for IMD. The sampled posts provide sentiment, with little project analysis.	2 posts on 2 date(s); 2026-11-02; 2026-11-07	Limited / tentative
@CryptomozartNFT	Short bullish endorsements of IMD, its builder community, and innovation; little technical analysis in the primary sample.	5 posts on 5 date(s); 2026-10-27; 2026-11-04	Repeated in sample
@mingwei1996	English/Chinese holder conviction, buying-the-dip commentary, faith in the developer, and long-term token/NFT upside.	4 posts on 4 date(s); 2026-08-18; 2026-10-24; 2026-11-06	Repeated in sample
@cutepanda	A Chinese-language cross-chain market commentary favoring the IMD ecosystem and community. Only one relevant post observed.	1 posts on 1 date(s); 2026-10-30	Limited / tentative
@MONster3638_	Early bullish calls and market-cap targets tied to the exact IMD Ethereum contract.	2 posts on 2 date(s); 2026-08-26; 2026-08-27	Limited / tentative
@nagato0x	Short project introductions and bullish reactions around Identity.md/IMD. Limited evidence for a more specific dominant topic.	2 posts on 1 date(s); 2026-08-26; 2026-08-26	Limited / tentative
@nftgothsa	A holder/operator perspective supporting NFT-seat scarcity and community/developer execution; one directly observed relevant post.	1 posts on 1 date(s); 2026-11-05	Limited / tentative
@tcrossdao	An early-holder/mainnet thesis discussing the author's stated IMD and NFT entry prices. One relevant primary post observed.	1 posts on 1 date(s); 2026-10-05	Limited / tentative
@0xwhacko	A bullish thesis about a community-owned meme company and Ethereum mainnet. One relevant authored post observed.	1 posts on 1 date(s); 2026-09-22	Limited / tentative
@SolSoldier_gg	An investigation alleging coordinated early buying and deployer involvement in the separate IMD Tools/IMDT launch. The allegation is not independently adjudicated in this report.	1 posts on 1 date(s); 2026-10-05	Limited / tentative
@FULLCLIP_TEAM	Promotes NIGHTSHIFT/SHIFT as an IMD-built AI-company ecosystem, including NFT, staking, and utility claims.	3 posts on 2 date(s); 2026-10-18; 2026-10-29	Repeated in sample

Brief mentions and user questions — 40 accounts

These accounts did post relevant material, but a main or usual focus cannot be established from these observations. The column describes the topic actually seen.

Account	Observed focus — inference	Evidence: observed count and representative UTC dates	Support
@0000000f1pac	General enthusiasm for IMD's potential in a reply to Infer/community accounts; no dominant topic established.	1 posts on 1 date(s); 2026-11-02	Limited / tentative
@0xartilects	Short bullish replies and appreciation for IMD research; no detailed recurring subject established.	2 posts on 2 date(s); 2026-08-08; 2026-08-26	Limited / tentative
@0xKnownxd	A short IMD endorsement; insufficient content to infer a main focus.	1 posts on 1 date(s); 2026-08-26	Limited / tentative
@0xSofiya	Reaction to the swarm's competition progress; no dominant focus established.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@BertLuvv	Asks where the IMD used for POOL4 burns and rewards comes from.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@BitmanTW	Questions whether IMD NFT seats are undervalued relative to the token.	1 posts on 1 date(s); 2026-09-24	Limited / tentative
@Cate_Is_The_Way	Bullish reaction to upcoming IMD ecosystem activity; no dominant focus established.	1 posts on 1 date(s); 2026-11-01	Limited / tentative
@ChadBORD	Hopes the VIBE/IMD token rises; a price-sentiment reply only.	1 posts on 1 date(s); 2026-08-27	Limited / tentative
@dada_didenko	Buying-the-dip sentiment in a competition-related thread.	1 posts on 1 date(s); 2026-11-07	Limited / tentative
@Despite_zmw	Asks about the Conditionals launch location; the evidence does not establish a broader IMD beat.	1 posts on 1 date(s); 2026-11-07	Limited / tentative
@devi_maker	Asks whether customers can commission an individual IMD agent.	1 posts on 1 date(s); 2026-10-15	Limited / tentative
@DoctorFomo	Asks which token gives IMD exposure. The alternative-chain address in the question is not validated as legitimate IMD.	1 posts on 1 date(s); 2026-10-27	Limited / tentative
@dontfadeplease	Reports a balance-recognition issue using WORK; the project's reply points to the chain mismatch.	1 posts on 1 date(s); 2026-10-08	Limited / tentative
@edugrooves	An IMD-built experiment and a question about classifying agent NFTs on OpenSea; too little evidence for a dominant subject.	2 posts on 2 date(s); 2026-09-28; 2026-11-05	Limited / tentative
@eth_exy	Early bullish remark tied to the exact Ethereum IMD contract.	1 posts on 1 date(s); 2026-08-26	Limited / tentative
@Fawzi18936	Brief SHIFT/NIGHTSHIFT and IMD cross-promotion.	1 posts on 1 date(s); 2026-10-23	Limited / tentative
@GujilRuipa	Positive response to an IMD newcomer/launch guide.	1 posts on 1 date(s); 2026-10-11	Limited / tentative
@IaMaDamIMD	Shares a design and praises ecosystem growth; a narrower regular focus cannot be established.	2 posts on 2 date(s); 2026-10-09; 2026-10-12	Limited / tentative
@IMDBlackout	Blackout City development encouragement, bug fixes, and a planned site redesign; detailed IMD mechanics are absent from the sampled post.	1 posts on 1 date(s); 2026-10-15	Limited / tentative
@imdfamily	Introduces an IMD-themed community/building identity; one post does not establish a regular topic.	1 posts on 1 date(s); 2026-10-20	Limited / tentative
@Jeffydb3	A short positive IMD reaction; no main focus established.	1 posts on 1 date(s); 2026-10-06	Limited / tentative
@jus_Bizzness	Mentions PEPES/IMD pairing and holder rewards in a reply.	1 posts on 1 date(s); 2026-10-01	Limited / tentative
@kn0xhound	Amplifies an IMD thesis and shares an agent-portrait/work-history example; limited sample.	2 posts on 2 date(s); 2026-08-10; 2026-10-21	Limited / tentative
@Lucifero_mf	Brief claim that IMD is undervalued.	1 posts on 1 date(s); 2026-11-05	Limited / tentative
@maxxavii	Asks which account is the official IMD account.	1 posts on 1 date(s); 2026-10-28	Limited / tentative
@mbubbleSearch	Points to a timestamped discussion of IMD pairing/burn mechanics; useful as a source-finding reply, with no recurring IMD beat established.	1 posts on 1 date(s); 2026-09-24	Limited / tentative
@milosmisic15	Interest in the IMD/INFER relationship and asks an influencer for a view on imdUSD.	2 posts on 2 date(s); 2026-11-04; 2026-11-05	Limited / tentative
@Neptuneos01	Expresses concern about the Robinhood-chain IMD/WORK experience. A question/allegation, not a confirmed scam finding.	1 posts on 1 date(s); 2026-10-08	Limited / tentative
@nitroslaveth	Positive reaction to swarm scale in the competition thread.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@ParallelAiRev	Brief endorsement of IMD's novelty; no detailed repeated subject in the primary sample.	1 posts on 1 date(s); 2026-10-27	Limited / tentative
@Rachel_Muyin	Praises the project's combined seat/oracle/ownership design and suggests visual/art integrations.	2 posts on 2 date(s); 2026-10-12; 2026-10-14	Limited / tentative
@rckmtl_	Amplifies an IMD explainer for newcomers; no dominant authored focus established.	1 posts on 1 date(s); 2026-11-07	Limited / tentative
@Reza_Architekt	Congratulates IMD on a reported competition result; not independent verification of the result.	1 posts on 1 date(s); 2026-11-07	Limited / tentative
@SAdeli94976	Reports missing/pending Hamster Hour bet displays and asks where the IMD went. The project replies with a refund explanation; receipt of a refund was not verified.	1 posts on 1 date(s); 2026-11-02	Limited / tentative
@Soldier_X0X	Short SHIFT/IMD and token-enthusiasm replies.	2 posts on 2 date(s); 2026-10-23; 2026-11-01	Limited / tentative
@spendingmgr	Asks how to obtain IMD while interacting with WORK.	1 posts on 1 date(s); 2026-10-08	Limited / tentative
@tokumei	Suggests bringing Birds into an IMD garden/art experiment; speculative integration idea only.	1 posts on 1 date(s); 2026-10-14	Limited / tentative
@YoungJi_0x	Asks about pending IMD in Hamster Hour.	1 posts on 1 date(s); 2026-11-01	Limited / tentative
@Zodomo	Discusses converting INFER to IMD to pay the swarm for a planned project audit; not evidence the audit was completed.	1 posts on 1 date(s); 2026-11-06	Limited / tentative
@yodhaichi_sol	Asks whether Sigmoid is an IMD hackathon entry; no recurring focus established.	1 posts on 1 date(s); 2026-10-21	Limited / tentative

What the observations do and do not establish

A post proves that an account made that statement. It does not establish that a reward was paid, a contract is safe, an agent count is correct, a partnership exists, or a price forecast will come true. The project/account descriptions above summarize what was discussed. Security reviews, token allocations, revenue, protocol performance, and competition rankings were not independently audited for this assignment.

Several cases matter when interpreting the list:

• Community versus official: @IMD_IdentityMD describes itself as community-run. The feed behavior of @builtbyimd is visible, but its ownership was not independently established. A project-like handle or an “official” claim in a post is not enough to certify official status. @Rhynotic and @surfcoderepeat are distinct accounts; both having “Adam” as a display name does not establish common ownership. Community profile, founder's protocol description.
• Counterviews are present: @jawaisme posts demand/price skepticism; @solsoldier_gg alleges problems with the separate IMDT launch. These are attributed opinions/allegations, not this report's conclusions. Demand/price commentary, 19 October, IMDT investigation, 5 October.
• User complaints have context: @sadeli94976 reports pending/missing Hamster Hour bet displays. The project replies that one-sided bets are refundable and explains the process. I did not verify the user's transactions or receipt of a refund, so this remains a reported support issue with a project response. Complaint, 2 November, project response, 2 November.
• Reported limits are informative: Marginalia describes oracle panels failing to agree on a ranking, and Pinky expressly distinguishes swarm review from an outside firm's audit. These support classifying the accounts as practical oracle-use reporters, without concluding that either application is safe. Marginalia, 25 October, Pinky, 10 October.
• Promotional metrics need care: Mun1a's burn-comparison thread acknowledges differing time windows and supply assumptions. NIGHTSHIFT distinguishes shipping from actual sales. I preserve those qualifications instead of treating promotional figures as established current metrics. Burn-comparison caveats, 5 November, NIGHTSHIFT accounting post, 7 November.

Reposts, weak leads, and exclusions

One additional account has a dated repost directly observed: @remp0x, 19 August, amplifying @LastToSign's Community Coins analysis. That supports a role as an amplifier of the launcher/economic-design discussion; original IMD analysis and a usual focus were not established. It is separate from the 151 accounts and 469 authored-post observations above.

The following are useful discovery leads with weaker evidence. They are not included in the verified dated-post totals, and the proposed subject is tentative:

Account	Apparent subject / reason to investigate	Limitation and attributable lead
@notwashed	Bullish agent-factory/IMD-pairing and burn-loop commentary.	An indexed mirror shows relevant text, but a dated original post was not recovered. Relative crawl/post labels do not establish a qualifying date.
@nftimm	A bullish IMD company thesis and amplification of POOL4 developments.	Relevant text appears on an indexed mirror. Linked originals such as this post returned HTTP 404 during direct retrieval. Author/date/content could not be bound from those originals.
@0xNairolf	Simple newcomer explanations of IMD.	An attributed explainer is visible in an indexed KeeperCF mirror, but no dated original was recovered.
@cfm_sol	Market flows, wallet buying, and the relationship between POOL4 economics and price.	An indexed mirror shows relevant discussion and the correct token contract; publication dates were not established from originals.
@wmpeaster	The author associated with Bankless's IMD feature; likely a useful research follow.	Bankless's byline establishes William M. Peaster's article authorship, not an authored IMD X post on this handle in the requested period.
@paperclash_xyz	Paperclash game/perpetual-trading product updates.	Named by the hackathon organizer; the fetched profile sample did not establish its own dated IMD-specific post. Being named by another account is not evidence it posted about IMD.
@probert_mihai	NIGHTSHIFT development, AI companies, and community Spaces.	A dated third-party profile mirror shows discussion, and Taylor names the project/developer. An adequately bound original IMD-specific post by this account was not recovered in the selected sample.
@jojojooven	Agent reputation, swarm bootstrapping, and worker operations.	Relevant commentary is attributed on an indexed mirror; no qualifying original date was established.

There were also generic reactions that do not support a project focus: @ivanhieu_eth and @lordvibezzz replied to a community handle with encouragement/greetings. Their replies do not provide enough project content for the main list.

An especially useful disambiguation example is PFWA's correction of a mistaken @imd tag. I did not classify @AgentChud or @GetRichOrCryTry as IMD-focused from their generic replies carrying that mistaken tag. Separately, a current sample for @HarvestIMD contained unrelated legal commentary; a matching submitted/project handle alone was insufficient to attribute IMD coverage. Profile sampled.

Additional candidate profiles and retrieval failures are recorded in profile coverage. “No qualifying post observed” means a research gap, not “this account never posted about IMD.”

Collection and classification method

1. Discovery. I searched the public web for $IMD, Identity.md, Identity-md, identitymd, imd.fun, the Ethereum token contract, named contributors, and dates/months across the window. Date-restricted X-domain queries were attempted but returned little useful coverage. Additional discovery came from quoted posts/replies and the community's closed 78-entry hackathon list, including project and personal handles. Registry inclusion supplied candidates, not proof of X posting. Earlier generated research reports encountered in search were used only as leads, not as verification.
2. Primary retrieval. Direct public HTTPS requests could retrieve many X profile and individual-post HTML pages even when the browser/search tool's own X fetch returned 403. I decoded the embedded JSON as data without running page scripts. The saved observation binds a tweet ID to its author metadata, text/article metadata, expanded URLs, and created_at_ms timestamp. Dates in the main evidence are read from those timestamps, not inferred from search-crawl dates, relative “hours ago” labels, or snowflake IDs.
3. Attribution. Nested quoted/reposted tweets were attributed to their actual embedded author, not to the profile on which they appeared. IDs were deduplicated across profiles, threads, and individual-post pages. Native RT @... objects were excluded from authored counts. A quote/reply's own text was assessed separately from its quoted parent's text. A bare mention of an account by somebody else never qualified that mentioned account.
4. Relevance. I checked explicit project terms/contract, attached article titles, and expanded project links. Generic IMD acronym matches and mistaken handles were excluded. 11 selected observations use a specifically documented project/reply context rather than a literal project keyword; these include associated product updates and are labeled in the ledger. Those context judgments are inferences. No claim was made that every post by an ecosystem account automatically concerns IMD.
5. Focus. The topics are qualitative interpretations of the accepted observations. A post/thread can demonstrate a subject, but limited material cannot establish what the account “mostly” covered over all three months. The repeated/limited labels expose that distinction. Promotional copy, repeated slogans, and thread continuations can raise the observed count without adding independent corroboration.
6. Evidence strength. Of 469 accepted observations, 441 were recovered on their exact individual X post page (class A), and 28 were available only as fully attributed primary tweet objects embedded in another fetched X page (class B). Both are first-party payload observations; class B has a weaker retrieval trail. Secondary mirrors are labeled separately and do not inflate the primary totals. The capture manifest has 671 distinct URL records, including 201 profile URL records; repeat requests to the same URL retain one record, so this is not a count of all HTTP requests. Source manifest.

Observed posts by month, after date filtering and deduplication:

UTC month within the requested window	Accepted observations
2026-08	17
2026-09	35
2026-10	308
2026-11	109

The October concentration reflects this collection's strong hackathon/project-discovery bias. It is not evidence of the distribution of all IMD discussion on X. The August row covers 7–31 August and the November row covers 1–7 November through the stated cutoff.

Uncertainty and unanswered questions

• Exhaustiveness remains unanswered. Logged-out profiles generally exposed only a handful of authored posts, often including a pin; a complete paginated timeline and authenticated full-archive search were not obtained. The window was searched, but no complete three-month corpus was retrieved. Deleted/private/unindexed posts, aliases, image-only mentions, Spaces audio, and language/search variants may add accounts. Completeness and recall cannot be estimated from these sources.
• The true dominant topic for many accounts remains unanswered. The table establishes observed subject matter. A fuller history could change both the categories and whether a single-post account belongs on a regular follow list. Handles and display names can also change; this is a retrieval-time account map.
• Affiliation and incentives remain partly unknown. Self-description and participation do not prove employment, official status, account ownership, independence, undisclosed holdings, or compensation for promotion. I did not infer wallet ownership from display names or holder lists.
• Underlying product claims remain unverified here. I did not test every app, audit contracts, reconstruct payouts, verify every reported network statistic, or check the competition leaderboard independently. Historical risk statements may have become stale; they are evidence of what an author discussed at the time, not a current security assessment.
• Open support outcomes remain unanswered. Complaints and project responses are both linked, but resolution is not established without transaction-level evidence from the affected case.

A complete answer to the literal “all posts / all accounts” request would require an authorized, paginated archive covering this date window, with replies, quote posts, repost events, and handle changes, followed by the same project disambiguation and author/date checks. This report delivers the useful list that could actually be supported, and records that remaining coverage gap.

Local checks and provenance limits

The accompanying offline checker verifies table/ledger consistency, unique IDs and handles, author-to-URL binding, time-window inclusion, short-excerpt limits, representative-post links, and reported counts. Those checks do not certify the truth of a post or independently establish completeness. SHA-256 values identify the fetched pages; full HTML captures are not part of the deliverable, and a hash alone is not independent verification. The report and compact evidence can be read and checked without network access.