Neptune & Triton Dev Update - May 11, 2026
1. Last Week by the Numbers
- Issues: 1 closed
- Pull Requests: 1 opened, 1 merged
- Commits: 5 merged into master
- Issues: 1 closed
- Commits: 1 merged into master
- Commits: 6 merged into master
2. Stand-up Summary
Alan Szepieniec
- Last Week / Coming Week: external project commitments.
- On the side: public technical communication on Telegram/forums; preparing a technical presentation on Tip5.
Thorkil Værge
- Last Week: Successfully implemented “cold mining” in Neptune Core, allowing for secure block production without hot-key exposure. Developed a new post-quantum secure address format and introduced “viewing keys” for granular transaction visibility. Managed upstream dependency updates, reducing security vulnerabilities by 90%.
- Coming Week: Finalizing the merge for the new address format (working title “secret address”); investigating technical solutions for mining pool decentralization; overseeing the scheduled hard fork.
Ferdinand Sauer
- Last Week: Attended the ZK Summit to gather competitive intelligence and architectural ideas; researched Miden VM’s implementation of specific features relevant to Triton VM.
- Coming Week: Re-orienting at the office to align on Triton VM development priorities; beginning work on zero-knowledge functionality and evaluating TIP 10 ROI.
3. Technical Discussion
Cold Mining & Security
The implementation of cold mining in neptune-core now supports all three revenue streams: composing, guessing, and proof upgrading. This architectural shift significantly hardens node security by keeping secret keys offline. Additionally, a major cleanup of upstream dependencies was completed, mitigating the vast majority of inherited security vulnerabilities. One remaining high-priority patch is being finalized to prevent potential node-crash vectors.
Post-Quantum Secure Addressing
A new address format has been designed to provide post-quantum resistance, assuming address secrecy is maintained. This format supports QR code integration and utilizes “viewing keys.” These keys allow for the decryption of incoming/outgoing messages to verify fund transfers without granting the ability to spend funds or view full transaction history, offering a balance between privacy and auditability.
Triton VM Priorities: STIR vs. FRI
The team reached a consensus that the zero-knowledge mechanism is the top priority for Triton VM, followed by WASM support. There was a technical debate regarding the implementation of STIR in TASM. The immediate performance gains of STIR remain unverified compared to existing methods.
Upcoming Hard Fork
A hard fork is scheduled for Tuesday. Testing has been completed, and the primary objective is to maintain long-term system stability. The neptune-explorer has been updated to track the “lustration status” and counter in real-time following this transition.
4. Updates and Announcements
- Scheduled Hard Fork: Tuesday, May 12th.