RHO: Measuring Computational Work
A normalized way to attribute computational resource consumption to specific execution events.
AI systems can tell you what they produced. Cloud systems can tell you what infrastructure cost. RHO connects those layers by attributing computational resource consumption to the execution event that caused it.
- Executionwhat ran
- Measurementresources used
- RHOnormalized unit
- Pricingtariff policy
- Obligationwhat is owed
- Settlementmoney moves
Six distinct stages. RHO is the third. Everything to its right is a separate policy or monetary system.
A unit of measurement, not a unit of money.
A kilowatt-hour measures electricity consumption. It is not itself the customer’s bill. A tariff converts measured consumption into a financial charge. RHO is designed to relate to computation the way the kilowatt-hour relates to electricity.
Energy consumed → kWh → tariff → bill
ExergyNetComputational execution → RHO → tariff → financial obligation
RHO measures. Pricing decides what that measurement is worth commercially.
RHO is not:
- a cryptocurrency or speculative token
- a stablecoin or dollar balance
- a security or monetary asset
- a joule or unit of energy
- redeemable for dollars
- a market-priced commodity
Bills describe infrastructure. RHO describes executions.
Conventional infrastructure accounting can usually answer questions like: How much did this GPU instance cost? How many API tokens were consumed? What was the monthly cloud bill? How much did a customer pay?
ExergyNet is addressing a more specific question:
That question matters more as machines act on their own behalf. It applies to:
- autonomous agents and multi-step workflows
- model calls, retrieval, and verification
- tool execution and distributed infrastructure
- machine-to-machine services and automated economic activity
RHO is ExergyNet’s architecture for this problem. It is not presented as the only possible one.
Useful computation creates value. RHO measures its resource cost.
Value comes from work the network performs: inference, retrieval, validated computation, authorized execution, data transformation, tool invocation, state transitions, automation, verification, or completing a computational service.
RHO standardizes how the resources behind that work are measured. The relationship runs in this direction only:
A highly valuable computation can consume very little RHO. A worthless one can consume a great deal. Measurement and economic value are different quantities. Converting one into the other is a separate pricing function, described below.
Two different questions, two different variables.
How much normalized computational resource was attributed to this execution?
What does the provider charge for that execution?
An execution may consume 25 RHO. A pricing policy, or tariff, determines the corresponding financial charge. The same RHO quantity could carry different tariffs for different services, just as 100 kWh is one quantity of energy regardless of the rate on the bill.
The figure of 25 RHO is illustrative. $X is deliberately unspecified: this page does not state a production price.
The customer pays for a service. RHO is the measurement in between.
- Request. A customer requests or authorizes a computational service.
- Execution. The service executes.
- Measurement. ExergyNet measures the resource consumption attributable to that execution.
- RHO. RHO records that normalized resource use.
- Pricing. A pricing policy converts the measurement into a financial obligation.
- Settlement. Existing monetary infrastructure can settle that obligation.
- Allocation. Authorized economic participants receive the amounts defined by the applicable settlement policy.
Today, customer usage on the ExergyNet Portal is billed against USDC-denominated account balances. A RHO-based tariff is not active. See Current Implementation Status.
We do. RHO addresses a different problem.
ExergyNet is not attempting to replace financial accounting. Payment records, ledgers, and invoices remain the right tools for money.
A conventional ledger can record that Customer A paid $4.82. It typically does not natively preserve the computational causal chain: which authorized machine execution produced that obligation, under what authority and policy, and against what state. ExergyNet extends accounting toward the computational event itself:
In ExergyNet’s execution model, a single machine action can be written as:
- Sᵢ
- initial state
- A
- authority: what the actor is permitted to do
- M
- model or runtime performing the work
- C
- capabilities available to the actor
- P
- governing policy
- X
- the execution event
- R
- resulting observation or output
- Sᵢ₊₁
- resulting state
The validated G0 normalization.
For the genesis accounting epoch (G0), the currently validated definition is:
- RHO
- the normalized quantity attributed to an operation.
- C (total non-overlapping, USD)
- the measured infrastructure cost attributable to the operation, in US dollars, counted once. Where the same underlying resource use appears in more than one accounting view, it is not added twice.
- 0.0001000000
- a fixed reference constant, defined for epoch G0.
Internally, G0 also fixes 1,000,000 µRHO per RHO, so small operations can be expressed as whole numbers. The measurement basis behind G0 covers two infrastructure classes. Its limits are stated in the status section below: notably, the GPU-inference cost term is modeled from pricing data rather than directly measured, and energy is not measured.
The public description stops here on purpose. Detailed cost-component definitions and attribution methods are maintained in ExergyNet’s internal metrology specification.
Rules RHO must obey.
Attribution
Every RHO record must be connected to an attributable computational resource or execution event.
No double counting
The same underlying resource expenditure must not be counted more than once merely because it appears in multiple telemetry or accounting sources.
Measurement is not price
A RHO quantity does not independently determine commercial price.
Measurement is not settlement
Creating a RHO accounting record does not itself transfer money.
Traceability
A RHO value should be derivable from its associated measurement and accounting evidence.
Explicit policy
Pricing, settlement, discounts, margins, and provider allocations belong to explicit policy layers, not to the definition of RHO.
RHO preserves accounting consistency, not economic value.
The invariant RHO is designed to satisfy is one of traceability:
This holds subject to the defined measurement policy and accounting epoch. Nothing is added to a RHO total because someone declares it: every quantity must be derivable from an attributable execution record.
Economic value may be created, destroyed, transferred, or priced independently of this identity. Its purpose is consistency and traceability, not a claim that value is conserved.
What exists, and what does not.
| Capability | Status | What that means |
|---|---|---|
| G0 normalization definition | Validated | The formula and reference constant are fixed for genesis epoch G0 (effective 2026-08-23). The constant is a normalization denominator only. |
| G0 measured cost basis | Validated, bounded | Measured on one AWS c6a.large host and one Azure A10-class GPU host. Base equivalents were recorded for three operation types (RECALL, WRITE, QUERY). The GPU-inference term, which dominates QUERY, is modeled from pricing data, not measured. Energy was not measured. Token counts used a word-count proxy. Pilot stage. |
| Tariff schedules | Shadow only | Candidate tariff schedules exist for analysis. They are not settlement authority, use uncalibrated assumptions, and do not drive any charge. |
| Settlement test with RHO on a test network | Testnet only | A RHO token contract on Base Sepolia (a public test network) was used to settle three metered memory operations end to end: 500 test RHO in total, with allowances spent to zero and replay attempts rejected. This exercised a settlement pathway. It carries no monetary value. |
| Mainnet issuance | Not active | No RHO has been minted on a production network. Mainnet minting is not authorized. |
| Market price, exchange, redemption | Not defined | RHO has no market price, no dollar peg, and no redemption right. It does not trade. |
| Production RHO-based tariff and billing | Not active | Customer usage on the Portal is billed against USDC-denominated balances today. Converting RHO into customer charges in production has not been activated. |
The next validation stage is direct GPU-side and energy instrumentation, followed by demonstrating the complete chain from measured execution to obligation to settlement. Until then, treat everything to the right of RHO in the flow above as designed, not deployed.
Go deeper.
RHO sits alongside ExergyNet’s other foundational concepts. Each has its own plain-English definition and evidence boundary.
A standalone public RHO accounting specification has not been published. This page is the canonical public definition. Implementation internals are intentionally omitted.