# Dev Update February 9, 2026

**URL:** <https://talk.neptune.cash/t/dev-update-february-9-2026/233>\
**Category:** News and Announcements\
**Created:** [February 9, 2026, 12:11pm UTC](https://talk.neptune.cash/t/dev-update-february-9-2026/233 "2026-02-09T12:11:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aszepieniec](https://talk.neptune.cash/user_avatar/talk.neptune.cash/aszepieniec/32/5_2.png) [@aszepieniec](https://talk.neptune.cash/u/aszepieniec)\
**Post date:** [February 9, 2026, 12:11pm UTC](https://talk.neptune.cash/t/dev-update-february-9-2026/233/1 "2026-02-09T12:11:05Z")

</div>

## Dev Update | Neptune & Triton Projects

### 1. Last Week by the Numbers

[neptune-core](https://github.com/Neptune-Crypto/neptune-core)

- Issues: 8 raised, 1 closed
- Pull Requests: 3 merged
- Commits: 26 merged into master

[triton-vm](https://github.com/TritonVM/triton-vm)

- Issues: 1 closed
- Commits: 1 merged into master

* * *

### 2. Stand-up Summary

**Thorkil Værge**

- **Last Week:** Proposed wallet optimizations via membership proof exclusion; collaborated on network relaunch utilizing a true claims cache and the updated Triton VM version.
- **Coming Week:** Currently on vacation; plans to test the archival mutator set approach for wallet updates upon return to evaluate code reduction.

**Ferdinand Sauer**

- **Last Week:** Advanced the reintegration of FRI into the STARK implementation, allowing users to toggle between STIR and FRI; enhanced the FRI verifier with transcript returns for Triton assembly compatibility. Initiated parameter derivation changes using the new conjectured bound.
- **Coming Week:** Resolving implementation bugs in parameter derivation; will provide statistics on parameter changes for 160-bit security (specifically opening counts) and target a PR merge following a final review.

**Alan Szepieniec**

- **Last Week:** Successfully relaunched the network in production using the checkpoint (block 23,041) claims cache. Identified a bug in the auto-consolidation mechanism causing balance mismatches on the dashboard.
- **Coming Week:** Focused on fixing the auto-consolidation balance bug; performing a content review of the Proof of Payment/Reserves PR; and implementing the new address format.

* * *

### 3. Technical Discussion

**FRI & STIR Integration**  
Significant progress was made on the STARK implementation to allow flexibility between the **FRI** and **STIR** protocols. A key technical requirement involved updating the **FRI** verifier to return a transcript, ensuring parity with the **STIR** verifier. This alignment is critical for the proper population of nondeterminism within the Triton assembly implementation.

**Parameter Derivation & Conjectured Bound**  
The team is currently transitioning parameter derivation to utilize a new conjectured bound. While currently blocked by minor implementation bugs, the shift is expected to slightly impact the number of “openings” required for 160-bit security, which in turn impacts proof size.

**Wallet & Network Optimization**  
To address performance bottlenecks for high-volume users (exchanges/mining pools), a proposal is on the table to ignore membership proofs in favor of the archival mutator set. On the networking front, the relaunch successfully utilized a true claims cache—effectively telling the Triton verifier which claims to accept based on the pre-populated checkpoint.

* * *

### 4. Updates and Announcements

- **Network Relaunch:** The network is officially live again following the release of[`neptune-core v0.6.0`](https://github.com/Neptune-Crypto/neptune-core/releases/tag/v0.6.0).
- **Checkpoint Established:** The production environment is now utilizing a true claims cache that is pre-populated with the claims induced by the first 23,401 blocks. These blocks are simply defined to be valid.
- **Upcoming Content:** A recording of the “Transactions in Neptune Cash” presentation is planned.
