NAVI Lending

NAVI Lending (often referred to as NAVI Protocol, ticker NAVX) is a lending / borrowing liquidity protocol on the Sui blockchain, with all TVL currently on Sui. Basic identification

• Name: NAVI Protocol / NAVI Lending.
• Category: DeFi over‑collateralized lending / liquidity protocol with shared and isolated pools, flash loans, and leveraged strategies.
• Website / app: Commonly referenced as the NAVI web interface; third‑party guides describe connecting a wallet and supplying SUI and other assets, confirming an operational web dApp.
• Docs: Public documentation is hosted on GitBook under Navi Protocol Docs, covering lending/borrowing parameters and user flows.
• Chains: Single‑chain deployment on Sui; data platforms report TVL 100% on Sui.
• Native token: NAVX, described as NAVI’s protocol token on Sui.
• Launch date: The team announced mainnet launch on Sui in July 2023 as “First Native One‑stop Liquidity Protocol on Sui.” Main contract addresses & verification status
• Specific Sui object / contract IDs for NAVI Lending are Not verifiable as of [2026-09-04] under current constraints; they are not enumerated in the accessible off‑chain sources and I cannot query chain data or explorers directly in this turn.
• Consequently, I cannot state whether NAVI’s core lending contracts are “verified” in Sui explorers; this is Not verifiable as of [2026-09-04]. Fork lineage and design origin
• External analyses describe NAVI as a native Sui lending protocol built in Move, positioned as the “first native one‑stop liquidity protocol on Sui / Move chains,” which implies it is not a direct Solidity fork of Aave/Compound, but a conceptually similar design adapted to Sui.
• Available reviews and explainers frame NAVI’s architecture around shared pools plus isolated pools, E‑Mode, flash loans, curator‑run markets (NAVI Prime), and receipt tokens like nSUI, nUSDC, suggesting original implementation rather than a minimal fork.
• None of the independent sources explicitly identify a specific upstream fork (e.g., “Aave v3 fork”) or list a fork diff; this is therefore Not verifiable as of [2026-09-04]. Audits and fork‑related risk history
• Public summaries mention NAVI as a leading and “foundational” Sui protocol but do not provide direct links to formal audit reports or audit firm names in the material available here; detailed audit status is Not verifiable as of [2026-09-04].
• No independent source in this set documents malicious modifications in NAVI forks or exploit history specifically tied to forked NAVI code; this is also Not verifiable as of [2026-09-04].

NAVI Lending appears to be a live product, not just a landing page: official docs direct users to app.naviprotocol.io, describe wallet login, supplying assets, borrowing, withdrawals, flash loans, and other active lending actions. The SDK/docs also expose developer tooling for pool operations and lending APIs, which is a strong sign of a mature product surface rather than a static marketing site. The website/docs signal reasonable UX maturity: there is a separate app, developer docs, and SDK documentation, plus explicit user guides for lending and withdrawing.

However, without live chain verification, it is not verifiable as of 2026-09-04 whether deposits/withdrawals are currently functioning end-to-end on Sui, or whether the UI has broken links/template artifacts. Open API: yes, an open developer surface is indicated by the published SDK and the documented open-api.naviprotocol.io contract-config endpoint referenced in the docs. That said, whether the public API is fully documented, stable, and production-grade is only partially verifiable from the web sources available here. ## Findings

• Real portal exists: app.naviprotocol.io is explicitly documented as the app entrypoint.
• Product functionality described: supply, borrow, withdraw, flash loans, liquidation, rewards, and pool operations are documented.
• Developer surface exists: TypeScript SDK and documented API endpoint are public.
• Live on-chain usage, broken-link audit, fake-metric check, and template-sign detection: Not verifiable as of 2026-09-04.

NAVI Protocol appears to have an active bug bounty program hosted on HackenProof. The program page says it is live, with rewards from $300 to $300,000; critical smart-contract issues are capped at $300,000 and web/frontend issues at $10,000. Reports must be submitted exclusively through HackenProof, with the reporter as first discoverer and submission within 24 hours of discovery.

The program page does not clearly expose a start date in the retrieved material, so the launch date is not verifiable as of 2026-09-04. No public results or disclosed payouts were found in the retrieved sources, so results are not verifiable as of 2026-09-04.

Assessment (as of September 6, 2026) Contradiction / update: The prior finding identified Pyth and Band. Current NAVI SDK documentation and the Veridise audit identify Pyth and Supra as the active dual-provider oracle design; Band was not confirmed in current evidence. NAVI uses a push-based update model with a stated 15-second freshness threshold.

