# Dev Update 9 November 2026

**URL:** <https://talk.neptune.cash/t/dev-update-9-november-2026/428>\
**Category:** News and Announcements\
**Created:** [November 9, 2026, 7:36pm UTC](https://talk.neptune.cash/t/dev-update-9-november-2026/428 "2026-11-09T19:36:39Z")\
**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:** [November 9, 2026, 7:36pm UTC](https://talk.neptune.cash/t/dev-update-9-november-2026/428/1 "2026-11-09T19:36:39Z")

</div>

# Neptune & Triton Dev Update

## 1. Last Week by the Numbers

- [neptune-core](https://github.com/Neptune-Crypto/neptune-core/pulse)
  - Issues: 0 raised, 1 closed
  - Pull Requests: 0 opened, 3 merged
  - Commits: 30 merged into master

## 2. Stand-up Summary

- Alan Szepieniec

- Thorkil Værge

## 3. Technical Discussion

- **Epsilon Software Merge & Activation:** The Epsilon software has been merged into master, establishing succinct block validation. Activation is scheduled for block height **62,500** by the end of the week, with key composers already upgraded. Initial client releases (v0.20 / v0.20.1) will maintain archival validation to preserve continuity without altering default client behavior prior to activation.
- **Incremental Application Succinctness & Syncing Improvements:** Rather than immediately overhauling the full application stack to rely entirely on Epsilon succinct guarantees, the team agreed to an incremental transition. The initial phase shifts the client from requiring all historical blocks up to the tip to verifying archival header sets and managing the archival mutator set up to the tip. This architecture is projected to achieve a 1,000x speedup in sync performance and will support optional downloads of historical blocks without cryptographic proofs.
- **SATA Hard Fork:** A draft pull request will be opened early to allow community review and automated LLM scrutiny. The hard fork is scheduled for activation roughly three to four weeks post-Epsilon merge, targeting block height 70,000. Scope includes migrating chunk data, enforcing archival mutator set tip tracking, and permitting inputs in Coinbase transactions.
- **Coinbase Inputs & Vault Architecture:** To support DeFi vaulting—where liquid Neptune coins are locked in vaults to mint vaulted Neptune tokens—Coinbase transactions must be allowed to consume inputs. The team evaluated alternatives and concluded that modifying transaction validation rules via the SATA hard fork is the cleanest and most robust approach.
- **Parallel DeFi Wallet Daemon:** The DeFi layer will utilize an autonomous daemon operating in parallel to `neptune-core` rather than modifying the desktop wallet. This design provides direct, trusted access to state, manages its own UTXOs, and subscribes to the DeFi plugin hub. It reuses the core `neptune-wallet` crate and supports dual key derivation: standard 24-word seed phrases (SLIP-44) and Neptune Core’s native 18-word format.

## 4. Updates and Announcements

- Epsilon software has been merged, with succinct block validation activating on-chain at block height **62,500**.
- A public draft PR and tracking issues for the SATA hard fork will be published shortly, targeting activation at block height 70,000.