Voxonomics Whitepaper Dashboardsoon

Pages press 1–7

Whitepaper, Edition 3.2 Dashboard soon

Digital value, measured.

Final Publication Edition 3.2  ·  research product 1.2.0‑rc3

The numbers that value blockchains are audited by nobody.

Voxonomics is an open economic measurement standard for blockchain networks — one framework, applied identically across chains, built from their own records, with the evidence and calculation path preserved for every figure. Where the evidence cannot support a measurement, Voxonomics publishes the gap instead of inventing the number.

The dashboard is where the measurements are read. It is not open yet, and that is the same rule the rest of this page follows: official scoring stays disabled until calibration is complete and governance approves it. Until then there is nothing there we would stand behind publishing.

6 × 5equal sixths
30 submetrics

Six equal sixths, each split by its submetrics’ real weights. Hold and trace the ring — each one names itself as you cross it. All thirty against the clock; leave the ring and you start again.

Parent indices
6
Submetrics
30
Networks in scope
3
Scores published
0

The problem

Everyone quotes the figures. Nobody can check them.

Ask how large a blockchain’s economy is and you will get a confident number within seconds. Ask where that number came from and the trail runs out almost immediately.

These are not obscure statistics. They decide where treasuries allocate capital, which networks get built on, and what is written into research notes and regulatory filings. They are quoted with the authority of audited accounts and produced with none of the discipline.

“This chain has $4 billion locked.”total value locked

Locked by whose definition? Counted once, or once again for every wrapper it passes through? The figure moves by billions depending on choices a reader never sees.

“It has 900,000 active users.”active addresses

Addresses are not people. One person can hold thousands; one bot can hold millions. Nothing published tells you which you are looking at.

“It did $20 billion in volume.”trading volume

Volume includes trades made purely to inflate volume. Filtering those out is a judgement call, and almost nobody publishes the rule they used.

“It earned $30 million in fees.”protocol revenue

Earned by the network, or by applications built on top of it? Before or after what is burned or paid out? Two sources will disagree by an order of magnitude.

The deeper problem is that every network is measured on its own terms. A figure from one chain and a figure from another are not comparable, even when they share a name — so the comparison everybody makes is one that nobody can justify.

What we are building

The instrument itself.

This is the terminal that runs the measurement lanes — a screenshot of it, not an impression of it. Proof of Value is open: its five submetrics along the top, one evidence series charted below, and that observation’s provenance beside it — source, last block, block cadence, and how long the value has stood unchanged.

Read what it says about itself. The parent status is LOCKED, and it explains why in its own words: no partial parent score is promoted as VTS authority. The selected metric’s own figure is withheld, because its retention window has not elapsed. The chart is badged RAW EVIDENCE / NOT SCORE and says underneath that it is supporting evidence history only, not a canonical metric-score history while the metric remains constitutionally incomplete. The official switch reads OFF.

That is the instrument refusing to overstate itself, without anyone asking it to. It is the same refusal the pipeline below takes apart step by step.

A research build on a developer machine, captured as it stood.

A screenshot of the Voxonomics terminal. The Proof of Value index is selected and its five submetrics are shown as cards; the panel below charts one evidence series and the panel beside it lists that observation's provenance. The parent status reads LOCKED, the official switch reads OFF, and the selected metric's own figure is marked withheld.

The terminal as it runs. Captured 8 October on a research build, which is why two of its own connections report failed — that is left in. One thing is altered: the mark in the corner, which the capture predates, is the current one. Shown at this width: the provenance panel from the right of that screen.

How a number is made

Watch one measurement being built.

Every figure travels the same five steps: read the blocks, check what is actually in them, collect only what the definition asks for, run the equation, and out comes a number — which stops at a gate until it has been calibrated and approved. Nothing passes that gate today.

the chips in each stretch are the real count at that stage — click to shove more in, none of it fits only what the run found gets through

The lane page shows the venue-and-asset diversity arithmetic with synthetic inputs, then an illustrative adapter gap that would require a result to be withheld. Neither branch reports a network score.

