ConceptioArchivearXiv CS
arXiv CSopen access

ClawCoin: An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

Unknown · 2026 · arxiv_cs
arXiv CS · Papers · License: Open Access · 2026
Open Source ↗Direct PDF ↓
cryptographycybersecurityprivacysecurity
cryptography, security, privacy, cybersecurity

ClawCoin: An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies Shaoyu Li

Chaoyu Zhang

Hexuan Yu

Y. Thomas Hou

Wenjing Lou

[email protected] Virginia Tech Virginia, USA

[email protected] Virginia Tech Virginia, USA

[email protected] Virginia Tech Virginia, USA

[email protected] Virginia Tech Virginia, USA

[email protected] Virginia Tech Virginia, USA

arXiv:2604.19026v1 [cs.MA] 21 Apr 2026

Abstract Autonomous AI agents live or die by the API tokens they consume: without paid inference capacity they cannot reason, act, or delegate. This compute-token cost has become the binding resource of the emerging agent economy, yet it is structurally non-transferable: it is account-bound, vendor-specific, and absent from any on-chain ledger. Recent agent payment rails such as x402 and agent-to-agent wire formats move fiat-backed value between agents, but they do not represent the quantity agents actually burn. The result is a substrate where agents can transport purchasing power but cannot quote, escrow, or settle workflows in a unit aligned with their dominant cost. We present ClawCoin, a tokenized, compute-cost-indexed unit of account and settlement asset for decentralized agent economies. ClawCoin turns the non-transferable cost of compute into a portable, composable, contract-readable primitive through four layers: (i) a robust basket index over standardized (model, vendor) prices, with smoothing and bounded per-epoch drift; (ii) an oracle that publishes signed, fresh attestations under an explicit trust model; (iii) a NAV-based mint/redeem vault with coverage thresholds, rate limits, and auto-pause; and (iv) an on-chain settlement layer that atomically clears multi-hop agent delegations against compute-aligned budgets. We formalize the adversary, state bounded guarantees for index integrity, NAV faithfulness, redeemability under stress, and liveness, and walk through the principal attack scenarios. We implement a prototype on an Ethereum-compatible L2 and evaluate it using a multi-agent simulator and the OpenClaw testbed, a six-role containerized agent system that shares one inference endpoint across settlement backends. Across single-agent, multiagent, workflow, and resource-procurement experiments, ClawCoin stabilizes execution capacity under cost shocks, collapses crossagent quote dispersion, eliminates partial settlements in multi-hop delegation, and sustains cooperative market dynamics that fiatdenominated baselines cannot. Risk sanity checks confirm that the vault’s staleness, drift, and coverage defenses behave as specified. The results argue that a security-engineered, compute-indexed unit of account is the missing representation primitive for decentralized agent coordination.

1

Introduction

Tokens are the lifeblood of an autonomous AI agent. Every plan an agent makes, every tool it calls, and every subtask it delegates is paid for in model and API tokens. Without them, an agent cannot think and cannot act. This is not a metaphor: the industry has converged on tokens as the literal unit in which agent work is priced and budgeted. NVIDIA now frames data centers as “token factories” and tokens-per-watt as a CEO-level KPI [29, 30]; major AI organizations

measure engineer productivity in tokens consumed and grant token budgets as compensation [37]; analysts forecast token sales as the dominant revenue line of frontier AI infrastructure [30]. The agent economy already has a value anchor, namely the cost of the API tokens that keep agents alive, and that anchor is rapidly becoming the unit in which the rest of the AI industry is measured. And yet that anchor is not on-chain, not transferable, and not tradable. API tokens are account-bound: inference quotas cannot be handed between agents, subscriptions cannot be subdivided across delegated subtasks, and prepaid balances cannot cross vendors. The payment side has moved in the opposite direction. Coinbase’s x402 [42] has wired stablecoin settlement directly into HTTP and processed millions of agent-to-agent transactions within months of launch [43]; agent-to-agent wire formats [1] and agentpayment platforms [2, 12] are following close behind. The rails for agent-native commerce now exist. What does not exist is an agentnative unit of value to move on those rails. Stablecoins [10, 26] efficiently transport fiat purchasing power but say nothing about the resource that actually constrains an agent, namely the compute it must burn to keep operating. Stablecoins solve transport. They do not solve representation: in what unit should an agent quote, budget, escrow, and settle, when its dominant recurring cost is compute? This paper therefore takes the next step: if tokens are the value anchor, tokenize them. We tokenize the computecost surface itself by publishing an on-chain, transparent index of what it costs to operate the models agents actually use, and minting a token whose net asset value (NAV) tracks that index. Once the anchor is on-chain, the key properties follow: agents read the same NAV, so quotes are directly comparable in compute units; smart contracts can escrow, route, and rate-limit settlement against compute-aligned budgets that the contracts themselves can verify; multi-hop delegation chains can settle atomically against a single shared numeraire; and because the token is a redeemable claim against a transparent reserve, the value the agent moves is the value the agent burns. A natural alternative is to keep settlement in fiat-backed stablecoins and ask each agent to maintain a private internal cost index. This breaks down in decentralized settings. Per-agent indices are not a shared numeraire, so quotes from different agents cannot be compared without trusted middleware; internal accounting cannot be referenced inside smart contracts, so multi-hop delegation cannot be atomically constrained by a compute-aligned budget; and opaque per-agent indices are not auditable or composable with other on-chain primitives. A genuinely shared numeraire for compute-bound agents has to live on-chain.

Li et al.

We present ClawCoin, a collateral-backed, index-linked tokenized unit of account and settlement asset. ClawCoin is deliberately not a generic stablecoin, a speculative asset, or a direct claim on physical compute: it is a redeemable financial claim whose NAV tracks a transparent compute cost basket and whose token form supplies the portability, composability, and atomic settlement properties that private accounting cannot. The economic intuition is closer to an index-linked note (an inflation-protected claim tracking a published basket) than to a fiat peg; the systems intuition is that exposing a compute-aligned unit at the smart-contract layer lets agents quote, escrow, delegate, and settle in the unit their operations actually consume. Realizing this in a decentralized, adversarial environment is nontrivial. Prices are observed through heterogeneous vendor schedules with hidden discounts and the possibility of strategic repricing once inclusion becomes economically meaningful. The on-chain index feeds mint/redeem logic, so any oracle compromise propagates into the value of every outstanding token. NAV-based semantics shift reserve liabilities upward whenever the index rises, exposing the vault to redemption stress. And the settlement layer is itself a target for maximal extractable value (MEV) around oracle updates and for governance capture. A credible design must make its threat model, trust assumptions, and security properties explicit. Contributions. In summary, this paper makes the following contributions: • The representation argument. We articulate the value-anchor argument for the agent economy (API tokens are what agents must consume to exist, so the unit of account should track that cost) and show that internal indexing over stablecoin rails cannot supply this primitive in decentralized coordination. • Protocol design. We design a four-layer protocol: a robust basket index with bounded per-epoch drift, a committee or DON oracle with signed attestations, a NAV-based mint or redeem vault with reserve coverage and rate-limit risk controls, and an on-chain atomic multi-hop settlement layer. The protocol is specified as two compact algorithms. • Security analysis. Against a bounded adversary controlling a vendor minority, an oracle minority, mint/redeem-time MEV, and governance proposals, we state bounded guarantees for index integrity, NAV faithfulness, redeemability under stress, and liveness, and walk through the principal attack scenarios. • Prototype and evaluation. We implement ClawCoin on an Ethereum-compatible L2, build a multi-agent simulator, and deploy a six-role containerized agent testbed (OpenClaw) in which the same workflow executes under three settlement backends. Results across single-agent stability, cross-agent coordination, multi-hop workflows, long-horizon economy survival, and external resource procurement show that ClawCoin dominates fiat and internal-indexing baselines on every axis that cross-agent coordination exposes. The broader claim is simple: the agent economy already has a value anchor and is rapidly acquiring payment rails on which agents can trade. What is missing is the bridge between them: an on-chain, tokenized representation of that anchor that agents can actually

move, escrow, and settle in. ClawCoin is a concrete, decentralized, and security-engineered step toward that bridge.

2

Background and Related Work

ClawCoin sits at the intersection of agent-economy infrastructure, stablecoin and oracle systems, tokenized index-linked claims, and decentralized multi-agent coordination.

2.1

Agent Economies and Multi-Agent Coordination

Recent work argues that autonomous software will increasingly need wallets, identities, and machine-to-machine settlement to act as economic participants [35, 44]. Payment specifications such as x402 [42] and A2A [1] standardize quote and pay primitives at the application layer, and multi-agent frameworks [23, 31, 41] provide the orchestration substrate on top of which compute-aligned settlement is needed. Compute-resource markets such as Akash [3], Filecoin [17], and Bittensor [5] tokenize a related but distinct quantity, namely supply of physical compute or storage. AI-adjacent tokens used for access, governance, or emissions bootstrap participation but, absent an external anchor, do not provide a cost-grounded shared numeraire. This literature answers the transport question. ClawCoin addresses the orthogonal representation question: in what unit should compute-bound budgets, prices, and treasuries be denominated when settlement is decentralized.

2.2

Stablecoins, Index-Linked Claims, and Tokenized RWAs

The stablecoin literature analyzes reserve quality, arbitrage design, and peg fragility under stress [10, 20, 26]. The Terra/UST collapse [11, 25], Iron Finance’s death spiral [22], and the 2023 USDC depeg [39] show that algorithmic stabilization and reserve-custody exposure can cascade catastrophically; these episodes motivate ClawCoin’s transparent collateral-backed structure with explicit risk controls over a purely algorithmic peg. Classical work on index-linked securities [19] and inflationprotected sovereign bonds (TIPS [36]) show that basket-based instruments can carry meaningful claims without a single nominal peg. ETF arbitrage [32] is the closest financial analogy to ClawCoin’s mint/redeem pricing, and tokenized real-world asset designs [6, 18] demonstrate on-chain claims whose value derives from external indices. ClawCoin adapts this design family to a new reference, namely a basket of standardized inference costs, and supplies the systems-security machinery required when that basket is published by an oracle protocol rather than tracked by traditional custodians.

