HomeVTA vs BTCDashboardLive MonitorNetwork EvidenceBlock ExplorerAnalyticsMethodology
RESEARCH STANDARD

How VTA Benchmark Measures

A transparent workflow for turning blockchain observations and documented protocol claims into reproducible benchmark records.

The 5-step workflow

Every benchmark should be traceable from its definition to its source and limitations.

Step 1

Define

Specify exactly what is being measured, the unit, population, time window and comparison rule.

Step 2

Collect

Use the VTA Core local node, documented sources, Bitcoin reference sources, or identified APIs/explorers.

Step 3

Normalize

Keep units, timestamps and sampling conditions consistent. Do not turn missing data into estimates.

Step 4

Verify

Cross-check hashes, timestamps, block heights and protocol claims where possible.

Step 5

Publish

Show the result together with source, methodology, sample size and limitations.

Current VTA evidence

The live VTA measurements shown on this site can come from a local Virtacoin Core node through the HTTPS bridge. These measurements are explicitly labelled as local node evidence.

A local node snapshot is not automatically a network-wide measurement. If a verified public network source is unavailable, the site keeps the network-wide field unavailable rather than estimating it.

Comparison rules

  • Documented protocol parameters are separated from current measurements.
  • Timestamps and sample sizes accompany live observations.
  • Missing data remains missing.
  • Algorithm choice alone is not treated as proof of security or payment superiority.
  • Conclusions should state the measurement conditions and limitations.

Source hierarchy

The project distinguishes between primary project documentation, local node measurements, identified network sources and secondary references.

VTA technical paper: the uploaded VirtaCoin paper documents a Scrypt proof-of-work design, a 60-second target and per-block difficulty retargeting. Those statements are historical documentation; current network conditions are measured separately.
Local node: block height, difficulty, best-block hash and block metadata received from the user's local VTA Core RPC are stored as typed evidence.
Network-wide data: only published when an independently verified current source is available.