Changelog 2026.8

Over the past three months, work across Nolus converged in one direction: bringing Solana online as a first-class home for the protocol. The Solray SDK hit its first end-to-end milestones, the money market was rebuilt for remote execution on Solana, and the app, data, and public surfaces all got steadier.

Solray SDK

The IBC link between Nolus and Solana runs end to end. The IBC connection and channel handshake complete in both directions, and token transfers round-trip both ways. The relayer's Solana backend grew from a skeleton into a complete endpoint: full query and message coverage, and event ingestion.

Remote margin positions execute on Solana end to end. The money market application carries a position through opening, swapping, transferring out, and closing, including atomic two-leg swaps routed through the Metis API in a single delivery. First-time recipients no longer need a pre-existing token account; the transfer creates one on the fly. The focus was foundational, setting up the user-facing flows that follow.

Protocol & Contracts

A new generation of the Nolus money market is getting prepped. The contracts were rebuilt around the remote execution: instead of leaning on interchain accounts and DEX connections reachable from Nolus, margin speaks to a dedicated controller that carries opening, swapping, repaying, liquidating, and closing to the network where the liquidity lives, with Solana registered as the first remote target. The superseded apparatus was deprecated outright. This generation is built and tested but not yet live; it arrives through governance in the releases ahead.

The remote path defends itself. Market Anomaly Guard (MAG), the safeguard that shields margin positions from unfair liquidations in volatile markets, now covers the remote path: every swap leg carries its slippage protection, a liquidation swap that times out is re-quoted automatically to buy time for the market to correct itself, and retries draw from a bounded budget. Error acknowledgements carry a cause code understood on both sides, so a failure is handled by what went wrong, not where it happened. Late, stale, or malformed callbacks are absorbed and failed opening swaps unwind cleanly. The net effect is that cross-chain hiccups resolve themselves instead of freezing a margin mid-flight.

A chain upgrade stages the network side. A new node release refreshes the chain's core dependencies and prepares its IBC layer for the Solana connection, alongside quality-of-life work: a node command for decoding contract queries and first-time documentation for the chain's custom modules.

Web App

A simpler, sturdier wallet lineup. Leap was retired end to end, with a self-healing guard so returning sessions reconnect instead of crashing. Phantom and Solflare connect through their native Solana interfaces, and direct Ledger connections left the picker while existing Ledger sessions keep reconnecting.

Assets sharing an IBC denomination, most visibly USDC, no longer show a zero price and sink to the bottom of dropdowns; a routing failure no longer wedges swaps until reload. External deposits show up without a refresh, and the hardened live stream can no longer blank out PnL or interest figures.

Clearer answers across the dApp. Exceeding the wallet's balance now says exactly that instead of an unexpected error, and the liquidation line on a position's chart was corrected and upgraded to a stepped history, rendering a moved trigger as it actually happened.

Blockchain Data & Indexing (ETL)

Ready before the protocol moves. The indexer was prepared for the next protocol generation ahead of its rollout: new margin states parse cleanly, reshaped events no longer abort aggregation snapshots, and the new cross-chain operations are recognized end to end. Any event the indexer does not yet recognize is captured and replayed once support ships, so nothing emitted ahead of its handler is lost.

nolus.io

The changelog archive came home. Twenty-three past editions, reaching back to the weekly era, now live on the Nolus blog, and the external changelog collection was retired. Elsewhere on the site, the brand page gained its hero artwork, an intermittent hover flicker was eliminated at its root cause, and proposal summaries no longer cut mid-word.

Knowledge Hub

Help-center answers were audited against reality. Every answer the AI support agent grounds on was checked against a verified brief: stale entries removed, others corrected in place, and four internal answers promoted to public articles. Support now says what the protocol actually does.

Docs

docs.nolus.io opened its doors. Developer documentation moved out of the Knowledge Hub into a purpose-built site: protocol concepts, complete node, validator, and relayer operator guides, live network endpoints, and a reference for the public data API's seventy-plus paths, with diagrams-as-code instead of screenshots and the security policy mirrored where developers read. The site also carries the agent-readiness signals the previous cycle brought to the dApp and nolus.io: machine-readable robots directives, an API catalog, and integrity-stamped manifests of its machine-readable corpora, with all three agent-facing surfaces documented in one place. The practical effect is that AI-assisted tooling can integrate with Nolus by contract, on every surface it touches.