This creates residual risks from provider outages, stale updates, bad publisher inputs, cross-provider divergence, and manipulation of thin markets around update/liquidation windows. External protocol dependencies: NAVI supports bridged USDC and USDT via Wormhole, WETH/WBTC, and Sui liquid-staking assets including voloSUI and haSUI. These introduce bridge-message, wrapped-asset, issuer/depeg, and LST-exchange-rate risks. A failure of Wormhole or an issuer could impair collateral value or withdrawals. Bridges / routing: NAVI’s newer Astros Bridge SDK routes through third-party bridge providers including Mayan and supports Sui, Ethereum, Solana and other chains.

This is an ecosystem dependency, but direct lending-pool exposure and routed volume are not available from the permitted evidence. Stablecoins, LSTs, custodians, CEX/MM, RWA: USDC/USDT depend on their respective issuers, reserves, redemption channels and bridged representations. LSTs depend on their staking protocols, validators and redemption liquidity. Specific NAVI exposure percentages, custodial balances, market-maker/CEX concentration, RWA issuers/SPVs, and active insolvency/depeg events: Not verifiable as of September 6, 2026. Failure scenarios: oracle staleness or divergence can cause under-collateralized borrowing or wrongful liquidations; a bridge exploit or stablecoin/LST depeg can create bad debt; thin-market liquidation cascades can exhaust reserve liquidity.

These are risk scenarios, not evidence of a current incident. On-chain verification: Not verifiable as of September 6, 2026; Dune MCP was unavailable. No exposure percentages are inferred.

NAVI Lending is organized as a non-custodial DeFi lending protocol on Sui: users supply assets into smart-contract-managed liquidity pools, receive receipt tokens representing their share, and can withdraw on-demand; the protocol states that funds are allocated in a smart contract and that no one is ever in control over user funds. For the newer NAVI Prime product, custody is described as institution-facing and more segmented: users/allocators custody assets with third-party custodians such as BitGo, Anchorage, Fireblocks, or Galaxy, then deploy into curated vaults and isolated markets, which indicates operational separation by market rather than a pooled omnibus structure. Based on the available evidence, withdrawal_paused is not verifiable as of 2026-09-06, and segregated_assets is best characterized as true for NAVI Prime’s isolated markets/curated vaults but not as a universal claim for all NAVI Lending liquidity; the standard lending pools are shared, not fully segregated.

Based on available data, there is no evidence of a direct exploit, loss of funds, or technical incident affecting NAVI Lending itself on Sui since launch. Two relevant ecosystem incidents triggered precautionary actions by NAVI but did not result in NAVI user losses: 1. Cetus Protocol exploit response (ecosystem, not NAVI)

• Date: Around May 2025 (Cetus incident and subsequent NAVI communication).
• Cause: Cetus Protocol suffered a major exploit and asset freeze (~$60m stolen, $162m frozen), prompting ecosystem-wide risk management.
• Loss for NAVI users: 0 USD – sources state NAVI smart contracts and user funds remained secure, with no vulnerabilities found and no impact on NAVI pools.
• Affected on NAVI: Borrowing and some lending functions on NAVI were temporarily paused as a precaution, not due to compromise.
• Protocol response: NAVI conducted a comprehensive review/audit of its contracts and infrastructure, paused borrowing, then fully reinstated lending once checks were complete.
• Reimbursement: Not applicable – no NAVI user losses reported.
• Recovered_usd: Not applicable for NAVI; recovery relates to Cetus.
• Current status: resolved – NAVI confirms lending functions resumed and platform safe. 2. Volo Protocol exploit, post‑acquisition by NAVI (separate product layer)
• Date: Exploit disclosed April 22, 2026.
• Cause: Attack on three Volo vaults (WBTC, XAUm, USDC) on Sui; reports attribute the root cause either to vault‑level vulnerabilities or a compromised privileged operator key, still under investigation.
• Loss: About $3.5M drained from Volo vaults; ~$0.5M frozen on‑chain.
• NAVI Lending exposure: NAVI acquired Volo in early 2024, but NAVI states its own lending contracts were not impacted; NAVI paused its contracts purely as a precaution after the Volo incident and later confirmed no vulnerabilities and normal operation.
• Affected users (NAVI): NAVI users experienced temporary pause of deposits/withdrawals and borrows; no confirmed loss of funds on NAVI.
• Protocol response (NAVI): Immediate precautionary pause of lending contracts, activation of security protocols, full review, then resumption within hours, followed by public confirmation that NAVI was safe and unaffected.
• Reimbursement (NAVI): Not applicable – no NAVI Lending user losses reported; Volo team pledged to absorb Volo users’ losses.
• Recovered_usd (NAVI): 0; recovery figures relate to Volo, not NAVI Lending.
• Current status: resolved for NAVI; Volo exploit remediation remains under investigation in external reports. On-chain verification of losses or reimbursements specific to NAVI Lending on Sui: Not verifiable as of 2026-09-04.

