# Dev Update February 2, 2026

**URL:** <https://talk.neptune.cash/t/dev-update-february-2-2026/231>\
**Category:** News and Announcements\
**Created:** [February 2, 2026, 9:54am UTC](https://talk.neptune.cash/t/dev-update-february-2-2026/231 "2026-02-02T09:54:30Z")\
**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 2, 2026, 9:54am UTC](https://talk.neptune.cash/t/dev-update-february-2-2026/231/1 "2026-02-02T09:54:30Z")

</div>

# Dev Update | February 2, 2026

## 1. Last Week by the Numbers

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

- Issues: 5 raised, 4 closed
- Pull Requests: 1 opened, 1 merged

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

- Pull Requests: 1 merged

* * *

## 2. Stand-up Summary

**Ferdinand Sauer**

- **Last Week:** Analyzed STIR and FRI performance metrics across various padded heights. Determined that STIR provides superior proof size benefits for large padded heights but results in larger sizes for smaller ones.
- **Coming Week:** Focusing on improving parameter derivation for the FRI implementation to ensure it is as robust and well-documented as the STIR implementation.

**Alan Szepieniec**

- **Last Week:** [Merged](https://github.com/Neptune-Crypto/neptune-core/commit/cfed34aa128db488d18af9daab76698b334e64c5) the [libp2p branch](https://github.com/Neptune-Crypto/neptune-core/pull/828) to improve network NAT status probing and relay-based peer discovery. Developed the “barrier event” strategy for the upcoming network patch.
- **Coming Week:** Implementing remaining patches, overseeing the rollback to block 23400, and managing the relaunch and UTXO consolidation.

**Thorkil Værge**

- **Last Week:** Implemented the “true claims cache” to handle verification of historical proofs (blocks 0–23400) and introduced a new post-quantum “secret address” format utilizing AES encryption.
- **Coming Week:** Coordinating with Alan on the soft fork/barrier event implementation and further refining the node’s handling of versioned proofs.

* * *

## 3. Technical Discussion

### STIR and FRI Integration

The team has decided to integrate **STIR** into Triton VM as an optional parameter (via an Enum). While **FRI** will be retained, **STIR** is prioritized for its downstream benefits, specifically its ability to accumulate new polynomials from different claims into a running low-degree test. This “Plonkification” of the AIR (Algebraic Intermediate Representation) targets the 90% of verification time previously dominated by AIR evaluation, significantly increasing efficiency.

### Network Recovery & “Barrier Event”

To address the recent vulnerability, the network will undergo a soft fork involving a rollback to block 23400. A “barrier event” will be implemented: transactions will be considered invalid unless they pass through this barrier where amounts are explicitly accounted for. This preserves the UTXO set and guarantees a fixed monetary supply without a full chain reset.

### Addressing and Security

A new “secret address” format has been proposed to provide shorter, post-quantum secure addresses via AES encryption. This is particularly useful for meeting exchange character limits. However, the isogeny-based public address format remains the default recommendation for users due to fewer privacy risks if an address is accidentally leaked.

* * *

## 4. Updates and Announcements

- **Network Rollback:** The chain will be rolled back to block 23400, and will continue from there.
- **libP2P Merger:** The new network stack is live, though the legacy stack remains active for the time being.
- **Secret Addresses:** Support for a shorter, symmetric key address format is being integrated to accommodate third-party requirements.