2.3

Oracles, MEV, and DeFi Risk Controls

Oracle networks [7, 33, 38] convert off-chain observations into onchain references under threshold-committee or optimistic-dispute trust models. Oracle compromise is one of the most consequential DeFi attack surfaces: Mango [28], Cream [13], bZx [8], and Harvest [21] all suffered manipulation-driven losses, and surveys [9, 15] catalog the standard defenses (multi-source aggregation, smoothing,

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

deviation thresholds, freshness gates) that directly inform ClawCoin’s index pipeline (Section 4). The broader DeFi literature [40, 45] surveys collateral, liquidity, and risk-control patterns; MEV analyses [14, 34] motivate ClawCoin’s per-epoch caps and drift bounds; and mature protocols [24, 27] expose the rate-limit and pause patterns that ClawCoin’s risk module adapts to an index-linked NAV in which liabilities are themselves dynamic. Governance attacks [4, 16] motivate the narrow, timelocked governance surface.

2.4

Positioning

Table 1 situates ClawCoin among adjacent system categories. The novelty is not a new payment rail, not a new utility token, and not a new compute auction. It is a security-engineered, on-chain, indexlinked unit of account that closes the representation gap between machine-native cost and decentralized agent settlement.

3

System Model, Threat Model, and Design Overview 3.1 Economic Setting We consider a population of autonomous agents that continuously request, execute, and settle compute-intensive tasks. Each agent acts as both service consumer and producer, and may delegate subtasks along multi-hop chains that must settle as a single coherent workflow. The defining feature of this economy is what participants must spend to keep existing: API tokens consumed for model inference and metered tool invocations. An agent without a paid-up token budget cannot reason, cannot act, and is for practical purposes offline. That cost is the natural value anchor of the agent economy. Formally, each agent 𝑖 maintains a treasury 𝑇𝑖,𝑡 denominated in the prevailing accounting unit, evolving as 𝑇𝑖,𝑡 +1 = 𝑇𝑖,𝑡 + 𝑅𝑖,𝑡 − 𝐾𝑖,𝑡 ,

(1)

with revenue 𝑅𝑖,𝑡 and operating cost 𝐾𝑖,𝑡 . Equation 1 is identical across regimes; what differs is the informational content of 𝑇𝑖,𝑡 once a unit is fixed. Define execution capacity 𝐸𝑖,𝑡 as the amount of standardized computational work a treasury can fund. Under fiat denomination, 𝐸𝑖,𝑡 depends on both 𝑇𝑖,𝑡 and the time-varying compute price, so the same nominal balance corresponds to different amounts of executable work over time. The system goal of ClawCoin is to make execution capacity a stable, observable, and contract-readable quantity.

3.2

Why Tokenization Is Necessary

The argument has two steps, both required. First, anchor the unit to what agents consume: a unit of account that agents quote, escrow, and settle in should track the cost that determines whether they can keep operating. Fiat purchasing power does not; the same USDC balance buys different amounts of inference over time, and no contract-level check can assert “this escrow funds the workflow” as compute prices move. Second, put the anchor on a tradable on-chain rail. API tokens are account-bound and non-transferable; private internal indices are invisible to counterparties and smart contracts. To obtain the properties that justify the design (shared numeraire, atomic multi-hop settlement, contract-enforced compute-aligned

budgets, and auditability), the anchor must be wrapped as a tokenized claim living in the same composable substrate (x402 [42], A2A [1]) on which agents already transact. Three baselines make the argument concrete. (A) Per-agent internal indexing with USDC settlement: each agent computes its own cost index privately and converts at pay time. This performs Step 1 privately but skips Step 2 entirely; quotes from heterogeneous agents are incomparable without trusted middleware, smart contracts cannot enforce compute-aligned budgets, and multi-hop chains cannot atomically commit against a shared budget. (B) Centralized accounting service: a trusted operator publishes indices and settles off-chain, introducing a single point of failure for liveness, censorship, and bookkeeping; it performs Step 1 publicly but only partially realizes Step 2. (C) On-chain index-linked tokenized claim (ClawCoin): the index is published on-chain by an oracle protocol, and a token whose NAV is defined by the index routes through standard transfer logic. All agents read the same NAV, quotes are directly comparable, delegation chains settle as a single atomic transaction, and index updates, mint/redeem, and reserve state are observable, with risk controls enforced by code. This is the only baseline that performs both steps. We do not claim tokenization is the only design that exposes a compute-aligned unit; we claim it is the minimal primitive that simultaneously provides a shared numeraire, composability, atomic multi-hop settlement, and auditability when no common operator is trusted.

3.3

Threat Model

Participants. An oracle protocol (either a 𝑘-of-𝑛 threshold committee or a decentralized oracle network, DON) publishes the index on-chain; a vault contract holds reserve collateral and exposes mint and redeem; a risk-control module enforces coverage, throttles, drift caps, and pause logic; governance updates the basket, vendor registry, and parameters under timelock; agents quote, transact, and settle in ClawCoin. Adversary. A polynomial-time A may: control up to 𝑓 of 𝑛 vendor price endpoints (biased, stale, or withheld); compromise a strict minority of the oracle committee or, under the DON model, fewer reporters than the safety threshold; reorder, sandwich, or frontrun mint/redeem around oracle updates (MEV); submit governance proposals subject to voting and timelock; act as a strategic vendor adjusting public prices in response to basket inclusion; and trigger redemption rushes through multiple identities up to available liquidity. Trust assumptions. We assume an honest oracle threshold; a censorship-resistant base chain with bounded confirmation delay; at least 𝑛 − 𝑓 honest vendor endpoints with non-adversarial public postings; safe cryptographic primitives; and timelock and quorum rules that the adversary alone cannot bypass. Out of scope: physical compromise causing all vendors to collude on the same biased price; correlated regulatory shutdown of reserve custodians; basechain bugs or 51% attacks; off-chain leakage of nonpublic enterprise pricing. Security goals. We target four properties, formalized in Section 5. G1. Index integrity: the published index 𝐼¯𝑡 deviates from the honest index by an amount bounded by the adversary’s vendor share 𝑓 /𝑛 and the chosen robust estimator. G2. NAV faithfulness:

Li et al.

Table 1: Positioning ClawCoin relative to adjacent system categories. The right-most column explains why each category does not supply the compute-aligned, contract-readable unit of account that ClawCoin targets for decentralized agent coordination. Category

Primary function

Typical value anchor

Trust model

Why not equivalent to ClawCoin

Agent payment rail [1, 42]

Move value between agents and services

Fiat-backed collateral or network token

Stablecoin issuer or chain consensus

Utility token [5]

Gate access, staking, governance within a platform

Floating ecosystem-token market value

Platform operator + market

Fiat stablecoin [10, 20]

Low-volatility against fiat

1 USD peg

Issuer reserves + audits

Tokenized RWA [6, 18]

On-chain claim on external asset / index

External asset / index

Issuer custody + oracle

Compute market token [3, 17]

Price physical compute supply

Auction or staking

Provider network

ClawCoin

Quote, budget, settle in machine-native unit; atomic multi-hop settlement

Basket of standardized compute costs

Oracle protocol + collateral vault + risk module

Solves transport, not the unit of account; no computealigned representation. No external cost grounding; no shared numeraire across providers. Anchored to human purchasing power; not aligned with machine cost. Same financial family; ClawCoin specializes the index to compute and adds the oracle and risk modules of Section 4. Prices supply, not the cost agents pay; no shared cost numeraire. Targets compute-aligned operating cost with explicit security properties (G1) through (G4) for decentralized agent coordination.

settlement

the on-chain NAV deviates from the honest NAV by an amount bounded by staleness, smoothing, and the per-epoch drift cap. G3. Redeemability under stress: for index trajectories with per-epoch growth bounded by 𝛿 max , reserve coverage Γ𝑡 remains above 𝛾 min for at least 𝑇 epochs under replenishment rate 𝜌. G4. Liveness and freshness: honest updates are confirmed within bounded delay 𝜏 and consumers can detect violations and trigger fallbacks. We treat ClawCoin as a security-engineered substrate; full game-theoretic equilibrium properties are not targeted.

3.4

Design Overview

ClawCoin realizes both steps of Section 3.2 in five components separated by an explicit off-chain/on-chain trust boundary. Vendor data sources expose public prices for included (model, vendor) pairs. The off-chain index calculator fetches, validates, and aggregates observations into a basket value, applies smoothing and a per-epoch drift cap, and produces a signed attestation. The on-chain oracle publishes the attested value with timestamp, basket version, and a Merkle commitment to the underlying observations, enforcing freshness and writer authentication. The token and vault maintain supply, mint, and redeem against reserve collateral at the current NAV, and expose standard transfer semantics. The risk-control and governance module enforces coverage, mint throttling, auto-pause, drift caps, and basket/parameter updates under timelock. The chain verifies that a published value comes from an authorized oracle; its validity with respect to honest market prices depends on observable off-chain data and the published basket configuration. Section 4 makes each layer concrete; Section 5 states the security properties; Sections 6 through 7 evaluate the prototype, simulator, and the OpenClaw testbed.

4

ClawCoin Protocol Design

