> For the complete documentation index, see [llms.txt](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2026-02-11.md).

# NAVI Lending Protocol Upgrade Announcement (2026/02/11)

We are excited to announce that **NAVI Lending is undergoing a major protocol upgrade!** This update introduces a suite of powerful new features designed to maximize capital efficiency, strengthen risk management, and unlock new possibilities for ecosystem partners and DeFi users alike.

***

#### **Launch Schedule**

* **Estimated Time:**
* **SGT:** 2026/02/11 8:00 AM
* **PST**: 2026/02/10 4:00 PM
* **ET**: 2026/02/10 1:00 PM
* **Lending Package Id:** 

  ```
  0x1e4a13a0494d5facdbe8473e74127b838c2d446ecec0ce262e2eddafa77259cb
  ```
* **Oracle Package Id:** 

  ```
  0x203728f46eb10d19f8f8081db849c86aa8f2a19341b7fd84d7a0e74f053f6242
  ```
* **SDK:** <https://github.com/naviprotocol/naviprotocol-monorepo>
* **Repo**: <https://github.com/naviprotocol/navi-smart-contracts/tree/main/lending_core/sources>

***

#### **Upgrade Overview**

**Lending Core:** The lending core has been significantly enhanced with new capabilities including **E-Mode (Efficiency Mode)** for optimized LTV on correlated asset pairs, **Multiple Isolated Markets** for independent lending pools with segregated risk, **Dynamic Borrow Weights** for fine-grained risk control, **Enhanced Liquidation** with designated liquidators and protected user accounts, and a redesigned **Incentive V3** reward engine with multi-token distribution and tiered borrow fee management.

**Oracle:** The oracle module has been restructured to support **multiple oracle sources** (Pyth, Supra, Switchboard) with improved price feed reliability and a unified interface for price queries across all markets.

#### Integration Guideline

1. The protocol will be published under a **new package ID**. The old package ID will be deprecated and **no longer functional**. Please update your contract calls to the new package ID once announced.
2. All legacy events will be retired. Going forward, **every event is consolidated into the `event` module**. If your application listens to on-chain events, please migrate accordingly.
3. The core lending interfaces — **deposit, withdraw, borrow, repay, and liquidation** — remain fully compatible. Existing integrations will **continue to work as expected** with no breaking changes.
4. For new features like **E-Mode** and **Multiple Markets**, please stay tuned for our upcoming **SDK updates and further documentation**.
5. The **oracle interface has been updated**. If your integration involves oracle price feeds, please refer to the new oracle module for the latest API.

***

#### Interface Changes

\
1\. **Oracle:  `update_single_price`  →  `update_single_price_v2`**

```move
// Old (deprecated)
public fun update_single_price(
    clock: &Clock,
    oracle_config: &mut OracleConfig,
    price_oracle: &mut PriceOracle,
    supra_oracle_holder: &OracleHolder,
    pyth_price_info: &PriceInfoObject,
    feed_address: address
)

// New
public fun update_single_price_v2(
    clock: &Clock,
    oracle_config: &mut OracleConfig,
    price_oracle: &mut PriceOracle,
    supra_oracle_holder: &OracleHolder,
    pyth_price_info: &PriceInfoObject,
    switchboard_aggregator: &Aggregator,  // new parameter
    feed_address: address
)
```

> **Note:** Switchboard is **not actively used** at this time — the `switchboard_aggregator` parameter serves as a placeholder for future support. You can use `0x1fa7566f40f93cdbafd5a029a231e06664219444debb59beec2fe3f19ca08b7e` as a placeholder until it is officially enabled. We recommend using our SDK to fetch the latest configuration.

2. **E-Mode: `enter_emode` / `exit_emode`**

Users can enter an E-Mode to enjoy higher LTV ratios on correlated asset pairs. The user must have **no existing collateral or debt** before entering or exiting E-Mode.

```move
// Enter E-Mode (with sender)
public fun enter_emode(storage: &mut Storage, emode_id: u64, ctx: &mut TxContext)

// Enter E-Mode (with AccountCap)
public fun enter_emode_with_account_cap(storage: &mut Storage, emode_id: u64, account_cap: &AccountCap)

// Exit E-Mode (with sender)
public fun exit_emode(storage: &mut Storage, ctx: &mut TxContext)

// Exit E-Mode (with AccountCap)
public fun exit_emode_with_account_cap(storage: &mut Storage, account_cap: &AccountCap)
```

> **Note:** Specific E-Mode pairs will be announced after the upgrade goes live.

3. **Multiple Markets**

The protocol now supports multiple independent lending markets. Each market is composed of its own set of shared objects (e.g., `Storage`, `IncentivePool`). When you pass the shared objects of a specific market, you interact with that market.

Your existing integration with the **main market** will continue to work as-is — simply keep using the same shared object inputs. To interact with additional markets (e.g., a 2nd market), use the corresponding shared objects for that market.

> **Note:** New market shared object IDs will be published as markets are created. We recommend using our SDK to fetch the latest market configuration.

#### **FAQ**

* **Q1: Is this an upgrade or a brand-new package?** **A:** This is an **upgrade to the existing major package**. Most module/method addresses will remain—watch for update notices.
* **Q2: Will current interfaces remain usable in E-Mode?** **A:** Yes, you will use the current interfaces after entering emode
* **Q3: Is the upgrade audited?** **A:** Yes. The upgrade is fully audited by Veridise and Movebit.

***

**——NAVI Protocol Team**