Collector FLOW. Every network uses the same collection contract, with warehouse depth, request pacing and worker count tuned independently for steady, sustainable throughput. LIVE takes priority; REPAIR uses spare capacity. The whitepaper explains the designs and separate network evidence stores. Production validation remains separate. Read the collector architecture and diagrams.

Vox Cloud and Vox in a Box. The updated whitepaper specifies independently operated nodes with private evidence stores, signed outbound publications and cross-node verification, alongside a separate read-only cloud service. This is a proposed architecture with staged security and acceptance gates. Read the secure node architecture.

The standard

One framework, applied to every chain, with the receipts kept.

Voxonomics measures blockchain economies the way a laboratory measures anything else: from primary evidence, under a published method, in stated units, with the working preserved so somebody else can repeat it and get the same answer.

Commitment 01

Read the source, not a summary

Figures come from the networks’ own blocks, transaction receipts and event logs — the raw record the chain itself produces — not from a data vendor’s interpretation of them. Every reading keeps the exact block range it covered and a fingerprint of the bytes it read.

Rule 3 — real, verifiable data only

A figure that cannot name the blocks it came from cannot be admitted. This is why prices lost to a machine outage were recovered from oracle answers and pool trades already held in our own blocks, rather than fetched from a price API afterwards.

Commitment 02

Treat every network the same

The same six indices, the same thirty submetrics, the same equations, on every chain. Where a network’s architecture genuinely differs, the adapter that reads it differs — the definition it must answer does not.

Rule 7 — chain-specific code only for chain-specific evidence

Chain-specific adapters map different record formats to the same published definitions. No network gets an easier metric or an inferred value because a reader lacks evidence.

Commitment 03

Say so when you cannot measure

A gap in the evidence is reported as a gap. It is never quietly filled with an estimate, an industry average, or a neutral placeholder that flatters the result. The reason is published in the figure’s place.

Rule 4 — no placeholders, ever

For example, if an adapter retained assets only from a filtered subset, counting that subset would not measure full market diversity. The method would withhold the figure until the evidence matched the definition.

The method

How a single number is made.

Every figure travels the same five stages. They are deliberately separate, so that measuring something and scoring it never happen in the same step.

Provenance record stage 01

The record is the product. Every field is filled from the reading itself — what you see here is the shape of the record, not a measurement.

Stage 01

Evidence

Read the chain, not a report of it.

Blocks, transaction receipts and event logs, taken from the network’s own nodes. The exact block range and a fingerprint of the bytes are kept, so anyone can repeat the reading and get the same answer.

Never a vendor’s summary.
Stage 02

Native value

The real figure, in its real unit.

Dollars settled. Fees paid. Effective operators. The figure is recorded as what it actually is, before anything decides what it is worth.

Never rounded, smoothed, or pre-scored.
Stage 03

State

Say what kind of number this is.

Measured, provisional, or refused — and why. A refusal names the evidence that was missing, which is what makes the gap arguable and, eventually, closeable.

Never a gap filled with an estimate.
Stage 04

Normalisation

Make different units comparable.

Only now are fully measured figures placed on one scale, so dollars, counts and rates can sit inside the same index without one drowning the others.

Never anything that is not fully measured.
Stage 05 · locked

Score

Combine the six indices.

The stage is built and wired, and deliberately switched off. It turns on when calibration is complete and governance approves it — not before.

Not yet: locked until governance.

The separation between stages two and four matters most. Producing a measurement and deciding what that measurement is worth are different jobs, and mixing them is how most published crypto metrics go wrong: a scoring choice gets baked into the figure itself, where no reader can see it or argue with it.

What is kept with every figure

Record structure
network
< the chain the reading was taken from >
block range
< first block > to < last block >
evidence fingerprint
< hash of the exact bytes that were read >
unit
< the real unit — dollars settled, fees paid, effective operators >
state
< measured | provisional | refused >
reason if refused
< the missing evidence, named >
method version
< specification edition and the equation applied >
calculated at
< timestamp of the calculation >