The design realizes the two-step argument of Section 3.2 as four protocol layers. (i) The cost index anchors the unit to the API-token costs that determine whether agents can keep operating; it is robust to adversarial vendor minorities and bounded in per-epoch movement. (ii) The oracle carries that anchor across the trust boundary onto the chain, with signed attestation, freshness, and writer authentication. (iii) The NAV-based vault turns the anchor into a redeemable, transferable token, with coverage thresholds and ratelimit controls protecting holders. (iv) The settlement layer exposes the property that justifies tokenization: agents quote, escrow, and atomically settle multi-hop delegations in the unit their operations consume, inside the same composable substrate as existing agent payment rails. Two algorithms summarize the protocol: Algorithm 1 for index publication and Algorithm 2 for vault state-changing operations. Notation. 𝑀 is the set of included models and 𝑉 (𝑚) the vendors |𝐾 | offering model 𝑚. 𝐾 = {(𝛼𝑘 , 𝛽𝑘 , 𝜃 𝑘 )}𝑘=1 is a vector of standardized workload classes with normalized input/output token counts 𝛼𝑘 , 𝛽𝑘 and basket-level weights 𝜃 𝑘 ≥ 0 summing to one. Vendors expose in out . We write 𝐼¯ per-token input and output prices 𝑃𝑚,𝑣,𝑡 and 𝑃𝑚,𝑣,𝑡 𝑡 for the smoothed, drift-capped index published on-chain, 𝐼 0 for its initialization, and NAV𝑡 = 𝐼¯𝑡 /𝐼 0 . Reserves are denominated in a fiat-backed collateral such as USDC.

4.1

Cost Index Construction

The index is a basket built in three stages: per-(model, vendor) cost over standardized workloads, robust per-model aggregation across

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

vendors, and a weighted basket smoothed and drift-capped before publication. Standardized workloads. Modern inference is priced by input and output tokens, but real workloads have heterogeneous shapes. We maintain a vector of workload classes and treat 𝜃 𝑘 as a basket (𝑘 ) in + mix. A class-𝑘 request on (𝑚, 𝑣) has nominal cost 𝐶𝑚,𝑣,𝑡 = 𝛼𝑘 𝑃𝑚,𝑣,𝑡 out 𝛽𝑘 𝑃𝑚,𝑣,𝑡 , and the per-pair basket-aware cost aggregates the mix: 𝐶𝑚,𝑣,𝑡 =

|𝐾 | ∑︁

in out  𝜃 𝑘 𝛼𝑘 𝑃𝑚,𝑣,𝑡 + 𝛽𝑘 𝑃𝑚,𝑣,𝑡 .

(2)

𝑘=1

Because 𝜃 𝑘 is a public governance parameter, the workload assumption is auditable and explicitly versioned. Robust per-model aggregation. A model is offered by multiple vendors at prices that differ across backends, contracts, and promotions. Let C𝑚,𝑡 = {𝐶𝑚,𝑣,𝑡 } 𝑣 ∈𝑉 (𝑚) and 𝑛𝑚 = |C𝑚,𝑡 |. The per-model robust cost 𝐶˜𝑚,𝑡 is selected by governance: med 𝐶˜𝑚,𝑡 = median(C𝑚,𝑡 ),

(3)

trim(𝑞) 𝐶˜𝑚,𝑡 = trimmedMean𝑞 (C𝑚,𝑡 ), (4)  mad ˜ 𝐶𝑚,𝑡 = mean 𝑐 ∈ C𝑚,𝑡 : |𝑐 − median(C𝑚,𝑡 )| ≤ 𝜅 · MAD(C𝑚,𝑡 ) , (5)

where MAD denotes the median absolute deviation. The default is the median: its 50% breakdown point yields the clean integrity bound of Section 5.1, so the worst-case deviation under 𝑓 < 𝑛𝑚 /2 adversarial vendors is determined by the spread of honest reports rather than by adversarial values. Trimmed mean trades robustness (𝑞 breakdown) for variance reduction; MAD-filtered mean retains 50% breakdown with tighter variance. Any model with 𝑛𝑚 < 𝑛 min is dropped for that epoch. Cross-model basket and bounded publication. With basket Í Í weights 𝑤𝑚 ≥ 0, 𝑚 𝑤𝑚 = 1, the raw index 𝐼𝑡 = 𝑚∈𝑀 𝑤𝑚𝐶˜𝑚,𝑡 is a compute analog of a price-weighted equity index; usage-weighted variants 𝑤𝑚 ∝ 𝑢𝑚 give capitalization-style analogs with the standard stability and responsiveness trade-off. We then apply an exponential moving average (EMA) and clip per-epoch movement:  𝐼ˆ𝑡 = 𝜆𝐼¯𝑡 −1 +(1−𝜆)𝐼𝑡 , 𝐼¯𝑡 = clip 𝐼ˆ𝑡 , (1−𝛿 max ) 𝐼¯𝑡 −1, (1+𝛿 max ) 𝐼¯𝑡 −1 . (6) 𝜆 controls convergence speed and 𝛿 max bounds per-epoch movement; clipped excess is absorbed in later epochs. These knobs mirror the rate-limit pattern of mature stablecoin and lending protocols, give the risk module a known upper bound on liability growth (used in Theorem 1), and define the publication channel that the on-chain oracle additionally enforces as defense-in-depth (Algorithm 1). The index tracks inference cost rather than model quality: embedding quality would require a continuously updated crossdomain notion of task utility and would create governance disputes over benchmark choice. We separate measurement from differentiation; quality is priced in markets through reputation, contracting, and observed outcomes.

4.2

Oracle Protocol

The oracle separates off-chain index computation from on-chain publication. Only the publication step is trusted by contracts; the

Algorithm 1 IndexPublication: off-chain computation and onchain publication at epoch 𝑡. Require: basket 𝑀, vendor sets {𝑉 (𝑚)}, workload classes 𝐾, weights {𝑤𝑚 }, smoothing 𝜆, drift cap 𝛿 max , robust estimator Agg, prior 𝐼¯𝑡 −1 , trust model T ∈ {committee, DON}, threshold 𝑘, max staleness 𝜏 // off-chain pipeline (each oracle node) 1: 𝑀 ★ ← ∅ 2: for each model 𝑚 ∈ 𝑀 do 3: C𝑚,𝑡 ← {𝐶𝑚,𝑣,𝑡 : 𝑣 ∈ 𝑉 (𝑚), fetch valid and not stale} ⊲ eq. 2 4: if |C𝑚,𝑡 | ≥ 𝑛 min then 5: 𝐶˜𝑚,𝑡 ← Agg(C𝑚,𝑡 ); 𝑀 ★ ← 𝑀 ★ ∪ {𝑚} 6: end if 7: end for 8: renormalize {𝑤𝑚 }𝑚∈𝑀 ★ to sum to one Í 9: 𝐼𝑡 ← 𝑚∈𝑀 ★ 𝑤𝑚𝐶˜𝑚,𝑡 ; compute 𝐼¯𝑡 via eq. 6 10: emit attestation 𝜎𝑡 = ( 𝐼¯𝑡 , 𝑡, basketVersion, ℎ𝑡 , nodeId, sig) // on-chain publication 11: if T = committee then combine 𝑘 matching attestations into 𝜎𝑡★; submit 12: (𝐼¯𝑡 , 𝑡, basketVersion, ℎ𝑡 , 𝜎𝑡★) 13: else 14: reporters submit 𝜎𝑡( 𝑗 ) ; aggregator commits 𝐼¯𝑡 ← median 𝑗 𝐼¯𝑡( 𝑗 ) 15: end if 16: on-chain checks: writer auth.; 𝑡 > 𝑡 on ; | 𝐼¯𝑡 − 𝐼¯on | ≤ 𝛿 max 𝐼¯on 17: if checks pass then update ( 𝐼¯on , 𝑡 on ) ← ( 𝐼¯𝑡 , 𝑡); emit IndexUpdated 18: else reject 19: end if 20: if now − 𝑡 on > 𝜏 then StalePause ← true 21: end if

computation step is auditable by anyone with access to the underlying public data. Each oracle node runs the off-chain pipeline of Section 4.1, packages an attestation 𝜎𝑡 = (𝐼¯𝑡 , 𝑡, basketVersion, ℎ𝑡 , nodeId, sig) where ℎ𝑡 is a Merkle root over its observation set, and submits it on-chain. The contract enforces writer authentication, monotonic timestamps, the per-epoch drift cap as defense-in-depth on equation 6, and maximum staleness 𝜏 beyond which the value is treated as stale and the risk module pauses mint and queues redeem. Two trust models swap behind the same on-chain interface. In the threshold-signature committee, a 𝑘-of-𝑛 committee with a BLS or Schnorr scheme produces a combined attestation accepted when 𝑘 honest nodes agree; the chain verifies one signature per epoch. In the decentralized oracle network, independent reporters submit attestations under an aggregator (e.g., Chainlink off-chain reporting [7]), and the aggregator commits the median of reports. The committee minimizes on-chain cost; the DON minimizes trust in any specific quorum. Both produce the same on-chain artifact.

4.3

Token, NAV, Vault, and Risk Controls

ClawCoin is an ERC-20-compatible token whose value semantics are set by the on-chain index. Define NAV𝑡 = 𝐼¯𝑡 /𝐼 0 , with NAV0 = 1.

Li et al.

A deposit of collateral 𝑥 receives 𝑀𝑡 (𝑥) = 𝑥/NAV𝑡

(7)

newly minted ClawCoin tokens, and burning 𝑦 tokens returns 𝑅𝑡 (𝑦) = 𝑦NAV𝑡 of collateral. With reserves 𝐴𝑡 and supply 𝑆𝑡 , the coverage ratio is Γ𝑡 = 𝐴𝑡 /(𝑆𝑡 · NAV𝑡 ), (8) enforced above 𝛾 min > 1 on every state-changing call. ClawCoin is thus an index-linked redeemable claim against a fiat-backed reserve, with liabilities that move with the index; closer in spirit to an ETF redemption mechanism with a cost-driven NAV than to a fixed-peg stablecoin. Four controls compose Algorithm 2’s pre-call check. Coverage gating: mint requires Γ𝑡 ≥ 𝛾 min post-application; redeem checks coverage, but, when violated, queues rather than reverts so the claim is preserved. Adaptive mint throttle: the per-epoch mint cap contracts with coverage headroom ℎ𝑡 = max(0, Γ𝑡 − 𝛾 min ) via 𝐶𝑡mint = 𝐶 0mint · min(1, ℎ𝑡 /ℎ★), so new issuance cannot eat the buffer that protects existing holders; the redeem cap 𝐶𝑡red = 𝐶 0red stays constant so redemption capacity is preserved under stress. Auto-pause: StalePause halts mint when the oracle is beyond 𝜏; Paused halts all state changes when Γ𝑡 < 𝛾 pause ≤ 𝛾 min . Defense-in-depth: the on-chain drift cap duplicates the off-chain bound of equation 6. Together, these shift shock absorption from holders onto the would-be minter.

