Triton VM<p>Triton VM is a STARK engine, featuring a virtual machine, a prover, and a verifier.</p>
https://talk.neptune.cash/inn/22023-08-10T06:34:28+00:00announcing Triton VM v0.33.0jfs2023-08-102023-08-104
<p><a href="https://github.com/TritonVM/triton-vm/releases/tag/v0.33.0" rel="noopener noreferrer">Triton VM v0.33.0</a> is now live. The main highlights are:</p>
<h3>Non-deterministic Initialization of RAM</h3>
<p>In all prior versions, the only way for programs to receive input was through public or secret input, i.e. using instructions <code>read_io</code>, <code>divine</code>, or <code>divine_sibling</code>. As of this version, RAM can be initialized before Triton VM starts execution. This means that elements that <em>might</em> need to be processed don’t waste precious clock cycles if they don’t end up being processed, as they can happily live in RAM without ever being read.</p>
<p>In future versions of Triton VM, non-deterministic RAM initialization might also be useful to place objects in RAM that depend on the current state of the VM. The zero-knowledge proof system already supports this behavior.</p>
<h3>Improved Speed</h3>
<p>Through changes to the proof system, better use of parallelization, and more efficient initialization of certain memory objects, the speed of the VM has increased noticeably. Depending on the hardware, the speedup factor should lie somewhere between 3 and 4 compared to the previous version, and almost 10 compared to the version that shipped with the initial release of Neptune’s alphanet.</p>