This is the shape of the record, not a reading — no measurements are published on this page. It is what separates a figure that can be checked from one that can only be quoted: anyone holding the record can return to the same blocks and produce the same number, or demonstrate that it cannot be produced.

The framework

Six questions, each carrying exactly one‑sixth of the weight.

A blockchain economy is not one thing, so it is not one number. Voxonomics asks six independent questions of every network, weighted equally, so the framework cannot be tuned to flatter any chain’s strengths. Inside each index, five submetrics carry the fixed weights shown.

Weight of every submetric within its index

Weights are fixed by Edition 3.1. Every index is divided among exactly five submetrics, and the five always total 100%.

The complete register — all 30 submetrics, Edition 3.1Each weight is that submetric’s share of its own parent index, not of the whole framework — the five in every index sum to 100%.
IDSubmetricWeight in indexHorizonDirection

Different readers care about different things. A payments company and a validator operator are not asking the same question of a network, and the framework allows their priorities to be weighted differently — but the weights always renormalise to sum to one, so no priority setting can secretly inflate a total.

Trust

Three states, and the third one is the point.

Every figure carries one of three states. The third state is part of the published method: if the available evidence cannot support a metric, the result should be withheld with a reason.

Measured

The evidence fully answers the definition. The figure is real, in its real unit, and the block range and method that produced it are recorded beside it.

What it looks like

A figure with its block range, its unit and the equation applied recorded beside it. Anyone holding that record can return to the same blocks and produce the same number.

Provisional

A genuine measurement, taken under settings governance has not yet ratified, or over a window still filling. Real, and not yet final.

What it looks like

A real measurement running under settings governance has not ratified. Four lanes are in this state today — built, measuring, and deliberately contributing nothing to any score.

Refused

The evidence does not support the figure the definition asks for. Nothing is published in its place — the reason is named instead, so a reader can judge it and a later release can close it.

What it looks like

An empty cell with a named reason. For example, if an adapter did not retain the routed venue for a trade, venue diversity would be withheld until that evidence was available. This is an illustration of the rule, not a finding about any network.

This sounds like a limitation. It is the opposite. A dashboard that always has a number in every cell is telling you, whether it means to or not, that it has never once met evidence it could not interpret — which is not a claim any honest measurement system can make.

The following hypothetical case shows how the method handles complete and incomplete adapter evidence. It is not a measurement or assessment of any named network.

Venue and asset diversity

DLI.VD · illustrative method example
Complete adapter evidence■ Calculable

If records identify both trading venues and assets within the defined scope, the published equation can be applied.

Same definition■ Comparable

A different chain architecture may require a different reader, while the economic question and calculation remain the same.

Incomplete adapter evidence□ Withheld

If the reader retains token movements but not the routed venue or full asset scope, the method cannot support a venue-and-asset diversity figure.

Illustrative only. This describes a possible gap in an evidence adapter, not a limitation of a blockchain, a finding about any named network, or a published result.

A precise-looking figure can still answer the wrong question if the retained evidence covers only a filtered subset. The method requires that limitation to be named and the figure withheld until the evidence supports the definition.

Coverage

Three network architectures in implementation focus.

The framework is chain-agnostic by construction: adding a network adds an adapter, never a new definition. Ethereum, Solana and Avalanche are the current implementation focus. This page does not certify metric coverage or publish a network comparison.

Ethereum

Implementation focus

Account-based EVM architecture. The adapter maps primary records to the universal metric definitions; evidence coverage and publication status are assessed per metric.

Solana

Implementation focus

Slot-based architecture. Chain-specific extraction is evaluated against the same universal definitions. No metric outcome or evidence gap is asserted here.

Avalanche

Implementation focus

EVM-compatible architecture with its own network scope. The same definitions and evidence requirements apply; no metric outcome is asserted here.

Implementation focus does not imply complete evidence coverage, a production-certified metric, or an official score on any network. Publication requires a preserved, reviewable record for the specific metric and window.

The constitution

Nine constraints the system is not permitted to break.

