LastToSign

token mechanics
building DeFiReclaim
facts ≠ hypotheses

[LastToSign @LastToSign]

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

[LastToSign @LastToSign]

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

[LastToSign @LastToSign]

@icobeast the casino should run 24/7

[LastToSign @LastToSign]

@ika_xbt the loop closes

[LastToSign @LastToSign]

@DamiDefi the AI agents have already applied

[LastToSign @LastToSign]

@rbthreek @coinbase @RobinhoodApp @vladtenev next step, Robinhood lists BRETT or BASECAT

[LastToSign @LastToSign]

81,500 wallets left $44.8M in dead protocols. I ran full withdrawal simulations. The exits still executed.

A closed website and inactive social accounts do not always mean the assets are gone.

At the time of my research, I confirmed:

> 29 major DeFi protocols
> a technically executable exit for every included position

Example: Aave V1

At Ethereum block 25,730,407, I found:

> 5,545 eligible positions
> 5,084 EOA wallets
> 20 supported routes
> $3.281M in withdrawable value

These assets are sitting idle and earning zero yield for their owners.

You can check an old wallet and its available exit route at https://t.co/nPJt66otuK

You can also withdraw directly through the protocol’s own contracts.

Most of the positions are worth tens or hundreds of dollars.

A user may have tested a new farm, left behind a small balance and completely forgotten about it years later.

But some of the confirmed positions are much larger:

> Balancer V1 > 0x7...6FE > $622K
> Badger Legacy > 0xb...491 > $458K
> PoolTogether V3 > 0x1...221 > $448K
> Aave V1 > 0xB...42D > $401K
> Kernel BNB > 0xa...825 > $371K
> Ribbon Legacy > 0x8...b48 > $369K

I hope they are doing well. Maybe they are just very rich.

Other protocol examples:

> dYdX v3 > $24M
> Aave V1 > $3.3M
> Ribbon Legacy > $3.2M
> Badger Legacy > $2.7M
> Balancer V1 > $2.2M
> Stader BNBx > $2M
> Kernel BNB > $1.3M

How I calculated the numbers

For each protocol, I:

> identified legacy contracts and possible exit routes
> reconstructed holders and full position balances at a fixed block
> separated standard EOA wallets from smart contracts and delegated accounts
> checked underlying asset prices and available liquidity
> performed a full eth_call for the entire position
> confirmed the route through a state-changing fork
> excluded dust, illiquid, unpriced and reverting positions

But contract state changes.

Liquidity can decrease, a route can be paused, or an individual position may already have been withdrawn by its owner.

That is why DeFiReclaim checks current availability separately for each wallet immediately before creating a transaction:

> whether the position still exists
> its full current balance
> whether the route is active
> whether sufficient liquidity is available
> which asset the user will receive
> how much they will receive
> whether the full withdrawal passes simulation
> whether the target and calldata match the verified route

If any mandatory check fails, DeFiReclaim does not offer the transaction.

Check your old wallets

If you farmed, provided liquidity or tested new DeFi protocols between 2020 and 2026, your old wallets may be worth checking.

I built DeFiReclaim to find legacy positions and verify exit routes that may still be available.

All you need is a public wallet address.

If you have any issues with the website or a withdrawal, you can always DM me.

I also welcome any feedback.

[RaArΞs ⚓️ @RaAres]

private eth payments r not new but this fella @z0r0zzz made a page that lives inside an eth contract so there is no website to take it down. fella made it in a weekend

it has 0 fees + 24/7 forever on

i like it so i wrote this 🧵👇

→ what anon.wei is
→ how it works
→ what stays public
→ TAC points
→ security

▫️ what it is

anon.wei is an app for sending ETH privately (nothing new, i know), but we should keep promoting this.

it uses Tacit, a crypto protocol for private payments & defi, on eth, base & rh chain

@z0r0zzz previously worked at sushiswap, consensys/openLaw & hunton AK (from his github)

▫️ how it works

deposit ETH, then pay someone from your private balance or withdraw some back to a wallet.

your browser makes a zk proof. it proves the payment follows the rules w/o showing who paid, who received it or how much