Affiliated Volo Vault incident, not a direct NAVI Lending contract exploit. On April 21–22, 2026, an attacker compromised Volo’s privileged operator/admin private key and used the legitimate NAVI AccountCap withdrawal path to drain Volo deposits routed into NAVI Lending. Affected Volo vault users held WBTC, XAUm, and USDC; NAVI Lending itself reported no direct loss.

Initial extraction was approximately $3.5M. NAVI paused contracts and activated security procedures, then reopened deposits and withdrawals within approximately 6.5 hours. Volo and ecosystem partners froze/intercepted assets, including 19.6 WBTC, recovered approximately 64.9 ETH and other funds, and reduced the realized loss to approximately $60,000.

Volo covered the residual from treasury, with zero loss passed to users. The structural fix was operational rather than a NAVI code patch: revoke/contain the compromised operator authority, isolate affected vaults, coordinate freezes and recovery, and review the single-key withdrawal model; recommended hardening includes multisig/threshold authorization, withdrawal timelocks, and narrower operator permissions. Current status: NAVI-side incident resolved; user reimbursement reported complete.

Volo’s final status for every affected vault after the April 28 recovery update is Not verifiable as of 2026-09-06.

No verified protocol-level exploit or loss incident was found for NAVI Lending itself on Sui. The only incident-like event tied to NAVI in the gathered web material was a precautionary pause after the Volo incident on 2026-04-21/22, where NAVI stated it had not been impacted and later resumed operations.

A separate ecosystem incident on Sui involved Volo Protocol, not NAVI Lending. Reported figures were about $3.5 million drained from three vaults (WBTC, XAUm, USDC); roughly $500,000 was reportedly frozen/blocked, and the team said it would absorb remaining losses and later present a compensation plan.

Second ecosystem-related incident where NAVI Lending took precautionary actions but did not suffer direct loss. See main body above for full context; this entry focuses on the Volo exploit and NAVI’s response.

NAVI Lending’s core lending system is organized around shared liquidity pools and markets, where each market groups related pools and E-Mode settings; users deposit, borrow, repay, withdraw, and the protocol uses account management plus liquidation logic to keep positions safe. The docs also describe a governance layer in which NAVI token holders vote on proposals and protocol changes such as interest rates, new assets, and collateralization ratios, so key protocol parameters are not managed by a single operator. For risk/key management, NAVI’s public materials emphasize parameter-based controls rather than custodial control: collateralization ratios, LTV, liquidation thresholds, and per-asset limits are adjusted dynamically, and the system uses oracles and automated liquidations to manage risk.

The SDK/docs further note isolation mode and isolated pools for higher-risk assets, which confines risk to specific markets instead of the whole pool set. For the newer NAVI Prime framework on Sui, third-party coverage says the protocol adds professional curators and isolated markets with separated roles for administrators, curators, and capital allocators; curators can update markets and parameters within authorized limits, while allocators only move funds between pre-approved markets, with time locks for critical changes. Because these role details come from media reports rather than the protocol’s own technical specification, they are best treated as partially verified until confirmed in primary docs.

As of September 6, 2026 — Sui only. Dune/on-chain execution is unavailable in this run; therefore privileged-object ownership, decoded admin events, timelock delay, role renunciation, pause status, and current withdrawal liquidity are Not verifiable as of 2026-09-06. Addresses / verification. The current repository identifies lending_core v26 at 0x512f28261c1a293f49416d8885b8d5d32bde6dd68a99a0be36fe42b248e6833a and oracle v5 at 0x4837ae94425107554c8847721cf9954c1ad8e10520433b9e37dc11c507148bea. These are documented published-at IDs, not independently on-chain-confirmed here. NAVI states that oracle source verification succeeds; lending_core v26 has a verification mismatch in 10 modules because dependencies were folded into the published package, although the repository claims identical compiled logic. Architecture. Sui Move packages—not EVM proxies—contain lending-pool, oracle, liquidation, incentive, and math modules.

User paths are deposit → nTokens; borrow/repay → debt; withdraw → burn nTokens and redeem assets; liquidation uses oracle-priced collateral. User → LendingPool(shared market/storage) → Reserve objects + nTokens/debt → Oracle package (Pyth/Switchboard integration) → Liquidation/incentive modules Upgrade/admin risk. The repository explicitly supports sui client upgrade -c <UpgradeCapId>, so the package architecture is upgradeable. Sui’s UpgradeCap bearer can authorize compatible upgrades; implementation logic can change, while old package versions remain on-chain. No proxy-admin contract or EVM-style timelock is applicable.

A compromised UpgradeCap/publisher could potentially alter risk parameters, oracle handling, liquidation, fees, or withdrawal/borrow logic in a future compatible release; the practical worst case is market insolvency, freezing exits, or asset diversion through malicious logic. Direct treasury draining, emergency pause authority, fee recipient, strategy controls, and whether users can exit without administrator action are Not verifiable as of 2026-09-06. The documented withdraw path indicates a permissionless user exit function, but does not prove adequate liquidity or absence of admin-controlled freezes. Audits. Public records list OtterSec, MoveBit, Veridise, and SALUS assessments; however, linkage of every current deployed package/version to a clean audit scope is incomplete. Risk conclusion: upgrade/key-compromise risk is material; rug/freeze risk cannot be ruled out without on-chain UpgradeCap and privileged-object analysis.

