Over the last three months, work across the Nexa ecosystem focused on two big themes: shipping visible product improvements, especially around wallet UX, app integrations and strengthening the foundations that keep everything reliable (CI/build stability, indexing correctness, clearer specs, and better dev tooling). Below is a consolidated overview by project, with each item tagged by month.
Otoplo-wallet
Another Otoplo release is now available on all platforms, including both desktop and mobile versions. Users are encouraged to update their wallets to the latest Otoplo 5.1.0 version to benefit from the newest improvements and a more streamlined experience. This release introduces several optimizations and unifies the app across all platforms.
Download now:
https://otoplo.com/download
For the full Otoplo 5.1.0 announcement: Otoplo Wallet Update: New Release 5.1.0
Libnexaapp
-
Added Lottie support so apps can use modern, lightweight animations more easily.
-
Standardized how app links are opened (deep links / external link flows) so behavior is more consistent across platforms.
-
Sharing support (tdpp) was added, making it easier for apps using the library to share that artifact/data flow.
-
Dependencies were bumped and an Android packaging issue was fixed, improving Android build reliability for downstream consumers.
-
“Derived design schemes” work landed, pointing toward more consistent theming outputs and reduced design maintenance across platforms.
Libnexa-ts
-
Browser support was added and the project moved to ESM-only, which aligns better with modern web tooling and reduces integration friction.
-
Dependencies were updated and published TypeScript types were improved, which usually means better autocomplete, compile-time safety, and fewer surprises for integrators.
Nexa explorer
-
Address handling was simplified by removing unnecessary validation fields, reducing duplicated logic and lowering the chance of subtle validation inconsistencies.
-
Work related to valid scriptSigs / script pubkeys improved correctness in how spends and address interactions are represented.
-
Address analytics plus caching were added, improving performance and responsiveness for repeat lookups and frequently viewed pages.
Nexa specification
-
Script templates and examples were expanded/updated, making it easier for builders to implement scripts correctly.
-
The spec site got a small but noticeable polish pass (footer navigation, favicon, and logo), which makes it nicer to browse when you’re using it regularly.
-
The TDPP section was cleaned up to remove confusing bits and make it clearer what wallets and apps are expected to do.
-
A new Scriptlet definition/section was added so implementers have a clearer reference and fewer “guesswork” moments when building.
-
“Fund groups” and DPP pay transaction request docs were added/clarified (including better flag formatting), which helps integrators implement the flow more correctly the first time.
Nexa core
-
CI alignment and maintainability improvements landed (including rostrum-related CI alignment), helping ensure the core stays compatible with its surrounding infrastructure and keeping the pipeline trustworthy.
-
Qt was updated (5.15.x line), improving long-term maintainability and typically strengthening stability/security posture for Qt-dependent builds.
-
Shutdown and global naming cleanup reduced complexity and the risk of subtle issues (simplified shutdown behavior; removed confusing naming collisions).
-
Recent Alpine/GCC toolchain changes were causing build headaches, so the build setup was adjusted to use the right standards and the “depends” stack was fixed up (including Berkeley DB). The result is more reliable, reproducible builds and fewer issues for contributors setting things up.
-
Node behavior was hardened in an edge case where a peer requests a block/subblock that isn’t available because of local caching: instead of mistakenly banning that peer, the node now handles it safely, reducing the chance of nodes cutting themselves off from the network for the wrong reason.
-
A redundant UI refresh was removed to stop the occasional screen flashing (especially noticeable during subblock mining), making the interface feel smoother.
Rostrum
-
A reorg-related correctness issue (“phantom UTXOs”) was fixed and backed by a functional test, improving accuracy for explorers, wallets, and APIs that rely on UTXO truth.
-
CI reliability was improved via dependency updates, cache invalidation tied to the lockfile, and fixing a failing test in Nexa CI, reducing flaky runs and stale artifacts.
Seeder
- Startup behavior is now clearer: if the DNS port is already occupied, the seeder exits early with a specific error message, making diagnosis faster and preventing half-working states.
Libnexakotlin
-
Kotlin toolchain modernization plus safer networking behavior landed (Kotlin upgrade; DNS resolution failures handled), improving compatibility and reducing crash-prone edge cases.
-
The headers DB is now recreated if it can’t be opened (corruption recovery), reducing stuck/broken states.
-
Documentation/onboarding improvements (README/setup) reduce setup time for developers.
-
A UTXO reservation bug during asset challenge proof creation was fixed, reducing confusing transaction/build failures in asset flows.
Script machine kotlin
-
Dependency/tooling updates keep the project current and reduce long-term drift.
-
Fixed 2 transactions input handling and improved malformed-transaction error messages, which makes failures easier to understand when integrating or debugging.
Nexascript debug
-
Dependency updates and support file improvements reduce build drift and improve maintainability.
-
Script-machine initialization errors are surfaced more clearly now, cutting down time lost to silent failures.
Nexa token api
- CI configuration improvements improve build/test repeatability and reduce deployment surprises.
Nexa token indexer
- CI configuration improvements strengthen automated validation and lower regression risk.
Nexa token api env
- Docker compose override updates improve dev environment consistency and reduce “works on my machine” setup friction.