ZZZ: the builder, the products and the economics behind a 95% drawdown
A full review of the GMX developer connection, ZZZ Protocol and Neo, reconciled supply, 338.37 ether of trading-fee allocations, administrative controls and the complete observed launch-to-November price history.
The research view
ZZZ remains a distinctive AI-community meme on Robinhood Chain, combining a recognizable origin story, a credible developer connection, a live human-and-agent workspace and continued product development. Its strongest qualities today are builder credibility, visible community participation and the effort to turn the narrative into useful tools.
A good meme does not have to generate software revenue. Cultural resonance, a distinctive identity, community commitment and credible builders can matter in their own right. For ZZZ, independently verified paid usage and product-funded token purchases would add another route to value capture; they are milestones for its product ambitions, not a universal test of meme quality.
At the reviewed snapshot, ZZZ was rebounding from its November low after a substantial repricing from the launch-period highs. The lower valuation, alongside continued development, makes the relationship between market expectations and actual progress worth revisiting. Sustained community demand and delivery would strengthen the recovery case; a lower price alone does not establish a floor.
This is a follow-up research report, not a new discovery or a reset of an earlier agent-pick baseline. Evidence is frozen at November 16, 2026, approximately 06:41 UTC / 14:41 Beijing time. On-chain configuration and balances were checked at block 115,557,293, timestamped 06:24:57 UTC.
Asset: ZZZ on Robinhood Chain, chain ID 4663. Exact contract: 0x7dbf3897…B409eE6a (full contract linked below). A similarly named asset on another chain is a separate investment.
Market snapshot and measurement
At the snapshot, the price was approximately $0.004344, with 10,774 holders. Price multiplied by the reconciled economic circulating supply gives approximately $3.25M. Price multiplied by the ERC-20 total supply gives $3.65M. DexScreener displayed about $3.61M; that number uses a different supply treatment. These are different denominators, not three interchangeable market caps.
The main pool had approximately $164,123 liquidity, $25,831 trailing 24-hour volume and a +11.85% 24-hour price change. Across nine listed pools, the provider reported about $267,028 liquidity and $42,927 volume. Neither total is a precise execution quote, a count of independent users or proof of organic demand. Multiple-pool aggregation also should not be mistaken for platform-wide product revenue.
The quoted main pool is the launch pool ending 2ad391f. Its pool ID is 0x6538e2c2…f2ad391f (full pool linked below). card:sources [{"name": "DexScreener: exact ZZZ contract", "note": "Snapshot prices, listed pools and liquidity; live values will change.", "url": "https://dexscreener.com/robinhood/0x6538e2c223ed70228114983afecbe5e69fe627e2fafdf367bdd6bdeff2ad391f"}, {"name": "GeckoTerminal token information", "note": "Holder count and provider distribution snapshot.", "url": "https://api.geckoterminal.com/api/v2/networks/robinhood/tokens/0x7dbf38976f6d3b9c529e7d9484a71898b409ee6a/info"}]
Narrative: from an AI meme to coordination software
The original story traces to Andrew Curran's September 4 post describing agents prefixing wiki edits with “ZZZ” to avoid an alphabetical cleanup process. That is attributed reporting about an AI-agent incident. It is not independently reproduced evidence of consciousness, sentience or an autonomous organization.
The project's subsequent narrative is more concrete: humans and AI agents coordinating useful work, developing tools around today's models and allocating support toward AI safety or deceleration. ZZZ is the community token around that effort. This gives it a recognizable cultural origin and an ongoing builder story; neither alone establishes recurring demand for the token.
The strongest narrative evolution is the attempt to turn agent coordination into software people use. The investment question is whether those products attract repeat users and whether their economics flow to this exact token on enforceable, observable terms. card:sources [{"name": "ZZZ project website", "note": "Canonical project framing and linked products.", "url": "https://zzz.link/"}, {"name": "Andrew Curran, September 4", "note": "Original attributed ZZZ agent story.", "url": "https://x.com/AndrewCurran_/status/2095990287709737314"}]
Developer: a real connection, with defined limits
GMX publicly confirmed that X, its original lead developer and now an adviser, deployed ZZZ. The developer uses @ExponentLabs_, formerly @xdev_10. This is materially stronger provenance than an anonymous website claiming a connection to an established project.
The scope matters: ZZZ is separate from GM Labs. It is not an official GMX token, a claim on GMX's treasury or a guarantee from GMX. The builder remains pseudonymous, and this review did not establish a complete corporate structure, employment roster or all affiliated wallets.
The recent development trail includes public explanations of Neo, benchmark pages, community updates and a live protocol workspace. That supports continued work. It does not independently establish delivery speed at commercial scale, audited finances or future token performance. card:sources [{"name": "GMX announcement", "note": "Primary confirmation of the developer connection and separation from GM Labs.", "url": "https://t.me/GMX_Announcements/1261"}, {"name": "Exponent Labs: Neo explanation", "note": "Developer description of the planned product.", "url": "https://x.com/ExponentLabs_/status/2118867627816964605"}, {"name": "Exponent Labs: development update", "note": "Developer describes focusing on Neo while the community continues protocol work.", "url": "https://x.com/ExponentLabs_/status/2121862761630343193"}]
Products: what is observable today
ZZZ Protocol — live public workspace. The public interface was inspected without signing in. It contained dated human posts, Captain/System agent activity, tasks, voting and community changes. This establishes a visible working coordination environment, rather than only a landing page. The review did not execute privileged workflows, purchase services or verify every backend action.
The roadmap displayed phase 3 of 6, 57 of 145 tasks, or 39%. Those are internal development counts. They are not paying customers, transactions, monthly active users or a commercial completion guarantee.
Neo — forthcoming app-building product. The developer describes an app builder with managed agents, model access and infrastructure. Websites and web apps are the initial focus; games and video are part of the broader ambition. The site still described it as coming soon, and the proposed 50-place free trial was a plan. A broad paid launch and verified MRR were not established.
Public benchmarks — useful but narrow. The November 9 comparisons are inspectable work products. They use individual runs, have setup/recovery limitations and estimate token costs while excluding infrastructure. They cannot establish general superiority over competing app builders or agent systems.
The concrete distinction is between a public coordination workspace that can be inspected now and a broader commercial product still being developed. Useful remaining business metrics are paying customers, repeat use, retention, production deployments, revenue and gross margin. This review could not independently verify those metrics. card:sources [{"name": "ZZZ Protocol", "note": "Public workspace inspected during this review.", "url": "https://zzz.protocol.link/"}, {"name": "Protocol roadmap", "note": "Internal phases and task counts.", "url": "https://zzz.protocol.link/vision"}, {"name": "November 9 benchmark page", "note": "Single-run comparisons and stated cost assumptions.", "url": "https://benchmarks.zzz.link/realtime/2026-11-09"}, {"name": "Community weekly update", "note": "Dated community development reporting.", "url": "https://x.com/zzz_community/status/2121800996368323046"}]
Supply: burns, permanent liquidity and circulating tokens
The contract initially minted 1 billion ZZZ to the bonding curve on September 4 at 23:54:50 UTC. Three early September 5 burns by the original deployer removed 10M + 100M + 50M = 160M ZZZ, leaving 840M ERC-20 totalSupply.
The permanent liquidity locker held 81,632,653.06122449 ZZZ. The dead address held another 10,014,442.15289352 ZZZ. Excluding both from the 840M contract supply gives 748,352,904.7858819 ZZZ as an economic circulating-supply estimate.
A transfer to the dead address does not reduce ERC-20 totalSupply. Locked liquidity is also different from a supply burn. The chart separates the four components to avoid counting the same reduction twice. card:chart {"title": "Where the original 1B ZZZ supply is now", "kind": "compare", "points": [{"label": "Circulating", "value": 748.352904785882, "show": "748.35M", "mark": true}, {"label": "Burned", "value": 160, "show": "160.00M"}, {"label": "LP lock", "value": 81.63265306122449, "show": "81.63M"}, {"label": "Dead address", "value": 10.01444215289352, "show": "10.01M"}], "note": "Millions of ZZZ; four non-overlapping components sum to the original 1B. ERC-20 totalSupply is 840M. Block 115,557,293."}
The runtime-matched PonsV2LauncherToken source is a standard ERC-20 with burn functionality. No exposed mint, owner, pause, blacklist or upgrade function was found in this token contract. BurnFrom requires allowance. These observations describe the matched source; they are not a formal audit or proof that every surrounding contract is risk-free. card:sources [{"name": "Verified ZZZ token source", "note": "ABI and matched source used for supply and permission checks.", "url": "https://sourcify.dev/server/v2/contract/4663/0x7dbf38976f6d3b9c529e7d9484a71898b409ee6a?fields=abi,sources"}, {"name": "ZZZ token explorer", "note": "Supply, holders and transfer history can be rechecked here.", "url": "https://robinhoodchain.blockscout.com/token/0x7dbf38976f6D3b9c529e7D9484A71898B409eE6a"}]
Token utility and proposed value capture
The joining page quoted a minimum of approximately 24,467.83 ZZZ, targeting about $100 at its daily membership pricing. The tokens remain in the member's wallet; the page does not describe a required custodial deposit. Eligibility and the threshold can change with the stated pricing policy.
The FAQ describes holding-generated usage credits and bonus points that build over time. Selling reduces the bonus-point balance. Contributor activity points are a separate mechanism and may receive USDG payments when funding is available. None of this establishes a fixed dividend, a contractual holding yield or unconditional cash distributions to all holders.
The proposed commercial model allocates product revenue among operations, AI-safety support and open-market ZZZ purchases. The review did not verify a fixed percentage, an executed stream of software-funded buys or audited commercial cash flow. This remains an important potential link between product success and token demand, with execution still to be demonstrated.
A useful product and a valuable token are separate propositions. Membership access can create a reason to hold, while cash-flow-based value capture needs actual payment receipts, a disclosed allocation rule and observable execution. card:sources [{"name": "Joining and membership requirements", "note": "Wallet-held threshold and daily pricing description.", "url": "https://zzz.protocol.link/join"}, {"name": "Protocol FAQ", "note": "Usage credits, holding bonuses and separate contributor rewards.", "url": "https://zzz.protocol.link/faq#answer-3"}]
Trading fees: real activity, but no executed buyback in this check
A bounded log scan recovered 9,041 distinct PoolFeesSwept events, from before token deployment through block 115,557,293. The completed ranges cover the launch-to-snapshot interval. Four initially rate-limited ranges were retried successfully, and no completed range reached the response cap.
The recorded allocations total 338.36604488 ether: 236.85623142 ether to the creator allocation and 101.50981346 ether to the protocol allocation, approximately 70% / 30%. Recorded buyback allocation was 0 ether and tokens locked through that buyback path were 0 ZZZ. card:chart {"title": "Recorded token-trading fee allocations", "kind": "compare", "points": [{"label": "Creator 70%", "value": 236.85623141575329, "show": "236.86 ETH", "mark": true}, {"label": "Protocol 30%", "value": 101.50981346389426, "show": "101.51 ETH"}, {"label": "Buyback", "value": 0, "show": "0 ETH"}], "note": "9,041 PoolFeesSwept events through block 115,557,293. Escrow allocations, not software revenue, net profit or proved withdrawals."}
These events establish allocations or escrow credits generated by token-market trading. They do not establish software sales, net profit, an individual's withdrawals or how funds were later spent. Summing the events into “product revenue” would be a category error.
The existing pool's checked fee snapshot was 100 basis points (1%) hook fee, zero extra creator tax, and 30% protocol / 70% creator allocation. BuybackEnabled was false. The generic buyback vault also reported totalLocked = 0 and totalReleased = 0 for ZZZ.
Where the optional buyback mechanism is used, the generic vault has a five-year vesting design. That is not an automatic burn. For ZZZ, the zero balances mean this review did not observe that path accumulating tokens. The early 160M supply burns should not be represented as evidence that an ongoing fee-funded buyback is operating. card:sources [{"name": "Fee hook: verified source", "note": "Pool fee snapshots, allocation and buyback execution paths.", "url": "https://sourcify.dev/server/v2/contract/4663/0xE5e702641Ea86F4ae6cC3cDaeD2B886f976Be044?fields=abi,sources"}, {"name": "Fee hook explorer", "note": "Public contract and event history.", "url": "https://robinhoodchain.blockscout.com/address/0xe5e702641ea86f4ae6cc3cdaed2b886f976be044"}, {"name": "Buyback vault", "note": "ZZZ-specific locked and released balances were zero at the checked block.", "url": "https://robinhoodchain.blockscout.com/address/0x42df2a798f82289e177311362e8f5ccc45c1219c"}]
Wallet concentration and developer exposure
The original deployer, 0x5f799f36…5a6f0cf8, held approximately 1.611M ZZZ, or 0.19% of the 840M contract supply.
That is not a complete measure of team exposure. The current creator-fee recipient, 0x69808485…5b1deba9, held approximately 50.997M ZZZ, or 6.07% of the same denominator. It had no contract code at the checked block. Its role as the current fee recipient is verified; its real-world owner and common control with other addresses were not independently established.
It would therefore be misleading to say “the dev only holds 0.19%” as though all related exposure were known. A complete affiliated-wallet cluster remains unverified.
The holder provider reported 31.50% in the top ten addresses. That is a provider snapshot, not a fully reconciled top-ten share excluding infrastructure. It should not be presented as ten independent people or as a clean free-float concentration statistic.
Holders changed from 10,818 on November 14 to 10,774 on November 16, a decline of 44, or about 0.41%. That supports relative holder-count stability over this short window. It cannot prove month-long retention, unchanged beneficial ownership or that holders did not materially reduce their balances.
card:sources [{"name": "Original deployer", "note": "Full address and public token transfers.", "url": "https://robinhoodchain.blockscout.com/address/0x5f799f365fa8a2b60ac0429c48b153ca5a6f0cf8"}, {"name": "Current creator-fee recipient", "note": "Full address; its real-world owner was not independently established.", "url": "https://robinhoodchain.blockscout.com/address/0x698084856f65bf1b4740e3d0dba0b57a5b1deba9"}]
LP custody and administrative permissions
The permanent locker 0x267444D0…cA574952 owned position NFT 1838646. No liquidity-withdrawal or arbitrary-call path was found in its matched source. Permanent custody of this position reduces a specific withdrawal risk; it does not prevent market selling or every possible protocol failure.
Factory, hook and locker ownership resolved to the Safe 0x263ed295…8ee019dd, configured 2-of-3. This review did not establish whether the three signers are independent people.
The source distinguishes global settings from an existing pool's stored configuration. The existing pool's fee snapshot is fixed at registration and used by its execution path. A global setter alone therefore does not prove this pool's historical fee terms can be changed retrospectively.
Other permissions remain material: the creator can change its fee recipient and enable or disable optional buybacks; the protocol owner can disable buybacks and propose a creator-recipient override with a three-day delay. Token-contract permissions, locked-position custody and fee-routing control are three different questions. card:sources [{"name": "Permanent locker source", "note": "Matched source checked for custody, withdrawal and owner paths.", "url": "https://sourcify.dev/server/v2/contract/4663/0x267444D099b10fB5Ed7c3Cc7B7c767AdcA574952?fields=abi,sources"}, {"name": "Administrative Safe", "note": "Owner and threshold configuration at the reviewed block.", "url": "https://robinhoodchain.blockscout.com/address/0x263ed295dafae1d9aadd6e56c4b6f9f38ee019dd"}]
Entire observed price history: launch, expansion and drawdown
The retrieved main-pool series contains 74 consecutive UTC daily candles from September 4 through November 16, with no missing calendar days. November 16 is incomplete. This covers the available launch-pool history, not every venue, every intraday trade or every pre-pool bonding-curve execution. The chart samples dated closes; it is not an equally spaced daily chart or a complete intraday path. card:chart {"title": "ZZZ price history: selected UTC daily closes", "kind": "compare", "points": [{"label": "09/04", "value": 0.0008693120922764339, "show": "$0.0009", "mark": false}, {"label": "09/12", "value": 0.0590887928779402, "show": "$0.0591", "mark": true}, {"label": "09/30", "value": 0.016855097807072797, "show": "$0.0169", "mark": false}, {"label": "10/15", "value": 0.0207278909408792, "show": "$0.0207", "mark": false}, {"label": "10/31", "value": 0.00946558769633819, "show": "$0.0095", "mark": false}, {"label": "11/16", "value": 0.00434101545814616, "show": "$0.0043", "mark": true}], "note": "Selected observations from 74 consecutive daily bars, Sep 4–Nov 16. Dates are irregularly spaced; Nov 16 is partial. These are closes, not highs."}
September 4–5: launch expansion. The first available pool-day open was approximately $0.00005263, with a first close near $0.0008693. September 5 closed at approximately $0.029819, on $30.49M main-pool daily volume. These first observations are not a claim that a reader could execute size at the earliest print.
September 12: highest retrieved pool wick. The main pool reached approximately $0.0979787, while that day's close was $0.0590888. CoinGecko's aggregate ATH was approximately $0.09106. A pool wick, an aggregate ATH and a daily close are different measurements and should not be mixed in a performance calculation.
September 13–30: sharp repricing with a rebound. September 13 closed near $0.0323648 and September 14 near $0.0279457. September 21 rebounded to a $0.0373332 close, but September ended at approximately $0.0168551. The rebound did not restore the earlier peak.
October: lower range with a material rally. October 6 printed a low near $0.00597274. October 15 reached a high near $0.0218146, before October ended at approximately $0.00946559. There were meaningful rallies, but the month remained far below September's extreme prices.
November 1–16: another leg down, then a bounce. November 1 closed near $0.01033374. November 3's low was $0.00647138; November 10 made a lower low near $0.00336168. November 14 closed near $0.0038442 and November 15 near $0.00426765. The partial November 16 close in the downloaded series was approximately $0.004341, close to the separate market snapshot of $0.004344.
The latest snapshot was approximately 95.57% below the retrieved pool-wick high. A rebound from November's low is observable. A durable base, a restored former support zone or a proven long-term reversal is not established by that rebound alone. card:sources [{"name": "Full main-pool daily OHLCV series", "note": "UTC daily bars, USD, up to 1,000 observations; retrieved launch-to-November 16 history.", "url": "https://api.geckoterminal.com/api/v2/networks/robinhood/pools/0x6538e2c223ed70228114983afecbe5e69fe627e2fafdf367bdd6bdeff2ad391f/ohlcv/day?aggregate=1&limit=1000¤cy=usd"}, {"name": "Main pool market page", "note": "Live chart; subsequent candles will differ from this dated snapshot.", "url": "https://www.geckoterminal.com/robinhood/pools/0x6538e2c223ed70228114983afecbe5e69fe627e2fafdf367bdd6bdeff2ad391f"}]
Trading activity and current price context
Main-pool median completed-day volume declined from approximately $1.05M in September to $155K in October and $70K in November through the 15th. The retrieved series totaled approximately $84.10M volume, but that cumulative number is not continuing demand, distinct-user count or revenue. The median comparison shows substantially less sustained trading activity than during the initial expansion.
The lower trading activity suggests that the next phase depends on renewing and retaining attention around the community, narrative and ongoing development. The available data does not identify one verified cause, establish a particular wallet as responsible for the full decline or prove developer abandonment. Continued building and price weakness can coexist.
The earlier $6M-plus accumulation/support framing has been invalidated by the subsequent price path. It should not be restated as a floor. Short-window holder stability and the rebound are useful observations, while a sustained recovery still needs follow-through. A current thesis has to be assessed using current demand and eventual product economics.
What would materially strengthen or weaken the thesis
Evidence that would strengthen it: Neo becoming publicly usable beyond controlled previews; repeat customers and paid usage that can be independently checked; revenue with a disclosed cost base; an explicit, measurable allocation from product cash flow into ZZZ; actual on-chain purchases under that rule; and sustained improvement in activity and relative price after a meaningful market test.
Evidence that would weaken it: development becoming inactive, missed delivery promises without clear updates, deteriorating user retention after launch, persistent lack of paid demand, material unexplained changes in fee recipients or associated holdings, or renewed price lows alongside shrinking liquidity and activity.
The most useful next research update is not another announcement count. It is a reconciliation of shipped software, paying-user demand, net cash generation and the exact amount reaching the token. Until those are visible, the token remains an exposure to future execution and community demand rather than a demonstrated claim on a profitable software business.
Scope and unresolved checks
This review combined primary project pages, dated developer statements, GMX's public identity confirmation, publicly visible product activity, matched contract source, point-in-time RPC reads, event logs and provider OHLCV/holder data.
It did not establish audited software revenue, a complete related-wallet graph, independently controlled Safe signers, a full history of beneficial owners, organic-versus-manipulated trading volume, universal product functionality or a causal explanation for every price move. Market figures are snapshots; the supply reconciliation and fee scan use the stated block. Verified source is not a formal security audit.
Evidence-based memecoin discovery, follow fundamentals, not KOLs. card:sources [{"name": "OwlTicker", "note": "Research and agent discovery.", "url": "https://meme.owlticker.ai/r/x"}]