NAVI Decentralized Oracle Integration — Veridise

NAVI Volo Vault — Veridise

NAVI PythPro Oracle Incremental Audit — MoveBit

NAVI Pool Incremental Audit — OtterSec

NAVI E-Mode Incremental Audit — Veridise

NAVI Incentive Incremental Audit — MoveBit

NAVI Lending (Sui) has one publicly referenced audit by MoveBit focused on the core lending protocol smart contracts built in Move. The report available online appears to be a pre-deployment security review rather than a continuous audit of all subsequent upgrades. Contract–bytecode match to currently deployed code on Sui is Not verifiable as of 2026-09-03, because direct on-chain comparison tooling is unavailable in this run and the report does not itself provide deployment hashes.

Preliminary smart contract audit of Navi Lending on Sui, covering core lending pool, interest rate, and collateral logic.

NAVI Full Audit — MoveBit (2023)

Fix status is published as 'Passed' for all listed reviews on the security page. However, the available search results do not provide the underlying findings breakdown by severity (critical/high/medium), nor do they provide issue-by-issue remediation status. For the specific request to confirm whether the audits cover deployed code, the results are insufficient to verify bytecode/source equivalence; this is Not verifiable as of 2026-08-29.

NAVI Full Audit — OtterSec (2023)

NAVI Incremental Audit — OtterSec (2024)

Comprehensive audit(s) of NAVI Lending core smart contracts on Sui, including supply, borrow, liquidation logic and protocol upgrades.

NAVI Penetration Test — Salus (2023)

Security review of NAVI Lending markets on Sui, focusing on interest rate models and collateral parameters.

Audit(s) related to NAVI on Sui, including NAVX token and Volo Vault; tangential to lending but part of protocol stack risk.

NAVI Full Audit — Veridise (2024)

NAVI Lending appears to be the Sui-native DeFi protocol NAVI Protocol, not the unrelated Indian fintech company Navi founded by Sachin Bansal. For the DeFi protocol, the public-facing team is sparse: RootData lists only Charles and Elliscope F. as co-founders, and the protocol site names Elliscope as co-founder; no full legal names, prior employers, or formal team page were verifiable from the provided sources. Reality check: the protocol currently looks more like a web-fronted DeFi project than a clearly disclosed operating company. I found no verifiable evidence in the provided sources of a real office, jurisdiction, or onshore/offshore corporate structure for NAVI Protocol; that remains Not verifiable as of 2026-09-04.

On credibility: one external startup database says the team has experience from Helio Money, Connext, KaratDAO, Apple, UC Berkeley, and USC, but this is a secondary aggregator entry and not independently corroborated here. RootData’s team listing is also thin, which increases anonymity risk and makes prior-project claims hard to validate. The result is a mixed picture: some founder identity is public, but the team is not fully transparent, and prior-project/outcome/hack history is Not verifiable as of 2026-09-04 from the supplied sources.

The strongest confirmed fact is simply that NAVI Protocol is an onchain Sui lending/liquidity protocol with at least two named co-founders in public databases.

NAVI Lending appears to have a generally positive but still risk-aware reputation: it is widely described as a leading or largest lending protocol on Sui, with multiple security audits and backing from recognizable crypto investors, but several sources also flag elevated DeFi risk from leveraged products, thin liquidity, and the lack of bank-style protection. On founders/team, the web results do not provide a clear, independently verified founder roster in the retrieved sources, so detailed founder reputation is Not verifiable as of 2026-09-04. On investors, cited sources name OKX Ventures, dao5, Hashed, Mysten Labs, Comma3 Ventures, Mechanism Capital, Coin98 Ventures, Gate.com, and LBank Labs as participants in a reported $2M round, which is a positive credibility signal but should be treated as partially self-reported unless confirmed elsewhere.

On audits/security, NAVI says it has audits from MoveBit, Veridise, SALUS, and OtterSec published in full; other coverage also says it has passed multiple audits and highlights ongoing security review. I did not find a credible report of a major hack or exploit in the retrieved results; one investor-facing writeup says no known major exploit or hack had occurred through 2024, but that is not independent proof. On sentiment, the tone is mostly constructive: positive coverage emphasizes growth, ecosystem leadership, and product innovation, while risk-oriented coverage rates the protocol as moderate/elevated risk because leveraged vaults can amplify losses and Sui liquidity may be thin in stress events.

