2026.3

Over the past two months, development across Nolus focused on strengthening the core systems behind the protocol. The work was centered around improving architecture, simplifying internal logic, and making the overall stack more scalable and maintainable.
​

During this period:

This cycle focused on refactoring, architectural improvements, and long-term system reliability, rather than feature-heavy releases.

The Money Market was updated with release v0.8.24, focusing on improvements to the lending layer and internal structure.

The update included refactoring of loan and repayment logic, improvements to liquidity flow handling, and general codebase cleanup. These changes are not directly visible in the UI, but they affect how margin positions are executed and managed under the hood.

More predictable loan handling and simplified internal logic improve stability and make future upgrades easier to implement. Given that Nolus positions rely on fixed protocol interest and structured loan lifecycle management, these improvements strengthen the reliability of the core system.

The Web App was transitioning toward a Backend-for-Frontend (BFF) architecture.

This introduces a backend layer that aggregates and serves data to the frontend, replacing the previous approach where the frontend interacted with multiple services directly. As part of this shift, data handling logic is being centralized and removed from the client.

The change improves consistency across views, reduces frontend complexity, and enables better performance through caching and controlled data access. It also creates a more flexible foundation for future product development.

The ETL system was restructured to separate data ingestion from data serving.

A dedicated ingest layer now handles raw blockchain data processing, while a separate API layer serves structured, query-ready data to applications and services. Previously, these responsibilities were more tightly coupled.

This separation allows ingestion and query workloads to scale independently, improves reliability under load, and creates clearer boundaries between data processing and data access. It also provides a more stable foundation for analytics, dashboards, and integrations.

The nolus.js library was extended with the introduction of an MCP server.

This adds a structured interface for interacting with Nolus programmatically, making it easier to build integrations and external tooling. Instead of relying on fragmented access patterns, developers now have a more unified way to interact with protocol data and services.

This improves developer experience and enables use cases such as automation, custom dashboards, and more advanced integrations.

Development of IBC Solray continued actively over the past two months and remains one of the primary long-term initiatives.

This period was focused on moving the project closer to a production-ready architecture, with work concentrated around:

The current phase is no longer purely experimental. The repository shows a transition toward finalizing core flows, particularly around how assets move between the two ecosystems and how those flows integrate with Nolus margin positions.