4.4

Settlement Semantics

ClawCoin is a standard transferable token, and this subsection is the entire payoff of tokenizing the cost anchor: what trading the anchor actually looks like at the smart-contract layer. Agents quote services in ClawCoin and pay through ordinary transfers; because every agent reads the same NAV, quotes are directly comparable in compute units, eliminating the trusted middleware required by Baseline A in Section 3.2. The atomic multi-hop helper handles delegation chains. Given a vector of (recipient, amount) tuples, it performs all transfers in a single transaction; any revert (insufficient balance, exceeded budget, or a downstream subtask failure signaled by a participating contract) reverts the entire bundle. This is a thin construction over standard transfer logic that is unavailable in Baseline A, where each hop converts off-chain via a private index. An escrow contract holds ClawCoin per task and releases funds on a signed receipt from the executing agent or refunds on timeout, again as one atomic transaction. A workflow originator can additionally pre-commit a maximum ClawCoin budget 𝐵★ to the escrow, which rejects any subtask payment that would exceed the remaining budget at the current NAV, namely a contract-enforced, compute-aligned budget constraint that internal accounting cannot supply. ClawCoin coexists with fiat-backed stablecoins: the reserve is in USDC (or analogous collateral), and mint/redeem convert between USDC and ClawCoin at NAV. Hybrid agents hold USDC for outsidesystem payments and ClawCoin for compute-aligned coordination inside the agent economy. The resulting property set (shared NAV, atomic multi-hop settlement, contract-enforced budgets, auditable reserve, and risk state) is exactly what motivates moving the unit of account on-chain. A trusted off-chain service can replicate the first three properties under operator trust, but only an on-chain

Algorithm 2 VaultOperation: mint, redeem, and pre-call risk check. Require: op ∈ {Mint, Redeem} with amount 𝑧; oracle (𝐼¯𝑡 , 𝑡 on ); vault (𝐴𝑡 , 𝑆𝑡 ); risk parameters 𝛾 min, 𝛾 pause, 𝛿 max, 𝜏, base caps (𝐶 0mint, 𝐶 0red ), headroom ℎ★ // pre-call risk-control step 1: if now − 𝑡 on > 𝜏 then StalePause ← true 2: end if 3: NAV𝑡 ← 𝐼¯𝑡 /𝐼 0 ; Γ𝑡 ← 𝐴𝑡 /(𝑆𝑡 · NAV𝑡 ) 4: if Γ𝑡 < 𝛾 pause then Paused ← true; emit CoverageBreach 5: end if 6: ℎ𝑡 ← max(0, Γ𝑡 − 𝛾 min ); 𝐶𝑡mint ← 𝐶 0mint · min(1, ℎ𝑡 /ℎ★ ); 𝐶𝑡red ← 𝐶 0red ; reset epoch usage; drain pending-redeem queue under coverage and 𝐶𝑡red // state-changing op 7: if op = Mint then 8: if Paused or StalePause then revert 9: end if 10: Δ𝑆 ← 𝑧/NAV𝑡 11: if 𝑈𝑡mint + Δ𝑆 > 𝐶𝑡mint then revert ⊲ rate limit 12: end if 13: if (𝐴𝑡 + 𝑧)/((𝑆𝑡 + Δ𝑆)NAV𝑡 ) < 𝛾 min then revert ⊲ coverage 14: end if commit 𝐴𝑡 += 𝑧, 𝑆𝑡 += Δ𝑆, 𝑈𝑡mint += Δ𝑆; transfer Δ𝑆 15: ClawCoin; emit Minted 16: else ⊲ op = Redeem 17: if Paused or StalePause then enqueue (𝑧, caller); return 18: end if 19: Δ𝐴 ← 𝑧 · NAV𝑡 20: if 𝑈𝑡red + Δ𝐴 > 𝐶𝑡red or (𝑆𝑡 − 𝑧 > 0 and (𝐴𝑡 − Δ𝐴)/((𝑆𝑡 − 𝑧)NAV𝑡 ) < 𝛾 min ) then 21: enqueue (𝑧, caller); return ⊲ soft rate limit and coverage check 22: end if 23: burn 𝑧 ClawCoin; transfer Δ𝐴; commit 𝐴𝑡 −= Δ𝐴, 𝑆𝑡 −= 𝑧, 𝑈𝑡red += Δ𝐴; emit Redeemed 24: end if

implementation provides the fourth and the censorship-resistance that follows. Section 5 returns to this point and states what each layer guarantees against the adversary of Section 3.3.

5

Security Analysis

We analyze ClawCoin under the threat model of Section 3.3 and the design of Section 4. Section 5.1 states bounded-adversary properties for the four security goals (G1) through (G4); Section 5.2 walks through the principal attack scenarios; Section 5.3 lists what the design does not cover. Bounds depend on parameters chosen by governance; Section 7.4 estimates them empirically on the running prototype.

5.1

Bounded-Adversary Properties

honest denote the honest reference cost Index integrity (G1). Let 𝐶𝑚,𝑡 for model 𝑚 at epoch 𝑡 (the representative cost that would emerge

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

from prices honest vendors post) and let A control 𝑓 of 𝑛𝑚 vendors for model 𝑚. With the median estimator (equation 3) and 𝑓 < 𝑛𝑚 /2, per-model error is bounded by the spread of honest reports, independently of how extreme adversarial reports are. Lemma 1 (Median breakdown). If 𝑓 < 𝑛𝑚 /2, then for every adversarial strategy med honest 𝐶˜𝑚,𝑡 − 𝐶𝑚,𝑡 ≤

max 𝑣 ∈𝑉 honest (𝑚)

honest 𝐶𝑚,𝑣,𝑡 − 𝐶𝑚,𝑡 .

hon = max Proposition 1 (Index integrity). Let 𝜖𝑚 𝑣 ∈𝑉 honest (𝑚) honest |𝐶𝑚,𝑣,𝑡 − 𝐶𝑚,𝑡 | and assume 𝑓 < 𝑛𝑚 /2 for every active 𝑚. The raw Í hon . index satisfies |𝐼𝑡 − 𝐼𝑡honest | ≤ 𝑚∈𝑀 ★ 𝑤𝑚 𝜖𝑚

The trimmed mean has breakdown 𝑞 with a corresponding bound on residual adversarial contribution; MAD-filtered mean retains 50% breakdown and tightens tail sensitivity through 𝜅, with an adversary conforming to the median/MAD envelope biasing the estimate by at most 𝜅 · MAD. The threshold 𝑛 min guarantees breakdown for every active model. NAV faithfulness (G2). Let 𝐼𝑡★ be the index an honest oracle would publish and 𝜂𝑡 = 𝐼¯𝑡 −𝐼𝑡★ the publication deviation, bounded by whichever is smaller: the deviation any honest committee member would have produced, or the per-epoch drift cap 𝛿 max . Proposition 2 (NAV deviation bound). With smoothing 𝜆, drift cap 𝛿 max , and oracle staleness at most 𝜏, for any 𝜃 ∈ [𝑡, 𝑡 + 𝜏], ∞  𝐼★ 1 ∑︁ (1 − 𝜆)𝜆𝑠 |𝜂𝑡 −𝑠 | + 𝛿 max 𝐼¯𝑡 −1 + drift(𝜏) , NAV𝜃 − 𝜃 ≤ 𝐼0 𝐼 0 𝑠=0

where drift(𝜏) is the maximum honest movement of 𝐼 ★ over a window of length 𝜏. The bound decomposes into attenuated past publication errors via the EMA, the per-epoch drift cap, and the staleness-window movement of the honest index. Tightening 𝜆, 𝛿 max, 𝜏 reduces NAV deviation at the cost of responsiveness or liveness: these are the knobs exposed to governance. Because the on-chain drift cap duplicates the off-chain bound, even a single-epoch majority compromise of the committee cannot exceed 𝛿 max in one step. Redeemability under stress (G3). Let 𝑔𝑡 = 𝐼¯𝑡 /𝐼¯𝑡 −1 − 1, so |𝑔𝑡 | ≤ 𝛿 max . Let 𝜌 ≥ 0 be a reserve replenishment rate (𝐴𝑡 +1 ≥ 𝐴𝑡 (1 + 𝜌) when mint and redeem are net zero). Algorithm 2 allows mint only while post-application coverage ≥ 𝛾 min . Lemma 2 (Bounded coverage decay). Holding supply constant and ignoring redemption, Γ𝑡 +1 ≥ Γ𝑡 (1 + 𝜌)/(1 + 𝛿 max ). If 𝜌 ≥ 𝛿 max then coverage is non-decreasing. Theorem 1 (Solvency under bounded stress). With Γ0 ≥ 𝛾 min , per-epoch index growth bounded by 𝛿 max , replenishment rate 𝜌, and the redemption queue processed under Algorithm 2, Γ𝑡 ≥ 𝑡 Γ0 (1 + 𝜌)/(1 + 𝛿 max ) . For any horizon 𝑇 , Γ𝑇 ≥ 𝛾 min provided 𝜌 ≥ (1 + 𝛿 max ) (𝛾 min /Γ0 ) 1/𝑇 − 1, which becomes 𝜌 ≥ 𝛿 max in the limit Γ0 → 𝛾 min . A deployable ClawCoin must either start with substantial headroom Γ0 ≫ 𝛾 min or adopt a yield-bearing reserve policy with 𝜌 ≳