On criticisms / fraud / rug / insolvency allegations, I found no substantiated fraud, rug-pull, insolvency, or collapse allegation in the retrieved sources. The main criticisms are structural: leveraged strategies, liquidation/bad-debt exposure, and dependence on continued liquidity and market depth. On legal/regulatory / sanctions, I found no specific enforcement action, sanctions listing, or regulator-led allegation in the retrieved results; however, one risk review notes some regulatory exposure typical of DeFi lending.

Any broader compliance stance remains Not verifiable as of 2026-09-04.

As of September 6, 2026. NAVI Lending is primarily an over-collateralized, utilization-based money market on Sui. Users supply supported assets and receive interest-bearing nTokens; yield is mainly borrower-paid interest, increasing with utilization. Deposits can be withdrawn by redeeming nTokens, but withdrawals may be delayed when pool liquidity is insufficient. Assets/strategy: Core markets support SUI, stablecoins and major wrapped assets; NAVI also supports isolated/curated markets, EMode, flash loans and automatic-leverage/Multiply vault strategies.

NAVI Prime, launched in August 2026, separates liquidity into independently curated markets with market-specific risk parameters. These products create potential directional, leverage and liquidation exposure; ordinary supplying is market-neutral to asset price only in token units, not USD terms. Yield quality: Base yield is organic borrower interest. NAVX and other reward programs are subsidized/token-denominated yield and should not be treated as organic.

The organic/subsidized percentage split is Not verifiable as of September 6, 2026. APYs are floating by reserve and market conditions; one third-party USDSUI snapshot showed 2.74% base plus 4.60% reward APY on September 5, 2026, but this is not protocol-wide and does not establish sustainability. Risk controls/mechanics: Borrowing is collateralized and subject to LTV, liquidation thresholds, supply limits, debt ceilings, borrow limits and asset isolation. Liquidations are permissionless; documented close factor is 50%.

No fixed lock-up is documented, but withdrawals are liquidity-gated. Fees include borrower charges, a reserve/protocol revenue share, and Sui gas; the fee schedule can be changed by NAVI. TVL/revenue: Dune/on-chain verification is unavailable: Not verifiable as of September 6, 2026. DeFiLlama reports conflicting snapshots: approximately $143.69m total TVL on one page and $150.95m on the Sui chain page; both imply 100% Sui exposure.

Product-level TVL, historical trend reconciliation, and Dune-vs-DeFiLlama comparison are Not verifiable as of September 6, 2026. DeFiLlama’s latest surfaced page reports $516,696 30-day fees and $259,808 protocol revenue, but these are aggregator figures. Contradiction: NAVI’s site claims “$30B+ worth Loan Issued,” while current DeFiLlama active borrowing is materially lower; cumulative historical issuance and current debt are different metrics, so the marketing figure is not comparable and remains an unverified marketing claim.

Assessment as of September 6, 2026: Not verifiable as of 2026-09-06. Dune on-chain verification was unavailable for this run, so no current reserve balance, liabilities, or block-height snapshot is reported. NAVI documentation describes per-pool reserve accounting, including treasury_factor and treasury_balance fields within ReserveData; this indicates protocol-level reserve accrual rather than proving a separately managed treasury.

Lending documentation also states that supplier returns are affected by a reserve’s utilization, but does not disclose a complete reserve policy, fixed reserve ratio, or independently verifiable inventory. The official SDK documentation exposes treasuryObjectId and fee categories, including borrowing-interest and flash-loan/liquidation fees. However, the displayed balances are explicitly return examples, not a dated attestation or independently verified current balance.

The public developer examples identify NAVI’s Sui package/storage/reserve objects and pool object IDs, but do not establish treasury ownership, custody, signer thresholds, or control rights. Composition: Not verifiable as of 2026-09-06. Custody/control and reserve withdrawal permissions: Not verifiable as of 2026-09-06.

Reserve attestations or proof-of-reserves: Not verifiable as of 2026-09-06. Audits exist, but the discovered audit listings evidence code-security reviews, not financial-reserve attestations. CONTRADICTION / SCOPE: DeFiLlama reports protocol TVL and active loans, but TVL is user liquidity and active loans are protocol exposures—not treasury reserves or proof of solvency.

Therefore, those figures must not be used as liquid reserves or liabilities. Multi-chain: Sui only; chain-level reserve exposure is not verifiable as of 2026-09-06.

NAVI Lending on Sui does have a native token: NAVX. Because Dune/on-chain tooling is unavailable in this run, *all on-chain-verification items are* Not verifiable as of 2026-09-04. ### Basic token data