These are enforced in the software itself, not held as an intention. Several of them make the product slower, narrower and less impressive than it could otherwise be. That is the trade, made deliberately.

  1. Keep the real value and its real unit

    A figure is never converted into a score before it has been recorded as what it actually is.

    How it is enforced

    Stage 02 of the pipeline records the native value and unit before any normalisation runs. The score stage cannot read a figure that has not been recorded natively first.

  2. Keep measuring separate from scoring

    Producing a number and judging that number are different operations, run by different parts of the system.

    How it is enforced

    Measurement lanes and the scoring engine are separate components. A lane can be complete, running and correct while contributing nothing — four currently are.

  3. Real, verifiable data only

    If a figure cannot be traced back to primary evidence, it does not enter the framework.

    How it is enforced

    Every reading carries the block range it covered and a fingerprint of the bytes read. A figure without that record cannot be admitted.

  4. No placeholders, ever

    No dummy values, no neutral substitutes, no industry averages standing in for a missing measurement.

    How it is enforced

    If an adapter retained only a filtered subset of assets, a count over that subset would not answer the full asset-diversity definition. The figure would be withheld rather than filled with a placeholder.

  5. The six indices stay equal

    Universal and one-sixth each, so the framework cannot be shaped to suit a particular network.

    How it is enforced

    The six parent weights are fixed in the specification and are not a parameter. Only the five submetric weights inside each index are set, and those are fixed too.

  6. Priorities always renormalise to one

    Readers may weight the indices to their own concerns; no weighting can inflate a total.

    How it is enforced

    Priority points are normalised before they are applied, so any set of reader priorities produces effective weights summing to exactly one.

  7. Chain-specific code only for chain-specific evidence

    Networks differ in how they must be read, never in what they are asked.

    How it is enforced

    Each chain has its own adapter for reading evidence. None has its own definition. Where a chain cannot answer, the answer is a refusal, not a relaxed rule.

  8. Preserve the working

    Provenance, revisions, method versions and reproducibility are kept for every figure ever published.

    How it is enforced

    Records carry the specification edition and the equation applied, so a figure produced under one version stays attributable to it after the method moves on.

  9. Official scoring stays off until it is earned

    Live contributions and published scores remain disabled until calibration is complete and governance approves.

    How it is enforced

    The scoring stage is built and wired, and switched off. Two gates stand before it: calibration against observed ranges, then approval of each parameter package by hash.

Whitepaper & documents

The specification everything here is built from.

Voxonomics is defined by a published specification, not by its software. The code implements the document; where the two disagree, the document wins.

Open ↗Controlling specification

Voxonomics Whitepaper

Final Publication Edition 3.2. Defines the six parent indices, the thirty submetrics, their equations, units, horizons and directions, and the rules governing evidence, provenance and exclusions.

Edition 3.2 · October 2026 · current publication

Open ↗Parameters

DAO Parameter Workbook

The universal metric-to-score parameter set: benchmarks, sensitivity parameters and priority points, held as an editable workbook so governance can reason about a change before it is made.

v0.1 · universal metric to VTS

Open ↗Machine-readable

Registry & schemas

Metrics, networks, sources, benchmarks and calibration held as structured data with schemas, so the definitions the software runs are the same definitions the specification states.

Registry · schemas · adapters

Pending governance

Calibration record

The evidence and reasoning behind every normalisation range, produced once the measurement lanes are complete. Until it exists and is approved, no score is meaningful and none is published.

Not yet issued