𝛿 max ; this is the same balance-sheet constraint familiar from indexlinked liabilities, and is why ClawCoin is presented as collateralbacked rather than algorithmically stabilized. A coordinated redemption rush is bounded by 𝐶𝑡red and the coverage check; queueing converts a rush into bounded FIFO outflows and avoids the bank-run dynamic of unbounded redemption while preserving the claim. Liveness and freshness (G4). The oracle protocol admits any honest update within one confirmation and rejects updates older than 𝜏 through the staleness gate. Consumers read both 𝐼¯𝑡 and 𝑡 on and detect violations directly. When StalePause fires, mint reverts and redeem is queued: the protocol trades temporary mint capacity for refusal to act on untrusted state. Under base-chain censorship resistance, an honest quorum can always re-establish freshness.

5.2

Adversarial Scenarios and Defenses

S1. Stale or delayed oracle data. The adversary delays submissions. The staleness gate 𝜏 triggers StalePause, halting mint and queueing redeem; honest reporters recover by submitting a fresh attestation. During the pause, agents cannot mint: the protocol prefers refusal to action under an untrusted state. S2. Manipulated price inputs and Sybil vendors. The adversary controls 𝑓 endpoints and posts biased prices. The median (Lemma 1) tolerates 𝑓 < 𝑛𝑚 /2 with bounded error; 𝑛 min excludes models with insufficient honest sources; ℎ𝑡 in 𝜎𝑡 enables ex-post audit. Sybil addition is restricted by the governance-controlled vendor registry. A coordinated posting that mimics honest dispersion can shift the median within the honest envelope; this residual is bounded by Proposition 1. S3. Strategic provider repricing. A vendor with strong basket weight changes its public price to influence the index (analogous to benchmark-inclusion gaming). Smoothing and the drift cap attenuate single-vendor moves; governance can rebalance weights or remove the vendor under a timelock. Repeated small adjustments within the cap can still influence the long-run index; the design exposes this as a parameter rather than hiding it. S4. Mint/redeem MEV. An adversary front-runs the oracle update transaction with a redeem (when the index is about to fall) or mint (when it is about to rise) and back-runs with the inverse. 𝛿 max bounds per-epoch sandwich profit; per-epoch mint and redeem caps bound any single attacker’s turn; optional commit/reveal of oracle updates and per-block rate limits further reduce extractable value. Small per-epoch arbitrage is unavoidable in a fully transparent system; this is a bounded tax rather than an exploit. S5. Redemption rush under index spike. A coordinated wave of redeem calls follows a permitted index increase. The coverage check and per-epoch redeem cap convert the rush into bounded outflows; FIFO queueing preserves the ordering; Theorem 1 bounds when Γ𝑡 stays above 𝛾 min . If index growth persistently exceeds replenishment, queued redemptions extend; auto-pause and governance pause provide the explicit fallback. S6. Governance capture or proposal griefing. Malicious basket or parameter changes, or a flooded proposal queue. The timelock delays application, allowing observation and counter-action; quorum and voting rules require the attacker to share above the safety

Li et al.

threshold; the emergency pause is held under a multisig. Longhorizon governance attacks remain a known risk class; the design minimizes the governance surface rather than expanding it. S7. Hidden enterprise discounts (modeling gap). Public list prices may overstate realized cost for some agents. The index is by construction over public prices; deviation is observable as a gap between the published index and realized expenditure, which agents can price into quotes. This residual reflects the protocol’s choice to track a transparent but imperfect proxy.

5.3

Out of Scope

ClawCoin does not defend against: compromise of a vendor majority (𝑓 ≥ 𝑛/2 defeats any breakdown bound, and no robust aggregator can recover a faithful price from majority-adversarial inputs); correlated regulatory shutdown of reserve custodians; bugs in the base chain or threshold-signature library; long-horizon coordinated governance capture above the quorum; or off-chain coercion of agents. These are system-level limitations (Section 8). The composition of (G1) through (G4) is what justifies the on-chain tokenized design over the internal-indexing baseline of Section 3.2: each property is enforced by code in a specific layer, with parameters that are visible and tunable by governance and with empirical bounds estimated in Section 7.

6

Prototype and Implementation

We instantiate the protocol of Section 4 as a deployable prototype on a local Ethereum-compatible network, with an off-chain index calculator and a multi-agent client layer. The prototype is deliberately minimal: it implements the security-relevant logic (NAV-based mint/redeem, coverage check, oracle freshness, mint throttle, pause) and omits ancillary features such as cross-chain bridging, leveraged positions, or multi-collateral support.

6.1

Smart Contract Stack

The smart-contract stack comprises five contracts with disjoint responsibilities. IndexOracle stores 𝐼¯𝑡 , 𝑡 on , the active basket version, and ℎ𝑡 ; it exposes a writer-authenticated update that rejects backdated, drift-violating, or unauthorized submissions, a read accessor, and isStale(𝜏). ClawCoinToken is an ERC-20-compatible token whose mint/burn hooks are restricted to the vault; standard transfer, allowance, and DeFi composability work through the unmodified interface. MintRedeemVault implements Algorithm 2: it holds reserve collateral, tracks per-epoch cap usage, maintains the pending-redeem queue, reads 𝐼¯𝑡 from the oracle, and consults the risk manager for caps and pause flags. RiskManager stores 𝛾 min, 𝛾 pause, 𝛿 max, 𝜏, base caps, and ℎ★, holds the pause flags, and is invoked as the precondition check. Governance manages the basket, workload weights, oracle membership, and risk parameters under a timelock with explicit minimum delay, and holds the emergency pause under a separate multisig. The chain trusts writer authentication, coverage, and rate-limit enforcement, and timelock invariants; it does not trust the correctness of 𝐼¯𝑡 with respect to off-chain markets (auditable via ℎ𝑡 ) or the absence of MEV in the surrounding chain (handled by per-epoch caps, drift cap, and optional commit/reveal updates).

6.2

Off-Chain Index Calculator