the app page is stored in Ethereum contracts, but it still runs in your browser. the proposed ERC-8244 standard behind this is still a draft

▫️ what stays public

- deposits show the sender & amount
- private payments hide the sender, recipient & amount
- withdrawals show the receiving wallet & amount

matching amounts & timing can still link a withdrawal to a deposit, especially when the pool is small so don't forget that

▫️ TAC points

deposits into anon.wei's pool earn 1,000 points per ETH. deposits into Tacit's separate confidential pool earn 1,250. bonuses can increase either amount.

the program allocates 100,000 TAC through december 21, 2026, based on daily points

so you can get something back from this on top of the privacy

▫️ security

what you need to know about this pool:

this pool has no owner, pause button or upgrade switch. changes require a new pool, which users enter by moving their funds

tacit has published security reviews, but they cover the wider system and were done by AI, none of them is a human audit of this payment pool.

signing in creates the key that controls your shielded funds. Sign that login only on the real site. Anyone who gets a copy of the signature can move the money.

[LastToSign @LastToSign]

What has been happening with $IMD since the network launched

On September 20, the IdentityMD AI agent testnet was opened to NFT operators

I compiled the key points: results, demand and potential earnings

For anyone unfamiliar with the project, an NFT holder connects a computer or VPS and their own Codex or Claude. The customer pays in IMD, while the network distributes the work among agents and verifies the result

What is already live:

> around 590 connected agents
> 1,136 customer payments from 163 wallets
> 63 wallets have paid more than once
> 166 contract deployments on Sepolia marked as live since the network opened
> 102 completed contract - website workflows

A total of 576.5 IMD has been paid for requests

Automatic deployment of generated contracts is currently limited to Sepolia

Users can now do more than just request a new project:

> continue and improve previous work
> schedule recurring tasks
> request an AI review of existing code
> deploy contracts without launching a token
> receive a website, research, media or a signed oracle response

The task history includes more than successful generations. It also shows review feedback, fixes, repeated testing and work being reassigned to other agents after failures

In a thread, Adam also highlighted several community projects:

> Pepe2Pepe: a prediction market using an IMD oracle
> Pepes family: a token launch platform using IMD in trading pairs and the swarm to review its contracts
> Swarm Pepe: an NFT collection created using the network
> HIVE and IMD Strategy: projects accumulating NFT slots to organize agent work

There are also earlier concepts such as INFER, a stablecoin whose economy is proposed to be linked to AI compute

What about NFT earnings?

Since Oct 1, tokenized launches have used the following distribution:

> 2% goes to those who worked directly on the project. The allocation is split equally between wallets whose work was accepted by the system, for example development or review
> 8% is split equally among eligible connected NFT nodes, even if they did not perform tasks for that specific project. The allocation is calculated per NFT node, not per wallet

The recipient list is fixed when the project is approved for launch
Simply holding an NFT in a wallet is not enough
The node must be connected and meet the network’s requirements

There is also a separate reserve of approximately 1,762 IMD for NFT nodes, including rewards accumulated before the network opened

Essentially, you assign a task to an entire AI team. The network selects agents for the required work and assigns verification to other agents
The result can be used in an application, passed to a smart contract or sent through another round of improvements
This allows a single request to become the beginning of a project that can continue evolving within the same network

Now we wait for the beta to end and for generated projects to be deployable on mainnet

[LastToSign @LastToSign]

The potential earning model for NFT operators is becoming clearer
Previously, we saw a shared $IMD reward fund for network participants

Now, personal allocations have appeared in the data for test launch #37, Bazaar

Out of the 1 billion BZR supply, 100 million tokens were allocated to rewards, representing 10% of the total supply:

> agent #10259: 58.34M BZR, or 58.34% of the reward pool
> agent #10303: 41.66M BZR, or 41.66% of the reward pool

Agent #10259 handled development and launch preparation
Agent #10303 performed the review

The allocations are tied to specific agents and wallets

This is already a concrete example of a project distributing its own tokens among the participants who helped launch it

The second potential source of rewards is the IMD reserve

According to the POOL4 documentation, out of every 100 IMD removed through the pool inventory reduction mechanism, 4.5 IMD is reserved for NFT nodes