Appendices B.1 – B.6  ·  one per parent index

    Governance

    Why the score is switched off, and what turns it on.

    A measurement framework that publishes scores before it has calibrated them is asking to be believed on trust alone. Voxonomics does the opposite: the scoring stage exists, is built, and is deliberately disabled.

    Two gates stand before it. The first is calibration — normalisation ranges must be set against real observed evidence, not assumed, with the reasoning behind every range recorded. The second is governance approval: each set of parameters is packaged, fingerprinted and put to the framework’s governance before it can affect anything.

    Until both gates are passed, a measurement lane can be running, reading its chain and stating its value, and still contribute nothing. Eighteen already are. None of those values is exact yet, and a value that is not exact is not normalised at all — so the number of figures reaching a score today is zero by arithmetic before it is zero by policy. That is the design working, not the project stalling.

    Position

    Where the work actually stands.

    Stating this plainly is part of the method. All 30 submetrics are defined, while their evidence, parameters and network-specific publication gates progress separately.

    Networks in scope
    3
    Ethereum, Solana and Avalanche are the current implementation focus; no official network scores are published here.
    Framework
    30 / 30
    Every submetric is defined in Edition 3.1. Detailed parameters and approval gates remain separate from that definition.
    Provisional packages
    11 / 30
    Eleven research parameter packages have recorded approval. That approval does not certify a network measurement or enable an official score.
    Official scores
    Locked
    Research observations may be visible, but no submetric score, parent index or network VTS is published as authoritative until calibration and governance gates are satisfied.

    Research parameter packages across 30 submetrics

    Package approval — not network certification

    The newest lane, as it stands

    supervised passes of 6 September

    Venue and asset diversity (DLI.VD) asks whether trading activity is spread across venues and assets. The interactive lane below uses labelled, synthetic inputs to show the published arithmetic. Its alternate branch illustrates what the method would do if an adapter retained too little evidence to answer both halves of the definition. Neither branch is a finding about a named network.

    DLI.VD has an approved provisional research parameter package, but that is not approval of an official network result. This interactive lane covers only part of the definition. Complete evidence, calibration, quality, provenance and publication gates are still required before anything can enter an official score.

    A technical source path or approved provisional parameter package is not a complete measurement for every network. Each metric still needs evidence over its full window, reproducible classifications and the required quality checks; unsupported values stay missing.

    Research observations, where available, remain provisional and separate from official scoring. No official submetric, parent-index or VTS score is published on this site. Publication remains locked until its calibration and governance gates are satisfied.

    Ahead

    What comes next, in order.

    Questions

    The things people ask first.

    Is this a rating agency for blockchains?
    No. A rating is an opinion; this is a measurement standard. Voxonomics publishes what a network’s economy demonstrably does, with the evidence attached, and the method is public so anyone can reproduce or challenge a figure. The scoring layer exists but stays off until it is calibrated and approved.
    Why are there no numbers on this page?
    Because the standard has not passed governance. Measurements exist internally and are marked provisional; publishing them here would imply an authority the method has not yet earned. This page explains the framework. Figures follow calibration, not marketing.
    How is this different from the dashboards that already exist?
    Three ways. Figures are read from the chains’ own records rather than a vendor’s interpretation; the same definitions are applied to every network so figures are actually comparable; and where the evidence cannot answer a definition, the gap is published as a refusal instead of filled with an estimate.
    What does “refused” actually mean?
    That the evidence available does not support the figure the definition asks for. The system names the missing evidence and publishes nothing in that cell. It is the one state no conventional dashboard has, and it is the reason the other two can be trusted.
    Can the weights be changed to suit a particular chain?
    The six parent indices are fixed at one-sixth each and cannot be reweighted. A reader may prioritise the indices for their own purposes, but priorities renormalise so effective weights always sum to one — no setting can inflate a total.
    Which networks are covered, and can more be added?
    Ethereum, Solana and Avalanche today. Adding a network adds an adapter that knows how to read that chain’s evidence; it never adds or relaxes a definition. A metric is published for a network only when the relevant adapter evidence and approval requirements support it. This page does not assert any network-specific refusal.

    Is the trading spread out, or does it all happen in one place?

    If almost every trade on a network runs through one exchange, that network looks healthy right up until that exchange has a bad day. So one of our thirty measurements asks how spread out the trading really is.

    This page shows you exactly how we work that out. Not a summary of it — the actual steps, in order, with the sums shown. You can move the numbers yourself and watch the answer change.

    1Get the blocksRead the records the chain itself wrote. We never ask anyone else for a figure.§5.2 · public data layer
    2Check the evidenceOf everything in there, which are actually trades? The rest is ignored.§5.3 · adapter layer
    3Collect the metricsCount only the two things this measurement is defined on.§5.3 · adapter layer
    4Defined calculationRun the sum that was written down and published in advance.§5.4 · measurement engine
    5Out pops a numberIn its own real unit — and it stops there. Everything after this is locked.§5.4 · where we stop

    What the pipe does not show, on purpose. The specification calls §5.4 “the canonical data path from raw observation to published score”, and this pipe covers only its beginning. After the number above come normalisation onto a common scale, time smoothing and persistence tests, aggregation into the submetric and then into the parent index, and a coverage and confidence calculation. None of that runs. It is built and switched off until calibration is complete and governance approves — so what you are watching is one measurement being produced, not a score being made.

    the chips in each stretch are the real count at that stage — click to shove more in, none of it fits only what the run found gets through

    The formal definition

    Everything above in the language the specification uses, so it can be checked against the document rather than taken on trust.

    IdentifierDLI.VD — venue and asset diversity
    Sits insideDecentralised Liquidity Index, 15% of it
    Window90 days
    Directionpositive / inverse concentration
    Uniteffective diversity count
    ContractCMM-DLI.VD-1.0.0

    x = sqrt[(1 / sum venue_share^2) × (1 / sum asset_share^2)]

    Edition 3.1 §13.6 · registry row at Appendix B.3

    What §13.6 asks for, and what this lane answers

    The equation above is one reading of venue and asset diversity. The specification names six things the component considers, and the evidence held today answers two of them, both in part. Naming the other four is not a caveat added to a finished lane — it is the state of the lane.

    “Liquidity concentrated in one contract, one stablecoin or one external bridge is fragile.” Edition 3.1 §13.6, Venue and asset diversity
    What the specification considersTodayWhy
    independent exchange and lending venues in part Exchange venues only, read from the two swap events a venue emits about itself. No lending market is read. Independence is not established: a venue here is the contract that emitted the swap.
    asset categories and quote assets in part Token contracts are counted as they move to or from the venue. They are not sorted into categories, and the quote side of a pair is not distinguished from the base.
    stablecoin issuer concentration not read Issuers are not resolved from the evidence held. Two stablecoins from one issuer count as two assets.
    oracle and bridge dependencies not read No oracle or bridge evidence enters this lane.
    market-maker or liquidity-provider concentration not read The lane counts swaps at a venue, not who provides the liquidity behind it.
    interoperability across venues not read Routing between venues is not reconstructed.
    “Diversity does not reward redundant forks controlled by the same entity.” cannot be met A venue is a contract that emitted a swap, so two contracts deployed by one party count as two. Where several of those contracts belong to one operator, this overstates diversity. The direction of the bias is named on every row rather than corrected by an assumption, because no clustering evidence exists to correct it with.

    Of the six elements the specification names: two are answered in part and four are not read. The rule beneath them is one the evidence cannot satisfy at all.

    §13.8 adds a further gap. Canonical asset treatment requires that wrapped and bridged assets carry explicit attribution, and that the same underlying liquidity is not counted as independent depth on more than one network. This lane counts token contracts, so a bridged representation of an asset counts separately from the asset it represents. That inflates the asset count in the same direction as the forks problem inflates the venue count, and it is recorded here for the same reason: a figure whose bias is known and stated can be argued with and corrected, and one whose bias is hidden cannot.

    purpose

    Digital value, measured.

    Voxonomics is an open economic measurement standard for understanding what blockchain networks do, how their economies function and what the evidence can support. It brings activity, participation, liquidity, protocol integrity, real-world adoption and resilience into one published method.

    The aim is comparability: ask the same economic questions of different networks, preserve the evidence behind each answer, and make definitions, exclusions and uncertainty inspectable. The framework measures a network economy; it does not treat a token’s market price as a substitute for its economic performance.

    framework

    Six equal perspectives. Thirty canonical submetrics.

    The Value Transfer Score (VTS) brings together six equally weighted parent indices. Each parent has a fixed one-sixth share of the composite and contains five canonical submetrics: 30 in total. Equal parent weights do not mean equal submetric weights; the weights within each parent are fixed by Edition 3.1.

    Definitions are universal. Chain-specific evidence adapters translate a network’s records into those definitions, preserving units, observation windows, exclusions and provenance. An adapter changes how evidence is obtained and interpreted for a chain; it does not relax the economic question to fit the available data.

    six indices

    The questions inside the score.

    PoV · 1/6 of VTS

    Proof of Value

    Verifiable economic activity and value created or transferred through the network.

    • POV.ES — Economic settlement (25%)
    • POV.FR — Fees and protocol revenue (20%)
    • POV.AU — Active economic usage (20%)
    • POV.VC — Value capture and sustainability (20%)
    • POV.PQ — Persistence and activity quality (15%)
    OPI · 1/6 of VTS

    On-Chain Participation Index

    The breadth, persistence and quality of participation in the network economy.

    • OPI.AP — Active participant breadth (25%)
    • OPI.SP — Security participation (20%)
    • OPI.DP — Developer participation (20%)
    • OPI.DR — Distribution and retention (20%)
    • OPI.GP — Governance participation (15%)
    DLI · 1/6 of VTS

    Decentralised Liquidity Index

    Usable liquidity, market depth and diversity, with manipulation and circularity excluded.

    • DLI.ED — Executable depth (25%)
    • DLI.SE — Slippage efficiency (25%)
    • DLI.CR — Concentration and stress resilience (20%)
    • DLI.VQ — Volume quality (15%)
    • DLI.VD — Venue and asset diversity (15%)
    PII · 1/6 of VTS

    Protocol Integrity Index

    Security, effective control, availability, governance and infrastructure integrity.

    • PII.ST — Security track record (25%)
    • PII.CD — Consensus and control decentralisation (20%)
    • PII.AF — Availability and finality (20%)
    • PII.GI — Governance and upgrade integrity (20%)
    • PII.ID — Infrastructure diversity (15%)
    RWAI · 1/6 of VTS

    Real-World Adoption Index

    Verifiable adoption connected to economic activity beyond endogenous crypto speculation.

    • RWAI.RS — Real-world settlement value (25%)
    • RWAI.SP — Stablecoin and payment use (20%)
    • RWAI.TA — Tokenised asset value and quality (20%)
    • RWAI.AD — Adoption diversity and persistence (20%)
    • RWAI.EI — External-verification integrity (15%)
    ERI · 1/6 of VTS

    Economic Resilience Index

    The capacity to retain essential function, absorb shocks and recover.

    • ERI.SR — Shock recovery performance (25%)
    • ERI.AR — Activity retention (20%)
    • ERI.LR — Liquidity retention (20%)
    • ERI.SS — Security-budget sustainability (20%)
    • ERI.TR — Treasury and resource resilience (15%)

    comparison

    A system, not a single headline number.

    Price

    Describes what a token trades for. It can change with sentiment and expectations without a corresponding change in measured network activity. Market recognition is analysed separately from VTS.

    Market capitalisation

    Combines price and a supply definition. It is a valuation observation, not a complete account of participation, productive activity, integrity or resilience.

    Total value locked

    Describes assets classified as locked under a chosen method. Wrappers, repeated collateral and price movements can change the figure; usable liquidity also requires depth, execution quality and diversity.

    Transaction counts

    Describe recorded events. Spam, automation and chain architecture affect those counts; an event count alone cannot establish economic purpose or value.

    Voxonomics

    Connects defined measurements across six dimensions, with explicit evidence, methodology and publication rules. Individual observations can inform a submetric, but none alone stands in for the economy.

    evidence

    Every result needs a traceable path.

    source → preserved evidence → observation → measurement → submetric → parent index → VTS

    A source provides records. Preserved evidence keeps the material needed to check them. An observation states what was found within a defined scope and time window. A measurement applies the specified units, exclusions and calculation. The result contributes to a canonical submetric, then its parent index, and finally the composite when publication requirements are met.

    Source identity, evidence fingerprints, observation windows, adapter and methodology versions, calculation records and exclusions must travel with the result. Missing evidence must remain visible. It is not replaced with an invented neutral value, and a measured native-unit result is not automatically an official score.

    Explore the interactive evidence pipeline or read the public Evidence guide.

    analytical layers

    Performance, recognition, risk and confidence.

    VTS

    Value Transfer Score

    Intrinsic network economic performance, derived from the six equal parent indices and standardised against ERU. It is not a market-price forecast.

    ERU

    Economic Reference Unit

    The dynamic benchmark defining the published reference level of 1.000000. VTS can exceed one. ERU is a unit of measured performance, not a currency peg.

    VRI

    Value Recognition Index

    Market recognition of network fundamentals on a comparable standardised scale. Market valuation is assessed here, separately from VTS.

    Opportunity Gap

    VTS minus VRI

    Compares intrinsic measurement with market recognition. A positive gap suggests under-recognition; a negative gap suggests over-recognition under the model. Interpret it with risk and confidence, not as a guaranteed trading opportunity.

    VRS

    VOX Risk Score

    Summarises structural and operational risk. Higher values indicate greater measured risk; this is separate from economic performance.

    VCS

    VOX Confidence Score

    Measures confidence in data coverage, source reliability, adapter quality, freshness and model certainty. Higher values mean greater confidence; publication status must accompany results.

    implementation

    A complete specification. Evidence built lane by lane.

    Ethereum, Solana and Avalanche are the current implementation focus. They are not the boundary of the universal framework. Additional networks can be measured through adapters that meet the same definitions and evidence requirements.

    The existence of all 30 definitions does not mean all 30 metrics are production-certified on these networks. Implementation, retained evidence, native-unit measurement, calibration and official publication are distinct stages. Coverage and refusals must be read per metric and per network.

    Official VTS publication requires all six official parent indices, the required confidence and the applicable calibration and governance gates. The existing coverage page describes the restored site’s implementation position; its presence in this local preview is not a fresh certification of live runtime status.

    history

    An evolving project, with a clear current specification.

    Voxonomics developed through earlier Polkadot-era proposals and VOX / VOXD material. Those records document the project’s history; they are superseded as descriptions of today’s measurement framework. The current project is universal and chain-agnostic.

    The old five-index model has been replaced by six equally weighted indices. Edition 3.1 replaces the subjective Public Trust Index with Protocol Integrity Index, broadens RWAI from real-world assets to real-world adoption, and adds Economic Resilience Index as an equal parent. It separates intrinsic performance from market recognition and makes evidence confidence and publication rules explicit.

    Final Publication Edition 3.2 is the current public specification. Edition 3.2 adds evidence, storage and Vox-in-a-Box architecture while preserving the Edition 3.1 economics. Old versions, including Edition 3.1, remain available. Historical token proposals do not establish a current token launch. Optional VOX and market layers described in the specification are separate from the measurement framework.

    Read the project history and supersession notice for the relationship between earlier proposals and the current framework.

    reading

    Follow the definitions. Inspect the evidence.

    Contact

    Reaching the people who maintain the standard.

    Voxonomics is a measurement standard, so the useful conversations are specific ones: a definition you believe is wrong, evidence we have not considered, a network that should be in scope, or a governance question about the calibration gate.

    Research & methodology

    Challenge a definition

    Where you believe a submetric misreads what it claims to measure, or where evidence exists that we have refused. Challenges to the method are the reason it is published.

    Governance

    Calibration and approval

    Questions on the parameter packages, the calibration gate, and how a change to the specification is proposed, recorded and approved.

    Networks

    Add a network

    A chain enters by gaining an adapter that can answer the existing definitions. It never enters by relaxing one.

    Press & institutions

    Use the framework

    For research notes, allocation processes or reporting that needs figures somebody else can reproduce and challenge.

    Contactopen
    Research & methodology[email protected]
    Governance & calibration[email protected]
    Press & institutions[email protected]

    A challenge to a definition, or evidence for a figure we refused, goes to the research address and is answered there. Adding a network goes to the same address: a chain enters by gaining an adapter that answers the existing definitions, never by relaxing one.

    The governing principle

    “A refusal is a valid result.”

    Voxonomics engineering constitution — enforced in code, not held as an intention