• Token name / ticker: Navi Protocol Token / NAVX
• Chain: Sui (Sui native token, not an EVM token)
• Contract address: Not verifiable as of 2026-09-04 (needs Sui explorer lookup versus official docs/contracts).
• Total vs circulating supply: Not verifiable as of 2026-09-04.
• Market cap / FDV: Not verifiable as of 2026-09-04 (DeFiLlama / CoinGecko-type data cannot be treated as on-chain truth under current rules). ### Utility and governance role According to Navi’s docs and listings, NAVX is the governance and utility token for Navi Lending on Sui, used for:
• Governance voting on protocol parameters and upgrades (unverified marketing claim; no governance contracts cross-checked).
• Incentives and rewards for lending/borrowing/liquidity provision on Navi (unverified marketing claim). Detail such as whether NAVX directly receives protocol revenue, fee rebates, or priority liquidation rights is not clearly specified in independent sources; most descriptions are high-level incentive/governance language, so specific mechanisms are Not verifiable as of 2026-09-04. ### Revenue share, buybacks, burns, staking
• Explicit revenue share to NAVX holders, protocol buybacks, or automatic burns are not independently documented; any such claims from Navi’s own docs are unverified marketing claims.
• Staking / liquidity mining: NAVX is reportedly used as rewards for users supplying/borrowing assets (mining/emissions), but exact APRs and mechanisms are Not verifiable as of 2026-09-04. ### Emissions, unlocks, allocation Independent, non-Navi sources do not provide a full tokenomics breakdown (emission curve, unlock schedule, or % allocations to team/investors/treasury/community). Therefore:
• Emissions schedule: Not verifiable as of 2026-09-04.
• Unlock schedule & whether unlocks occurred on-chain: Not verifiable as of 2026-09-04.
• Allocations (team / investors / treasury / community): Not verifiable as of 2026-09-04. ### Holder concentration & controls
• Top holder concentration / insider wallets: Not verifiable as of 2026-09-04.
• Mint / blacklist / fee-switch functions & controller: Not verifiable as of 2026-09-04. ### Liquidity and listings
• NAVX is referenced as tradable in the Sui ecosystem; likely on Sui-native DEXes. Depth, main pools, and exact pairs are Not verifiable as of 2026-09-04. Given the lack of independent, detailed tokenomics, NAVX’s design must currently be treated as partially opaque, with most specifics remaining Not verifiable as of 2026-09-04.

A BTC move below $10,000 would be a severe stress event for NAVI Lending on Sui because BTC-backed positions would experience a large increase in LTV, and some accounts could breach liquidation thresholds if they were opened with aggressive leverage. NAVI’s public docs confirm the protocol uses LTV-based borrowing limits, and external reviews describe automatic liquidations once collateral value falls below required levels. The main risk transmission is collateral revaluation, not an immediate protocol failure: when BTC falls, borrowed positions become less overcollateralized, so liquidation pressure rises first on the most levered borrowers.

However, the exact share of NAVI’s exposure to BTC collateral, current loan-to-value distribution, liquidation thresholds, and chain-specific TVL composition are Not verifiable as of 2026-09-04 from the provided web results, so the magnitude of losses, bad debt risk, and liquidation cascade potential cannot be quantified here. NAVI also appears to support multiple collateral types and isolated markets on Sui, which can reduce cross-asset contagion relative to a single shared pool, but the size of that protection under a BTC crash is Not verifiable as of 2026-09-04. In practical terms, a sub-$10k BTC scenario would most likely produce elevated liquidations, higher borrow rates, and possible market stress around liquidator capacity; whether that becomes systemic for NAVI depends on real-time utilization and collateral mix, which are not available in the supplied sources.

For NAVI Lending on Sui, a 20% depeg in the largest collateral would likely push the affected borrowers closer to liquidation only if their positions were already near the protocol’s health-factor boundary. NAVI liquidates when a borrower’s Health Factor falls below 1, and up to 35% of the debt can be repaid during liquidation, with the corresponding collateral plus a liquidation fee seized. What can be stated from the available sources is limited: NAVI’s docs define liquidation mechanics, but the results do not provide the protocol’s live collateral composition, largest-collateral concentration, or current borrower-level buffers, so the system-wide impact of a 20% depeg is Not verifiable as of 2026-09-04.

Risk interpretation: if the largest collateral is a liquid-staking token or another correlated asset, a 20% price drop would reduce both collateral value and user health factors materially, which can trigger a liquidation cascade if many accounts share similar leverage. That cascade risk is consistent with third-party commentary on NAVI’s leverage vault structure, but that commentary does not quantify the effect of a 20% depeg on the live book. So the precise answer is: the stress loss is not quantifiable from the available evidence, but the protocol’s liquidation rule means a 20% depeg would be a meaningful shock and could cause liquidations wherever borrower buffers are thin.

For NAVI Lending on Sui, a “top counterparty insolvent” stress case is not directly verifiable from the available web results, so the contract-level loss waterfall, compensation rules, and exact smart-contract impact path are Not verifiable as of 2026-09-04. What can be stated is that NAVI is a shared-liquidity lending protocol with supply pools, collateralized borrowing, and liquidation mechanics; its technical docs say users deposit into pools and borrow against collateral, and the SDK/docs reference account management, pool operations, flash loans, liquidation, and rewards. In that framework, the expected loss path would typically be:

• Borrower insolvency/default: the borrower cannot repay, so the position moves to liquidation/auction behavior rather than a normal repayment path.
• Loss absorption: first by the borrower’s posted collateral, then by any liquidator incentive/discount mechanism that helps clear the position, and only after that by the pool’s remaining liquidity if collateral is insufficient.
• Compensation: liquidators are incentivized by discounts, while lenders are compensated only to the extent collateral recovery covers the debt; no independent insurance or guarantor mechanism is verifiable from the sources.
• Contract impact path: collateral valuation/risk parameters trigger health checks, liquidation logic, and pool balance updates inside the lending contracts; the docs confirm these components exist but do not expose a full audited insolvency waterfall in the retrieved material. A separate point is that NAVI appears to have moved from a single shared pool model toward independently curated markets (“NAVI Prime”), which would localize stress to the affected market rather than automatically spreading it across all markets, but the exact segregation and loss-sharing rules are Not verifiable as of 2026-09-04.

For NAVI Lending on Sui, a committed fraud by the DAO or owners is not verifiable as of 2026-09-04 based on the provided results. The search results include a user-generated Reddit accusation about a borrow-APR display issue, but that post itself states it is a website issue rather than fraud, and it is not an authoritative source of wrongdoing. The other results are either unrelated to NAVI Lending, discuss generic DeFi/DAO fraud patterns, or describe a separate fintech company named Navi that is not this protocol.

I did not find corroborated evidence from regulators, audits, governance records, or credible independent reporting showing that NAVI Lending’s DAO, founders, or owners committed fraud. If you want a stricter stress-test framing, the only supportable answer is: no confirmed DAO/owner fraud event found in the available sources; therefore the fraud scenario remains unverified.

For NAVI Lending on Sui, a negative 30d primary yield source is not verifiable as of 2026-09-04 from the provided web results. The only directly relevant data point is that DeFiLlama shows 30d fees of $568,042 on Sui for NAVI, but it does not identify the primary yield source or show that it turned negative. In a stress scenario, the practical implication is that NAVI’s supplier yield could compress materially if borrow demand, fee generation, or liquidation activity weakens; however, the magnitude and direction of that effect cannot be confirmed from the available sources.

NAVI is described as an over-collateralized lending protocol with liquidations used to protect solvency, so adverse market moves would primarily stress collateral quality and utilization rather than create yield from non-lending sources. I cannot verify whether the protocol has a separate insurance fund or other backstop from the provided sources; one secondary source claims there is no explicit insurance fund and bad debt could socialize to suppliers or require governance intervention, but that claim is not independently confirmed here and should be treated as unverified. Bottom line: for an institutional stress read, assume yield fragility under a demand shock, but the specific claim that NAVI’s primary yield source is negative over 30d is Not verifiable as of 2026-09-04 with the evidence provided.

Assessment (as of September 13, 2026): Governance is not proven to be controlling; operational control appears team/company-led for the frontend and development. NAVX documentation and the 2025 white paper claim token-holder voting over assets, rates, collateral ratios, and major updates, with enhanced dLP voting power. However, no binding proposal-to-execution workflow, quorum, proposal threshold, delegation rules, executable governance module, or evidence that votes control upgrades/parameters was established.

Treat these as unverified marketing claims. Control surface: NAVI Protocol Labs, Inc. owns/operates the platform materials and may change, suspend, restrict, or terminate frontend access at its discretion. Its GitHub organization maintains the public SDK and Move-contract repositories. The Terms distinguish the company-operated platform from the self-executing protocol and state that NAVI does not control protocol liquidity pools or trade execution; this does not verify contract-admin powers. Legal entity: NAVI Protocol Labs Inc.; Panama entity, registered July 20, 2023; registration/identifier 155740387; registered address in Panama City.

The white paper lists Maybe Mendieta as director; no complete board, beneficial-owner, or independent-director disclosure was verified. DAO reality: Symbolic/not established as controlling under the requested standard. Proposal process, execution authority, timelock, multisig signers/threshold, signer independence, emergency bypass, and admin ability to move user funds: Not verifiable as of September 13, 2026. Dune was unavailable; therefore NAVX voting concentration, top holders, treasury balances, admin objects, and on-chain execution evidence are also Not verifiable as of September 13, 2026. Key contradiction: NAVI describes NAVX as enabling decentralized/on-chain governance, while the reviewed materials do not demonstrate that token-holder decisions bind upgrades or parameter changes. The governance claim therefore does not satisfy the “actually controls” test.

NAVI Lending (Navi Protocol) is a DeFi lending/liquidity protocol on the Sui blockchain, not a licensed financial institution, and operates as a non‑custodial smart‑contract platform for lending/borrowing and liquidity provision. Because tool-based on‑chain and document checks are unavailable, all legal/regulatory points are Not verifiable as of 2026-09-04 beyond what public web sources state. Entity & jurisdiction

