Dev Update 2026-06-01

News and Announcements
1

Dev Update — June 1, 2026

1. Last Week by the Numbers

Note: GitHub pulse data is unavailable for this week. No repository activity metrics are recorded.

2. Stand-up Summary

Thorkil Værge

  • Last Week: Announced the successful release of version 0.11, introducing two address formats (a viewing address revealing the AES key and an elliptic curve key exchange variant).
  • Coming Week: Integrating these new address formats directly into the Neptune wallet application.

Alan Szepieniec

  • Last Week: Reviewed the new address formats and confirmed their soundness. Reviewed the univariate batching mechanism and returned it to the team for revision due to soundness uncertainties.
  • Coming Week: Continuing engineering and soundness reviews while balancing external commitments.

Ferdinand Sauer

  • Last Week: Implemented the univariate batching mechanism and its supporting instructions. Started integrating the current development branch of Triton VM into the TASM library.
  • Coming Week: Incorporating Alan’s review feedback into the univariate batching pull request and shifting focus toward implementing TIP 10.

3. Technical Discussion

Version 0.11 Address Formats

The version 0.11 release introduces a critical architecture upgrade featuring two distinct address formats:

  1. A Viewing Address that directly exposes the AES key for encrypting notifications.
  2. An Elliptic Curve Key Exchange Address that conceals the AES key assuming the absence of quantum adversaries (and in the presence of quantum adversaries, is no less secure than viewing addresses).

Univariate Batching & Triton VM Upgrades

The team evaluated the soundness of the newly proposed univariate batching mechanism. This process is designed to execute prior to the low-degree test (STIR or FRI). The introduced instructions modify the existing dot_step instructions, ensuring full system functionality even if subsequent instruction optimizations face delays.

Currently, the TASM library aligns with Triton VM version 3, which lacks STIR, a proof of Zero Knowledge, and univariate batching.

Project Prioritization & Pipeline

A technical consensus was achieved to prioritize core Triton VM development over immediate TASM code updates. The sequential pipeline for upcoming milestones is established as follows:

  1. Complete the technical implementation of TIP 10.
  2. Implement “funky instructions” (specialized operations designed to compress and hash rows simultaneously without hitting memory).
  3. Revise the recursive verifier inside the TASM code once Triton VM master stability is achieved.

4. Updates and Announcements