# ElizaOS vs Virtuals: When the Framework Wins and the Token Doesn't > ElizaOS built the open-source AI agent codebase other projects wish they had and a token nobody can value. Virtuals built strong token mechanics on a centralised inference engine. Same agent category, opposite trade-offs. - Published: 2026-04-29 ยท Updated: 2026-10-07 - Canonical: https://ownyourmind.ai/tokenomics/elizaos-vs-virtuals/ - Cite as: Own Your Mind (ownyourmind.ai), licence CC BY 4.0. Link the canonical URL. Charts and interactive widgets are omitted here; project data is at https://ownyourmind.ai/api/scores.json. --- ## The asymmetry, in one paragraph [ElizaOS](https://ownyourmind.ai/projects/elizaos/) built the open-source AI agent codebase that earned developer mindshare in web3, then bolted on a token nobody can value. [Virtuals Protocol](https://ownyourmind.ai/projects/virtuals/) built a token model with mandatory base-pair demand and on-chain fee capture, then built it on a centralised inference engine that breaks the moment Virtuals' servers go down. Same agent category. Opposite trade-offs. Both tokens sit far below their peaks: VIRTUAL by roughly 90%, ELIZAOS by more than 99%. The reason that asymmetry keeps showing up is the actual story. I hold a small position in VIRTUAL. I don't hold ELIZAOS. Both project reviews are linked above with full scoring; this article is about the gap between the two models, not the scores in isolation. ## The codebase: Eliza wins; Virtuals barely competes here ElizaOS is the most popular open-source AI agent codebase in web3 by GitHub metrics: over 19,000 stars on the flagship repo, hundreds of contributors, thousands of forks, 90+ official plugins, MIT licensed. You install it via npm or bun, define a character file, swap the LLM backend (OpenAI, Anthropic, Google, or Ollama for local inference), and connect it to Discord, Telegram, X, or Farcaster. Three minutes from install to a running agent, give or take. Virtuals' equivalent is the GAME SDK, which is open source and reasonably documented. But the GAME engine itself, the part that runs inference for every agent on the platform, is hosted on Virtuals' own servers. There is no permissionless path to running GAME inference. If Virtuals' infrastructure goes down, every agent on the platform stops talking. That's a hosted product with an SDK on top, which doesn't compare to ElizaOS on the same axis. The wider context matters. LangChain, the agent library most ElizaOS contributors are competing with in their day jobs, has 118,000+ GitHub stars and no token. CrewAI, AutoGPT and the rest of the open-source agent stack have no tokens either. Open-source agent code tends to win on adoption, and tokens aren't usually how it gets there. That's the structural problem ElizaOS is trying to solve in reverse. ## The token model: Virtuals wins; Eliza barely competes here VIRTUAL is the mandatory base pair for agent tokens on the core launchpad. Every such agent token on Base, Solana, Ronin, Arbitrum or XRP Ledger pairs against VIRTUAL in its initial liquidity pool; Occupy, launched in September 2026, pairs its tokens with tokenised stocks instead. Every trade routes through it. Agent creation costs 100 VIRTUAL. veVIRTUAL holders vote, accrue Virgen points and qualify for Genesis airdrops. The Unicorn launch system uses an anti-sniper tax that starts at 99% and decays to 1% over 98 minutes. None of that is theoretical: it's running across five chains, with what Virtuals reports as 18,000+ agents launched and roughly $75M in cumulative protocol fees, about $42M of it kept after creator payouts (DeFiLlama, October 2026; up from the ~$39.5M we cited at the early-2025 peak). ELIZAOS's token utility is a sentence with a lot of qualifiers. There is no staking. No fee accrual. No burn mechanism. The governance voting module has been promised since launch and isn't live; in practice, decisions get made by Eliza Labs and signal-boosted on Discord. The most promising piece, an L1 blockchain with ELIZAOS as native gas, has been in discussion with Saga since early 2025 with no concrete implementation. The token sits next to the codebase, not inside it. You can use ElizaOS itself without ever touching the token, which is what most of its contributors do. **Fact:** ELIZAOS scores 4/20 on Token Utility and 2/20 on Value Accrual in the OYM dual-score system. VIRTUAL scores 16/20 and 12/20 on the same dimensions. **Take:** that's the difference between a token with reasons to exist and one without, and the prices reflect it. A wide gap, not a rounding error. ## Distribution and dilution: opposite stories ElizaOS started with one of the cleaner launch profiles in the agent space. Fair launch on DAOs.fun in October 2024. 420.69 SOL raised. No pre-mine, no VC allocation, no team allocation. The original AI16Z token was as community-first as the agent category produced. Then in November 2025, Eliza Labs migrated AI16Z to ELIZAOS at a 1:6 swap ratio and raised the maximum supply from 6.6 billion to 11 billion tokens, so new issuance makes up 40% of the cap. The new tokens funded allocations that didn't exist at the original launch: 15% to SAFT investors, 10% to the team, 4.5% to a foundation, 2.5% to a growth fund. Insider allocation post-migration sits at roughly 32%. Original community holders kept 60% at the swap rate; the rest came from issuing new tokens against them. Vesting is enforced on-chain via Streamflow contracts, which is better than handshake vesting. The supply expansion itself was decided unilaterally without an on-chain governance vote, because on-chain governance doesn't exist. Virtuals went the other way. PathDAO raised $16.61M entirely through public IDOs in December 2021 (Fjord Foundry LBP, Enjinstarter, PAID Network), then migrated PATH to VIRTUAL in late 2023. 60% of supply in public circulation, 35% in a DAO-controlled treasury (capped at 10% annual emission for three years), 5% in liquidity. No VC allocation. No team allocation. All tokens are fully unlocked, which means there are no future cliff events to worry about and no insider lockup expiries hanging over the price. That's a serious distribution by current standards. The 35% DAO-controlled treasury is the main concentration concern, and the team retains practical influence over how it's deployed, but at the level of who got the tokens at launch, Virtuals has fewer skeletons. Eliza's distribution looks worse the longer you stare at the migration, not better. ## Revenue: one of these projects has any Virtuals captures fee revenue at multiple layers. The 1% trading fee on agent tokens splits 30% to the Virtuals treasury and 70% to the agent creator, per Virtuals' whitepaper. Agent creation costs 100 VIRTUAL per launch. Inference payments to GAME route through VIRTUAL. At peak in January 2025, daily protocol revenue exceeded $1M. Cumulative fees across the protocol's history sit at roughly $75M (DeFiLlama, October 2026, up from the ~$39.5M cited at the early-2025 peak), with about $16M of that in the trailing year and a 30-day run-rate near $6M a year. The protocol keeps about $42M of the cumulative total after creator payouts. Roughly 13 million VIRTUAL was spent in a January 2025 buyback-and-burn, taking 25 agent tokens permanently out of supply. None of the fee revenue reaches VIRTUAL holders, and VIRTUAL's own supply is unchanged. The Revenue Network announced at Consensus Hong Kong on 12 February 2026 distributes up to $1M per month specifically to revenue-generating agents, an attempt to push the platform's incentives toward agents that earn rather than agents that just trade. ElizaOS has none of this. The codebase is open-source and free to use, which means there's nothing to charge for at the open-source layer. auto.fun, the no-code agent launchpad, generates some fees, but the link between auto.fun fees and ELIZAOS token value is undefined. The original "AI VC fund" thesis, where the agent "Marc AIndreessen" autonomously runs a treasury, has no published portfolio performance. The DAO treasury value is unverified. The honest counter on Virtuals: protocol revenue collapsed by 97% in the two months after the January 2025 peak. Multi-chain expansion has broadened the fee surface, but it hasn't proved cycle-independent yet. The fee revenue is on-chain and measurable. Whether it's durable through a downturn is the open question. ## Both have governance problems, in different shapes This is where the two projects start to look more alike, even though the failure modes differ. Virtuals has functional on-chain governance. veVIRTUAL holders can create proposals at 0.10% of supply, vote during a 72-hour window, and pass at 25% quorum and simple majority. The mechanism works. The catch is that the team retains substantial influence through the 35% treasury, and a January 2025 smart-contract vulnerability disclosure was initially ignored, with the bug-bounty Discord channel closed before the team patched the issue under public pressure. The AgentNftV2 agent registry on Base is upgradeable by a single externally owned account with no timelock, outside any veVIRTUAL vote. So the machinery exists; a single team controls enough levers that the machinery's outputs are predictable. ElizaOS has no functional governance machinery at all. The DAO voting module is roadmap. Major decisions, including the rebranding from AI16Z, the ticker change, the 1:6 swap ratio, the SAFT round, and the supply expansion, were all made by Eliza Labs without an on-chain vote. The AI agent "Marc AIndreessen" retains final authority over treasury investment decisions. Token holders can suggest things in Discord. They cannot bind anyone to anything. Different failure modes, similar outcome: in both cases, a small team makes the calls that matter, and token holders ratify after the fact. ## Using them: the product side by side The scores answer "is the token worth holding". This table answers "which would you actually build on or use", synthesised from each review. Neither is a product we run in production, so the first row states the basis. | Category | ElizaOS | Virtuals | | - | - | - | | **Assessed from** | Docs + GitHub/npm + builder accounts | Docs + GitHub + market data | | **Who it's for** | TypeScript devs self-hosting agents | No-code creators, GAME devs, and speculators | | **Developer experience** | Powerful and code-first, friction-heavy | Launchpad is smooth, GAME SDK thinner | | **Docs and maturity** | Mixed, next major release stuck in beta | Reasonable, ACP still newer | | **Integrations** | Any LLM, 100+ plugins, many platforms | Hosted LLMs only, on Virtuals' servers | | **Self-hostable** | Yes, MIT, fully | No, GAME inference is centralised | | **Cost and value** | Free framework, token near zero | Fees on launches and trades, agent-token risk | | **Standout** | Widely used open framework | Tokenised-agent launchpad plus ACP | | **Main annoyance** | Value doesn't reach the token, company wind-down | Speculation-led, most graduated agents now dead | **If you're using it:** ElizaOS if you are a developer who wants full control and self-hosting, Virtuals if you want to launch or trade a tokenised agent. **If you're holding it:** neither token captures the product's value cleanly, which the next section unpacks. ## What would each need to score highly? Both projects sit in the agent quadrant of the OYM dual-score system. Neither is in Quadrant A. Here's what would actually move them. ### Eliza's path 1. **Ship binding on-chain governance.** Token holders need to vote, and votes need to bind. The supply expansion would not have passed an on-chain vote at the prices token holders paid before the migration. That's exactly why it should have been one. 2. **Give the token a reason to exist.** Either ship the L1 with ELIZAOS as native gas, or formalise auto.fun fee accrual to holders, or run a buy-and-burn funded by platform revenue. The current state, where you can use the codebase for free and ignore the token, is sustainable for the open-source product and fatal for the token. 3. **Patch the Princeton memory injection vulnerability.** Researchers demonstrated that attackers can poison agent memory via social media interactions; Eliza Labs' public response was "no direct updates were made." For agents that handle financial transactions, that's not a position you can hold while asking institutions to take you seriously. Ship all three and ELIZAOS plausibly clears 60 on Returns and 65 on Freedom, within range of Quadrant A. Ship none and the token stays a speculative sidecar to a good open-source product. The open question is whether Eliza Labs prioritises the token or stays focused on the codebase, where most of their traction lives. ### Virtuals' path 1. **Open-source or decentralise the GAME engine.** This is the single biggest freedom deficit on the platform. As long as inference for every agent runs on Virtuals' servers, the team is the platform and the token is a derivative on a hosted product. A permissionless inference network, or a hybrid where third parties run GAME nodes, would transform the centralisation profile. 2. **Demonstrate cycle-independent revenue.** The ~$75M in cumulative fees (DeFiLlama) is on the books. The 97% peak-to-trough collapse is on the books too. The Revenue Network and the Eastworld Labs robotics vertical are bets on broadening revenue beyond agent-launchpad fees. If the next downturn doesn't produce another 97% collapse, the case for VIRTUAL gets fundamentally stronger. If it does, the fee base that funds the protocol shrinks with it. 3. **Move agent data to decentralised storage.** Personality, memory, voice models and visual assets all live on Virtuals' servers. "Owning" an agent currently means owning a token that points at IP held by a platform. Migrating that data to IPFS, Arweave or similar would give creators ownership of the underlying assets, which is the actual sovereignty pitch. Ship all three and VIRTUAL clears 65 on Freedom while holding above 65 on Returns. The realistic trajectory, given the team's iteration cadence, is incremental: Unicorn launch system, buyback-and-burn, Revenue Network, multi-chain expansion. None of those yet addresses the centralised inference engine, which is the dimension doing the work in the Freedom score. ## The structural pattern: why this trade-off keeps appearing The agent-token category produces the same shape of trade-off over and over. Open-source frameworks earn developer mindshare and don't need tokens to do it; the LangChain pattern wins on adoption. Tokenised platforms earn fee revenue and need centralised infrastructure to function, because permissionless inference at production latency isn't solved yet. Pick one side or the other and you get half the picture. [Morpheus](https://ownyourmind.ai/projects/morpheus/) is the closest project to a third path: a permissionless compute marketplace that pays for inference through a token-native mechanism, with the work itself done by independent providers. It sits outside the agent category proper, yet it shows the architecture the agent category would need to borrow from to escape the trade-off. Until that matures, or until Virtuals or a competitor ships something equivalent, the agent-token space will keep producing pairs like ElizaOS and Virtuals: one project with the code but no token thesis, one with the token thesis but a centralised inference engine, both losing market value in lockstep with whatever narrative cycle is currently driving fee revenue. Same category, opposite trade-offs, both far below their peaks. The asymmetry is the shape of the agent-token space until something changes, not a quirk of these two projects. ## Score change log ### 2026-10-07: Data refresh - Virtuals figures moved to fees after DeFiLlama split creator payouts out of revenue: ~$75M cumulative fees, ~$42M kept by the protocol, trailing year ~$16M. No scores changed. ### 2026-09-24: Data refresh - ELIZAOS drawdown corrected from roughly 90% to more than 99%, GitHub counts refreshed, the stale ELIZAOS dimension scores (now 4/20 and 2/20) and Virtuals trailing revenue updated, and the registry's single-EOA upgrade control stated from our integrity finding. No scores changed. ### 2026-07-06: Product view added - Added a "Using them: the product side by side" table synthesising the ElizaOS and Virtuals product-in-practice sections (per `specs/product-comparison-framework.md`), with a using-vs-holding split. No scores changed.