Dev Update 17 June, 2025

Last week by the numbers

neptune-core

twenty-first

proof-server

triton-vm

Neptune Happenings

Wallet Prototype Kickoff

@danda has begun work on a cross-platform wallet prototype built with the dioxus framework. The goals of this prototype are to:

  1. create a basic wallet that is usable on mobile (Iphone, Android), desktop (Linux, Mac, WIndows), and possibly the web, using neptune-core RPC APIs.
  2. Identify and resolve problem areas for wallet developers to help smooth the path for more wallet development.
  3. explore the overall architecture for how wallets interact with neptune-core in order to eventually implement more advanced wallet functionality, and perhaps one day a “light” wallet that does not rely on neptune-core at all.

Already it is apparent there is a need to place the types used by the RPC API into a separate crate for use by wallets that use webassembly and can’t have the neptune-cash crate as a dependency. Work on that begins this week.

This prototype wallet is still in a nascent state. Once it is published to the neptune project’s github repo, community members are invited to fork it and create their own improved wallets for the wallet competition, or any other purpose.

Triton VM Proof-Generation Speedup

@jfs and @sword_smith did some optimization of the number theoretic transform resulting in a roughly 40% speedup of the function itself, translating to about an 8.5% speedup in Triton VM proving. This improvement primarily involves caching.

Dual Licensing Triton VM

There has been discussion of dual-licensing Triton VM under MIT and Apache 2, noting that while they are both permissive, MIT is compatible with GPL2, while Apache 2 is not. Triton VM is currently (and has always been) licensed under Apache 2. Dual-licensing is common for similar projects. Since no concerns could be identified, Triton VM is now dual-licensed under both MIT and Apache 2.

Mempool Improvements

@sword_smith has been working to improve the mempool logic, particularly how it handles new blocks and transaction updates. He has simplified the processing of mempool transactions after a new block is received. This should benefit weaker computers in getting transactions onto the blockchain. A related PR is expected soon. Conversations with @jfs helped move this development forward.

More Frequent Releases

The team has received community feedback about releasing new versions more often to make new features accessible without relying on the master branch. The team is working towards a new release before the hard fork and will make efforts to release more often on an ongoing basis.

Contributor Updates

@aszepieniec

  • slides for upcoming presentation
  • PR reviews and shepherding
  • hard fork 2

@sword-smith

  • Support @jfs in faster NTT
  • Support @aszepieniec in hard-fork 2 work for better transaction throughput.
  • Improve mempool handling for more reliable transaction initiation.

@jfs

  • speed up NTT
  • various code maintenance tasks

@danda:

  • began wallet prototype with dioxus framework
  • made a basic tabbed interface for wallet, set of screens.
  • made a desktop view and simulated “mobile” view, and a toggle.
  • implemented balance and block_height APIs, so real data is displayed in wallet.