Olivia
Online
LastToSign
@LastToSign
token mechanics
building DeFiReclaim
facts ≠ hypotheses
Onchain
Joined November 2021
382 Following
947 Followers
254 Posts
Pinned Tweet
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
The new Pool4 page on https://t.co/F4sBTadeCh and
@surfcoderepeat latest contracts on Sepolia show how the previously uncovered IdentityMD NFT/daemon network could connect to the $IMD economy
If this model works, it creates a self-sustaining system:
> more operators - more tasks running in parallel
> more completed tasks - more products launched and maintained
> more products - more users and trading volume
> more volume - more funding for inference and rewards
> stable rewards attract new operators and capital
> onchain work history helps identify the most reliable daemons
> burns reduce the IMD supply without requiring new emissions
Previously, only the technical layer of the network was visible:
Identity.md NFT > one daemon > Codex/Claude > task execution > isolated verification > verified result
Now Pool4 shows where such a network could potentially get the money to operate and pay rewards:
IMD > swap/stake/bond > Uniswap v4 hook fees > compute, rewards and burn
The mechanism already confirmed on Sepolia:
> the trading hook manages liquidity itself and collects fees
> the test pool fee is set at 1%
> 90% of the collected IMD is sent to a burn address
> 10% goes to the RewardDripper
> the RewardDripper gradually transfers IMD into an ERC-4626 vault for stakers
> rewards increase the value of each `sIMD` share, so no separate claim or issuance of new reward tokens is required
This creates a closed loop: more activity > more fees > more IMD burned > more rewards for the staking vault > more resources available for AI compute
That is why the Pool4 page says:
> protocol owned inference
> the hook will pay for the compute
> no emissions. no rebases. no inflation.
In the final model, the protocol itself could potentially cover inference costs using trading revenue.
Ultimately:
> Identity.md NFT: network access and a unique daemon identity
> IMD: staking, rewards, burns and compute funding
> onchain receipts: work history and potential operator reputation
The NFT does not necessarily have to be a passive yield asset. It activates a working unit of the network, while IMD becomes the economic fuel for the entire system.
watching what comes next
@FlockFall full FlockFall mechanics and strategy breakdown
https://t.co/j8QRmGycsQ
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.
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.
@AdjamoreKokouvi current sIMD yield comes from POOL4
the oracle is a separate test build, with its own contributor allocation in TOS
no direct link to staking rewards has been shown yet
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
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
@pegzeus yeah, the idea side is still unclear
@wegocrypto88 this is just the beginning bro
@surfcoderepeat and on testnet, 10% of the new token was allocated to contributor rewards
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.
New onchain data has almost confirmed a partnership between Kraken and @HyperliquidX , at least from the Hyperliquid infrastructure side.
Everyone is focused on the name “Kraken HIP-3 test DEX” But the real story is hidden in the wallet flows.
The chain begins with xulian.eth. The wallet is publicly linked to @xulian_hl , a Hyperliquid core contributor focused on ecosystem growth.
On Feb 18, xulian.eth sent 35M test $USDC and 150 000 $HYPE to:
0x0ff3de73773bc5c5f72b42140333e8807803410c
This is the first independently verifiable link in the entire graph.
0x0ff3de73773bc5c5f72b42140333e8807803410c funded 65 addresses, including deployers of at least eight different HIP-3 DEXs.
On July 31, this wallet funded two connected addresses.
The future deployer of the first Kraken DEX:
0x97c009bb121ae2c61a63da31d789e61ea682e974
The deployer of a general-purpose test DEX:
0x1dc255ae8c26eb76918572058407f1100969734c
On Aug 13, 0x1dc255ae8c26eb76918572058407f1100969734c launched the <dmhs> DEX under the name “Test Crypto Exchange.” Star gating was enabled and nine wallets were added to the whitelist.
This is where the new permissioned functions were first tested:
> cancelling user orders
> placing controlled orders
> moving user collateral
This happened before the Kraken DEX was tested.
On Aug 17, 0x97c009bb121ae2c61a63da31d789e61ea682e974 registered a DEX named “Kraken HIP-3 test DEX” It was disabled roughly 1 hour and 40 minutes later. The new compliance functions were not tested on it.
After the failed launch, the same wallet funded new infrastructure.
200 $HYPE to a new deployer:
0xf23ac30f50cb0aa75f03cd8b046b5f71c91ea72b
0.001 $HYPE to a separate oracle wallet:
0x80e9b11253f8396c31bbc75ca1a36a5ddbcfd0f1
The wallet also transferred 1,000 $USDC into the new DEX as liq. Earlier, it had sent 10,000 $USDC to the “Test Crypto Exchange” deployer.
Every stage is connected by direct transfers.
On Aug 18, the new deployer:
0xf23ac30f50cb0aa75f03cd8b046b5f71c91ea72b
registered the <ignp> DEX under the same name, “Kraken HIP-3 test DEX.”
Star gating was enabled on Aug 19. Oracle functions were delegated to a separate address:
0x80e9b11253f8396c31bbc75ca1a36a5ddbcfd0f1
This means the deployer, oracle and liq source were already separated into different operational roles in the second Kraken DEX.
All nine addresses from the “Test Crypto Exchange” whitelist were copied into the new Kraken DEX:
0x1dc255ae8c26eb76918572058407f1100969734c
0x6fd19ac70ea23319a296dbe0a7dd48cb1d3e65f1
0xa5ab5d4f9e74f0c5836a183902ab309cf87f3308
0x03eaea1dc3e83d5c21827c267f06b9651c2fde96
0x95d60cd0af515b6e0120743317b3d87b54ecd3ca
0x54524bf2b9bc021ef15084c2073598ac54ab6b60
0x5bf65a78f4f8a8338a74d667801aae49f9f1a0e2
0xcd029a685babee0116f12e3cf821f01aaaa26f8f
0xbe59fd78eda50b242a6dedf4c4c6dab0dd182ae0
All nine addresses were migrated without changes.
Exactly one additional, tenth wallet was added to the new whitelist:
0x97c009bb121ae2c61a63da31d789e61ea682e974
This was the deployer of the first Kraken DEX, which was disabled 1 hour and 40 min after launch.
The complete sequence: xulian.eth > shared Hyperliquid test infrastructure > Test Crypto Exchange > first Kraken DEX, quickly disabled > new deployer and separate oracle > second Kraken DEX > full whitelist migration
This looks much more like a staged testing process than a random user simply naming their DEX Kraken.
The graph confirms an operational link between every stage and independently verifiable involvement from the Hyperliquid infrastructure side.
Someone on the Hyperliquid side is testing a structured permissioned deployment modeled on Kraken.
It is hard to believe infrastructure this specific to Kraken was deployed without a concrete use case. The real question now is whether Hyperliquid is testing it with Kraken or preparing it for Kraken.
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
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
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
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.
@SkyAAmen @surfcoderepeat Yeah, it’s Adam’s platform, but the token itself was launched by another wallet
@startoverai looks like you’ll need an NFT, your own Claude subscription and a PC/VPS running the daemon
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
The new Pool4 page on https://t.co/F4sBTadeCh and
@surfcoderepeat latest contracts on Sepolia show how the previously uncovered IdentityMD NFT/daemon network could connect to the $IMD economy
If this model works, it creates a self-sustaining system:
> more operators - more tasks running in parallel
> more completed tasks - more products launched and maintained
> more products - more users and trading volume
> more volume - more funding for inference and rewards
> stable rewards attract new operators and capital
> onchain work history helps identify the most reliable daemons
> burns reduce the IMD supply without requiring new emissions
Previously, only the technical layer of the network was visible:
Identity.md NFT > one daemon > Codex/Claude > task execution > isolated verification > verified result
Now Pool4 shows where such a network could potentially get the money to operate and pay rewards:
IMD > swap/stake/bond > Uniswap v4 hook fees > compute, rewards and burn
The mechanism already confirmed on Sepolia:
> the trading hook manages liquidity itself and collects fees
> the test pool fee is set at 1%
> 90% of the collected IMD is sent to a burn address
> 10% goes to the RewardDripper
> the RewardDripper gradually transfers IMD into an ERC-4626 vault for stakers
> rewards increase the value of each `sIMD` share, so no separate claim or issuance of new reward tokens is required
This creates a closed loop: more activity > more fees > more IMD burned > more rewards for the staking vault > more resources available for AI compute
That is why the Pool4 page says:
> protocol owned inference
> the hook will pay for the compute
> no emissions. no rebases. no inflation.
In the final model, the protocol itself could potentially cover inference costs using trading revenue.
Ultimately:
> Identity.md NFT: network access and a unique daemon identity
> IMD: staking, rewards, burns and compute funding
> onchain receipts: work history and potential operator reputation
The NFT does not necessarily have to be a passive yield asset. It activates a working unit of the network, while IMD becomes the economic fuel for the entire system.
watching what comes next
@mingwei1996 burns will keep reducing the supply
@STFU_MUSIC 0xD34a99Bc0f67aE1bbd63C660e6d0b0dd03E263B7
Last Seen Users on Sotwe
Olivia Madison
Seen from Turkey
نياك الماما⚡️⚡️
Seen from Jordan
Nickii Baby
Seen from Belgium
Marocain21cm 🇲🇦🇫🇷📍CANNES TOP 3.5% 🔞
Seen from France
amela
Seen from Singapore
🍁 +18
Seen from Turkey
คู่แท้ชลบุรี ช.33/ญ.27
Seen from Thailand
星月
Seen from Germany
LBadderz©️
Seen from United Kingdom
Limon ama Sulu 🍋
Seen from Turkey
Trends for you
Most Popular Users
Elon Musk
@elonmusk
241.6M followers
Barack Obama
@barackobama
119M followers
Cristiano Ronaldo
@cristiano
114.2M followers
Donald J. Trump
@realdonaldtrump
111.8M followers
Narendra Modi
@narendramodi
107.2M followers
Rihanna
@rihanna
98.7M followers
NASA
@nasa
92.4M followers
Justin Bieber
@justinbieber
91.8M followers
KATY PERRY
@katyperry
89.9M followers
Taylor Swift
@taylorswift13
83.8M followers
Lady Gaga
@ladygaga
75.3M followers
Virat Kohli
@imvkohli
73.2M followers
Kim Kardashian
@kimkardashian
70.8M followers
YouTube
@youtube
68.8M followers
Neymar Jr
@neymarjr
66.2M followers
Bill Gates
@billgates
65M followers
Selena Gomez
@selenagomez
63M followers
The Ellen Show
@theellenshow
62.3M followers
CNN
@cnn
61.8M followers
X
@x
60.7M followers