308,330 replays · 8784 open divergences
Reference-validated
Rust TVM for TRON
tvm-rs is a Rust implementation of the TRON Virtual Machine, continuously validated against java-tron through deterministic corpus replay.
tvm-rs compatibilitylive
Corpus replays308,330
Exact matches299,546
Open divergences8784
Golden fixtures38
Compatibility
Every fixture is captured from java-tron and replayed independently by tvm-rs.
Corpus Replays
308,330
Pass
299,546
Diverged
8,784
Status Match
99.80%
Output Match
99.90%
Log Match
99.80%
Internal Tx Match
97.75%
State Diff Match
99.59%
Energy Match
99.63%
Energy Delta
0.37%
of evaluated
How validation works
Execution data flows from the reference implementation to an independent replay.
java-tron
Reference implementation
Corpus Recorder
Capture VM execution
VM Fixture
Portable deterministic input
CorpusDb
Standalone pre-state
tvm-rs
Rust VM replay
Compare
Result + state diff
java-tron
Reference implementation
Corpus Recorder
Capture VM execution
VM Fixture
Portable deterministic input
CorpusDb
Standalone pre-state
tvm-rs
Rust VM replay
Compare
Result + state diff
Reference vs Implementation
java-tron is not a runtime dependency — it is a reference source.
java-tron
Reference implementation
- —Executes the original TRON VM
- —Captures VM-visible pre-state
- —Produces expected execution results
- —Used only as compatibility reference
Fixture
tvm-rs
Rust implementation
- —Executes fixtures independently
- —Strict state access through CorpusDb
- —Reproduces logs, output and state changes
- —Reports deterministic divergences
tvm-rs does not call java-tron during replay.
Capture once. Replay independently.
What we compare
tvm-rs covers VM execution scope. Executor-level concerns belong to throg.
tvm-rs·VM scope
- Execution status
- Return data
- Energy used
- Logs
- Internal transactions
- VM state diff
throg·Executor scope
- Bandwidth
- Stake / delegation
- Energy acquisition
- Fee settlement
- Burn
- Block processing
Projects
Rust infrastructure for TRON.