Dev Update: Neptune & Triton
1. Last Week by the Numbers
No GitHub pulse data available for the current period.
2. Stand-up Summary
Alan Szepieniec
- Last Week: Focused on troubleshooting the release protocol after the v0.9.0 activation failure. Managed the deployment of v0.10.0 and v0.10.1 to stabilize the network for the upcoming hard fork.
- Coming Week: Will be stepping back from active development tasks for the month of May due to external professional commitments.
Thorkil Værge
- Last Week: Improved transaction merging logic and auto-consolidation support to optimize block inclusion. Added support for “lustrations” to the official lightweight Neptune wallet. Provided DevOps support for the development of a stateless smartphone application leveraging the UTXO index.
- Coming Week: Implementing a new transaction upgrader rule specifically for merging transactions without fees. Designing a new address format based on community proposals and preparing a technical response regarding the transition back to Nakamoto consensus.
3. Technical Discussion
Hard Fork and Versioning
Critical technical issues with the release protocol necessitated the immediate release of versions 0.10.0 and 0.10.1. These updates are mandatory for all participants to ensure compatibility with the hard fork scheduled for block 38,000 (estimated in approximately one week). The update resolves issues regarding tag persistence and build-task activation failures encountered in v0.9.0.
Transaction Throughput and Merging
To increase network efficiency, improvements were made to how transaction initiators handle merging. A new “upgrader” role is being developed; this operator will focus exclusively on merging transactions to maximize throughput. By operating without charging fees, this role aims to streamline the mempool without increasing costs for users.
Consensus Rationale
The team discussed the technical shift back to Nakamoto consensus. Documentation is being prepared to explain why previous arguments for memory-hard proof-of-work are no longer considered valid in the current architectural context of Neptune Cash, specifically regarding long-term network security and stability.
4. Updates and Announcements
- Hard Fork Warning: All node operators must upgrade to v0.10.1 immediately to remain on the correct chain at block 38,000.
- New Wallet Features: Support for “lustrations” is now live in the lightweight wallet application.
5. Misc
- Policy Change: Going forward, development updates will now strictly focus on Neptune Cash development. Non-technical ecosystem or external marketing content will be filtered; as will any technical discussions relating only to forks.