This page is the central comparison layer for the VTA Benchmark project. It intentionally does not assign an overall winner. Documented protocol characteristics are shown separately from measurements that still need to be collected under identical conditions.
Compare consensus parameters and architecture using pinned source/document evidence.
Collect actual block, fee, confirmation and network measurements with timestamps and methodology.
If a metric cannot be independently measured, it remains “Not measured” rather than receiving an estimated value.
| Metric | VTA | Bitcoin | Evidence / interpretation |
|---|---|---|---|
| Block target | 60 sec (VTA paper/source) | ~600 sec average design target | Source-defined; not a live performance result |
| Proof of Work | Scrypt | SHA-256 / double-SHA-256 | Algorithm difference alone does not prove overall security |
| Difficulty adjustment | Per-block after VTA transition | 2016-block adjustment interval on Bitcoin mainnet | Consensus design comparison |
| Actual block interval | Measure from timestamp samples | Measure from timestamp samples | Requires equal sample methodology |
| Transaction fee | Measure | Measure | Same transaction-size/fee conditions required |
| Confirmation latency | Measure | Measure | Broadcast-to-confirmation test required |
| Reorg / stale blocks | Measure | Measure | Requires historical/live chain sample |
| Network propagation | Measure | Measure | Requires multi-node timestamp collection |
| Node synchronization | Measure | Measure | Requires clean-node controlled test |
| Code / validation | Audited | Audited separately | Do not reduce code complexity to a single score |
Collect consecutive block timestamps and calculate mean, median, P95, standard deviation and interval distribution.
Use matched transaction sizes and record absolute fee, fee/byte and confirmation delay.
Run identical broadcast-to-confirmation experiments and publish 1, 2, 3 and 6-confirmation timing.
Measure observed stale/orphan blocks and reorganization depth from reproducible chain samples.
Use controlled multi-node timestamp collection to estimate block propagation behavior.
Run clean disposable nodes and record download time, bandwidth, CPU, RAM and disk activity.