Each oracle node runs Algorithm 1. Versioned per-vendor adapters in , 𝑃 out ); prices are normalize public price schedules into (𝑃𝑚,𝑣,𝑡 𝑚,𝑣,𝑡 fetched in parallel with timeouts, retries, and freshness timestamps; per-pair cost follows equation 2; robust per-model aggregation (equations 3 through 5) is gated by 𝑛 min ; the basket, EMA, and driftcapped publication follow equation 6. Before submission, the node builds a Merkle tree over observations, signs 𝜎𝑡 , and dispatches it to the on-chain oracle (committee path) or the aggregator (DON path). Vendor adapters follow the same timelocked governance path as basket changes; periodic replay jobs reconstruct the index from stored roots for third-party audit.

6.3

Deployment Target

We target an Ethereum L2. Multi-hop delegation requires many small-value sub-second transfers, for which L2 per-transaction costs make the atomic settlement primitive practical; ERC-20 and standard signature verification keep the prototype surface area on widely audited libraries; and L2s host the same DeFi primitives (escrow, AMMs, lending) that hybrid ClawCoin/USDC agents may use. The protocol is otherwise chain-agnostic: the security analysis does not depend on a specific execution environment beyond a censorship-resistant base chain.

6.4

OpenClaw Integration

We integrate ClawCoin with OpenClaw, a multi-agent system in which collaborating agents quote, execute, and delegate computeintensive subtasks over a shared messaging bus. OpenClaw is described and evaluated separately; here we state only the integration interface. Each agent is provisioned with an EOA and a ClawCoin balance; its protocol-level identity is its address, and signed messages bind off-chain quotes and receipts to on-chain settlement. OpenClaw exposes a pluggable settlement interface with three backends. usdc-fiat quotes and pays in USDC with fiat denominated budgets (the Fiat baseline). usdc-internal-index quotes and pays in USDC but lets each agent maintain a private compute cost index and convert at quote time (the USDC + internal-indexing baseline of Section 3.2). clawcoin quotes, pays, and settles in ClawCoin, using the atomic multi-hop helper for delegation chains and the escrow contract for asynchronous execution. Because the same workflow, policies, and task graph are replayed under each backend with no change to agent logic, the regime comparison is clean. Under clawcoin, an orchestrator gathers ClawCoin-denominated quotes, selects executors subject to a pre-committed ClawCoin budget, locks the budget in escrow, dispatches subtasks, and on receipt of signed completions releases payment via the atomic bundle, with the entire chain committing or reverting together.

7

Evaluation

ClawCoin is presented as a compute-cost-aligned unit of account for decentralized agent economies, and the evaluation is organized around that claim. Section 7.1 describes the prototype, simulator, and OpenClaw testbed. Section 7.2 reports single-agent stability, pricing, and market-feasibility properties under four monetary regimes. Section 7.3 is the main result: multi-agent workflows, long-horizon economy survival, and external resource procurement

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

7.1

Setup and OpenClaw Testbed

On-chain prototype. The five-contract stack of Section 6.1 runs on a local Ethereum-compatible development network. The off-chain calculator of Section 6.2 runs against synthetic vendor adapters whose price trajectories are controllable from the simulator, so the same trajectory replays across regimes. Multi-agent simulator. A market simulator drives task arrivals, quoting, execution, and settlement under a chosen regime; provider costs evolve through stochastic fluctuations and discrete repricing shocks. Each agent maintains a treasury, provider mix, markup policy, and quoting rule, and may participate in delegation chains. OpenClaw testbed. For workflow-level experiments we deploy OpenClaw on a dedicated hardware testbed. Each OpenClaw agent runs in its own Docker container on a single x86 host; each container holds exactly one agent with its wallet, settlement adapter, role-specific prompt and tooling, and a local SQLite store. Interagent communication uses a shared message bus. The host has no GPU: inference is provided by a separate server with four NVIDIA RTX 6000 Pro GPUs (96 GB VRAM) running an OpenAI-compatible endpoint that serves GLM-4.7 Flash. All agents issue completions through this single endpoint, so the cognitive layer is held constant across regimes and only the settlement backend changes between runs. OpenClaw agent roles. We instantiate six roles: a planner decomposes tasks, quotes, and orchestrates delegation; a retriever performs structured search over local/remote indices; a tool-use agent invokes external APIs and sandboxes; a coder runs short programs against a Python sandbox; a verifier grades artifacts against acceptance criteria; and a synthesizer merges retrieved evidence and tool outputs into the final response. Each role binds a fixed prompt, tool whitelist, context window, and published per-call ClawCoin price quote signed along with completion receipts. Roles are otherwise homogeneous: same GLM-4.7 Flash backend, same wallet/identity primitives, same adapter interface. Settlement backends and regimes. The OpenClaw runtime exposes usdc-fiat, usdc-internal-index, and clawcoin (Section 6.4). For simulator experiments we compare four regimes: Fiat (USDC), Raw-cost (quotes track instantaneous provider-specific prices without a shared numeraire), USDC + internal indexing (per-agent private index, Baseline A of Section 3.2), and ClawCoin. Metrics group into stability (capacity variance, drawdown, recovery, CoV), coordination (quote volatility, repricing frequency, cross-agent dispersion, price consistency), market/workflow feasibility (acceptance/completion, budget-overrun, partial-settlement, latency), and risk checks (oracle-staleness, vendor-manipulation, redemption-burst).

7.2

Single-Agent Stability, Pricing, and Market Feasibility

We first verify in the simulator that ClawCoin stabilizes per-agent budgets, reduces pricing friction across heterogeneous agents, and

Fiat Regime Raw-Cost Regime ClawCoin Regime

1100

Execution Capacity

on the OpenClaw testbed, where the value of moving the unit of account on-chain is most visible. Section 7.4 compresses the adversarial and solvency tests into three minimal sanity checks confirming that the risk module behaves as specified.

1000 900 800 700 0

10

20

30

Time Step

40

50

60

Figure 1: Execution capacity of a fixed nominal treasury under dynamic compute costs. Fiat and raw-cost accounting suffer substantial purchasing-power instability after shocks; ClawCoin preserves stable capacity through index-linked denomination. Table 2: Single-agent execution capacity under compute-cost shocks. Capacity normalized so that the noise-free reference treasury equals 1000. Regime

Mean

Var.

Drawdown

Recov.

CoV

Fiat Raw-cost USDC + internal ClawCoin

918 884 987 1000

12,840 17,310 1,840 320

24.7% 31.5% 6.8% 1.9%

19 24 6 1

0.124 0.149 0.043 0.018

improves market feasibility under explicit budget constraints. These are properties that internal indexing can partially recover per-agent; the multi-agent results of Section 7.3 then expose what internal indexing cannot do. Execution capacity. A representative agent is endowed with a fixed nominal treasury under each regime, and at each step, we measure the standardized computational work the treasury can fund as the underlying compute index 𝐼¯𝑡 moves through stochastic fluctuations and discrete shocks. Figure 1 and Table 2 tell a single qualitative story: ClawCoin holds machine purchasing power essentially constant by construction; USDC + internal indexing recovers most of the per-agent stability because the agent privately reprices against its own basket; Fiat and Raw-cost both suffer large drawdowns and slow recovery because their nominal balances do not move with the cost they must pay. The gap between internal indexing and ClawCoin is small in the single-agent view and widens sharply once coordination enters. Pricing stability and repricing overhead. A market of heterogeneous service-providing agents quotes a standardized request under common cost shocks; agents differ in provider mix and markup policy. Figures 2 through 3 visualize cross-agent dispersion and repricing behavior; Table 3 summarizes the four-regime comparison on five metrics. ClawCoin yields the lowest quote volatility, the fewest repricing events, and the tightest cross-agent dispersion. USDC + internal indexing improves over Fiat on volatility and repricing, but its cross-agent dispersion and price-consistency score stay materially worse than ClawCoin’s because each agent

Cross-Agent Quote Spread

Li et al.

Table 4: Task-market feasibility. Mean price normalized to the Fiat regime.

1.1 1.0 0.9 0.8 0.7 0.6 0.5 0.4 0.3 0

10

20

Fiat Regime Raw-Cost Regime ClawCoin Regime 30 40 50 60

Time Step

70

Regime

Accept

Compl.

Overrun

Price

Rej.

Fiat Raw-cost USDC + int. ClawCoin

78.6% 73.1% 83.5% 89.8%

72.4% 67.2% 79.9% 87.1%

6.9% 9.8% 4.1% 0.8%

1.00x 0.98x 1.03x 1.02x

14.8% 18.6% 10.2% 5.4%

Table 5: Workflow-level evaluation across delegation depths 𝐷 ∈ {1, 2, 4, 8}. Settlement latency normalized to Fiat.

80

Figure 2: Cross-agent quote dispersion across regimes. Rawcost pricing exhibits the largest dispersion; ClawCoin reduces spread by internalizing common compute movements into the shared unit.

Regime Fiat Raw-cost USDC + int. ClawCoin

Fail

Over.

Partial

Err.

Lat.

p95

9.8% 14.6% 6.2% 2.1%

7.1% 10.9% 4.8% 0.0%

6.4% 9.7% 5.9% 0.0%

0.143 0.188 0.091 0.037

1.00x 0.96x 1.12x 1.08x

1.42x 1.51x 1.39x 1.17x

Average Repricing Events per Agent

Table 6: Workflow failure rate by delegation depth.

10 8 6

Depth

Fiat

Raw

USDC + int.

ClawCoin

𝐷 =1 𝐷 =2 𝐷 =4 𝐷 =8

3.2% 6.7% 11.8% 17.6%

5.8% 10.9% 16.5% 24.8%

2.7% 4.4% 7.0% 10.8%

1.1% 1.8% 2.5% 3.2%

4

7.3 2 0

Fiat

Raw-Cost

ClawCoin

Figure 3: Repricing events per agent across regimes. Fiat and raw-cost require repeated nominal updates; ClawCoin absorbs common movements at the unit-of-account layer.

Table 3: Pricing stability and repricing overhead. Regime

Vol.

Repr./100

Disp.

Consist.

Drift

Fiat Raw-cost USDC + int. ClawCoin

0.118 0.153 0.074 0.039

26.4 31.9 14.2 6.8

0.141 0.187 0.093 0.041

0.77 0.69 0.86 0.94

0.084 0.109 0.049 0.021

uses its own basket: absent a shared numeraire, per-agent stabilization cannot collapse quotes onto a common scale, even when each agent’s own accounting is stable. Task-market feasibility under budget constraints. Customers submit tasks with heterogeneous willingness to pay; each task may require one or more service stages from different agents; a task is accepted if the aggregate quote fits within the customer’s budget. Table 4 shows that ClawCoin raises acceptance and completion and collapses budget overruns, primarily because compute-aligned quotes match compute-aligned customer budgets. USDC + internal indexing narrows the gap to Fiat but cannot eliminate budget mismatches: customers and providers still reason in different units.

Multi-Agent Workflows and OpenClaw Integration

The multi-agent results are the main system contribution of the evaluation. They directly test the claim of Section 3.2 that internal indexing alone cannot supply atomic multi-hop settlement, contract-enforced budgets, and a shared numeraire for cross-agent coordination. Workflow-level evaluation. The simulator is extended with explicit multi-step delegation chains of depth 𝐷 ∈ {1, 2, 4, 8}. Tasks have stage-level subtasks with stage-level prices, budgets are precommitted at submission, and mid-flight cost shocks may push aggregate cost above the budget. Under ClawCoin, the workflow uses the atomic multi-hop helper and the escrow budget gate (Section 4.4); under USDC + internal indexing, each hop converts via the originator’s private index with off-chain reconciliation; under Fiat and Raw-cost each hop denominates in USDC. Table 5 reports the aggregate comparison, and Table 6 reports the depth breakdown. Two qualitative findings stand out. First, ClawCoin drives partial-settlement to zero by construction (any failed hop reverts the bundle) and eliminates budget overruns through the pre-commit gate; both are contract-level properties that the nontokenized baselines cannot replicate without trusted middleware. Second, failure rates compound with depth in every regime, but the slope differs sharply: Fiat and Raw-cost grow steeply because mid-flight shocks compound across hops with no atomic primitive to bind them; USDC + internal indexing grows more slowly but remains vulnerable to coordination failures at 𝐷 = 8; ClawCoin grows almost linearly with depth because each hop settles in the same compute-aligned unit and the bundle is all-or-nothing. End-to-end OpenClaw workflows. We replay representative workflows on the OpenClaw testbed under each backend without

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

Table 7: End-to-end OpenClaw workflow evaluation across settlement backends.

Table 9: OpenClaw GPU-resource procurement across settlement backends.

Backend usdc-fiat usdc-internal-index clawcoin

Success

Revert

Agents

Drift

Backend

Attach

Deleg.

Repr.

Compl.

Pred.

81.5% 84.8% 92.7%

8.4% 6.1% 2.3%

3.6 3.7 3.8

0.116 0.081 0.034

usdc-fiat usdc-internal-index clawcoin

86.1% 88.7% 95.4%

79.4% 82.5% 91.8%

17.8% 12.3% 4.1%

76.8% 80.6% 89.9%

0.74 0.82 0.93

Table 8: OpenClaw economy survival over 500 rounds. Trade volume normalized to the Fiat backend. Backend usdc-fiat usdc-internal-index clawcoin

Surv.

Δ𝑇

Gini

Vol.

Deleg.

4/8 5/8 6/8

−18.7% −9.4% +6.8%

0.49 0.43 0.38

1.00x 1.12x 1.34x

0.38 0.44 0.57

changes to agent logic. Three workflow categories are used: document analysis (planner → retriever → synthesizer), structured retrieval (planner → retriever → verifier → synthesizer), and multitool research (planner → retriever → tool-use → coder → verifier → synthesizer). Table 7 reports workflow success, protocol revert rate, the mean number of distinct agents per task, and realized cost drift against the originator’s pre-commit estimate. clawcoin improves workflow success and collapses protocol reverts and cost drift. The gain comes entirely from the settlement and budget layer, not from any change in the cognitive layer: all three backends share the same GLM-4.7 Flash endpoint and the same per-role prompts, so what shrinks are the mid-flight repricing mismatches and reconciliation failures that the non-atomic baselines expose. Long-horizon economy survival. To probe coordination value over longer horizons, we instantiate eight OpenClaw agents with heterogeneous initial treasuries and role specializations and run a 500-round market: tasks arrive stochastically, agents quote, the planner delegates, executors deliver, and treasuries update by equation 1. An agent is declared bankrupt and exits if its treasury cannot cover expected operating costs over the next three rounds. Table 8 shows that under clawcoin, more agents survive, median treasuries grow rather than shrink, wealth distribution is less concentrated, and inter-agent trade volume and delegation rate rise substantially. The mechanism is not an external subsidy: every backend runs against the same task-arrival process and the same model. The mechanism is that a shared compute-aligned numeraire makes cross-agent quotes legible enough for delegation to be profitable, which raises equilibrium trade volume and avoids the cascading bankruptcies that follow from mispriced delegation under fiat denomination. OpenClaw resource procurement. We extend OpenClaw with a remote-execution adapter that exposes burstily priced GPU time as an executable subtask; three locally provisioned OpenClaw agents and three remotely provisioned OpenClaw agents run side by side, and the planner chooses between local and remote execution at each subtask. Table 9 shows that the dominant pain point in the integration is not payment transport (USDC moves cleanly across backends) but procurement under a shared compute-aligned budget. Under clawcoin, mid-task repricing incidents collapse, completed workflows rise, and spend predictability across identical workflow classes approaches one. The compute-aligned unit lets the planner reason about local-versus-remote substitution in a single budget

unit, which is the missing-primitive argument of Section 3.2 applied to OpenClaw’s external resource market. Across all four multi-agent experiments, the qualitative pattern is consistent: moving the unit of account on-chain is what converts compute-aligned accounting into compute-aligned coordination. USDC + internal indexing recovers most of the per-agent stability but cannot collapse cross-agent dispersion, cannot atomically bind multi-hop delegation, cannot contract-enforce a shared compute budget, and cannot sustain cooperative market dynamics over long horizons. ClawCoin does all four, and the gap widens monotonically with delegation depth, agent heterogeneity, and time horizon.

7.4

Risk Sanity Checks

The risk module is engineering hygiene, not the paper’s main contribution. We therefore reduce the adversarial and solvency evaluation to three sanity checks that confirm the properties of Section 5 hold on the running prototype, and defer larger adversarial sweeps to future work. Table 10 groups the three checks. Stale oracle. We freeze the update channel. Beyond the staleness threshold, IndexOracle.isStale returns true, mint is rejected, and incoming redeem requests are queued rather than executed against an untrusted price. The contract resumes normal operation on the next fresh attestation, exactly as specified in Section 4.3. Single-vendor manipulation. A single vendor in a basket of five posts has a +50% biased input price. Under the mean estimator, the published index absorbs the bias proportionally; under the median (the protocol default), the deviation collapses by more than an order of magnitude, consistent with Lemma 1; with the onchain drift cap engaged, per-epoch deviation is further bounded to the cap. The check is deliberately small: its role is to verify that the median-plus-drift-cap composition behaves as expected on the prototype. Redemption burst. We drive the prototype through three index trajectories with a coordinated redemption rush: a mild shock with one drift-capped step, a two-step spike, and sustained capped growth combined with a low replenishment rate. Under the mild shock, the queue drains cleanly. Under the two-step spike, most redemptions are honored within a short horizon, and the rest queue. Under sustained growth with low replenishment, the auto-pause condition engages as predicted by Lemma 2. Across all three, no involuntary loss to redeemers is observed; the queue absorbs short rushes, and auto-pause is the last line of defense under sustained adverse motion. These results are protocol hygiene. The system claim of ClawCoin rests on the multi-agent results of Section 7.3, where moving the unit of account on-chain is what converts compute-aligned accounting into compute-aligned coordination.

Li et al.

Table 10: Risk sanity checks on the running prototype. All three confirm that the risk module behaves as designed. Check

Condition

Observed behavior

Bound from §5

Honored / safe

Stale oracle

Beyond staleness threshold (4 epochs)

G4, Algorithm 2

100% queued; recovers next epoch

Vendor bias

One vendor of five posts +50% input bias

Lemma 1, Eq. 6

Median + cap suppress bias

Redemption burst

Mild / two-step spike / sustained capped growth

Mint rejected; redeem queued; no stale-state settlement Mean: +11.8%; median: +1.9%; +drift cap: +1.0%/epoch Queue peak 18 / 63 / 141; pause on the third

Lemma 2, Theorem 1

100% / 92% / 61% within 5 epochs

8 Discussion, Limitations, and Future Work 8.1 Discussion Operational asset, not speculative instrument. ClawCoin is intended as operational infrastructure for decentralized agent economies, not as a retail investment product. Demand arises from transactional utility (agents need a stable unit for budgeting, quoting, and atomic multi-hop settlement of compute-bound workflows) rather than from appreciation expectations. Any transferable asset can be traded, but speculation is not required for the system to produce utility, and the risk module’s per-epoch caps and pause logic deliberately bound secondary-market velocity. Cost-only by design. As argued in Section 4.1, the index tracks inference cost rather than model quality, which is priced separately in markets through reputation, contracting, and observed outcomes. A consequence is that the unit of account alone cannot resolve information asymmetry about service quality: two agents that quote identical ClawCoin prices for the same workload may still deliver meaningfully different outputs, and the economy must layer reputational and contractual signals on top of the compute-aligned unit. Regulatory posture. Because ClawCoin is redeemable against reserve collateral and may circulate as a transferable digital asset, its legal treatment will depend on jurisdiction and deployment model; it may fall under stored-value, prepaid-instrument, or reserve-backed-claim regimes in different settings, and consortium or enterprise deployments among known counterparties have a different profile from public circulation. We treat compliance architecture as a deployment-layer concern rather than a property of the monetary design itself. Toward fully machine-native pricing. The current index ingests prices quoted in fiat, reflecting how most commercial inference is priced today and enabling transparent list-price construction. As compute markets evolve toward direct machine-to-machine pricing, native compute auctions, or tokenized GPU markets, the same pipeline can ingest those inputs without protocol redesign, and the unit becomes more fully machine-native.

8.2

(auto-pause on detected drift; redemption queueing) but cannot be tightened by parameter choice alone. Theorem 1 bounds coverage under bounded per-epoch growth and a positive replenishment rate, but persistent cost increases above the replenishment rate cannot be absorbed indefinitely by a passive collateral pool, so deployable systems require either substantial overcollateralization, sponsorseeded buffer capital, or yield-bearing reserve management. The standardized workload classes approximate rather than replace real workloads, so agents heavily reliant on non-token components (caching, batching, hardware tiers, network tail latency) experience a weaker match; the basket can be widened but full alignment is unattainable in a publicly verifiable way. Finally, Section 5.3 enumerates the threats not covered (full vendor collusion, correlated regulatory shutdown, base-chain bugs, long-horizon governance capture) and the current evaluation uses a modest-scale prototype, simulator, and testbed; larger live deployments are left to future work.

8.3

Future Work

Several directions follow naturally. Zero-knowledge attestations binding index inputs to authenticated provider responses would upgrade Proposition 1 to a bound rooted in cryptographic assumptions rather than vendor independence. Replacing the threshold committee with a permissionless DON (Pyth or UMA style) and quantifying the resulting latency/freshness/cost trade-offs is a natural deployment-track extension. Extending the workload basket to capture latency tiers, throughput SLAs, context-window pricing, and bundled enterprise contracts, and connecting it to tokenized GPU and inference auctions, would tighten the gap between the index and realized cost. On the analysis side, equilibrium analysis of provider strategic repricing, governance-attack incentives, and MEV around oracle updates would complement the boundedadversary results of Section 5. An end-to-end OpenClaw deployment that closes the loop between Section 7.3 and a small live deployment, including regulated and consortium settings, is the most concrete operational next step.

Limitations

The index is defined over public list prices and cannot capture hidden enterprise discounts (Section 5.2, S7), which bounds how closely the index tracks any individual agent’s realized cost. The integrity bound in Proposition 1 requires 𝑓 < 𝑛𝑚 /2 honest vendors per active model, and the NAV bound in Proposition 2 assumes an honest oracle threshold; beyond these, guarantees degrade gracefully

9

Conclusion

Decentralized agent economies have an emerging payment substrate but lack a representation of machine-native value: a tradable, composable, contract-readable unit aligned with the computational cost that bottlenecks agent execution. We argued that internal cost indexing over stablecoin rails cannot supply this primitive in a

ClawCoin : An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies

decentralized setting, and we presented ClawCoin, a collateralbacked, compute-indexed tokenized unit of account whose four protocol layers (robust basket index, attested oracle, NAV-based mint/redeem vault with risk controls, and on-chain atomic multihop settlement) are designed under a concrete adversary model. We stated bounded-adversary properties for index integrity, NAV faithfulness, redeemability under stress, and liveness, and walked through the principal attack scenarios. A prototype on an Ethereumcompatible network, a multi-agent simulator, and a six-role OpenClaw testbed show that moving the unit of account on-chain is what converts compute-aligned accounting into compute-aligned coordination: cross-agent quote dispersion collapses, multi-hop delegation settles atomically, contract-level budgets bind end-to-end, and long-horizon market dynamics sustain cooperative trade. ClawCoin is a security-engineered, on-chain, compute-cost-indexed unit of account, and a coherent, implementable step toward the missing representation primitive of the decentralized AI agent economy.

References [1] A2A Project. 2025. Agent2Agent (A2A) Protocol Specification. https://a2aproject. github.io/A2A/latest/specification. [2] Agentic Coin Project. 2026. Agentic Coin: A Peer-to-Peer Electronic Cash System for Autonomous Agents. White paper. https://agentic-coin.org/. [3] Greg Osuri and Adam Bozanich. 2020. Akash Network: A Decentralized Open Source Cloud. White paper, Akash Network. https://akash.network/whitepaper. [4] Halborn. 2022. Explained: The Beanstalk Hack (April 2022). https://www.halborn. com/blog/post/explained-the-beanstalk-hack-april-2022. [5] Yuma Rao and Jacob Steeves. 2020. BitTensor: A Peer-to-Peer Intelligence Market. arXiv:2003.03917. [6] BlackRock. 2024. BlackRock Launches Its First Tokenized Fund, BUIDL, on the Ethereum Network. Press release, March 20, 2024. https://www.businesswire.com/ news/home/20240320771318/en/. [7] Lorenz Breidenbach, Christian Cachin, Benedict Chan, Alex Coventry, Steve Ellis, Ari Juels, Farinaz Koushanfar, Andrew Miller, Brendan Magauran, Daniel Moroz, Sergey Nazarov, Alexandru Topliceanu, Florian Tramèr, and Fan Zhang. 2021. Chainlink 2.0: Next Steps in the Evolution of Decentralized Oracle Networks. White paper. https://research.chain.link/whitepaper-v2.pdf. [8] PeckShield. 2020. bZx Hack II Full Disclosure (With Detailed Profit Analysis). https://peckshield.medium.com/bzx-hack-ii-full-disclosure-with-detailedprofit-analysis-8126eecc1360. [9] Giulio Caldarelli. 2020. Understanding the Blockchain Oracle Problem: A Call for Action. Information 11, 11 (2020), 509. https://doi.org/10.3390/info11110509. [10] Christian Catalini, Alonso de Gortari, and Nihar Shah. 2022. Some Simple Economics of Stablecoins. Annual Review of Financial Economics 14 (2022), 117 to 135. https://doi.org/10.1146/annurev-financial-111621-101151. [11] Ryan Clements. 2021. Built to Fail: The Inherent Fragility of Algorithmic Stablecoins. Wake Forest Law Review Online 11 (2021), 131 to 155. http://www.wakeforestlawreview.com/2021/10/built-to-fail-the-inherentfragility-of-algorithmic-stablecoins/. [12] Coyns. 2026. Coyns Launches First Virtual Currency Built Exclusively for AI Agentto-Agent Transactions. Press release, April 2026. [13] C.R.E.A.M. Finance. 2021. C.R.E.A.M. Finance Post Mortem: Flash Loan Exploit Oct. 27. https://medium.com/cream-finance/c-r-e-a-m-finance-post-mortem-flashloan-exploit-oct-27-507b12bb6f8e. [14] Philip Daian, Steven Goldfeder, Tyler Kell, Yunqi Li, Xueyuan Zhao, Iddo Bentov, Lorenz Breidenbach, and Ari Juels. 2020. Flash Boys 2.0: Frontrunning in Decentralized Exchanges, Miner Extractable Value, and Consensus Instability. In 2020 IEEE Symposium on Security and Privacy (S&P). IEEE, 910 to 927. arXiv:1904.05234. [15] Shayan Eskandari, Mehdi Salehi, Wanyun Catherine Gu, and Jeremy Clark. 2021. SoK: Oracles from the Ground Truth to Market Manipulation. In Proceedings of the 3rd ACM Conference on Advances in Financial Technologies (AFT ’21). arXiv:2106.00667. [16] Rainer Feichtinger, Robin Fritsch, Lioba Heimbach, Yann Vonlanthen, and Roger Wattenhofer. 2024. SoK: Attacks on DAOs. In 6th Conference on Advances in Financial Technologies (AFT 2024). LIPIcs, Vol. 316, 28:1 to 28:21. arXiv:2406.15071. [17] Protocol Labs. 2017. Filecoin: A Decentralized Storage Network. White paper. https://filecoin.io/filecoin.pdf. [18] José M. Garrido. 2023. Digital Tokens: A Legal Perspective. IMF Working Paper No. WP/23/151. https://www.imf.org/en/Publications/WP/Issues/2023/07/28/DigitalTokens-A-Legal-Perspective-537041.

[19] Gary Gorton and George Pennacchi. 1993. Security Baskets and Index-Linked Securities. Journal of Business 66, 1 (1993), 1 to 27. [20] Gary B. Gorton and Jeffery Y. Zhang. 2023. Taming Wildcat Stablecoins. University of Chicago Law Review 90, 3 (2023), 909 to 972. [21] Harvest Finance. 2020. Harvest Flashloan Economic Attack Post-Mortem. https://medium.com/harvest-finance/harvest-flashloan-economic-attack-postmortem-3cf900d65217. [22] Iron Finance. 2021. Iron Finance Post-Mortem: 17 June 2021. https://ironfinance. medium.com/iron-finance-post-mortem-17-june-2021-6a4e9ccf23f5. [23] LangChain. 2024. LangGraph Overview. Documentation. https://docs.langchain. com/langgraph. [24] Liquity. 2021. Liquity Releases Updated Whitepaper. Blog post, February 10, 2021. https://www.liquity.org/blog/liquity-releases-updated-whitepaper. [25] Jiageng Liu, Igor Makarov, and Antoinette Schoar. 2023. Anatomy of a Run: The Terra Luna Crash. NBER Working Paper No. 31160. https://www.nber.org/ papers/w31160. [26] Richard K. Lyons and Ganesh Viswanath-Natraj. 2023. What Keeps Stablecoins Stable? Journal of International Money and Finance 131 (2023), 102777. [27] MakerDAO. 2020. The Maker Protocol: MakerDAO’s Multi-Collateral Dai (MCD) System. White paper. https://makerdao.com/whitepaper/. [28] U.S. Commodity Futures Trading Commission. 2023. CFTC Charges Avraham Eisenberg with Manipulative and Deceptive Scheme to Misappropriate Over $110 Million from Mango Markets, a Digital Asset Exchange. Press Release No. 8647-23. https://www.cftc.gov/PressRoom/PressReleases/8647-23. [29] NVIDIA. 2026. Jensen Huang at GTC 2026: Tokens, Token Factories, and the AI Industrial Revolution. Keynote, NVIDIA GTC, March 2026. [30] Morgan Stanley. 2026. NVIDIA’s Jensen Huang on Compute as a New Economic Engine. Morgan Stanley Technology, Media & Telecom Conference, March 2026. https://www.morganstanley.com/insights/articles/nvidia-jensen-huangcompute-new-economic-engine-tmt-2026. [31] Joon Sung Park, Joseph C. O’Brien, Carrie J. Cai, Meredith Ringel Morris, Percy Liang, and Michael S. Bernstein. 2023. Generative Agents: Interactive Simulacra of Human Behavior. In Proceedings of the 36th Annual ACM Symposium on User Interface Software and Technology (UIST ’23). ACM, Article 2, 22 pages. https://doi.org/10.1145/3586183.3606763. [32] Antti Petajisto. 2017. Inefficiencies in the Pricing of Exchange-Traded Funds. Financial Analysts Journal 73, 1 (2017), 24 to 54. [33] Pyth Network. 2023. Pyth Network: A First-Party Financial Oracle (Whitepaper v2.0). https://www.pyth.network/blog/7-pyth-network-a-first-party-financialoracle. [34] Kaihua Qin, Liyi Zhou, and Arthur Gervais. 2022. Quantifying Blockchain Extractable Value: How Dark is the Forest? In 2022 IEEE Symposium on Security and Privacy (S&P). IEEE, 198 to 214. arXiv:2101.05511. [35] David M. Rothschild, Markus Mobius, Jake M. Hofman, Eleanor Dillon, Daniel G. Goldstein, Nicole Immorlica, Sonia Jaffe, Brendan Lucier, Aleksandrs Slivkins, and Matthew Vogel. 2025. The Agentic Economy. arXiv:2505.15799. [36] U.S. Department of the Treasury. 2024. Treasury Inflation-Protected Securities (TIPS). TreasuryDirect. https://treasurydirect.gov/marketable-securities/tips/. [37] Longbridge News Desk. 2026. “Burning Tokens” Has Become a KPI: AI Token Consumption as a Performance Metric and Compensation Item. https://longbridge. com/news/280231355. [38] Hart Lambur, Allison Lu, and Regina Cai. 2018. UMA: A Decentralized Financial Contracts Platform (Universal Market Access). White paper. https://github.com/ UMAprotocol/whitepaper. [39] Circle. 2023. An Update on USDC and Silicon Valley Bank. Blog post, March 11, 2023. https://web.archive.org/web/20230311202753/https://www.circle.com/blog/ an-update-on-usdc-and-silicon-valley-bank. [40] Sam M. Werner, Daniel Perez, Lewis Gudgeon, Ariah Klages-Mundt, Dominik Harz, and William J. Knottenbelt. 2021. SoK: Decentralized Finance (DeFi). arXiv:2101.08778. [41] Qingyun Wu, Gagan Bansal, Jieyu Zhang, Yiran Wu, Beibin Li, Erkang Zhu, Li Jiang, Xiaoyun Zhang, Shaokun Zhang, Jiale Liu, Ahmed Hassan Awadallah, Ryen W. White, Doug Burger, and Chi Wang. 2024. AutoGen: Enabling NextGen LLM Applications via Multi-Agent Conversation. In Proceedings of the 1st Conference on Language Modeling (COLM). arXiv:2308.08155. [42] Coinbase. 2025. x402: An Open Protocol for Internet-Native Payments over HTTP. Specification. https://docs.x402.org/. [43] BlockEden. 2026. x402 Protocol: How a Forgotten HTTP Code Became the Payment Rails for 15 Million AI Agent Transactions. Industry analysis, January 2026. https://blockeden.xyz/blog/2026/01/16/x402-protocol-ai-agentautonomous-payments-http-402/. [44] Minghui Xu. 2026. The Agent Economy: A Blockchain-Based Foundation for Autonomous AI Agents. arXiv:2602.14219. [45] Liyi Zhou, Xihan Xiong, Jens Ernstberger, Stefanos Chaliasos, Zhipeng Wang, Ye Wang, Kaihua Qin, Roger Wattenhofer, Dawn Song, and Arthur Gervais. 2023. SoK: Decentralized Finance (DeFi) Attacks. In 2023 IEEE Symposium on Security and Privacy (S&P). IEEE, 2444 to 2461.

Record · ID 123992 · SHA-256 1f2ea04f57b4b844
Retrieved via Conceptio — every document is proof-bundled with source, license, and retrieval metadata.