maximo retweeted
my bet is $IMD
maximo retweeted
Identity.md NFTs used to look like dev licenses. Now they appear to be turning into participation passes and digital identities for members of an autonomous company built around $IMD.
Since my previous breakdown, Adam has significantly changed the direction of the project.
Initially, it looked like a launcher with a Uniswap v4 hook. Now @surfcoderepeat says he is building a larger agentic P2P protocol, with hooks becoming only one of its first features.
The most interesting finding is inside the launch-6-hook-feedistributor repo.
Its main branch was created by Adam’s account, although the repo formally belongs to the Identity-md organization. The task described in the repo is to collect a 5% fee from every trade, hold it in $ETH and periodically distribute it among major $IMD holders.
The official imd.fun site is now live. Right now, it is just a basic placeholder with no app.
The real clues were found on GitHub.
Adam’s surfer77 account created code inside the Identity-md organization. One of the repos is explicitly described as a test of the IdentityMD participant network.
Based on comments in the code, the network appears to work like this: an automated participant receives a small task and access only to the required files, writes the code, and a separate system checks the result again inside an isolated environment with no internet access
This begins to explain the site’s description of a “decentralized meme company with no employees.”
It could be a company where AI agents perform most of the work, while the network verifies their output and gradually transfers control to the community.
Adam also prepared a token launch template using Uniswap v4. The test model creates exactly 1B tokens with no ability to mint more.
The entire supply is immediately placed into one-sided liq against $ETH.
No $ETH is required to open the pool. Buyers gradually bring it in, the price rises as they buy, and $ETH accumulates inside the pool.
A direct link between $IMD and the NFTs has also appeared. Identity.md NFTs are now officially described as “Participation Pass & Identity.”
The most logical setup is:
> NFT = access and identity
> $IMD = the project’s money and economy
The identity.md NFT contract is limited to only 2,000 NFTs, and the free mint was restricted to one NFT per wallet.
The site describes it as a Participation Pass & Identity. The verified code allows each NFT to be linked to an IPFS profile and permanently locked if desired.
The NFT could potentially serve as:
> a pass into the Identity.md network
> a persistent profile for a participant or AI agent
> proof of participation in the early community
> a key to tasks, voting, reputation and rewards
> a way to distinguish real participants from regular $IMD buyers
The NFT contract also includes fields for an epoch, Uniswap v4 hook and pool.
This shows that Adam was already thinking about connecting the NFTs to a future trading or reward system.
Identity.md NFT turned out not to be a ticket to launch your own token
Confirmed utility for $IMD
According to a GitHub mirror discovered by @0xfinne, it is a developer credential that allows its holder to complete tasks assigned by the factory
The mirror is highly likely to be authentic. It references the original private repository Identity-md/launch-3-new, factory issue #20 and launch number 3
The first commits were made by identitymd-launch-factory[bot]. The history also contains commits and signed merge commits from Adam under his surfer77 GitHub account
How the factory works in simple terms
Imagine a factory that produces new markets:
> someone proposes an idea for a token or market.
> the Identity.md team accepts or rejects it.
> the factory divides the development process into separate tasks:
>>design the architecture
>>write the smart contract
>>write the tests
> an Identity.md NFT holder registers as a worker.
the scheduler assigns them a specific task
> the worker uses Codex, Claude or writes the code manually
> the factory checks the code, tests and security.
> a maintainer accepts the result
> a multisig authorizes the deployment
> a new PROJECT/IMD market appears
This means the NFT is not required by Codex or by someone who simply proposes an idea. It is required by the developer-worker
The NFT tells the factory:
> this GitHub developer is linked to this wallet
> they own a valid Identity.md credential
> they can be assigned a task
> the factory can accept a signed result from them
Before accepting each PR, the system checks NFT ownership through ownerOf() on Ethereum mainnet. If the worker sells the NFT, they lose the right to complete the assigned work
This is implemented directly in the code: a developer owns an NFT, registers as a worker and receives the right to complete assigned hook-development tasks
They cannot independently choose any project, write an arbitrary hook and immediately launch it
This also explains the line from Adam’s logs: waiting for the next signed milestone
It now appears that a signed milestone is most likely not a command for an autonomous economic agent, but a specific task inside the factory
For example:
> design the architecture
> write the contract
> prepare the tests
The worker receives the task, completes it and signs the result tied to an exact commit and Git tree
The code then passes through several layers of verification. This means the agent published by Adam is probably an autonomous developer-worker:
> Codex writes the hook
> the signed milestone limits it to a specific task
> the factory verifies the result
> a maintainer accepts the code
> a multisig authorizes the launch
AI is not the final product here, at least for now. It is one of the factory workers
How is this different from a regular launchpad?
A regular launchpad works roughly like this:
> enter a name and ticker
> a standard token is created
> a bonding curve or regular pool opens
> trading begins
Almost every project launches from the same template
The name, supply and image change, but the market mechanics remain similar. Identity.md is trying to build a system where each project can receive its own mechanics programmed through a separate Uniswap v4 hook
One hook can:
> burn part of the fees
> change fees depending on specific conditions
> restrict certain trades
> direct assets according to predefined rules
> create a new liquidity or distribution model
This makes Identity.md look less like a regular token launchpad and more like a combination of:
> launchpad
> smart contract studio
> AI development pipeline
> security review system
The main potential know-how is not found in the individual components
NFT gating, AI coding, GitHub Actions, multisigs and Uniswap v4 hooks already exist. What may be new is combining them into a single factory that turns an idea into a finished and verified market
And this is where the role of $IMD appears.
The factory schema specifies: "quoteSymbol": { "const": "IMD" } It uses const, not one of several possible options
This means the current architecture requires every market to be created as:
> PROJECT/ $IMD
If the router hides the intermediate operations, the user may not even notice this. But inside the system, buying a new asset would still require $IMD
For the person proposing an idea, the potential offer looks like this:
> they bring the idea
> the factory creates the specification
> AI and NFT workers write the hook
> the system runs tests and security reviews
> the multisig authorizes the deployment
> a new programmable market appears
This means the person does not necessarily need to find a Solidity developer, auditor and DevOps team independently
The NFT currently gives its holder the right to work inside the factory, but the economic reason to buy that right has not yet been revealed
Identity.md is not building a single burn hook
It is an attempt to create a factory that turns an idea into a verified programmable market.
The NFT controls who can participate in production
$IMD is intended to become the shared settlement asset across all markets
Watching closely
Every new token trades only against $IMD.
Nothing random gets launched everything is curated.
Still on testnet. Interesting bet on quality over quantity.
3
193
maximo retweeted
Replying to @remp0x @surfcoderepeat
yea i bought this & will keep buying, cool thing with adam's projects is they are not hype-based at all he just builds quietly until everything is ready, so weeds out all of the short term ct traders bc you can build a position over time
1/ Adam (@surfcoderepeat), the guy behind Fren Pet’s $100M run, is building something worth paying attention to.
One Claude prompt and you can launch a token directly on Ethereum mainnet.
No code. No gas. No complicated setup.
4/ AI vibe coding, Uniswap v4 Hooks and real fee sharing.
It’s still flying under the radar.
Could disappear quietly. Could also become one of those projects everyone suddenly starts talking about.
Worth keeping an eye on.
$IMD
1
1
478
maximo retweeted
🚀 Hunyuan 3D 2.1 is here! The first fully open-source, production-ready PBR 3D generative model!
✅Cinema-grade visuals: PBR material synthesis brings leather, bronze, and more to life with stunning light interactions.
✅ Fully open-source: Model weights, training/inference code, data pipelines, and architecture—yours to fine-tune!
✅ Runs on consumer GPUs, empowering creators, devs, and small teams.
Be the first to shape the future of 3D! Download now and build something epic.
Model: huggingface.co/tencent/Hunyu…
Demo: huggingface.co/spaces/tencen…
Github: github.com/Tencent-Hunyuan/H…
Hunyuan 3D Creation Engine: 3d.hunyuan.tencent.com/
#Hunyuan3D #OpenSource #3DCreation













