There are many developments to review from May 2026. Still, a lot of attention is being given to preparing for the upcoming hard fork, testing, and cleanup efforts. Tailstorm integration is currently the most critical work that requires time, patience, and testing. Alongside that, NexScript v1.1.0 was released, as well as continued work on LibNexaKotlin and wallet updates, with further developments happening in parallel.
Find full development updates for May 2026, including details on preparations for the protocol upgrade, work on the Nexa explorer, the ecosystem, and more.
Preparing for the Hard Fork
With the second Nexa Hard Fork approaching, the team is still working on preparations, testing, cleanups, and various other improvements.
One of the biggest changes is moving from time-based to height-based activation, and from setting a pinned block to comparing the timestamps of the chain tips. Another round of cleanup removed dead weight from the script engine, including the pay-to-pubkey script type and the always-on flags for 64-bit integers and native introspection. Also, the team is testing and hardening Tailstorm robustness, and pruned subblocks now correctly show a NOTFOUND message with no penalties to peers. The last change lowered the priority at which the anti-spam messaging layer flags a peer as misbehaving, improving node connectivity.
There are many developments underway, including Tailstorm subblock handling and node lock ordering. The same is true of the C++20 toolchain migration, whose updated CI images are already in place, and of new overflow protection for token sends in the wallet and GUI.
Block Explorer: Rebuilt Node Communication
The old JSON-RPC library and in-process request queue were replaced with a lightweight client governed by a single global Redis semaphore. The semaphore now uses role-scoped keys, allowing the web and worker tiers to maintain separate concurrency budgets without starving one another. Follow-up work also improved the robustness of the new transport layer, including surfacing JSON-RPC error bodies, handling lost locks and unhealthy node states, and introducing bounded per-request block fan-out. The Redis layer was migrated to the ioredis client and legacy dependencies removed, with a startup smoke test added to catch misconfiguration early.
Memory usage and per-render costs on very large addresses are reduced, and background cache warming is gated to skip the heaviest addresses. A round of queue hardening resolved stuck indicators and partial fetches while improving token and NFT worker throughput. The mobile interface received further improvements with a toggleable search overlay and better responsiveness across blocks, tokens, and pagination. Separate development and production start scripts were added, the homepage bundle is now cached, and the explorer was configured to discourage indexing and block a range of AI crawlers.
Wallets and SDKs
One of the larger changes fixed a possible lock-order hazard during destination creation and now allows wallets to be deleted even while their addresses are still being installed into the bloom filter. The team also synchronized address generation, bloom-filter installation, and merkle-block loading to improve transaction filtering reliability. Several smaller fixes corrected sign-magnitude decoding of the value minus one, adjusted the default anti-spam backdating behavior, and resolved an RPC call that was incorrectly requesting a token melt instead of a token balance.
A new static deadlock detector was introduced as an IDE plugin, capable of analyzing Kotlin code that uses the project’s mutex library, building a lock graph, and reporting cycles that may lead to thread deadlocks before runtime. A new set of reusable Compose UI components also landed for wallet builders.
Conclusion
There was more work on various ecosystem projects and tooling, and all the developments are public and widely available to review on Nexa’s GitLab. With the coming main blockchain layer upgrade and Tailstorm protocol integration, vast amounts of attention are going into this network upgrade.
If you have any questions, feedback, or suggestions, join our community forum, channels, and chat groups.
Find all the developments in detail on Nexa GitLab:
https://gitlab.com/nexa