Skip to main content

2026.1

Updated this week

Over the last month, Nolus has gone through an intensive development cycle focused on core protocol systems, infrastructure, and developer tooling. Across the Nolus GitHub organization, the team shipped 772 commits in 31 days, with nearly 193,000 lines of code changed and a net increase of over 40,000 lines after substantial refactoring and cleanup. Work was deliberately concentrated across a small number of critical repositories, reflecting a focus on long-term maintainability, performance, and scalability rather than surface-level changes. The sections below highlight the most meaningful outcomes of this effort and how they translate into tangible improvements across the Nolus stack

Web App

The Nolus web app now runs entirely on Nolus-owned, enterprise-grade infrastructure, with no reliance on external cloud providers such as AWS or Google Cloud. This shift gives the team full control over performance, reliability, and security at the application layer.

A major architectural improvement in this release is the introduction of server-side rendering (SSR). As a result, initial load times and overall navigation responsiveness have improved significantly, particularly for first-time visits and lower-latency connections.

On the user experience side, the update introduces:

  • smoother page transition animations

  • refined modal and popup animations

  • improved large-number rendering for balances, PnL, and position metrics

These changes are part of an ongoing initiative to make the app feel more fluid, responsive, and predictable, especially during frequent interactions such as opening, managing, and repaying margin positions.

In parallel, the UX has been simplified by removing non-core complexity. This includes deprecating flows such as multi-hop token transfers from EVM networks and other edge-case interactions that were not essential to Nolus’ core protocol offering. The result is a more focused product surface that emphasizes clarity over optional complexity.

ETL (Indexer)

The Nolus ETL system has undergone its largest upgrade since its initial production release nearly two years ago.

It now provides:

  • full historical protocol data

  • structured and normalized storage in a PostgreSQL database

  • publicly accessible API endpoints

Despite the significantly larger data scope, performance has improved. Thanks to enhanced caching and query optimization, most API responses are returned in milliseconds, while maintaining near real-time freshness.

This upgrade lays the groundwork for:

  • more advanced analytics

  • improved dashboards and monitoring

  • future public and internal data tooling built on reliable historical datasets

Money Market

A long-running refactoring effort of the Nolus money market codebase is nearing completion, with finalization expected by mid-February.

The primary goal of this initiative is simplification and maintainability:

  • reducing internal complexity

  • clarifying responsibilities across modules

  • making the system easier to reason about and extend

Once completed, this refactor will significantly lower the cost of future development, enabling the team to deliver new features and scalability improvements faster and with lower operational risk.

Solray and Hermes Lite

Development of IBC Solray has progressed substantially over the past month and is now in its final phase. The remaining work focuses on application-level logic for:

  • token transfers

  • flows tailored specifically to Nolus protocol needs

At the same time, the dedicated relayer hermes-lite has been heavily refactored and simplified. This effort resulted in:

  • nearly 40,000 lines of code removed

  • approximately one-third fewer external dependencies

The outcome is a leaner, easier-to-audit relayer that is simpler to operate and extend. Hermes-lite is now prepared for its next phase: extending support to Solana, alongside existing Cosmos-based workflows. At this stage, it represents one of the most streamlined and purpose-built Cosmos relayer forks in active use.

Infrastructure

Nolus now operates a full-stack Solana infrastructure in-house, supporting both Solana devnet and mainnet environments. This setup includes:

  • RPC nodes

  • Yellowstone gRPC

  • Metis API

The team is investing heavily in hardware and software optimization to achieve:

  • low latency

  • high request throughput

  • robustness under sustained load

Owning this infrastructure removes external bottlenecks and allows the system to be tuned specifically for Nolus’ protocol and application requirements.

Other Notable Additions

A new centralized monitoring, alerting, and action backend has been added to the internal software stack.

This system enables the team to:

  • monitor infrastructure and services in real time

  • trigger alerts and automated actions

  • manage endpoints

  • analyze on-chain data

  • provide faster and more effective user support

It acts as a unified control layer across infrastructure, protocol operations, and support workflows, significantly reducing response times and operational overhead.

Did this answer your question?