Dev Update Feb 9, 2026

News and Announcements
1

Dev Update | March 9, 2026

1. Last Week by the Numbers

neptune-core

  • Issues: 2 raised
  • Pull Requests: 1 merged, 2 opened

triton-vm

  • Issues: 1 raised
  • Pull Requests: 1 merged
  • Commits: 1 merged into master

2. Stand-up Summary

Alan Szepieniec

  • Last Week: Contributed to the exchange integration endpoints PR and refactored the UTXO unlock step to be explicit within the transaction pipeline. Enable triton-vm-prover to relay its task to an arbitrary command or binary.
  • Coming Week: Will begin work on the VXB wallet integration pending the final status of exchange endpoints and address outstanding PR reviews.

Thorkil Værge

  • Last Week: Updated exchange integration endpoints to support all required functionality (including coin/amount validation and UTXO claiming). Implemented and integration-tested the send functionality. Resolved race conditions in the transaction initializer and rectified state mutation violations in the RPC server by introducing a personal namespace and enforced mutable self patterns.
  • Coming Week: Primary focus shifts to the VXB wallet. This includes adding a Neptune Core endpoint for transaction publishing rewards and conducting DevOps research into reproducible binary builds via GitHub Actions to ensure user trust.

3. Technical Discussion

State Management and RPC Security

To align with core development principles, the team refactored the RPC server to prevent unauthorized state mutation.

  • Namespace Isolation: A new personal namespace was introduced for node-specific wallet operations.
  • Access Control: These features require the unsafe_rpc flag to be set to true, acting as a guardrail to ensure third-party callers cannot trigger sensitive state changes.
  • Locking Strategy: To eliminate race conditions, a new rule was established: functions may only acquire a global state lock once. This simplifies the complexity introduced by the stake_lock abstraction.

Environment Variable Standardization

To prevent naming collisions and follow best practices, all environment variables within the ecosystem will now be prepended with a standard prefix (e.g., NEPTUNE_).

4. Updates and Announcements

  • Version 0.7 Release: Preparations are underway to publish Neptune Core v0.7. This version marks a significant upgrade over v0.6.1 and will be released following the final merge of the exchange integration PR.