Thursday, June 4, 2026
API
Protocol
WASM
Tooling

Release: mx-api-service: v1.20.0

Infrastructure Upgrades and Fixes in v1.20.0

The latest release of the API service introduces core infrastructure updates, modules dependencies fixes, and bug fixes aimed at improving resource management, performance, and security.

Core Upgrade: Node.js 24.14, NestJS v11, and Dependencies

The service transitioned to Node.js 24.14 and NestJS v11, with all internal and third-party dependencies updated to their current versions.

  • Performance: Node 24.14 upgrades the V8 engine, improving async execution and garbage collection to lower CPU overhead under load. NestJS v11 optimizes dependency injection, reducing memory footprint and startup times.
  • Security: Modernizing the runtime and updating all package dependencies patches upstream vulnerabilities to meet security compliance standards.

Module Import Fixes and Database Optimization

  • Issue: Incorrect module importing caused NestJS to instantiate duplicate instances of shared services (broken singletons), resulting in redundant resource allocation.
  • Fix: Refactored the codebase to use standard NestJS forRoot() patterns at the root level, ensuring services are instantiated exactly once.
  • Result: Eliminated duplicate service instances, reducing active database connections and improving connection pool efficiency.

ElasticSearch Query Fix

  • Issue: Range queries failed to return all matching documents when searching a timeframe spanning before and after the Barnard protocol release.
  • Cause: The system transitioned from seconds (timestamp) to milliseconds (timestampMs), causing filtering inconsistencies across that boundary.
  • Fix: Updated the search logic to handle the unit transition properly, ensuring complete data retrieval.

General Optimizations

  • Protocol Readiness: Added support for new data fields, execution results, and epoch cache handling.
  • Cache & Resources: Decreased mempool TTL, optimized broadcast intervals, and increased the Node.js event listener limit.
  • Configuration: Blocked interactive documentation routes in production and added dApp network configuration overrides.

More details: GitHub↗

For questions or help, reach us on Telegram or Discord channels.

Do you need more information?

Explore projects, tokens, and integrations built on MultiversX