# Dev Update 13th May, 2025

**URL:** <https://talk.neptune.cash/t/dev-update-13th-may-2025/61>\
**Category:** News and Announcements\
**Tags:** dev-updates\
**Created:** [May 13, 2025, 4:44am UTC](https://talk.neptune.cash/t/dev-update-13th-may-2025/61 "2025-05-13T04:44:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![neptune-team](https://talk.neptune.cash/user_avatar/talk.neptune.cash/neptune-team/32/18_2.png) [@neptune-team](https://talk.neptune.cash/u/neptune-team)\
**Post date:** [May 13, 2025, 4:44am UTC](https://talk.neptune.cash/t/dev-update-13th-may-2025/61/1 "2025-05-13T04:44:37Z")

</div>

![banner](https://talk.neptune.cash/uploads/default/original/1X/0fc55a840dae83fe6f9450838709887959af7da4.jpeg)

This week saw [3 merged pull requests](https://github.com/Neptune-Crypto/neptune-core/pulls?q=is%3Apr+is%3Aclosed+is%3Amerged+merged%3A2025-05-05..2025-05-12). These primarily address reported crashes, in particular:

1. [#568](https://github.com/Neptune-Crypto/neptune-core/issues/568) – Node Crashes Upon Startup – when resynching membership proofs.
2. [#579](https://github.com/Neptune-Crypto/neptune-core/issues/579) – “job cancelled by caller” error while composing causes panic or shutdown

@sword-smith is back from holiday and has jumped into some benchmarking and performance optimizations.

### Mempool redesign

@jfs dedicated their efforts to refining the design of the new mempool, building upon the progress made the prior week. This iteration of the design incorporates insights from established blockchain projects such as Bitcoin and Monero. However, Neptune’s distinct approach to cryptocurrency necessitates a tailored solution, as existing designs cannot be directly adopted. For instance, Neptune uniquely features three-stage mining, a characteristic not found in other cryptocurrencies. Nonetheless, understanding the fundamental design principles of other systems provides valuable context for defining the scope and responsibilities of Neptune’s new mempool, thereby bolstering our confidence in its architecture. The work is now transitioning to a more technical level, as illustrated by the API suggestion, and will continue in the coming weeks.

Contributor updates:

@aszepieniec

- work on `RemovalRecordList`
- discuss and finish up [twenty-first PR #251](https://github.com/Neptune-Crypto/twenty-first/pull/251)
- discuss and synthesize [roadmap](https://talk.neptune.cash/t/informal-roadmap/56/2)
- articulate thoughts regarding the [mempool issue and upgrading](https://talk.neptune.cash/t/thoughts-on-the-mempool-issue-and-upgrading/52)

@danda

- finished and merged #579 “job cancelled by caller” error while composing causes panic
  - continue composing if job-cancelled error occurs
  - enables proving job-cancellation to work in test environment
  - add mine\_loop tests for job cancellation
  - job\_queue::JobHandle improvements (works like tokio JoinHandle)
  - reorganization job\_queue: split queue.rs and move triton\_vm

- merged PR #584: improve job\_queue ergonomics
  - follow on to 579.
  - provides detailed job-queue usage examples and makes it much easier to work with job-results. (no need to downcast)

@jfs

- PR reviews & development comments
- discuss Merkle tree & MMR indexing
- discuss roadmap
- mempool
  - read up on Monero’s, Bitcoin’s, etc. mempool design & code
  - flesh out & write up API proposal