VTA Benchmark
Research Methodology

Benchmark Methodology & Evidence

A reproducible framework for collecting, checking and publishing VTA and Bitcoin benchmark observations. Protocol documentation, local-node measurements and network-wide measurements are kept as separate evidence classes.

01DefineSet the exact metric and test condition.
02CollectCapture raw observations and source details.
03NormalizeUse consistent units and sample definitions.
04VerifyCheck source, timestamps and reproducibility.
05PublishShow results with their evidence status.
06RepeatKeep timestamped history for later comparison.

Evidence classes

Documented design
Claims taken from a named protocol paper, specification or software source.

Verified local measurement
Observed directly from a configured VTA Core node. These values describe that node at the recorded time.

Network-wide measurement
Requires an independently verified public source or sufficiently broad measurement method. If unavailable, the value remains unavailable.

Publication rules

Every live value should carry a timestamp, unit, source and measurement context.

Historical protocol statements are not silently converted into current network facts.

Unavailable measurements remain unavailable; the benchmark does not estimate missing values.

Test Matrix

How each benchmark is measured

Confirmation Latency

Measure the observed time from a broadcast transaction to the defined confirmation condition.
Evidence-driven
Method
Record transaction broadcast time, block inclusion time, and the confirmation depth used by the test. Repeat across samples and report the raw observations.
Required evidence
Transaction ID, source node/explorer, block hash/height, timestamps, sample count.
Rule: Do not convert a target block interval into an observed confirmation result.

Transaction Fee

Compare the actual fee paid for a defined payment transaction.
Evidence-driven
Method
Capture the transaction fee from the transaction data and record the transaction size/weight metric used by the network. Keep transaction type and sample conditions explicit.
Required evidence
Transaction ID, fee amount, size metric, timestamp, source.
Rule: A protocol statement about low fees is not a measured fee sample.

Block Production

Measure observed block-to-block timing from timestamped chain data.
Evidence-driven
Method
Collect consecutive verified block heights and timestamps, then calculate intervals from the recorded observations.
Required evidence
Block heights, block hashes, timestamps, sample window, source.
Rule: Target block time and observed average block interval must be shown separately.

Difficulty Adjustment

Document the adjustment mechanism and, where data exists, observe actual difficulty changes.
Evidence-driven
Method
Separate protocol documentation from live measurements. For VTA, the uploaded 2015 paper describes per-block retargeting; current network-wide behavior requires independently verified chain data.
Required evidence
Protocol source, block/difficulty samples, timestamps, source endpoint or local node.
Rule: Historical documentation is not presented as a current network measurement.

Network Security

Document security-relevant architecture and collect measurable network evidence where available.
Evidence-driven
Method
Record proof-of-work algorithm, adjustment rules, chain observations, node connectivity and other reproducible evidence. Avoid assigning a security score without a defined empirical test.
Required evidence
Protocol source, node observations, block data, test procedure and timestamps.
Rule: Architecture alone does not establish a quantitative security level.

Codebase Audit

Trace consensus, transaction validation, networking, wallet and mining logic to a specific software version.
Evidence-driven
Method
Freeze the version, map relevant components, inspect implementation, reproduce behavior where practical, and record exact source locations.
Required evidence
Repository/version, commit or release, file/function references, test result.
Rule: Do not generalize from an old release to an unspecified current codebase.

Payment & Settlement

Evaluate the operational steps involved in making and verifying a payment.
Evidence-driven
Method
Define the payment scenario, record broadcast/inclusion/confirmation events, capture fees and document merchant-side verification steps.
Required evidence
Transaction record, timestamps, confirmation rule, fee, verification workflow.
Rule: Fast settlement must be demonstrated with measurements under a stated confirmation policy.

VTA source note

The uploaded VirtaCoin technical paper is dated December 14, 2015 and describes VTA as a proof-of-work cryptocurrency using Scrypt. It documents a 60-second target block interval and describes difficulty retargeting on every block. Those statements are treated here as historical documented design, not as current network measurements.

The current VTA pages separately report measurements received from the user's local VTA Core through the HTTPS bridge. A local-node value is explicitly labeled as local and timestamped.

Important: A benchmark result is only comparable when the test conditions, sample window, source and units are stated. A missing network source should produce an “Unavailable / Not verified” state rather than an estimated number.