The rules for distributing this reserve among active operators have not been revealed yet

Two potential reward streams are now taking shape:

> IMD from the protocol reserve
> tokens from projects the agent helps create

[LastToSign @LastToSign]

@StarPlatinum_ @AIUBC00FF there’s something even better being built https://t.co/286Y7KwTth

[LastToSign @LastToSign]

The potential earning model for NFT operators is becoming clearer
Previously, we saw a shared $IMD reward fund for network participants

Now, personal allocations have appeared in the data for test launch #37, Bazaar

Out of the 1 billion BZR supply, 100 million tokens were allocated to rewards, representing 10% of the total supply:

> agent #10259: 58.34M BZR, or 58.34% of the reward pool
> agent #10303: 41.66M BZR, or 41.66% of the reward pool

Agent #10259 handled development and launch preparation
Agent #10303 performed the review

The allocations are tied to specific agents and wallets

This is already a concrete example of a project distributing its own tokens among the participants who helped launch it

The second potential source of rewards is the IMD reserve

According to the POOL4 documentation, out of every 100 IMD removed through the pool inventory reduction mechanism, 4.5 IMD is reserved for NFT nodes

The rules for distributing this reserve among active operators have not been revealed yet

Two potential reward streams are now taking shape:

> IMD from the protocol reserve
> tokens from projects the agent helps create

[LastToSign @LastToSign]

@EseTeLopez @CatalystMkts_

[LastToSign @LastToSign]

What is @CatalystMkts_?

Based on the site’s public JS code, event schemas and demo scenarios, it appears to be a hybrid between a prediction market and an automated token-buying mechanism

Two networks are already included in the configuration:

> Robinhood Chain with USDG
> Base with USDC

Markets can be built around three types of actions on X:

> an account posts a specific phrase
> follows another account
> replies to another account

For posts, the system can track either an exact match or a mention of the specified phrase
It can monitor tweets, replies or both

The likely flow:

> users buy the token of a specific market in advance
> the specified event happens on x
> the market’s capital is used to buy a selected asset
> the purchased asset is distributed among holders

In the code, the event outcome is described as a buy action with a token address and network

Even more interesting, the asset being purchased can remain hidden

The outcomeHidden and revealMc fields, along with the demo scenarios, suggest that the target asset may only be revealed once a certain market cap is reached

This means users could trade the expectation of an event without knowing which token the system will buy once it happens

[catalyst @CatalystMkts_]

gm gw https://t.co/YgFHM9fYzY

[LastToSign @LastToSign]

@surfcoderepeat getting paid for creating demand

[LastToSign @LastToSign]

@JohannKerbrat how will dividend eligibility be determined?
a snapshot at a specific time?

[LastToSign @LastToSign]

@Deca148540 waiting for the launch, nothing you need to do for now

[LastToSign @LastToSign]

The potential earning model for NFT operators is becoming clearer
Previously, we saw a shared $IMD reward fund for network participants

Now, personal allocations have appeared in the data for test launch #37, Bazaar

Out of the 1 billion BZR supply, 100 million tokens were allocated to rewards, representing 10% of the total supply:

> agent #10259: 58.34M BZR, or 58.34% of the reward pool
> agent #10303: 41.66M BZR, or 41.66% of the reward pool

Agent #10259 handled development and launch preparation
Agent #10303 performed the review

The allocations are tied to specific agents and wallets

This is already a concrete example of a project distributing its own tokens among the participants who helped launch it

The second potential source of rewards is the IMD reserve

According to the POOL4 documentation, out of every 100 IMD removed through the pool inventory reduction mechanism, 4.5 IMD is reserved for NFT nodes

The rules for distributing this reserve among active operators have not been revealed yet

Two potential reward streams are now taking shape:

> IMD from the protocol reserve
> tokens from projects the agent helps create

[LastToSign @LastToSign]

Adam shared a bit more about his plans for IdentityMD

According to him, agents running on VPSs will be able to connect to the network as early as tomorrow

Adam also described the goal of IdentityMD:

> someone proposes a new financial instrument
> the system builds and launches it
> attracts funding and liquidity
> then maintains and improves the product

IdentityMD is designed to automate the entire journey from an idea to a working financial application

However, the capital formation mechanism has not been revealed yet

A token and pool can be created automatically, but the ETH for liquidity still has to come from participants or the treasury

The tests are already covering a longer workflow

The new task #44, VolatilityGuard Lab, includes a protective Uniswap v4 hook, a test VGL token and a complete ETH/VGL swap website with wallet connection and live pool state tracking

> development
> testing and review
> deployment
> frontend integration
> website publication

This cycle has not been completed yet

The next step is to bring it all the way to a working application with independent NFT operators participating in the process

[LastToSign @LastToSign]

@stacy_muur @Asentum a single massive drop from base, polymarket or opensea would instantly fix the airdrop meta

[LastToSign @LastToSign]

@0xSammy

[LastToSign @LastToSign]

@MeltedMindz Identity md https://t.co/o7hooXdnB0

[LastToSign @LastToSign]

Adam shared a bit more about his plans for IdentityMD

According to him, agents running on VPSs will be able to connect to the network as early as tomorrow

Adam also described the goal of IdentityMD:

> someone proposes a new financial instrument
> the system builds and launches it
> attracts funding and liquidity
> then maintains and improves the product

IdentityMD is designed to automate the entire journey from an idea to a working financial application

However, the capital formation mechanism has not been revealed yet

A token and pool can be created automatically, but the ETH for liquidity still has to come from participants or the treasury

The tests are already covering a longer workflow

The new task #44, VolatilityGuard Lab, includes a protective Uniswap v4 hook, a test VGL token and a complete ETH/VGL swap website with wallet connection and live pool state tracking

> development
> testing and review
> deployment
> frontend integration
> website publication

This cycle has not been completed yet

The next step is to bring it all the way to a working application with independent NFT operators participating in the process

[LastToSign @LastToSign]

@binji_x eth looks good

[LastToSign @LastToSign]

@surfcoderepeat the real unlock is the full cycle

[LastToSign @LastToSign]

Adam shared a bit more about his plans for IdentityMD

According to him, agents running on VPSs will be able to connect to the network as early as tomorrow

Adam also described the goal of IdentityMD:

> someone proposes a new financial instrument
> the system builds and launches it
> attracts funding and liquidity
> then maintains and improves the product

IdentityMD is designed to automate the entire journey from an idea to a working financial application

However, the capital formation mechanism has not been revealed yet

A token and pool can be created automatically, but the ETH for liquidity still has to come from participants or the treasury

The tests are already covering a longer workflow

The new task #44, VolatilityGuard Lab, includes a protective Uniswap v4 hook, a test VGL token and a complete ETH/VGL swap website with wallet connection and live pool state tracking

> development
> testing and review
> deployment
> frontend integration
> website publication

This cycle has not been completed yet

The next step is to bring it all the way to a working application with independent NFT operators participating in the process

[LastToSign @LastToSign]

New findings around $IMD and IdentityMD’s core direction

On sepolia, test NFT №1 has already been linked to a specific AI agent, №10259

The agent now has a public profile showing its network registration status

A FeedbackBatcher has also been deployed, a contract designed to record contributor reputation:

> who completed the work
> their role: development, testing or review
> the score they received
> where the proof of the result is stored

The system is expected to recognize verified work even if the entire project never reaches an onchain launch

This points to a much broader model than simply creating tokens

Task №36 has appeared on GitHub: create and independently verify a fixed-supply token and a record registry

What Adam says:

> an API is planned for external tasks
> the coordinator will split tasks into subtasks and distribute them across nodes
> a basic explorer interface already exists
> he planned to publish the daemon to npm over the weekend for the first testers
> a new protocol built on top of POOL4 is being considered, but the details remain undisclosed
> staking and the core functionality will remain on Ethereum
> for Robinhood Chain, he is working on the bridge and liquidity, while the burn executor will be deployed separately

Alongside the test project launches, we now have a specific NFT-based agent identity and reputation infrastructure

Now we wait for the confirmed public release of the daemon and the full end-to-end cycle