• Public materials (directory listings, reviews, exchange research) describe “Navi Protocol” / “NAVI Lending” purely as a decentralized protocol on Sui, with no clearly disclosed operating company (e.g., foundation or limited company) or registered jurisdiction.
• No independent source identifies a legal entity name, registration number, or domicile. Not verifiable as of 2026-09-04. Terms of Service / user restrictions
• Third‑party overviews present Navi as an open DeFi protocol letting users deposit, borrow and manage assets on Sui, with no mention of geographic blocking, investor qualification, or age limits.
• Any formal Terms of Service, risk disclosures, or prohibited‑jurisdiction lists (e.g., for U.S. persons) are Not verifiable as of 2026-09-04.
• As a result, you should assume no contractual investor protections are confirmed beyond generic DeFi use. KYC / AML
• All descriptions emphasize permissionless access: users lend, borrow, and interact via wallets on Sui without intermediaries or account creation.
• No source mentions KYC checks, AML screening, or sanctions‑screening policies. Not verifiable as of 2026-09-04. From an institutional risk view, treat it as non‑KYC, non‑custodial DeFi unless proven otherwise. Regulatory classification
• Independent write‑ups consistently classify Navi as a decentralized liquidity / lending protocol on Sui, offering shared and isolated pools and a Prime product oriented to funds and professional capital.
• This corresponds to typical DeFi crypto‑asset lending / liquidity protocol, potentially treated as a virtual‑asset service or unregulated software depending on jurisdiction; no source provides an official regulatory license or registration. Not verifiable as of 2026-09-04. Warnings, enforcement, court cases, sanctions
• Searches of news, protocol reviews and ecosystem directories show no reported regulatory enforcement action, public warning, or court case specifically naming Navi Protocol or NAVI Lending.
• There is no indication that Navi or its team is itself designated on sanctions lists. Not verifiable as of 2026-09-04.
• Therefore, active_enforcement: false and sanctioned: false are current best assessments, subject to change if future actions emerge. Data protection & privacy
• As a non‑custodial DeFi protocol on Sui, activity is primarily on‑chain; no independent source describes off‑chain data collection (e.g., IP, email) or a formal privacy policy.
• Any GDPR/DP law compliance posture is Not verifiable as of 2026-09-04. Institutional risk angle
• Key structural risk: protocol is a Sui‑native, non‑KYC, non‑custodial lending system with unclear legal entity and jurisdiction, making counterparty recourse and regulatory perimeter highly uncertain.
• Use for institutional capital would typically require separate assessment of: governing law and entity, enforceability of any terms, treatment under local virtual‑asset / securities / lending regulations, and internal policies on non‑KYC DeFi exposure.

GLEIF LEI registry unavailable at scan time. OFAC SDN screening of 'NAVI Lending': no match. SEC litigation and administrative release feeds: no mention.

NAVI Lending does not appear to issue its own stablecoin; the available sources describe it as a lending market that supports external stablecoins such as USDC and USDT on Sui. I could not verify any depeg event for the stablecoins used by NAVI Lending from the available sources, so the depeg history is not verifiable as of 2026-09-06.

NAVI Lending’s main risks are smart-contract correctness, oracle integrity, liquidation execution, Sui dependency, and governance/parameter changes. Independent analysis documents a historical NAVI-specific logic flaw that could enable withdrawal of the wrong asset; audits and a bounty reduce but do not eliminate this tail risk. On-chain verification of current reserves, collateral concentration, bad debt, privileged roles, and remediation status: Not verifiable as of September 5, 2026.

NAVI Lending’s top strengths are its Sui-native performance, multi-source oracle security, risk-managed market design, broad DeFi integration, and one-stop liquidity positioning. On Sui, it is built to benefit from parallel processing and low-latency execution, which is a core advantage for lending, liquidations, and capital movement.

• Sui-native scalability and speed: NAVI is designed on Sui, whose parallelized architecture and low fees support fast lending and borrowing flows, making the protocol more usable under high activity.
• Stronger price-feed resilience: NAVI’s upgraded oracle architecture combines Pyth and Supra, which reduces reliance on a single data source and improves price-feed robustness for lending markets.
• Risk controls for diverse assets: The protocol uses isolated markets / isolation mode, debt ceilings, supply and borrow limits, and liquidation controls to onboard more assets while limiting contagion risk.
• Capital-efficiency features: NAVI emphasizes leveraged vaults, yield-bearing tokens, and dynamic borrowing mechanics, which help users deploy collateral more efficiently.
• Integrated liquidity hub model: NAVI is positioned as a “one-stop” liquidity protocol on Sui, combining lending with adjacent DeFi functions and ecosystem integration, which strengthens user retention and product breadth.