Last week by the numbers
neptune-core
neptune-types
neptune-proton
Neptune Happenings
Peer Whitelisting
A feature has just been merged that enables a node to be configured so it will only make or accept connections with a provided list of IPs. This can be useful when multiple nodes share a network connection. One node can act as the bridge while the other nodes connect only to eachother. This prevents bandwidth contention from multiples nodes sending and receiving blocks at the same time over the internet link.
Mempool Bug Fix and Wallet Performance Boost
@sword-smith fixed a bug in the mempool’s handling of reorganizations, specifically addressing an un-cleared field that could lead to invalid data in corner cases. He also significantly improved the wallet’s state update speed, achieving at least a 100x speedup each time a new block arrives. This should be a big win for wallets managing hundreds or thousand of UTXOs. Such nodes would sometimes spend tens of seconds per block checking if the block affects the wallet’s funds.
Wallet Competition Entry Deadline has Passed
The deadline for the wallet competition was Sept 1 2025. The VXB team produced the only submission. Neptune devs will review the wallet’s source code to determine if it is eligible for the prize. Further details will be forthcoming.
Roadmap for neptune-core 0.4.0
A roadmap has been created for the next release. Three of the four major items are complete.
Contributor Updates:
- slides (Introduction to zk-STARKs)
raised some neptune-core patches to reduce sync and mining friction:
- ensure block data written before db to avoid data-store corruption during power-cut.
- make block sync work more reliably on slow link
- add flag --restrict-peers-to-list
- log guessing rate and estimates when mining