The benchmark's VTA Core node reported client version 2.9.1.0 (numeric version 2090100).
The same local node reported protocol version 70002.
No complete release-by-release consensus activation timeline is claimed here without exact tagged commits and activation conditions.
| Area | Finding | Status |
|---|---|---|
| Client version | Local VTA Core node reported v2.9.1.0 / numeric version 2090100. | Verified local observation |
| P2P protocol version | Local node reported protocol version 70002. | Verified local observation |
| Version-to-consensus equivalence | A client version number by itself does not establish which consensus rules differ from another release. | Audit rule |
| Protocol handshake compatibility | The source must be traced through version negotiation, peer admission and message handling for a release-specific compatibility claim. | Not fully traced |
| Consensus activation | Exact activation heights/timestamps/version bits or equivalent mechanisms require release/tag-specific source evidence. | Not fully verified |
| Hard-fork compatibility | No claim is made that all VTA releases are mutually compatible; this requires a release matrix and historical chain replay. | Not measured |
| Soft-fork compatibility | No activation timeline is asserted without exact historical source and chain evidence. | Not measured |
| Chain replay test | No full historical replay across multiple VTA software versions was performed by this page. | Not measured |
| Network-wide upgrade adoption | No current peer-version census is claimed. | Not measured |
Record exact release/tag/commit hashes before comparing consensus behavior.
Identify the actual height, timestamp, block version, or other activation condition in source and chain history.
Run old and new implementations against the same historical blocks to detect divergent validation results.