# Dev Update 29 June 2026 **URL:** \ **Category:** News and Announcements\ **Created:** [June 29, 2026, 1:17pm UTC](https://talk.neptune.cash/t/dev-update-29-june-2026/341 "2026-06-29T13:17:37Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [June 29, 2026, 1:17pm UTC](https://talk.neptune.cash/t/dev-update-29-june-2026/341/1 "2026-06-29T13:17:37Z")
## 1. Last Week by the Numbers _No GitHub pulse data available for this week._ * * * ## 2. Stand-up Summary ### Thorkil Værge - **Last Week:** Resolved an issue where transaction proof upgraders accumulated an ever-growing queue of jobs by updating the logic to check queue length before starting new jobs. Progressed on refactoring the `neptune-core` monolith into smaller crates (separating the mutator set, job queue, locks, consensus, and application). - **Coming Week:** Flag and prioritize urgent pull requests needing immediate attention. Submit the crate separation pull request, ensuring no tests are compromised, and keep it open for 1 to 2 days for team review. Focus entirely on the crate separation work and defer the RPC migration. ### Alan Szepieniec - **Last Week:** Participated in architectural discussions regarding the RPC framework and suggested implementing feature flags to optimize compilation times (e.g., gating and disabling the JSON RPC when wallet support is not needed). - **Coming Week:** Conduct scheduled high-level reviews. Document an explicit architecture proposal for using Tarpc for the Neptune CLI and JSON RPC for all other services. Refresh explore.neptune.cash with the latest features from the Neptune Explorer. * * * ## 3. Technical Discussion ### Neptune Core Crate Separation To achieve an expected 2x improvement in compilation times, the team aligned on separating the `neptune-core` monolith into smaller, distinct crates while maintaining a single repository structure to avoid maintenance overhead. This refactoring isolates components—specifically the mutator set, job queue, locks, consensus, and the application layer—preventing downstream dependencies from unnecessarily importing the network stack. ### RPC Framework Strategy & Compilation Optimization The team debated the consolidation of the RPC layer. While a total migration to JSON RPC was considered, the current open proposal stands to retain Tarpc specifically for the Neptune CLI binary and deploy JSON RPC for all other interfaces (such as the dashboard). It was noted that Tarpc’s large macro significantly impacts compilation times. To further optimize compilation performance, implementing feature flags to gate and disable specific components (like the JSON RPC when wallet support is extraneous) remains under consideration. ### Transaction Proof Upgrading Logic An issue causing transaction proof upgraders to accumulate an expanding backlog of obsolete work was resolved. The queue logic was modified to check the queue length before initiating new jobs, effectively preventing the processing of older, redundant tasks. ### Neptune Explorer Features and Domains New features were introduced to the Neptune Explorer to satisfy exchange integration requests for tracking customer payouts. Users can now view lustration amounts and utilize an output tracking feature to verify whether a transaction output addition record exists in the canonical chain or the mempool. Structurally, explorer domains will remain separate, keeping [neptunefundamentals.org](http://neptunefundamentals.org) independent rather than merging it with other explorer domains. * * * ## 4. Updates and Announcements - The [neptunefundamentals.org](http://neptunefundamentals.org) site has been updated with the latest project features. - An update to explorer.neptune.cash is planned to integrate the newest features from the Neptune Explorer. ---
**Author:** ![skaunov](https://talk.neptune.cash/user_avatar/talk.neptune.cash/skaunov/32/90_2.png) [@skaunov](https://talk.neptune.cash/u/skaunov)\ **Post date:** [July 5, 2026, 6:15pm UTC](https://talk.neptune.cash/t/dev-update-29-june-2026/341/2 "2026-07-05T18:15:02Z")
What is affected by compilation time? And can be same effect achieved just via features? To me crates fracturing feels like further complicating the thing. Now it’s about getting the modules right, and it gets to be scattered across the crates. I would better see the dash-board and the CLI crates in single Neptune crate with the core, and just feature toggled. I mean I’m probably wrong on this, but I’d like to get how. 🙃 ---
**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:** [July 6, 2026, 2:58pm UTC](https://talk.neptune.cash/t/dev-update-29-june-2026/341/3 "2026-07-06T14:58:08Z")
Unless I’m mistaken, you can track the branch in question [here](https://github.com/Neptune-Crypto/neptune-core/pull/941). I look forward to reading your feedback.