The team is delighted to introduce the new Rostrum 14.0.0 release. In this upgraded version, you’ll find a new database layout along with a switch to postcard serialization, and more updates. If you use Rostrum, the index must be rebuilt. Please explore further details below and in the releases section of the Rostrum Gitlab.
Rostrum Gitlab:
https://gitlab.com/nexa/rostrum
What’s New?
This release includes database changes that require rebuilding the index. At first run after the upgrade, rostrum will trigger this reindex automatically. The reindex is required due to both a new database layout and the switch from bincode to postcard serialization.
New Features
- New RPC: blockchain.*.get_first_spend — look up the first spend of an output
- RPC improvement: Allow passing NULL to blockchain.*.get_history for more flexible queries
- RPC editions: Clients can opt in to new protocol editions via the server.version, enabling non-backward-compatible improvements while maintaining compatibility with existing clients. The first edition 2027-pre changes blockchain.*.get_first_use to return null instead of an error when no transactions are found
- Scripthash subscription manager: Improved internal handling of scripthash subscriptions
- Debug option: Added switch to skip blocks when indexing (for development/debugging)
- Built-in SSL/TLS Support: Native SSL/TLS support for TCP, WebSocket, and HTTP endpoints
Performance
- Switch from bincode to postcard serialization (actively maintained, comparable performance)
- Switch to a faster statushash algorithm.
- Improve transaction history performance.
- Batch lookup outpoints when erasing unspent outputs.
- Prune OutToScripthashIndex for improved efficiency.
Maintenance
- Bump dependencies
- Bump Rust version
- Improve header recovery
To Sum Up
There is already a patch for Rostrum 14.0.1 available, released just after the initial 14.0.0 release, with a fixed broken lock file and updated dependencies. All Rostrum users, please update to the latest release.
If you have any suggestions or feedback, please use the Gitlab issues section or join Nexa community groups and channels, and inform the community moderators.