# Table of Contents - [Introduction | Astros](#introduction-astros) - [Overview | Navi Protocol - docs](#overview-navi-protocol-docs) - [Community Links | Navi Protocol - docs](#community-links-navi-protocol-docs) - [White Paper | Navi Protocol - docs](#white-paper-navi-protocol-docs) - [Get Tokens on SUI | Navi Protocol - docs](#get-tokens-on-sui-navi-protocol-docs) - [Supply & Earn | Navi Protocol - docs](#supply-earn-navi-protocol-docs) - [Liquidations | Navi Protocol - docs](#liquidations-navi-protocol-docs) - [NAVI Pro | Navi Protocol - docs](#navi-pro-navi-protocol-docs) - [Notifications | Navi Protocol - docs](#notifications-navi-protocol-docs) - [Borrowing | Navi Protocol - docs](#borrowing-navi-protocol-docs) - [Flash Loan | Navi Protocol - docs](#flash-loan-navi-protocol-docs) - [NAVI AI Trading Bot | Navi Protocol - docs](#navi-ai-trading-bot-navi-protocol-docs) - [Astros DEX Aggregator | Navi Protocol - docs](#astros-dex-aggregator-navi-protocol-docs) - [💰 Integrating Fees | Astros](#-integrating-fees-astros) - [Getting Started | Astros](#getting-started-astros) - [Astros UI SDK | Astros](#astros-ui-sdk-astros) - [Liquidation Mechanics | Navi Protocol - docs](#liquidation-mechanics-navi-protocol-docs) - [Tutorial | Astros](#tutorial-astros) - [Glossary | Navi Protocol - docs](#glossary-navi-protocol-docs) - [Slippage | Astros](#slippage-astros) - [Supported Assets | Navi Protocol - docs](#supported-assets-navi-protocol-docs) - [Aggregator Components | Astros](#aggregator-components-astros) - [Aggregator API | Astros](#aggregator-api-astros) - [Granular Asset Risk Management | Navi Protocol - docs](#granular-asset-risk-management-navi-protocol-docs) - [Introduction | Astros](#introduction-astros) - [Liquidation Mechanics & Walkthrough | Navi Protocol - docs](#liquidation-mechanics-walkthrough-navi-protocol-docs) - [Deposits and Withdrawals | Astros](#deposits-and-withdrawals-astros) - [$xBTC Campaign FAQ | Navi Protocol - docs](#-xbtc-campaign-faq-navi-protocol-docs) - [Trading | Astros](#trading-astros) - [Hackathon - Overflow NAVI Bounty | Navi Protocol - docs](#hackathon-overflow-navi-bounty-navi-protocol-docs) - [Bug Bounty Program | Navi Protocol - docs](#bug-bounty-program-navi-protocol-docs) - [Audit Report | Navi Protocol - docs](#audit-report-navi-protocol-docs) - [Perpetual Trading | Astros](#perpetual-trading-astros) - [Referral | Astros](#referral-astros) - [NAVI Media Kit (logos) | Navi Protocol - docs](#navi-media-kit-logos-navi-protocol-docs) - [NAVX Tokenomics | Navi Protocol - docs](#navx-tokenomics-navi-protocol-docs) - [2025 Roadmap | Navi Protocol - docs](#2025-roadmap-navi-protocol-docs) - [Insurance Funds | Astros](#insurance-funds-astros) - [Margin | Astros](#margin-astros) - [Liquidation Process | Astros](#liquidation-process-astros) - [Funding | Astros](#funding-astros) - [Index and Mark Price | Astros](#index-and-mark-price-astros) - [Audit | Astros](#audit-astros) - [ADL | Astros](#adl-astros) - [FAQ | Navi Protocol - docs](#faq-navi-protocol-docs) - [Trading Fees | Astros](#trading-fees-astros) - [Points | Astros](#points-astros) - [Trading Volume Points | Astros](#trading-volume-points-astros) - [Astros Vault FAQ Page 1 | Astros](#astros-vault-faq-page-1-astros) - [Social Points | Astros](#social-points-astros) - [Astros Vault Campaign – Phase1 | Astros](#astros-vault-campaign-phase1-astros) - [Open Interest (OI) Points (Coming Soon) | Astros](#open-interest-oi-points-coming-soon-astros) - [Referral Points | Astros](#referral-points-astros) - [PnL Points(Coming Soon) | Astros](#pnl-points-coming-soon-astros) - [Contact Us | Astros](#contact-us-astros) - [Lending & Borrowing | Navi Protocol - docs](#lending-borrowing-navi-protocol-docs) - [Privacy Policy | Navi Protocol - docs](#privacy-policy-navi-protocol-docs) - [Settlement & Update Frequency Summary | Astros](#settlement-update-frequency-summary-astros) - [Privacy Policy | Astros](#privacy-policy-astros) - [Liquidation Points(Coming Soon) | Astros](#liquidation-points-coming-soon-astros) - [Terms of Service | Astros](#terms-of-service-astros) - [Terms of Service | Navi Protocol - docs](#terms-of-service-navi-protocol-docs) - [Build with NAVI Protocol | NAVI Protocol Developer Docs](#build-with-navi-protocol-navi-protocol-developer-docs) - [Decentralized Oracle | NAVI Protocol Developer Docs](#decentralized-oracle-navi-protocol-developer-docs) - [NAVI Uptime Status Page | NAVI Protocol Developer Docs](#navi-uptime-status-page-navi-protocol-developer-docs) - [Contract Configuration | NAVI Protocol Developer Docs](#contract-configuration-navi-protocol-developer-docs) - [Contract Integration with NAVI | NAVI Protocol Developer Docs](#contract-integration-with-navi-navi-protocol-developer-docs) - [NAVI API Collection | NAVI Protocol Developer Docs](#navi-api-collection-navi-protocol-developer-docs) - [FAQ | NAVI Protocol Developer Docs](#faq-navi-protocol-developer-docs) - [Smart Contract Overview | NAVI Protocol Developer Docs](#smart-contract-overview-navi-protocol-developer-docs) - [Flash Loan | NAVI Protocol Developer Docs](#flash-loan-navi-protocol-developer-docs) - [Lending Core | NAVI Protocol Developer Docs](#lending-core-navi-protocol-developer-docs) - [Retrieve Pools Info inside Contract | NAVI Protocol Developer Docs](#retrieve-pools-info-inside-contract-navi-protocol-developer-docs) - [Get the Latest Package ID | NAVI Protocol Developer Docs](#get-the-latest-package-id-navi-protocol-developer-docs) - [Calculator | NAVI Protocol Developer Docs](#calculator-navi-protocol-developer-docs) - [Get Pools Config and Oracle Price Feeds | NAVI Protocol Developer Docs](#get-pools-config-and-oracle-price-feeds-navi-protocol-developer-docs) - [Integration with Account Cap | NAVI Protocol Developer Docs](#integration-with-account-cap-navi-protocol-developer-docs) - [Get Flashloan Config | NAVI Protocol Developer Docs](#get-flashloan-config-navi-protocol-developer-docs) - [Oracle Interface | NAVI Protocol Developer Docs](#oracle-interface-navi-protocol-developer-docs) - [afSui, haSui, vSui API | NAVI Protocol Developer Docs](#afsui-hasui-vsui-api-navi-protocol-developer-docs) - [Dynamic Calculator | NAVI Protocol Developer Docs](#dynamic-calculator-navi-protocol-developer-docs) - [Storage | NAVI Protocol Developer Docs](#storage-navi-protocol-developer-docs) - [Demo | NAVI Protocol Developer Docs](#demo-navi-protocol-developer-docs) - [Release History | NAVI Protocol Developer Docs](#release-history-navi-protocol-developer-docs) - [NAVI API | NAVI Protocol Developer Docs](#navi-api-navi-protocol-developer-docs) - [NAVI Lending Protocol Upgrade Announcement (2025/11/17) | NAVI Protocol Developer Docs](#navi-lending-protocol-upgrade-announcement-2025-11-17-navi-protocol-developer-docs) --- # Introduction | Astros The Astros DEX Aggregator is a core part of the NAVI Ecosystem, providing seamless integration for high-performance decentralized trading with optimized execution, security, and a smooth user experience ### [](https://naviprotocol.gitbook.io/astros/#key-features) **Key Features** 1. **High-Performance Trading** The Astros DEX Aggregator offers fast and low-latency trading through optimized smart contracts and algorithms, ensuring stable and efficient transactions even during peak trading periods. 2. **Order Splitting** For large trades, the Astros DEX Aggregator automatically splits orders across multiple liquidity pools, helping users achieve the best prices for their transactions. 3. **Multi-Hop Trading** To further optimize trading costs and liquidity, the aggregator supports multi-hop trades, finding the best transaction paths across multiple routes to maximize value for users. 4. **Security and Reliability** Security is Astros's top priority. The DEX Aggregator employs multi-layered security protocols to ensure user funds are safe and trades execute smoothly. 5. **Zero Fee** The Astros DEX Aggregator charges **no fees**, providing users with a cost-effective and seamless trading experience. 6. **Performance** Built to meet the demands of high-volume trading, the Astros DEX Aggregator operates on powerful, redundant servers capable of horizontal scaling. This infrastructure allows us to seamlessly handle increasing traffic and growing trading activity without compromising speed or efficiency. Features Astros Aggregator Swap Rate Excellent Order Splitting Supported Multi-Hop Trading Supported API Latency (ms) 200 ms Fee 0% Backend Reliability Transparent with Uptime Status Page Backend Performance Capable of dynamic horizontal scaling ### [](https://naviprotocol.gitbook.io/astros/#supported-exchanges) **Supported Exchanges** * [Bluefin](https://trade.bluefin.io/) * [Aftermath](https://aftermath.finance/) * [Deepbook V3](https://www.deepbook.tech/) * [Momentum](https://app.mmt.finance/) * [Magma](https://app.magmafinance.io/) * [Turbos](https://turbos.finance/) * [LST Tokens](https://www.volosui.com/) * [Cetus](https://www.cetus.zone/) * [FlowX](https://flowx.finance/) (**Upcoming**) * More * For business inquiries about integrating your DEX pools or markets, please reach out to us. [📬Contact Us](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations) [NextAstros UI SDK](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media) Last updated 4 months ago * [Key Features](https://naviprotocol.gitbook.io/astros/#key-features) * [Supported Exchanges](https://naviprotocol.gitbook.io/astros/#supported-exchanges) --- # Overview | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs#what-is-navi) What Is NAVI? -------------------------------------------------------------------------------------- NAVI is the inaugural liquidity protocol on Sui. It enables users to participate as liquidity providers or borrowers within the Sui Ecosystem and provides a one-stop shop for all kinds of DeFi activities through its exhaustive ecosystem of apps. NAVI Provides an ecosystem of DeFi applications including Lending/Borrowing with NAVI Protocol, decentralized trading and Cross-chain swaps with Astros, and SUI Liquid Staking with Volo. On NAVI, liquidity providers supply assets to the market, earning passive income through yields, while borrowers have the flexibility to obtain loans for different assets. With its focus on providing essential DeFi infrastructure, NAVI has become a key player in the rapidly evolving Sui Ecosystem. The protocol's innovative features, such as Flash Loans, Automatic Leverage Vaults, LST Strategies and Isolation Mode, enable users to leverage their assets and access novel trading opportunities with minimized risks. NAVI's design provides support for digital assets at different risk levels, while its advanced security features ensure the protection of user funds and the mitigation of systemic risks. The name "NAVI" finds its roots in the original Indian language, meaning "Be Kind to People." This philosophy is reflected in the NAVI team's commitment to fostering mass adoption of DeFi by relying on the simplicity and security offered by the Move programming language. [](https://naviprotocol.gitbook.io/navi-protocol-docs#key-offerings) Key Offerings: ---------------------------------------------------------------------------------------- * Money Market diversity - 20+ Liquidity pools across BTCFi, Sui DeFi and native Stablecoins * Earn interest on supplied liquidity * Borrow at optimal interest rates * Deep liquidity that enables diverse DeFi yield Strategies. * Advanced capital management dashboard * One-click claim & compounding feature * One-click Stablecoin position migration [](https://naviprotocol.gitbook.io/navi-protocol-docs#why-navi) Why NAVI? ------------------------------------------------------------------------------ NAVI provides a decentralized liquidity protocol that enables users to lend and borrow cryptocurrency assets directly, bypassing intermediaries through a shared liquidity pool system. For each supported asset, NAVI establishes dedicated liquidity pools where users can deposit their assets, each one with their separate parameters. The amount available for borrowing is determined by a collateralization ratio, which adjusts dynamically according to supply and demand. For a deeper dive into the details, check out the Developers Docs. [](https://naviprotocol.gitbook.io/navi-protocol-docs#navx-token) NAVX token --------------------------------------------------------------------------------- NAVI features a governance system empowering NAVX token holders to participate in decision-making by voting on proposals and protocol updates. This includes decisions like setting interest rates, introducing new assets to the platform, and adjusting the collateralization ratio. For a comprehensive breakdown of tokenomics, take a look at the [NAVX Tokenomics](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics) page. [](https://naviprotocol.gitbook.io/navi-protocol-docs#glossary) Glossary ----------------------------------------------------------------------------- If you are unsure about any specific terms feel free to check the [Glossary](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/glossary) . Overall, Navi's architecture provides a decentralized and efficient way for users to lend and borrow assets, without the need for traditional financial intermediaries. In the following pages, we'll go in-depth into how the NAVI liquidity protocol works in all its aspects, from high-level mechanics to granular risk management features we've implemented If you still have any questions or issues, feel free to reach the Navi team over the live chat within the app or in the [discord](https://discord.com/invite/R6Xkbee8Xq) or [telegram channel](https://t.me/navi_protocol) [NextCommunity Links](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/community-links) Last updated 9 months ago * [What Is NAVI?](https://naviprotocol.gitbook.io/navi-protocol-docs#what-is-navi) * [Key Offerings:](https://naviprotocol.gitbook.io/navi-protocol-docs#key-offerings) * [Why NAVI?](https://naviprotocol.gitbook.io/navi-protocol-docs#why-navi) * [NAVX token](https://naviprotocol.gitbook.io/navi-protocol-docs#navx-token) * [Glossary](https://naviprotocol.gitbook.io/navi-protocol-docs#glossary) --- # Community Links | Navi Protocol - docs ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252Few3ndjCz3E3TXFMl6TjF%252F1500x500.jpeg%3Falt%3Dmedia%26token%3De7ed25cd-cceb-4faf-a2f1-90cebdbf549a&width=768&dpr=4&quality=100&sign=62f893a3&sv=2) Website: [**https://www.naviprotocol.io/**](https://www.naviprotocol.io/) Launch APP: [**https://app.naviprotocol.io/**](https://app.naviprotocol.io/) Twitter: [**https://twitter.com/navi\_protocol**](https://twitter.com/navi_protocol) Discord: [**https://discord.gg/R6Xkbee8Xq**](https://discord.gg/R6Xkbee8Xq) Telegram: [**https://t.me/navi\_protocol**](https://t.me/navi_protocol) Medium: [**https://medium.com/@navi.protocol**](https://medium.com/@navi.protocol) Naver Blog: [**https://blog.naver.com/naviprotocol**](https://blog.naver.com/naviprotocol) Linkedin: [**https://www.linkedin.com/company/94845461**](https://www.linkedin.com/company/94845461/admin/feed/posts/) [PreviousOverview](https://naviprotocol.gitbook.io/navi-protocol-docs) [NextWhite Paper](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper) Last updated 9 months ago --- # White Paper | Navi Protocol - docs ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252F7M16ebIAtLXE1AMxz2tG%252FNavi.png%3Falt%3Dmedia%26token%3Dff7edd45-b228-446c-b55b-bbd1bc359e9d&width=768&dpr=4&quality=100&sign=79303ff6&sv=2) IN ACCORDANCE WITH TITLE II OF REGULATION (EU) 2023/1114 ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#table-of-contents) Table of Contents **A. Information about the Person Seeking Admission to Trading** A.1 Name A.2 Legal Form A.3 Registered address A.4 Head office A.5 Registration Date A.6 Legal entity identifier A.7 Another identifier required pursuant to applicable national law A.8 Contact telephone number A.9 E-mail address A.10 Response Time (Days) A.11 Parent Company A.12 Members of the Management body A.13 Business Activity A.14 Parent Company Business Activity A.15 Newly Established A.17 Financial condition since registration **B. Information about the issuer, if different from the offeror or person seeking admission to trading** B.1 Issuer Information B.2 Name B.3 Legal Form B.4 Registered address B.5 Head office B.6 Registration Date B.7 Legal entity identifier B.8 Another identifier required pursuant to applicable national law B.9 Parent Company B.10 Members of the Management Body B.11 Business Activity B.12 Parent Company Business Activity **C. Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114** C.1 Name C.2 Legal Form C.3 Registered address C.4 Head office C.5 Registration Date C.6 Legal entity identifier of the operator of the trading platform C.7 Another identifier required pursuant to applicable national law C.8 Parent Company C.9 Reason for Crypto-Asset White Paper Preparation C.10 Members of the Management body C.11 Operator Business Activity C.12 Parent Company Business Activity C.13 Other persons drawing up the crypto- asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 **D. Information about the Crypto-Asset Project** D.1 Crypto-asset project name D.2 Crypto-assets name D.3 Abbreviation D.4 Crypto-asset project description D.5 Details of all natural or legal persons involved in the implementation of the crypto-asset project D.6 Utility Token Classification D.7 Key Features of Goods/Services for Utility Token Projects D.8 Plans for the token D.9 Resource Allocation D.10 Planned Use of Collected Funds or Crypto-Assets **E. Information about the Admission to Trading** E.1 Public Offering or Admission to trading E.2 Reasons for Public Offer or Admission to trading E.3 Fundraising Target E.4 Minimum Subscription Goals E.5 Maximum Subscription Goal E.6 Oversubscription Acceptance E.7 Oversubscription Allocation E.8 Issue Price E.9 Official currency or any other crypto- assets determining the issue price E.10 Subscription fee E.11 Offer Price Determination Method E.12 Total Number of Offered/Traded Crypto- Assets E.13 Targeted Holders E.14 Holder restrictions E.16 Refund Mechanism E.17 Refund Timeline E.18 Offer Phases E.19 Early Purchase Discount E.20 Time-limited offer E.21 Subscription period beginning E.22 Subscription period end E.23 Safeguarding Arrangements for Offered Funds/Crypto-Assets E.24 Payment Methods for Crypto-Asset Purchase E.25 Value Transfer Methods for Reimbursement E.26 Right of Withdrawal E.27 Transfer of Purchased Crypto-Assets E.28 Transfer Time Schedule E.29 Purchaser's Technical Requirements E.30 Crypto-asset service provider (CASP) name E.31 CASP identifier E.32 Placement form E.33 Trading Platforms name E.34 Trading Platforms Market Identifier Code (MIC) E.35 Trading Platforms Access E.36 Involved costs E.37 Offer Expenses E.38 Conflicts of Interest E.39 Applicable law E.40 Competent court **F. Information about the Crypto-Assets** F.1 Crypto-Asset Type F.2 Crypto-Asset Functionality F.3 Planned Application of Functionalities F.4 Type of white paper F.5 The type of submission F.6 Crypto-Asset Characteristics F.7 Commercial name or trading name F.8 Website of the issuer F.9 Starting date of offer to the public or admission to trading F.10 Publication date F.11 Any other services provided by the issuer F.12 Language or languages of the white paper F .13 Digital Token Identifier Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available F.14 Functionally Fungible Group Digital Token Identifier, where available F.15 Voluntary data flag F.16 Personal data flag F.17 LEI eligibility F.18 Home Member State F.19 Host Member States **G. Information on the rights and obligations attached to the crypto-assets** G.1 Purchaser Rights and Obligations G.2 Exercise of Rights and obligations G.3 Conditions for modifications of rights and obligations G.4 Future Public Offers G.5 Issuer Retained Crypto-Assets G.6 Utility Token Classification G.7 Key Features of Goods/Services of Utility Tokens G.8 Utility Tokens Redemption G.9 Non-Trading request G.10 Crypto-Assets purchase or sale modalities G.11 Crypto-Assets Transfer Restrictions G.12 Supply Adjustment Protocols G.13 Supply Adjustment Mechanisms G.14 Token Value Protection Schemes G.15 Token Value Protection Schemes Description G.16 Compensation Schemes G.17 Compensation Schemes Description G.18 Applicable law G.19 Competent court **H. Information on the Underlying Technology** H.1 Distributed ledger technology H.2 Protocols and technical standards H.3 Technology Used H.4 Consensus Mechanism H.5 Incentive Mechanisms and Applicable Fees H.6 Use of Distributed Ledger Technology H.7 DLT Functionality Description H.8 Audit H.9 Audit outcome **I. Information on Risks** I.1 Offer-Related Risks I.2 Issuer-Related Risks I.3 Crypto-Assets-related Risks I.4 Project Implementation-Related Risks I.5 Technology-Related Risks I.6 Mitigation measures **J. Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts** S.1 Name S.2 Relevant legal entity identifier S.3 Name of the crypto-asset S.4 Consensus Mechanism S.5 Incentive Mechanisms and Applicable Fees S.6 Beginning of the period to which the disclosure relates S.7 End of the period to which the disclosure relates S.8 Energy consumption S.9 Energy consumption sources and methodologies ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#regulatory-disclosures) Regulatory Disclosures **01\. Date of Notification: 2025-09-16** **02\. Statement in accordance with Article 6(3) of Regulation (EU) 2023/1114:** This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. The person seeking admission to trading of the crypto-asset is solely responsible for the content of this crypto-asset white paper. **03\. Compliance statement in accordance with Article 6(6) of Regulation (EU) 2023/1114** This crypto-asset white paper complies with Title II of Regulation (EU) 2023/1114 and, to the best of the knowledge of the management body of NAVI Protocol, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import. **04\. Statement in accordance with Article 6(5), points (a), (b), (c):** The crypto-asset referred to in this white paper may lose its value in part or in full, may not always be transferable and may not be liquid. **05\. Statement in accordance with Article 6(5), point (d):** The utility token referred to in this white paper may not be exchangeable against the good or service promised in the crypto-asset white paper, especially in the case of a failure or discontinuation of the crypto-asset project. **06\. Statement in accordance with Article 6(5), points (e) and (f):** The crypto-asset referred to in this white paper is not covered by the investor compensation schemes under Directive 97/9/EC of the European Parliament and of the Council. The crypto-asset referred to in this white paper is not covered by the deposit guarantee schemes under Directive 2014/49/EU of the European Parliament and of the Council. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#summary) Summary **07\. Warning:** This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council (36) or any other offer document pursuant to Union or national law. **08\. Characteristics of the Crypto-Asset** NAVX is the utility and governance token for the NAVI Protocol. Purchasers of NAVX tokens have the right to participate in the protocol's governance by voting on proposals, such as changes to interest rates, the addition of new assets, or adjustments to collateral ratios. Holders can also provide liquidity for NAVX trading pairs and lock their tokens to receive benefits like boosted rewards, a share of protocol revenue, and enhanced voting power. These rights are exercised by participating in on-chain governance votes or by interacting with the protocol's liquidity features through a compatible wallet. According to the issuer, no modifications to these rights and obligations are anticipated or planned. **09\. Utility Token Summary** The $NAVX token is the native utility and governance token for the NAVI Protocol, a decentralized liquidity platform offering crypto-asset lending and borrowing services with a total supply of 1,000,000,000 tokens. The token’s primary utilities include: (i) Governance, allowing holders to vote on protocol proposals such as adding new assets, setting interest rates, and adjusting collateral ratios; and (ii) Dynamic Liquidity Provision (dLP), where users who provide liquidity for NAVX pairs and lock the resulting LP tokens can receive benefits like boosted rewards, a share of protocol revenue, and enhanced voting power. No restrictions on the transferability of the token are specified in the provided information. **10\. Key Information About the Admission to Trading** No public offer of NAVX tokens is being made, as the token is already in circulation. This document concerns the admission of the token to trading, and as such, there are no fundraising targets, issue prices, or subscription periods. The goal of the admission is to provide a seamless trading experience for the community. No crypto-asset service provider has been appointed to place the token. Admission to trading is being sought on several platforms, including Kraken, OKX, and Coinbase. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#a.-information-about-the-person-seeking-admission-to-trading) A. Information about the Person Seeking Admission to Trading A.1 Name: NAVI PROTOCOL LABS INC. A.2 Legal Form: 6TPA A.3 Registered address: Financial Center, Balboa Avenue and Aquilino De La Guardia Street, Floor 51, Suite 5102, Panama City, Republic of Panama. A.4 Head office: Campo Alegre Edificio Angeliki, Local 1A, Planta Baja Apdo. , Panama, 0832-00402, RE A.5 Registration Date: 2023-07-20 A.6 Legal entity identifier: N/A A.7 Another identifier required pursuant to applicable national law: 155740387 A.8 Contact telephone number: +1 213 265 2115 A.9 E-mail address: team@naviprotocol.io A.10 Response Time (Days): 007 A.11 Parent Company: N/A A.12 Members of the Management body: Name Business Function Business Address Maybe Mendieta Director Financial Center, Balboa Avenue and Aquilino De La Guardia Street, Floor 51, Suite 5102 A.13 Business Activity: NAVI Protocol is the most trusted DeFi infrastructure on #Sui with the leading Lending + LSDeFi platforms. Co-led by OKX Ventures, Hashed, and Dao5. NAVI dominates the leading spot in both lending and liquid staking in the Sui network since its launch. Website Link: [https://naviprotocol.io/](https://naviprotocol.io/) A.14 Parent Company Business Activity: N/A A.15 Newly Established: false A.17 Financial condition since registration: Since its launch to the end of 2025 Q2, the total revenue has reached 28.61M, including borrowing fee 17.79M, interest income: 9.99M, and liquidation income 794K, flash loan income 25.85K. Business development and performance: - Revenue and expenses: fees from lending, DEX, and staking; costs include development, marketing, operations. - KPIs: TVL growth, trading volume, active users - Material changes: steady growth in TVL and trading volume - Extraordinary events: no major financial restructuring. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#b.-information-about-the-issuer-if-different-from-the-offeror-or-person-seeking-admission-to-trading) B. Information about the issuer, if different from the offeror or person seeking admission to trading B.1 Issuer Information: false, the offeror and entity are the same, so this section is not applicable B.2 Name: N/A B.3 Legal Form: N/A B.4 Registered address: N/A B.5 Head office: N/A B.6 Registration Date: N/A B.7 Legal entity identifier: N/A B.8 Another identifier required pursuant to applicable national law: N/A B.9 Parent Company: N/A B.10 Members of the Management Body: N/A B.11 Business Activity: N/A B.12 Parent Company Business Activity: N/A ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#c.-information-about-the-operator-of-the-trading-platform-in-cases-where-it-draws-up-the-crypto-asse) C. Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114 C.1 Name: N/A, This section is not applicable, as neither the operator of a trading platform nor any other person, apart from the issuer, has drawn up or contributed to the preparation of the crypto-asset white paper. C.2 Legal Form: N/A C.3 Registered address: N/A C.4 Head office: N/A C.5 Registration Date: N/A C.6 Legal entity identifier of the operator of the trading platform: N/A C.7 Another identifier required pursuant to applicable national law: N/A C.8 Parent Company: N/A C.9 Reason for Crypto-Asset White Paper Preparation: N/A C.10 Members of the Management body: N/A C.11 Operator Business Activity: N/A C.12 Parent Company Business Activity: N/A C.13 Other persons drawing up the crypto- asset white paper according to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114: N/A C.14 Reason for drawing the white paper by persons referred to in Article 6(1), second subparagraph, of Regulation (EU) 2023/1114: N/A ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#d.-information-about-the-crypto-asset-project) D. Information about the Crypto-Asset Project D.1 Crypto-asset project name: NAVI Protocol D.2 Crypto-assets name: NAVX D.3 Abbreviation: NAVX D.4 Crypto-asset project description: NAVI Protocol is the most trusted DeFi infrastructure on #Sui with the leading Lending + LSDeFi platforms. Co-led by OKX Ventures, Hashed, and Dao5. NAVI dominates the leading spot in both lending and liquid staking in the Sui network since its launch. Website Link: [https://naviprotocol.io/](https://naviprotocol.io/) D.5 Details of all natural or legal persons involved in the implementation of the crypto-asset project: Name Business Function Business Address Maybe Mendieta Director Financial Center, Balboa Avenue and Aquilino De La Guardia Street, Floor 51, Suite 5102 D.6 Utility Token Classification: true D.7 Key Features of Goods/Services for Utility Token Projects: Navi's offering includes a decentralized liquidity protocol. It allows users to lend and borrow cryptocurrency assets without intermediaries, using a shared liquidity pool system. D.8 Plans for the token: Navi has a governance system that allows NAVX token holders to vote on proposals and changes to the protocol. This includes setting interest rates, adding new assets to the protocol, and changing the collateralization ratio. D.9 Resource Allocation: The funding round was co-led by OKX Ventures, dao5, and Hashed, with participation from other notable investors including Mysten Labs, Comma3 Ventures, Mechanism Capital, GeekCartel Capital, Nomad Capital, Coin98 Ventures, Cetus Protocol, Maverick, Viabtc, Assembly Partners, Gate.io, Hailstone Labs, Benqi and LBank Labs. D.10 Planned Use of Collected Funds or Crypto-Assets: **Team:** 20% — Allocated for team members to align with long-term project success. **Treasury:** 10% — Reserved for daily operations and strategic initiatives. **Liquidity Provision:** 4% — To support market makers and secure liquidity. **Public Sale (IDO):** 1.2% — Allocated for the initial decentralized exchange offering. **Marketing:** 3% — Used for promotional and outreach activities. **Ecosystem & Airdrop:** 45.8% — Dedicated to incentivizing TVL growth, running campaigns and airdrops. Includes the initial early supporters incentive. **Investors / Advisors:** 16% — Allocated for investors and advisors. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#e.-information-about-the-admission-to-trading) E. Information about the Admission to Trading E.1 Public Offering or Admission to trading: ATTR E.2 Reasons for Public Offer or Admission to trading: We aim to provide a seamless trading experience for our community, enabling them to trade our token across multiple platforms. E.3 Fundraising Target: N/A E.4 Minimum Subscription Goals: N/A E.5 Maximum Subscription Goal: N/A E.6 Oversubscription Acceptance: N/A E.7 Oversubscription Allocation: N/A E.8 Issue Price: N/A E.9 Official currency or any other crypto- assets determining the issue price: N/A E.10 Subscription fee: N/A E.11 Offer Price Determination Method: N/A E.12 Total Number of Offered/Traded Crypto- Assets: 1000000000 E.13 Targeted Holders: ALL E.14 Holder restrictions: No restrictions except applicable law E.16 Refund Mechanism: N/A E.17 Refund Timeline: N/A E.18 Offer Phases: N/A E.19 Early Purchase Discount: N/A E.20 Time-limited offer: N/A E.21 Subscription period beginning: N/A E.22 Subscription period end: N/A E.23 Safeguarding Arrangements for Offered Funds/Crypto-Assets: N/A E.24 Payment Methods for Crypto-Asset Purchase: Payments may be made in supported cryptocurrencies (e.g., USDT, USDC, ETH) and, where applicable, via fiat currency through approved payment channels. E.25 Value Transfer Methods for Reimbursement: N/A E.26 Right of Withdrawal: N/A E.27 Transfer of Purchased Crypto-Assets: Through vesting tools and custodian service provider E.28 Transfer Time Schedule: 2024-07-07 E.29 Purchaser's Technical Requirements: Purchasers must have a compatible blockchain wallet that supports the token’s network. E.30 Crypto-asset service provider (CASP) name: N/A E.31 CASP identifier: N/A E.32 Placement form: N/A E.33 Trading Platforms name: Kraken, OKX, Coinbase E.34 Trading Platforms Market Identifier Code (MIC): PGSL, N/A, FREX E.35 Trading Platforms Access: Investors can access the platforms via their official websites or mobile applications after completing any required registration and KYC procedures. E.36 Involved costs: Standard trading fees apply as set by the trading platform. Navi Protocol does not charge additional access fees. E.37 Offer Expenses: N/A E.38 Conflicts of Interest: No known conflicts of interest exist between the issuer, offeror, and trading platforms. E.39 Applicable law: Republic of Panama E.40 Competent court: For legal matters related to the offering, the competent court will be located in Panama, where our company is incorporated. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#f.-information-about-the-crypto-assets) F. Information about the Crypto-Assets F.1 Crypto-Asset Type: NAVX tokens are considered as crypto-assets other than EMTs and ARTs under Regulation (EU) 2023/1114. NAVX tokens are fungible utility tokens. F.2 Crypto-Asset Functionality: The $NAVX token has a wide range of use cases within NAVI Protocol. These use cases for $NAVX have been designed to promote growth and asset composability across the broader Sui DeFi ecosystem. They are part of the structured journey toward achieving decentralization, community governance, and vital protocol autonomy. F.3 Planned Application of Functionalities: The core functionalities of the NAVI Protocol are already fully operational within the Sui ecosystem. These include robust lending and borrowing services for a wide array of assets (such as SUI, USDT, USDC, WETH, and the native NAVX token), Flash Loans, Automatic Leverage Vaults, and initial Liquid Staked Token (LST) strategies. The NAVX token currently underpins the protocol's governance, enables Dynamic Liquidity (dLP) provision for boosted emissions and revenue sharing, and grants voting power to holders. Furthermore, the NAVI Pro platform, launched in 2024, already features a user-leveling system offering liquidation forecasting (V1) and reward auto-compounding (V2), while the Astros DEX Aggregator is live, facilitating decentralized trading and cross-chain swaps. F.4 Type of white paper: OTHR F.5 The type of submission: NEWT F.6 Crypto-Asset Characteristics: The $NAVX token is the native utility and governance token of the NAVI Protocol, operating on the Sui blockchain. It is classified as a "crypto-asset other than asset-referenced tokens or e-money tokens" under MiCAR. The token has a maximum total supply of 1,000,000,000 $NAVX. The primary characteristics and utilities of the $NAVX token are: 1. Governance: Token holders can participate in the governance of the NAVI Protocol by voting on proposals and updates. This includes decisions regarding the introduction of new assets, setting interest rates, and adjusting collateralization ratios for the money markets. 2. Dynamic Liquidity Provision (dLP): Users can provide liquidity to NAVX trading pairs on decentralized exchanges (DEXes) and lock the resulting LP tokens within the NAVI Protocol. This dLP mechanism grants several benefits: • Boosted Rewards: Earn additional $NAVX rewards on top of standard supply/borrow APY. • Revenue Sharing: A portion of the fees generated from borrowing activities on the platform is distributed to dLP holders. • Enhanced Voting Power: dLP holders have more leveraged voting power in governance compared to regular $NAVX token holders. • Reward Eligibility: Locking a specific percentage of a user's deposit value in dLP tokens is required to activate $NAVX emission rewards for their supplied and borrowed assets. F.7 Commercial name or trading name: NAVI Protocol F.8 Website of the issuer: [https://naviprotocol.io/](https://naviprotocol.io/) F.9 Starting date of offer to the public or admission to trading: 2025-10-14 (tentative) F.10 Publication date: 2025-10-14 F.11 Any other services provided by the issuer: The issuer also provides a DEX aggregator and a Telegram bot as part of its ancillary services. F.12 Language or languages of the white paper: English F.13 Digital Token Identifier Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available: N/A F.14 Functionally Fungible Group Digital Token Identifier, where available: N/A F.15 Voluntary data flag: false F.16 Personal data flag: false F.17 LEI eligibility: true F.18 Home Member State: IE F.19 Host Member States: AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, EL, HU, IS, IT, LI, LV, LT, LU, MT, NL, NO, PL, PT, RO, SK, SI, ES, SE ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#g.-information-on-the-rights-and-obligations-attached-to-the-crypto-assets) G. Information on the rights and obligations attached to the crypto-assets G.1 Purchaser Rights and Obligations: Navi has a governance system that allows NAVX token holders to vote on proposals and changes to the protocol. This includes setting interest rates, adding new assets to the protocol, and changing the collateralization ratio. G.2 Exercise of Rights and obligations: Navi has a governance system that allows NAVX token holders to vote on proposals and changes to the protocol. This includes setting interest rates, adding new assets to the protocol, and changing the collateralization ratio. G.3 Conditions for modifications of rights and obligations: No modifications to the rights and obligations of purchasers are anticipated or planned. G.4 Future Public Offers: Not applicable. G.5 Issuer Retained Crypto-Assets: 300,000,000 The issuer retains 30% of the total NAVX supply (1,000,000,000 NAVX), allocated as follows: 20% for the Team (200,000,000 NAVX) and 10% for the Treasury (100,000,000 NAVX)，subject to lock-up and governance rules as disclosed in the whitepaper. G.6 Utility Token Classification: true G.7 Key Features of Goods/Services of Utility Tokens: Navi's offering includes a decentralized liquidity protocol. It allows users to lend and borrow cryptocurrency assets without intermediaries, using a shared liquidity pool system. G.8 Utility Tokens Redemption: The $NAVX token has a wide range of use cases within NAVI Protocol. These use cases for $NAVX have been designed to promote growth and asset composability across the broader Sui DeFi ecosystem. They are part of the structured journey toward achieving decentralization, community governance, and vital protocol autonomy. G.9 Non-Trading request: true G.10 Crypto-Assets purchase or sale modalities: N/A G.11 Crypto-Assets Transfer Restrictions: Not applicable. G.12 Supply Adjustment Protocols: false G.13 Supply Adjustment Mechanisms: N/A G.14 Token Value Protection Schemes: false G.15 Token Value Protection Schemes Description: N/A G.16 Compensation Schemes: false G.17 Compensation Schemes Description: N/A G.18 Applicable law: Republic of Panama G.19 Competent court: For legal matters related to the offering, the competent court will be located in Panama, where our company is incorporated. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#h.-information-on-the-underlying-technology) H. Information on the Underlying Technology H.1 Distributed ledger technology: The NAVI Protocol is a native liquidity protocol built on the Sui blockchain, a decentralized Layer 1 distributed ledger technology (DLT). The protocol's smart contracts are developed using the Move programming language to leverage its security and simplicity features. The underlying Sui blockchain employs a Delegated Proof-of-Stake (DPoS) consensus mechanism and supports parallel transaction execution to enhance scalability and transaction speed. The native governance token, NAVX, is issued on the Sui chain. H.2 Protocols and technical standards: The NAVI Protocol is built on the Sui blockchain, a Layer 1 network that operates on a Delegated Proof-of-Stake (DPoS) consensus mechanism. The protocol's smart contracts are developed using the Move programming language, leveraging its security and object-centric model. The native governance token, $NAVX, is a native asset on the Sui chain. The protocol also provides a NAVI SDK for developers to integrate its functionalities into their applications and integrates with other Sui ecosystem components like DeepBook for liquidations and various oracles for price data. H.3 Technology Used: The NAVI protocol is a decentralized liquidity protocol built on the Sui blockchain, utilizing the Move programming language and its corresponding Virtual Machine (VM). The protocol's core functions, such as lending, borrowing, and liquidations, are managed through a system of smart contracts, including a primary \`LendingPool\` contract. Key technological features include Flash Loans, Automatic Leverage Vaults, and an Isolation Mode designed for the secure listing of new assets. To ensure accurate asset pricing, the protocol relies on multiple oracle partners. Liquidations are managed through integrations with DeepBook and other Automated Market Makers (AMMs). For developers seeking to build on the ecosystem, NAVI provides a Software Development Kit (SDK) to facilitate the creation of integrated applications and automated bots. Users can interact with the protocol and manage their assets using any SUI-compatible wallet. H.4 Consensus Mechanism: The NAVI Protocol is built on the Sui blockchain and relies on its native consensus mechanism for security and transaction validation. Sui utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism. In this system, SUI token holders delegate their stake to a fixed set of validators responsible for processing transactions. These validators secure the network and, in return, receive staking rewards, which are then distributed to the SUI holders who delegated their stake. H.5 Incentive Mechanisms and Applicable Fees: The Navi Protocol's economic model utilizes several incentive mechanisms and fees to ensure its stability and reward participants. To maintain the health of the lending pools, liquidators are incentivized to act when a borrower's position becomes under-collateralized. These liquidators can repay a portion of the debt and receive the borrower's collateral at a discounted price, known as a 'liquidation bonus'. The protocol, in turn, collects a platform fee equivalent to 10% of these liquidation incentives. For users, the primary incentives are derived from supplying and borrowing activities. Liquidity providers earn passive income from the interest paid by borrowers. Furthermore, users can enhance their returns through the Dynamic Liquidity Provision (dLP) mechanism. By providing liquidity to NAVX token pairs on external DEXes and locking the LP tokens, users can receive boosted $NAVX emission rewards on their activities and a share of the protocol's borrowing fee revenue. A portion of the interest paid on all loans is allocated to the protocol's treasury, as defined by each asset's 'Reserve Factor'. Specific services have their own fee structures. Flash Loans incur a fee of 0.06% of the borrowed amount, which is directed to the protocol treasury. The NAVI AI Trading Bot applies a 1% transaction fee on all trades and features a referral program that offers rewards and fee discounts. H.6 Use of Distributed Ledger Technology: falseH.7 DLT Functionality Description: N/AH.8 Audit: trueH.9 Audit outcome: The Navi Token audit (OtterSec, Jan 2024) found no critical issues, only one best-practice suggestion (hardcoded TreasuryCap recipient), which was fixed. The Navi Oracle audit (Veridise, Jun 2024) identified 13 issues (1 high, 2 medium, others low/warnings), with some fixed and others only acknowledged, highlighting risks around stale prices, centralization, and missing validations. [Audit links](https://naviprotocol.gitbook.io/navi-protocol-docs/security/audit-report) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#i.-information-on-risks) I. Information on Risks I.1 Offer-Related Risks: An investment in NAVX tokens involves a high degree of risk and is suitable only for sophisticated investors who are capable of understanding and evaluating the risks involved. Prospective purchasers should carefully consider the risks described below before purchasing NAVX tokens. The occurrence of any of these risks could have a material adverse effect on the NAVI Protocol, the value of the NAVX tokens, and a purchaser's ability to trade or use them. **Market and Price Volatility Risks** The market for crypto-assets is new, rapidly evolving, and subject to extreme price volatility and unpredictable fluctuations. The value of NAVX is not static and may be subject to significant downward pressure due to a variety of factors, including, but not limited to: * **Market Sentiment:** Negative publicity, changes in investor confidence, and broader market trends in the crypto-asset space can severely impact the token's price. * **Trading Volume and Liquidity:** The value of NAVX is dependent on the existence of liquid secondary markets on decentralized (DEX) and/or centralized (CEX) exchanges. A lack of active buyers and sellers may result in low trading volume, leading to high price volatility, increased slippage on trades, and difficulty in liquidating NAVX holdings at a desired price. * **Initial Decentralized Exchange Offering (IDO):** The price of NAVX tokens during the Public Sale (IDO) may not be indicative of its market price following the offering. The token's price could decline significantly after it becomes available on public trading platforms. **Risks Associated with the NAVI Protocol** The utility and value of the NAVX token are intrinsically linked to the performance, adoption, and security of the NAVI Protocol. Any adverse developments affecting the protocol will directly impact the NAVX token. * **Dependence on Protocol Success:** The NAVX token's primary utility is within the NAVI ecosystem, particularly for governance and liquidity provision incentives. If the NAVI Protocol fails to attract and retain a substantial user base, or if its Total Value Locked (TVL) declines, the demand for and value of NAVX could diminish significantly. * **Smart Contract Risk:** As explicitly stated in the project's FAQ, the NAVI Protocol operates on smart contracts that are susceptible to unforeseen bugs, vulnerabilities, or exploits. Despite having undergone multiple audits by firms such as OtterSec, Movebit, and Salus, there is no guarantee that the code is free from flaws. A successful exploit could result in the loss of user funds and irreparable damage to the protocol's reputation and the token's value. * **Oracle Risk:** The protocol relies on decentralized oracles to obtain accurate price feeds for assets, which is critical for calculating collateral value and triggering liquidations. Manipulation of or failures in these oracle systems could lead to incorrect pricing, unwarranted liquidations, or the accumulation of bad debt within the protocol, thereby threatening its solvency and the value of NAVX. * **Liquidation Mechanism Risks:** The protocol's stability depends on an efficient liquidation process to manage undercollateralized loans. In times of extreme market volatility and network congestion, liquidations may not occur in a timely manner. This could lead to bad debt accruing to the protocol, potentially undermining its financial health and causing a loss of confidence among users and token holders. * **Governance Risks:** NAVX token holders participate in protocol governance. While this provides a decentralized decision-making process, it also introduces risks. Contentious proposals, low voter turnout, or malicious actors influencing votes could lead to decisions that are detrimental to the long-term health and security of the protocol. **Risks Associated with the Underlying Infrastructure** * **Sui Blockchain Risk:** The NAVI Protocol is built on the Sui blockchain. Its performance, security, and stability are entirely dependent on the Sui network. Any attacks, outages, or technical failures of the Sui blockchain, such as a 51% attack, could render the NAVI Protocol inoperable and cause a total loss of value for NAVX tokens. The Sui network operates on a Delegated Proof-of-Stake (DPoS) model with a relatively small set of validators, which may present a higher degree of centralization risk compared to other blockchains. **Execution and Operational Risks** * **Competition:** The DeFi lending and borrowing sector is highly competitive. NAVI Protocol faces competition from existing and future protocols on Sui and other blockchains. Failure to innovate, adapt, and maintain a competitive edge could lead to a loss of market share, negatively affecting the protocol's growth and the NAVX token's value. * **Roadmap Uncertainty:** The team has outlined an ambitious roadmap for 2025, including multi-chain expansion and new ecosystem products. There is a risk that the team may not be able to deliver on these plans due to technical challenges, funding issues, or shifting priorities. Failure to achieve key roadmap milestones could lead to a loss of community and investor confidence. **Legal and Regulatory Risks** The legal and regulatory landscape for crypto-assets, decentralized finance, and token offerings is uncertain and constantly evolving across various jurisdictions. Future legislative or regulatory actions could severely restrict the operations of the NAVI Protocol, the utility of the NAVX token, or the ability for NAVX to be traded on exchanges. Such developments could impose significant compliance costs or even render the project's business model untenable, leading to a significant decline in the token's value. I.2 Issuer-Related Risks: N/AI.3 Crypto-Assets-related Risks: Participation in the NAVI Protocol and the holding of its associated crypto-assets, including the native NAVX token, involve substantial risk. Users should carefully consider their financial situation and risk tolerance before engaging with the protocol. The value of crypto-assets is highly volatile and can be influenced by a multitude of factors. Potential users must understand that they could lose all or a substantial portion of their deposited funds. The following is a non-exhaustive list of the key risks associated with the NAVI Protocol and its crypto-assets. **Protocol-Specific Risks** 1. **Smart Contract Risk:** The NAVI Protocol operates based on complex, self-executing smart contracts deployed on the Sui blockchain. While these contracts have undergone multiple security audits by reputable firms such as OtterSec, Movebit, and Salus, and are subject to an ongoing Bug Bounty Program, there is an inherent risk of unforeseen bugs, vulnerabilities, or flaws in the code. A malicious actor could exploit such a vulnerability to drain funds from the protocol's liquidity pools, deny access to user funds, or otherwise disrupt protocol operations, leading to a partial or total loss of user assets. 2. **Liquidation Risk:** This is a primary risk for users who borrow assets on the protocol. A user's position is quantified by a 'Health Factor,' which represents the safety of their supplied collateral against their borrowed debt. If the value of a user's collateral decreases or the value of their borrowed assets increases, their Health Factor will decline. If the Health Factor drops below 1, the position is deemed undercollateralized and becomes eligible for liquidation. During a liquidation event, a portion of the borrower's collateral (up to 35%) is forcibly sold at a discount to a third-party liquidator to repay the debt. This process incurs a liquidation penalty (or bonus for the liquidator), resulting in a net loss for the borrower beyond the normal market depreciation of their assets. 3. **Oracle Risk:** The protocol relies on external price feeds, known as oracles, to determine the value of supplied and borrowed assets for calculating collateral ratios and triggering liquidations. The NAVI Protocol may use a combination of oracles to ensure price accuracy. However, these oracles are a potential point of failure. They could be subject to manipulation, technical failure, or network congestion, leading to the broadcast of inaccurate price data. Inaccurate pricing could cause premature or unfair liquidations, or fail to trigger necessary liquidations, which could lead to the accumulation of bad debt within the protocol. 4. **Risk of Bad Debt:** The protocol is designed to remain overcollateralized at all times. However, in scenarios of extreme market volatility, the value of collateral could drop so rapidly that the liquidation process is insufficient to cover the outstanding debt. This is particularly relevant for assets with thin liquidity, where large liquidations could cause significant price slippage. Such events could result in bad debt, where the protocol's liabilities exceed its assets, potentially leading to losses for liquidity providers. **Asset-Specific and Market Risks** 1. **Asset Volatility and Liquidity Risk:** The NAVI Protocol supports a wide range of assets, from 'Blue Chip' crypto-assets to more volatile 'long-tail and exotic assets'. All crypto-assets are subject to extreme price volatility. A sudden and significant drop in the price of an asset used as collateral can rapidly decrease a user's Health Factor and lead to liquidation. Furthermore, long-tail assets often have lower trading volumes ('thin liquidity'). In a liquidation scenario, selling a large amount of a thinly traded asset could be difficult, potentially leading to bad debt as described above. To mitigate this, NAVI employs granular risk management tools like Supply Limits and Debt Ceilings, but the underlying risk remains. 2. **NAVX Token Risk:** The native NAVX token serves as a governance and utility token within the ecosystem. Its value is subject to market fluctuations and is not guaranteed. The utility of the token in governance (voting power) and liquidity provision (dLP mechanism) is tied to its market value and can be impacted by price volatility. Furthermore, the token has a defined emission and vesting schedule for team members, investors, and other stakeholders, which could introduce selling pressure on the market at various points in time. **External and Systemic Risks** 1. **Underlying Blockchain Risk:** The NAVI Protocol is built on the Sui blockchain. As such, it is susceptible to any risks inherent to the Sui network itself. These risks include, but are not limited to, consensus mechanism failures, network outages, undiscovered vulnerabilities in the Move programming language, or successful 51% attacks. The Sui network utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism with a relatively small set of 100 validators, which presents a higher degree of centralization compared to other blockchains and could increase its vulnerability to collusion or attack. 2. **Regulatory and Legal Risk:** The legal and regulatory landscape for decentralized finance (DeFi) and crypto-assets is constantly evolving and varies significantly by jurisdiction. Future laws, regulations, or legal actions could impose restrictions on the operation of the NAVI Protocol, its users, or the types of assets it supports, potentially impacting its functionality and the value of its associated assets. I.4 Project Implementation-Related Risks: The implementation of the NAVI Protocol project and the achievement of the objectives outlined in its roadmap are subject to a range of risks. These risks, if they materialize, could lead to delays in development, failure to deliver planned features, or an inability to achieve strategic goals, which may adversely affect the utility and value of the NAVX token. Prospective purchasers should carefully consider the following project implementation-related risks: **1\. Risks Associated with Roadmap Execution and Delays** The project's success is contingent upon the timely and effective execution of its 2025 roadmap. This roadmap includes ambitious milestones such as open-sourcing the SDK, multi-chain expansion, platform rebranding, infrastructure enhancements, and the launch of new ecosystem products. * **Developmental Complexity:** Features outlined, such as 'AI-driven trading tools' and 'fully autopilot advanced lending strategies,' involve significant technical complexity. There is a risk that these features may be more difficult or take longer to develop than anticipated, or they may not function as intended upon release. * **Timeline Slippage:** Any of the planned quarterly deliverables could face delays due to unforeseen technical challenges, resource constraints, or shifts in strategic priorities. Significant delays could erode community confidence and provide a competitive advantage to rival protocols. * **Failure to Deliver:** There is no guarantee that all features and expansions described in the roadmap will be successfully implemented. A failure to deliver on key promises could negatively impact user adoption and the overall viability of the ecosystem. **2\. Technological and Third-Party Dependency Risks** NAVI Protocol's functionality is intrinsically linked to the underlying Sui blockchain and a network of external partners and protocols. * **Underlying Blockchain Risk:** The protocol is built entirely on the Sui blockchain. Any performance issues, security vulnerabilities, network outages, or fundamental changes to the Sui network could directly and adversely affect NAVI Protocol's operations. Furthermore, the Sui blockchain utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism with a limited set of 100 validators. While this design enhances transaction speed, it introduces a higher degree of centralization compared to other blockchains, potentially increasing vulnerability to collusion or 51% attacks, which could compromise the integrity of the entire ecosystem. * **Programming Language Risk:** The protocol's smart contracts are written in Move, a language developed by Meta. While designed for security, Move has a smaller pool of experienced developers and security auditors compared to more established languages like Solidity. This could increase the risk of undiscovered vulnerabilities or create challenges in sourcing development talent. * **Third-Party Integrations:** The protocol relies on integrations with various third-party services, including multiple DEXs (Cetus, Turbos, Bluefin, Aftermath) for its DEX Aggregator, DeepBook for liquidations, and multiple oracle providers for price feeds. Any failure, exploit, or operational disruption of these external services is beyond the NAVI team's control and could severely impact the protocol's functionality, security, and solvency. **3\. Team and Governance Risks** The project is currently dependent on its core team, and its future decentralization carries its own implementation risks. * **Key Personnel Risk:** The NAVI Protocol team is described as a 'seasoned team of founders and builders'. The project's continued development and strategic direction are highly dependent on this core team. The departure of key members could disrupt operations and delay the execution of the roadmap. * **Transition to Decentralized Governance:** The roadmap outlines a transition towards greater community governance through mechanisms like 'Vetoken'. This transition is complex and poses several risks. The implementation could face technical hurdles, community engagement might be lower than expected, or the governance process could prove inefficient, leading to slow decision-making or contentious proposals that hinder the protocol's progress. **4\. Market Adoption and Competition Risks** The success of NAVI Protocol is not guaranteed and depends heavily on its ability to attract and retain a substantial user base in a highly competitive environment. * **Competition:** The DeFi lending and borrowing space is intensely competitive, with numerous established and emerging protocols on Sui and other blockchains. NAVI Protocol may fail to differentiate itself sufficiently or may be out-competed by projects with greater resources, brand recognition, or technological innovations. * **Failure of Growth Initiatives:** The project's growth strategy relies on marketing campaigns, user incentives, hackathons, and bounty programs. There is no assurance that these initiatives will be successful in attracting the required volume of liquidity providers, borrowers, and developers to create a sustainable and thriving ecosystem. A failure to achieve a critical mass of users and Total Value Locked (TVL) could threaten the long-term viability of the protocol. **5\. Inherent Security Risks in Implementation** Despite rigorous security measures, the implementation of a complex DeFi protocol is subject to inherent security risks. * **Smart Contract Vulnerabilities:** The protocol has undergone multiple security audits. However, no audit can provide a complete guarantee against all potential vulnerabilities. Undiscovered bugs, logic errors, or exploits in the smart contract code could lead to a loss of user funds. As the protocol evolves and new features are added according to the roadmap, new code will be deployed, introducing new potential attack vectors. * **Oracle Manipulation Risk:** The protocol's reliance on oracles for asset pricing creates a risk of manipulation. A sophisticated attacker could potentially manipulate the price feeds from oracles, leading to unfair liquidations or the draining of funds from the protocol's pools. _As stated in the project's own documentation, NAVI Protocol should be treated as a Beta product, and participation involves significant risk. Users and potential token holders should not invest or risk more than they are willing to lose._ I.5 Technology-Related Risks: Participation in the NAVI Protocol ecosystem entails exposure to a range of significant technology-related risks inherent in decentralized finance (DeFi) applications and the underlying blockchain infrastructure. While the NAVI Protocol team has implemented numerous security measures, including multiple smart contract audits, a bug bounty program, and granular risk management parameters, these risks cannot be entirely eliminated. Users should be fully aware of the following potential technological risks before interacting with the protocol. **1\. Smart Contract Vulnerabilities** The core logic of the NAVI Protocol is executed by smart contracts deployed on the SUI blockchain. Despite undergoing extensive audits by reputable firms such as OtterSec, Movebit, and Salus, there remains a risk of unforeseen bugs, design flaws, or vulnerabilities within the codebase. A malicious actor could potentially exploit such a vulnerability to drain funds from the liquidity pools, manipulate internal accounting, or cause the protocol to cease functioning correctly. A successful exploit could result in the partial or total loss of user funds deposited in the protocol. **2\. Underlying Blockchain Risks (SUI Blockchain)** NAVI Protocol operates on the SUI blockchain and is therefore inherently exposed to the risks of its underlying infrastructure. * **Consensus Mechanism and Centralization:** SUI utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism with a limited set of 100 validators. This relatively low number of validators introduces a degree of centralization, making the network potentially more susceptible to collusion or 51% attacks compared to more decentralized networks. Such an attack could lead to transaction censorship, block reorganization, or network halts, directly impacting the reliability and security of the NAVI Protocol. * **Network Maturity and Stability:** The SUI mainnet was launched in May 2023, making it a relatively young blockchain. As such, its core protocol may contain undiscovered vulnerabilities, and its long-term performance under extreme network congestion or adverse conditions is not as battle-tested as more established blockchains. A critical failure of the SUI network could render the NAVI Protocol inoperable and place user funds at risk. * **Programming Language Risks:** The protocol is developed using the Move programming language. While designed with a focus on security and asset safety, no programming language or its associated compiler and virtual machine is immune to undiscovered flaws. A critical vulnerability in the Move language or its implementation on SUI could have widespread consequences for all applications in the ecosystem, including NAVI. **3\. Oracle and Data Feed Risks** The protocol's operations, particularly lending, borrowing, and liquidations, are critically dependent on accurate and timely price data for supported assets, which is supplied by external oracles. There is a significant risk of oracle manipulation, where an attacker could compromise or influence the price feeds. Inaccurate price data could lead to unfair liquidations of solvent positions or allow attackers to borrow assets against artificially inflated collateral, creating bad debt within the protocol and causing losses for liquidity providers. While NAVI mitigates this by using multiple oracle providers, a coordinated attack or a systemic failure across several data sources remains a possibility. **4\. Liquidation Mechanism Risks** The solvency of the NAVI Protocol relies on a robust and efficient liquidation mechanism to close under-collateralized positions. This automated process is subject to several risks: * **Market Volatility and Network Congestion:** During periods of extreme price volatility ("black swan" events), rapid price drops combined with high network congestion on the SUI blockchain could prevent liquidations from being executed in a timely manner. This could cause the protocol to accumulate significant bad debt. * **Liquidator Incentive Failure:** The process depends on third-party liquidators who are incentivized by a liquidation bonus. If gas fees on the SUI network become prohibitively high or if the available liquidity on integrated DEXs (like DeepBook) is insufficient, liquidators may be unable or unwilling to participate. This lack of liquidation activity would leave the protocol exposed to under-collateralized debt. **5\. Ecosystem and External Dependencies** NAVI Protocol integrates with and depends on various other components and platforms, each introducing its own set of risks: * **Bridged Assets:** The protocol supports assets bridged from other blockchains (e.g., Wormhole USDC and WETH). The security of these assets is contingent on the security of the respective cross-chain bridge. An exploit of a bridge could cause the bridged asset to de-peg and lose its value, which would severely impact the NAVI liquidity pools holding that asset. * **DEX Aggregator Dependencies:** The Astros DEX Aggregator, part of the NAVI ecosystem, relies on external DEXs for trade execution. A vulnerability, liquidity issue, or failure at one of these third-party DEXs could negatively affect users of the aggregator. * **NAVI AI Trading Bot:** This Telegram-based bot introduces significant custodial and platform risks. By automatically creating and hosting wallets for users, it creates a potential single point of failure. Users are exposed to risks of flaws in the bot's code, vulnerabilities in the Telegram platform, and a heightened risk of scams and social engineering attacks. _Given these risks, NAVI Protocol should be considered a high-risk platform. Users must conduct their own due diligence and should not supply or borrow funds that they are not prepared to lose._ I.6 Mitigation measures: NAVI Protocol is built upon the Sui blockchain, leveraging the inherent security features of the Move programming language. The protocol has implemented a multi-faceted and robust framework to mitigate the technological risks associated with its DeFi lending and borrowing platform. These measures are designed to protect user funds, ensure protocol solvency, and maintain operational integrity. **1\. Smart Contract and Code Security** To address the risk of vulnerabilities and unforeseen bugs within the smart contracts, NAVI Protocol adheres to a stringent security regimen: * **Comprehensive Auditing:** The protocol's codebase has undergone multiple, extensive audits by reputable third-party security firms, including OtterSec, Movebit, Salus, and Verdise. These audits cover various aspects of the protocol, from the core lending contracts to tokenomics and penetration testing, with reports publicly available for transparency. * **Continuous Bug Bounty Program:** NAVI maintains an active Bug Bounty Program to incentivize the responsible disclosure of vulnerabilities by security researchers and developers. Rewards are tiered based on the severity of the finding, with up to 2,000,000 NAVX offered for critical vulnerabilities that could lead to the extraction of Total Value Locked (TVL). * **Secure by Design with Move:** The protocol is developed using the Move programming language, which is designed with a focus on resource safety and access control, inherently preventing entire classes of bugs common in other smart contract languages. The Sui blockchain's use of the Move Prover further allows developers to formally verify that code executes as intended, adding a critical layer of pre-deployment security. **2\. Oracle and Data Integrity** To mitigate the risk of price manipulation through oracle attacks, which could lead to improper liquidations and protocol insolvency, NAVI has implemented a resilient oracle security model: * **Multi-Oracle Architecture:** The platform does not rely on a single price feed. Instead, it aggregates quotes from multiple oracle partners to establish a reliable and accurate price for each asset. This redundancy ensures that the failure or compromise of a single oracle does not jeopardize the protocol. * **Diverse Oracle Mechanisms:** NAVI leverages a combination of oracle solutions, including Time-Weighted Average Price (TWAP) oracles where appropriate. This approach minimizes susceptibility to short-term price manipulation attacks, such as those executed via flash loans. **3\. Market and Liquidity Risk Management** The protocol incorporates granular risk parameters to manage the volatility and liquidity risks associated with the diverse range of assets it supports, especially long-tail and exotic assets: * **Supply Limits:** Each asset has a configurable supply cap, limiting the total amount that can be deposited into the protocol. This prevents over-exposure to a single, potentially volatile asset and protects the protocol from the risks associated with thinly traded tokens whose value could be easily manipulated. * **Debt Ceilings:** This parameter restricts the total amount of debt that can be borrowed against a specific type of collateral. Debt ceilings provide a precise tool to limit the systemic risk posed by a single collateral asset, preventing it from being used to open excessively large debt positions. * **Isolation Mode:** For newer or higher-risk assets, NAVI employs an "Isolation Market." Assets listed in this mode have a specific debt ceiling, and users can only borrow a pre-approved set of stablecoins against them. This effectively quarantines the risk associated with these assets, preventing any potential contagion from affecting the solvency of the main lending pools. **4\. Liquidation Mechanism Robustness** A timely and efficient liquidation process is critical to the health of any lending protocol. NAVI has engineered its liquidation mechanics to be reliable and robust: * **Economic Incentives:** The protocol offers a liquidation bonus—a discount on the collateral being purchased—to incentivize a decentralized network of third-party liquidators to monitor the protocol and promptly liquidate undercollateralized positions. This permissionless system creates a competitive and efficient market for liquidation. * **Deep Liquidity Integration:** To ensure that liquidations can be executed smoothly without significant price slippage, NAVI is tightly integrated with external liquidity sources on Sui, such as the DeepBook centralized limit order book. This provides a reliable venue for selling collateral in a timely manner. * **Proactive User Risk Management Tools:** To help users avoid liquidation, NAVI provides several tools: * **Health Factor Notifications:** Through an integration with Notifi, users can set up alerts via Email, Telegram, or Discord to be warned when their health factor drops, allowing them to take corrective action. * **Liquidation Forecast:** The NAVI Pro dashboard includes a feature that visually displays a user's current liquidation price, helping them better understand and manage their position's risk. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#j.-information-on-the-sustainability-indicators-in-relation-to-adverse-impact-on-the-climate-and-oth) J. Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts S.1 Name: NAVI PROTOCOL LABS INC. S.2 Relevant legal entity identifier: N/A S.3 Name of the crypto-asset: NAVX S.4 Consensus Mechanism: The NAVI Protocol is built on the Sui blockchain and relies on its native consensus mechanism for security and transaction validation. Sui utilizes a Delegated Proof-of-Stake (DPoS) consensus mechanism. In this system, SUI token holders delegate their stake to a fixed set of validators responsible for processing transactions. These validators secure the network and, in return, receive staking rewards, which are then distributed to the SUI holders who delegated their stake. S.5 Incentive Mechanisms and Applicable Fees: The Navi Protocol's economic model utilizes several incentive mechanisms and fees to ensure its stability and reward participants. To maintain the health of the lending pools, liquidators are incentivized to act when a borrower's position becomes under-collateralized. These liquidators can repay a portion of the debt and receive the borrower's collateral at a discounted price, known as a 'liquidation bonus'. The protocol, in turn, collects a platform fee equivalent to 10% of these liquidation incentives. For users, the primary incentives are derived from supplying and borrowing activities. Liquidity providers earn passive income from the interest paid by borrowers. Furthermore, users can enhance their returns through the Dynamic Liquidity Provision (dLP) mechanism. By providing liquidity to NAVX token pairs on external DEXes and locking the LP tokens, users can receive boosted $NAVX emission rewards on their activities and a share of the protocol's borrowing fee revenue. A portion of the interest paid on all loans is allocated to the protocol's treasury, as defined by each asset's 'Reserve Factor'. Specific services have their own fee structures. Flash Loans incur a fee of 0.06% of the borrowed amount, which is directed to the protocol treasury. The NAVI AI Trading Bot applies a 1% transaction fee on all trades and features a referral program that offers rewards and fee discounts. S.6 Beginning of the period to which the disclosure relates: 2024-01-01 S.7 End of the period to which the disclosure relates: 2024-12-31 S.8 Energy consumption: ~46,000 – 77,000 kWh S.9 Energy consumption sources and methodologies: Sources: Active validator nodes maintaining the NAVI network Methodology: Average power per validator node × number of active validators × 24 hours × 365 days Reference: Validator specifications, industry server benchmarks, DPoS node energy estimation [PreviousCommunity Links](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/community-links) [NextGet Tokens on SUI](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui) Last updated 2 months ago * [Table of Contents](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#table-of-contents) * [Regulatory Disclosures](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#regulatory-disclosures) * [Summary](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#summary) * [A. Information about the Person Seeking Admission to Trading](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#a.-information-about-the-person-seeking-admission-to-trading) * [B. Information about the issuer, if different from the offeror or person seeking admission to trading](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#b.-information-about-the-issuer-if-different-from-the-offeror-or-person-seeking-admission-to-trading) * [C. Information about the operator of the trading platform in cases where it draws up the crypto-asset white paper and information about other persons drawing the crypto-asset white paper pursuant to Article 6(1), second subparagraph, of Regulation (EU) 2023/1114](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#c.-information-about-the-operator-of-the-trading-platform-in-cases-where-it-draws-up-the-crypto-asse) * [D. Information about the Crypto-Asset Project](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#d.-information-about-the-crypto-asset-project) * [E. Information about the Admission to Trading](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#e.-information-about-the-admission-to-trading) * [F. Information about the Crypto-Assets](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#f.-information-about-the-crypto-assets) * [G. Information on the rights and obligations attached to the crypto-assets](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#g.-information-on-the-rights-and-obligations-attached-to-the-crypto-assets) * [H. Information on the Underlying Technology](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#h.-information-on-the-underlying-technology) * [I. Information on Risks](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#i.-information-on-risks) * [J. Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper#j.-information-on-the-sustainability-indicators-in-relation-to-adverse-impact-on-the-climate-and-oth) --- # Get Tokens on SUI | Navi Protocol - docs If you’re new to the Sui ecosystem and haven’t explored it yet, you’ll need to acquire some SUI tokens in your wallet to kick off your DeFi adventure. Here are a few tips to help you obtain your first SUI tokens ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-1.bridge-assets-from-another-network-with-astros) 1.Bridge assets from another network with [Astros](https://astros.ag/bridge/Sui-Ethereum/USDC-0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48) [Astros](https://astros.ag/swap/SUI-NAVX) , a DEX aggregator that is part of NAVI’s line of DeFi applications provides users with seamless, low-cost, and near-instant cross-chain swaps from Solana, Ethereum, Polygon, Arbitrum, and Avalanche. Prerequisite - set up a Sui-compatible wallet such as [Sui Wallet](https://suiwallet.com/) , [Phantom](https://phantom.com/) , [Suiet](https://suiet.app/) , [Nightly](https://nightly.app/) , [OKX Web3 Wallet](https://web3.okx.com/rewritethesystem) , [Binance Web3 Wallet](https://web3.okx.com/rewritethesystem) , etc. If you are looking to bridge any asset and swap it into one of the 20+ supported assets on NAVI Protocol: 1）Head to [https://astros.ag/bridge/Sui-Ethereum/SUI-ETH](https://astros.ag/bridge/Sui-Ethereum/SUI-ETH) 2）Select your source chain (e.g Polygon) 3）Select your source asset (e.g. USDC) 4）Select Sui as your destination chain 5）Select your destination asset (e.g. USDC on Sui) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcPV_Es1QjTUFsNEv7Mwt9MT1mdrRGdRZSKp_UPe-_P3x-S_RCX1Z_I0l6wn6lbGCZmkfgzquLX86Jc4w8fPoQQa-yDX0L5OmeI-CME-e_olJlz7OqdbFCeA2TMMbKxsb7qj0S_Mg%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=3def269d&sv=2) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-2.swap-assets-on-the-astros-integrated-widget) 2.Swap assets on the Astros integrated widget Once you have some assets on Sui Network, you can also swap them directly on the NAVI Protocol page, through the Astros integrated DEX aggregator widget. 1）On the [https://app.naviprotocol.io/](https://app.naviprotocol.io/) page, either press “S” or click the “Swap” tab 2）This will open the Astros widget where you can swap any Sui-based token, with the best routes and gas-free. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXe-iSoo6Svuocln4jDbHMehb0JZ83cSql7EbGKN3EN2eC3VgIFBnhSdFbGKIvy81h7b-DLf4KUwXofQ9G-V8-ROjtah3SAfkIRf5xwVrM0u55EmZAw_Iy5tPgQS-N2FR-9Nm8wcxQ%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=1887927d&sv=2) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-3.get-tokens-through-cex) 3.Get tokens through CEX You can also buy SUI tokens from centralized exchanges and withdraw it to your on-chain wallet. Mainstream CEXes like [Bybit](https://www.bybit.com/en-US/bysui/) , [Kucoin](https://www.kucoin.com/express) ,[Binance](https://www.binance.com/en/convert/USDT/SUI) all support SUI token withdrawal now. * **OKX:** [**https://web3.okx.com/dex-swap?chain=sui,sui&token=0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::coin,0x2::sui::sui**](https://web3.okx.com/dex-swap?chain=sui,sui&token=0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::coin,0x2::sui::sui) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252Fcpu2ZQtabHchOKQv4yyk%252Fokx.png%3Falt%3Dmedia%26token%3D8534d619-a541-4dbd-8f05-2649b05e959f&width=768&dpr=4&quality=100&sign=3c71c9c7&sv=2) * **Bybit:** [**https://www.bybit.com/fiat/trade/express/home**](https://www.bybit.com/fiat/trade/express/home) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252Fs1Q6DtA21AS6b8yBgoYy%252Fimage.png%3Falt%3Dmedia%26token%3Dbd153dfb-e8ba-4cb9-8639-447d780dec59&width=768&dpr=4&quality=100&sign=91383ae&sv=2) **Bybit** * **Kucoin:** [**https://www.kucoin.com/express**](https://www.kucoin.com/express) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FrhjLS52MCIA2plbXcYSS%252Fimage.png%3Falt%3Dmedia%26token%3D3ab10b22-169c-4528-ab57-e1a5d4c19f63&width=768&dpr=4&quality=100&sign=6b72af15&sv=2) **Kucoin** * **Binance:** [**https://www.binance.com/en/convert/USDT/SUI**](https://www.binance.com/en/convert/USDT/SUI) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252F9Iele2ieQszQwqX6uJ51%252Fimage.png%3Falt%3Dmedia%26token%3D588c1bdf-b242-4a7e-88e7-3fe6ba0ba183&width=768&dpr=4&quality=100&sign=b03df4a3&sv=2) **Binance** [PreviousWhite Paper](https://naviprotocol.gitbook.io/navi-protocol-docs/introduction/white-paper) [NextSupply & Earn](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn) Last updated 8 months ago * [1.Bridge assets from another network with Astros](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-1.bridge-assets-from-another-network-with-astros) * [2.Swap assets on the Astros integrated widget](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-2.swap-assets-on-the-astros-integrated-widget) * [3.Get tokens through CEX](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui#id-3.get-tokens-through-cex) --- # Supply & Earn | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#connect-wallet) Connect Wallet ------------------------------------------------------------------------------------------------------------------------- Head over to [app.naviprotocol.io](https://app.naviprotocol.io/) to access our app. To interact with NAVI, you will need an SUI-compatible wallet. Click the ”Connect Wallet” button at the top right corner of the screen and select your preferred wallet. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcm36HDyVz2MVNDU3BlMuglUZ3sq7yuO6KlLOzQ3tneadLNh1iObvRSiSlWi0Bgf4Z7Ua_V-VQA6bgv2D_z_z9sJfF8w3U8wn3B0q2L966C6mcAYt54u5gyQBJWs_DBqPzicH8IbQ%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=22150ccf&sv=2) [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#deposit-supply) Deposit/Supply ------------------------------------------------------------------------------------------------------------------------- Once the wallet is connected, you can continue to the next step. By clicking the “Supply” button of the asset you owned, you will be able to deposit your assets in the navigational window on the right side. You can also click the "Details" button, to view the asset information page that will give you more insight into the LTV, Collateral value, and liquidation rates. * Select the asset that you will want to supply as collateral. * Input the amount that you would like to deposit using manual input, max, or the slider. * Check the APY, Gas Fee, and Health Factor, then click on confirm to supply ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXex3bPmxQ-kHxJKZ5IUXxLL50dAUG0xDAtgd7bTHT1eB7Xl_LSGYn3gTAW7TA5P8xxyvN-6pLvE7f3ecVko-SdLimU_VYrjN2Mr1RqboMchVIj8S4ByNuNhmpvLndYCLWh7w_XPTA%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=c0cd2f31&sv=2) Once the transaction is confirmed, your supply is successfully registered and you will begin to earn interest. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#how-to-calculate-my-earnings) How to Calculate My Earnings? ------------------------------------------------------------------------------------------------------------------------------------------------------ Liquidity Providers receive continuous earnings that evolve with market conditions based on: * The interest rate payment on loans - Suppliers share the interests paid by borrowers corresponding to the average borrow rate times the utilization rate. The higher the utilization of a reserve grows, the higher the yield for suppliers will be. Check out [Lending & Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) to see the borrow interest rate model in action. Each asset has its own market of supply and demand with its own APY (Annual Percentage Yield) which evolves with time. We suggest you check the average annual rate over the past 30 days to evaluate the rate evolution. Besides, more historical data can be found on the overview of each asset reserve in the home section of the app. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#is-there-a-minimum-or-maximum-amount-to-supply) Is there a minimum or maximum amount to supply? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ You can supply any amount you want, there is no minimum or maximum limit. However, it's important to take into account that for small deposits, it is possible that the transaction cost of the process is higher than the expected earnings. It is recommended that you consider this when depositing smaller amounts. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#how-do-i-withdraw) How do I withdraw? -------------------------------------------------------------------------------------------------------------------------------- To withdraw, click on the “Withdraw” button in “Your Supplies” for the asset you wish to withdraw. Select the amount to withdraw and submit the transaction. Be careful, withdrawals may reduce your health factor and increase the risk of liquidation. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdZUsdTJNICGhFbNbipGIyn2YmpAO4yBPnW-jtEHpLWQdS6mTnTND3oisdSMzWzAhTUGpRAuVZoutd0EET86bbuXB-bPWoTXTbxfLlrAoTRK91m21PHM9pZN9VHugKAB2P19PBqYg%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=94a7a8&sv=2) #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#undefined) ​ [PreviousGet Tokens on SUI](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/get-tokens-on-sui) [NextBorrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing) Last updated 9 months ago * [Connect Wallet](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#connect-wallet) * [Deposit/Supply](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#deposit-supply) * [How to Calculate My Earnings?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#how-to-calculate-my-earnings) * [Is there a minimum or maximum amount to supply?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#is-there-a-minimum-or-maximum-amount-to-supply) * [How do I withdraw?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn#how-do-i-withdraw) --- # Liquidations | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#introduction) Introduction ------------------------------------------------------------------------------------------------------------------ Liquidation is the process that occurs when a borrower's health factor goes below 1 due to their collateral value not properly covering their loan/debt position. This might happen when the collateral decreases in value or the borrowed debt increases in value against each other. In a liquidation, **up to 35%**(depending on the token) of a borrower's debt is repaid and that value plus liquidation fee is taken from the collateral available, so after a liquidation that amount liquidated from your debt is repaid. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#what-is-the-health-factor) What is the health factor? --------------------------------------------------------------------------------------------------------------------------------------------- The health factor is the numeric representation of the safety of your deposited assets against the borrowed assets and their underlying value. The higher the value is, the safer the state of your funds is against a liquidation scenario. A Health Factor below 1 suggests that the collateral will enter liquidation phase. The health factor depends on the **liquidation threshold** of collateral against the value of borrowed funds. You can find all of the collateral parameters in the [Lending & Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) section. If you would like to know more technical details about the health factor calculation, please read more details [here](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) . We highly recommend to understand these parameters before conduct any borrow/lending activity. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FpObYl4YMlZGvEIDRHu42%252Fimage.png%3Falt%3Dmedia%26token%3D6b0f12ef-1a4c-4a24-b026-392ce2ee57db&width=768&dpr=4&quality=100&sign=be9109a1&sv=2) Risk Parameters Safeguard Solvency For each wallet, these risks parameters enable the calculation of the health factor: Hf\=∑Supplyi in USD × Liquidation ThresholdiTotal Borrows in USDH\_f = \\frac{ \\sum{Supply\_i \\: in \\: USD \\: \\times \\: Liquidation \\: Threshold\_i}}{Total \\: Borrows \\: in \\: USD}Hf​\=TotalBorrowsinUSD∑Supplyi​inUSD×LiquidationThresholdi​​ ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#undefined) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#liquidation-threshold) \* Liquidation Threshold The liquidation threshold is the percentage at which a position is defined as undercollateralized. For example, a Liquidation threshold of 80% means that if the value rises above 80% of the collateral, the position is undercollateralized and could be liquidated. The delta between the **LTV** and the **Liquidation Thresh**old is a safety mechanism in place for borrowers. For each wallet, the Liquidation Threshold is calculated as the weighted average of the Liquidation Thresholds of the collateral assets and their value: Liquidation Threshold\=∑Supplyi in USD × Liquidation ThresholdiTotal Supply in USD Liquidation \\: Threshold= \\frac{ \\sum{Supply\_i \\: in \\: USD \\: \\times \\: Liquidation \\: Threshold\_i}}{Total \\: Supply \\: in \\: USD \\:}LiquidationThreshold\=TotalSupplyinUSD∑Supplyi​inUSD×LiquidationThresholdi​​ ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#undefined-1) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#loan-to-value) \* Loan to Value **The Loan to Value (”LTV”) ratio** defines the maximum amount of assets that can be borrowed with specific collateral. It is expressed as a percentage (e.g., at LTV=75%, for every 1 Sui worth of collateral, borrowers will be able to borrow 0.75 Sui worth of the corresponding currency). Once a borrowing occurs, the LTV evolves with market conditions. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#how-much-is-the-liquidation-penalty) \* How much is the liquidation penalty? The liquidation penalty (or bonus for liquidators) depends on the asset used as collateral. Once the user is liquidated, he will pay a penalty in proportion as a reward to the liquidator. You can find out the parameters for each assets in [Lending & Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#liquidation-factor) \* Liquidation Factor The liquidation factor directs a share of the liquidation penalty to a collector contract from the ecosystem treasury. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#what-happens-when-my-health-factor-is-reduced) What happens when my health factor is reduced? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Depending on the value fluctuation of your supplies, the health factor will increase or decrease. If the health factor increases, it will improve the borrow position by making the liquidation threshold more unlikely to be reached. In the case that the value of collateralized assets against the borrowed assets decreases instead, the health factor is also reduced, causing the risk of liquidation to increase. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#how-do-i-avoid-liquidation) How do I avoid liquidation? ----------------------------------------------------------------------------------------------------------------------------------------------- In order to avoid the reduction of your health factor leading to liquidation, you can repay the loan or deposit more assets in order to increase your health factor. Out of these two available options, repaying the loan would increase your health factor more. [PreviousBorrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing) [NextFlash Loan](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan) Last updated 1 year ago * [Introduction](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#introduction) * [What is the health factor?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#what-is-the-health-factor) * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#undefined) * [\* Liquidation Threshold](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#liquidation-threshold) * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#undefined-1) * [\* Loan to Value](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#loan-to-value) * [\* How much is the liquidation penalty?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#how-much-is-the-liquidation-penalty) * [\* Liquidation Factor](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#liquidation-factor) * [What happens when my health factor is reduced?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#what-happens-when-my-health-factor-is-reduced) * [How do I avoid liquidation?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations#how-do-i-avoid-liquidation) --- # NAVI Pro | Navi Protocol - docs ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro#user-leveling-system) **User Leveling System** NAVI Pro introduces a unique user-leveling system. Put simply, levels are proportional to users' positions in NAVI Protocol and their general participation in the ecosystem. Each level will grant access to different extensions and advanced features within NAVI Pro. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252F0zI3dNsHGfkCsC5SfbsO%252Fpremium%2520access.png%3Falt%3Dmedia%26token%3D2cd3196d-3113-45e0-b5e9-e94578531e11&width=768&dpr=4&quality=100&sign=cf39800b&sv=2) **Users of different levels will have different extended functions.The following is an introduction from low to high level** #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro#liquidation-forecast-v1-member) Liquidation forecast ( V1 Member) Visually display the liquidation value of the user's current positions, the distance from the current amount to liquidation, and the allowable range of total token value fluctuations. Additionally, calculate when the tokens in the user's account will be liquidated if their value rises (or falls) to the threshold based on the current Supply/Borrow data. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FMwkQHZ2AJS7OiufOhAKK%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252015.30.35%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3D62457e93-a4de-4a6d-8836-e80e4434733b&width=768&dpr=4&quality=100&sign=5c3e0aaa&sv=2) #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro#reward-auto-compound-v2-member) Reward Auto compound ( V2 Member) Users can directly stake the rewards they receive into the corresponding token pool. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252F2l35KMAmRXAGS9k7i7m9%252Freward%2520autocompound.png%3Falt%3Dmedia%26token%3De95f4074-777a-4fe3-9411-9bac2ff39ab5&width=768&dpr=4&quality=100&sign=2e79e59c&sv=2) #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro#strategies-v3-4-member) Strategies ( V3/4 Member) By interacting across different protocols to achieve asset recycling and maximize returns, Strategy will help users achieve high yields with one-click interactions, eliminating the need to switch between multiple platforms. Three types of strategies will be launched in the first phase： Advanced LST Strategy、Liquidity pool Strategy、Collaboration Strategy Advanced LST Strategy： Maximize returns by staking Sui tokens and re-supplying liquid staking Sui through a looping strategy Liquidity pool Strategy： Earn extra yields by borrowing and providing liquidity to DEXes. Collaboration Strategy： Earn extra yields by borrowing from NAVI and participating in partner protocols. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FXnspWuCuEq0v99L7MmVn%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252017.03.43%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3Dfbb96868-5bbc-4e2d-b2c0-faa72f8c3511&width=768&dpr=4&quality=100&sign=bcfa7371&sv=2) #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro#additional-features) Additional Features In the portfolio dashboard, we no longer need to switch and stake token pools one by one. Now we support one-click staking. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252Fv5bRJSikAuGKhGP5WU5k%252Fone%2520click%2520Supply.png%3Falt%3Dmedia%26token%3D8e766921-a104-4284-94ea-737b7c4490bf&width=768&dpr=4&quality=100&sign=62352f64&sv=2) NAVI PRO's new features will continue to be updated, so stay tuned. [PreviousNotifications](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/notifications) [NextAstros DEX Aggregator](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/astros-dex-aggregator) Last updated 9 months ago --- # Notifications | Navi Protocol - docs We are cooperate with [Notifi](https://notifi.network/) to help users better detect changes in their health factors. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FX0KpN6AafnjnLTcnTxUl%252FWechatIMG686.jpg%3Falt%3Dmedia%26token%3Dd6c97b84-9941-47bb-97c4-a167b83655cd&width=768&dpr=4&quality=100&sign=dd55b0f3&sv=2) The user clicks the "NOTIFI" button to set up notifications. Supports notifications through three channels: Email, Telegram, and Discord. After filling in the email address and telegram username, open the discord connection button and click “Next”, at this time, the wallet will pop up a signature request. Please click "Sign". ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FT0kwQtP8EI5Rscw7pSC7%252Fimage.jpeg%3Falt%3Dmedia%26token%3Dd62bbd20-4860-4d2c-b327-4cc023e91ff4&width=768&dpr=4&quality=100&sign=faa4abfc&sv=2) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FlRiZ2Z913TxEpVMgzq8S%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252015.49.44%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3D53380b00-c587-458d-9131-dc3d186edce0&width=768&dpr=4&quality=100&sign=2fd69081&sv=2) Now you can enter the main interface of notifications ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FV9H7xz49QxZme0rzqqJN%252F2.png%3Falt%3Dmedia%26token%3D23c37910-1abd-4fb3-906b-ae2ebc109fe2&width=768&dpr=4&quality=100&sign=28994e61&sv=2) Click the settings button in the upper left corner to enter the settings interface. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FX6BkZZyeCbleVHj51yGr%252F6.png%3Falt%3Dmedia%26token%3D377e6e74-1df3-4661-944f-07ff7e3b2c2c&width=768&dpr=4&quality=100&sign=7928a2d3&sv=2) When setting up notification channels for the first time, you need to verify or bind them one by one. 1. Email ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FbaGfWJn3y64KIuw8eBi7%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252017.24.05%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3D40baa2ca-9740-4979-ae36-4ed57f26052e&width=768&dpr=4&quality=100&sign=72a0bb56&sv=2) Verification Email 1. Telegram ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252F82xJIoKaeTVt6G0mplfp%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252017.25.04%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3Dcdd5cd67-ff87-4d39-92ca-a29ae08bff30&width=768&dpr=4&quality=100&sign=1916a0fb&sv=2) Navi Protocol Bot 1. Discord ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FqRKPy8EMqSH4bYgY2nQ0%252F10.png%3Falt%3Dmedia%26token%3Dadd52231-9067-43de-a453-3fe8092bc290&width=768&dpr=4&quality=100&sign=22130d7c&sv=2) Discord After successful verification or binding, you will be reminded of the current health factor dynamics according to the reminder parameters you set (if you do not take any action, we will send you a reminder message every 7 hours) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252Fxj40HcW6jDc4h2ST2eLo%252F11.png%3Falt%3Dmedia%26token%3D86a59ffb-18e5-4f9c-81bf-4d4e0f1595b3&width=768&dpr=4&quality=100&sign=3c9a65b7&sv=2) [PreviousFlash Loan](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan) [NextNAVI Pro](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro) Last updated 9 months ago --- # Borrowing | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#what-is-borrow) ​What is Borrow? --------------------------------------------------------------------------------------------------------------------- One of NAVI’s key features is to allow users to collateralize capital and borrow assets so that they can utilize them in the broad Sui DeFi ecosystem. This means you can supply an asset as collateral and borrow out another type of asset (check out the [Supply & Earn](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn) section for more info). Please see the below steps for the details: [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#borrowing) Borrowing --------------------------------------------------------------------------------------------------------- Before borrowing, you need to make sure you have deposited assets as collateral. The maximum amount that users are eligible to borrow depends on the value of deposits, asset type, and the assets' available liquidity. * Once you have deposited assets as collateral, click on “Borrow” in the right panel to access the borrowing interface. * Scroll down to the asset you wish to borrow and select the amount * Confirm your transaction in your wallet and finalize the borrow procedure. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcad7CKryYmTUXIfLh4ECpugz2wfguJ7xFbF7DvwPX9G6rKuR-VwJtl9Juf-R4mx94fZ7seTBufH4Efg2KMwdi_FlRYjuS6uN3bejn3EHeRnQewetJvepqN2fFabRqqIzUtmJmmbA%3Fkey%3D33GO0JS-NU-2-0txD4NVe7Fn&width=768&dpr=4&quality=100&sign=3c0cab7e&sv=2) [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#max-borrow) Max Borrow ----------------------------------------------------------------------------------------------------------- The assets supplied by the user will affect the maximum loan value. The loan amount is limited based on the health factor. When the max button is clicked, the minimum health factor that the user can achieve will be calculated, formula is: Hf\=∑Supplyi in USD × LiquidationThresholdi∑Supplyi in USD ×  MAXLTViH\_f = \\frac{ \\sum Supply\_i \\: in \\: USD \\: \\times \\: Liquidation Threshold\_i}{\\sum Supply\_i \\: in \\: USD \\: \\times \\: \\: MAX LTV\_i}Hf​\=∑Supplyi​inUSD×MAXLTVi​∑Supplyi​inUSD×LiquidationThresholdi​​ [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#how-do-i-repay-my-loan) How do I repay my loan? ------------------------------------------------------------------------------------------------------------------------------------ You repay the loan in the original format of the asset one borrowed. For example, if you borrow 1 Sui initially, you need to pay back 1 Sui + interest accrued(in Sui). You can only repay with your wallet balance, not collateral. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FqykMA4Q2AGyceOX5boFw%252F%25E5%25B1%258F%25E5%25B9%2595%25E5%25BF%25AB%25E7%2585%25A7%25202025-03-31%2520%25E7%259A%2584%252015.03.23%2520%25E4%25B8%258B%25E5%258D%2588.png%3Falt%3Dmedia%26token%3Deb92410a-ce31-4fd8-bb59-7697f6264a7f&width=768&dpr=4&quality=100&sign=8b95b386&sv=2) * If you have debts, the debt amount and "**Repay**" button will appear at the top of the operation area. Click the **Repay** button to the next step. * Enter the amount to repay, the tokens will be deducted from your wallet balance. * Click on the “**Confirm**” button and approve the transaction in Sui compatible wallet * Once the transaction succeeded, the loan is repaid at the input amount. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#reward-limit-in-borrow) Reward Limit in Borrow ----------------------------------------------------------------------------------------------------------------------------------- If you borrow the same token as you supplied, this will significantly reduce the rewards you can receive. EffectiveAmount\=SupplyAmount−BorrowAmountEffective Amount = Supply Amount - Borrow AmountEffectiveAmount\=SupplyAmount−BorrowAmount In case the user has practiced borrow nesting to extremes, the effective amount will reduce to 0. Effective Amount: the effective liquidity counting towards users’ rewards. [PreviousSupply & Earn](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/supply-and-earn) [NextLiquidations](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations) Last updated 6 months ago * [​What is Borrow?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#what-is-borrow) * [Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#borrowing) * [Max Borrow](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#max-borrow) * [How do I repay my loan?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#how-do-i-repay-my-loan) * [Reward Limit in Borrow](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/borrowing#reward-limit-in-borrow) --- # Flash Loan | Navi Protocol - docs NAVI Flash Loans are an innovative financial tool exclusive to the blockchain domain, enabling users to borrow assets without providing upfront collateral. These loans, also known as **One-Block Borrows**, must be initiated and fully settled within the same blockchain block. Their success relies on the execution of predefined conditions within this strict timeframe. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#overview) Overview -------------------------------------------------------------------------------------------------------- With a flash loan, users can access the pool's liquidity for a single transaction—but only for reserves for which borrowing is permitted—as long as the money borrowed plus the associated fee is returned or, if permitted, a debt position is opened by the end of the transaction. NAVI Protocol offers two options for flash loans: * `flashloan`: This type of flash loan allows users to borrow liquidity from pools above, both the money borrowed and debt receipt will be sent to the address who start the transaction. * `flashloan_with_AccountCap`: This type of flash loan allows users to borrow liquidity from pools above, but the money borrowed will be sent to the account cap address and debt receipt will be sent to the address who start the transaction. Transaction initializer must destroy the receipt at end of the block to make this transaction happen. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#flash-loan-config) Flash Loan Config Pool Fee to LP Fee to Treasury Max Borrow Min Borrow Sui 0% ~0.2%~ 0.06% 3,000,000 0 vSUI 0% ~0.2%~ 0.06% 3,000,000 0 haSui 0% ~0.2%~ 0.06% 2,000,000 0 wUSDC 0% ~0.2%~ 0.06% 5,000,000 0 nUSDC 0% ~0.2%~ 0% 10,000,000 0 USDT 0% ~0.2%~ 0.06% 5,000,000 0 USDY 0% ~0.2%~ 0.06% 1,000,000 0 AUSD 0% ~0.2%~ 0.06% 1,000,000 0 suiETH 0% ~0.2%~ 0.06% 1,000 0 wETH 0% ~0.2%~ 0.06% 500 0 NAVX 0% ~0.2%~ 0.06% 5,000,000 0 CETUS 0% ~0.2%~ 0.06% 5,000,000 0 FDUSD 0% ~0.2%~ 0.06% 2,000,000 0 wBTC 0% ~0.2%~ 0.06% 10 0 NS 0% ~0.2%~ 0.06% 5,000,000 0 DEEP 0% ~0.2%~ 0.06% 5,000,000 0 BUCK 0% ~0.2%~ 0.06% 5,000,000 0 suiUSDT 0% ~0.2%~ 0.06% 5,000,000 0 BLUE 0% ~0.2%~ 0.06% 2,000,000 0 ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#key-details) Key Details Flash loans are currently enabled for **all** pools, with an initial borrowing cap for each pool. The borrowing fee is distributed between Liquidity Providers (LPs) and the protocol's treasury: LP Fee: **0%** Treasury Fee: Initially set at 0.2%, temporarily reduced to 0.06% to attract more developers. Refer to the AssetConfig for current fees. The NAVI Protocol Team regularly assesses risk factors and may adjust maximum borrow limits in the future. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#execution-flow) Execution Flow For SUI developers, a helpful model to consider when developing your solution: 1. Initialize all the parameters required in a [PTB (Programmable Transaction Block)](https://docs.sui.io/guides/developer/sui-101/building-ptb) 2. Your contract calls the `pool::lending::flash_loan_with_ctx` contract, requesting a Flash Loan of a certain `amount(s)` of `pool(s)` 3. After some sanity checks, the `Lending Contract` transfers the requested `amounts` of the `coins` to your contract, then issue receipt to `receiver` address. 4. Your contract, now holding the flash loaned `amount(s)`, executes any arbitrary operation in the ptb. 5. Call `pool::lending::flash_repay_with_ctx` and send the borrowed money plus fee as an object to the contract. 6. All of the above happens in 1 ptb transaction (hence in a single sui block). ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#getting-started) Getting Started You may refer [NAVI-Developer Doc](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/) or [navi-sdk](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/how-to-interact-with-the-contract/navi-sdk) for efficient development [PreviousLiquidations](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/liquidations) [NextNotifications](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/notifications) Last updated 1 year ago * [Overview](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#overview) * [Flash Loan Config](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#flash-loan-config) * [Key Details](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#key-details) * [Execution Flow](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#execution-flow) * [Getting Started](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan#getting-started) --- # NAVI AI Trading Bot | Navi Protocol - docs **Welcome to the NAVI AI Trading Bot! 🚀** Your ultimate solution for seamless and efficient DeFi trading. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#why-choose-navi) ✨ Why Choose NAVI? ---------------------------------------------------------------------------------------------------------------------------------- * **Buy & Sell**: Trade your favorite tokens effortlessly and securely. * **Referral Rewards**: Invite your friends and earn exciting bonuses. * **User-Friendly**: Enjoy simple commands, fast execution, and real-time updates. [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#ready-to-begin) 🔰 Ready to Begin? --------------------------------------------------------------------------------------------------------------------------------- Type **/start** to explore all commands and features. 🎉 Let the trading adventure begin! * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#useful-links) 🔗 **Useful Links** -------------------------------------------------------------------------------------------------------------------------------- * **🎯 Trading Bot**: [https://t.me/NAVITradingBot](https://t.me/NAVITradingBot) * **🔔 Hot Trends Channel**: [https://t.me/Navi\_SniperBot](https://t.me/Navi_SniperBot) * **💬 Telegram Community**: [https://t.me/navi\_protocol](https://t.me/navi_protocol) * **🐦 NAVI Aggregator**: [https://www.navi.ag/](https://www.navi.ag/) ⚠️ **Important Notice**: Be cautious of scams on Telegram. Always use official links to keep your assets secure. * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-start-guide) ✈️ **Quick Start Guide** ------------------------------------------------------------------------------------------------------------------------------------------ If this is your first time using the NAVI AI Trading Bot, we recommend reading this guide to get started quickly: 1. Click the [Telegram link](https://t.me/NAVITradingBot) to access the bot. 2. Hit the **START** button to begin your journey. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F757519164-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FYTRq6w3DGapKHxfqaA3Z%252Fuploads%252FaqAvvTcyeSsm209qSIOU%252Fimage.png%3Falt%3Dmedia%26token%3D477165b7-3bce-4f09-9bff-532e1ecad00f&width=768&dpr=4&quality=100&sign=86dcb71d&sv=2) When using it for the first time, you need to create one wallet to support subsequent operations. When you press start, the system will automatically create a wallet for you and host it in the bot background, and prompt the following message. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXeoPETuo2sNJpUbU-w09FjxwW-4Cd0bmK6kAjG4EIp83R11bFQWyC5ujSAZChzPQazK4ogJGDthBEVzysbiwK0EPjVods4SLgzumPUwX4NuFF72gDA8jGM_tUksiVxSCPwuGpQkKA%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=49e71e13&sv=2) As shown below: After finding the wallet in the settings and pressing it, you can create a new wallet here, or import your mnemonic wallet. Of course, you can also export your mnemonic here. You can send **/start** at any time or click the function button provided by the bot to use it. Of course, remember to recharge gas and your funds before trading. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdYIzoxolWzzfstiKY6LZANNgAGN8XFPiBUaHYuVvwRgFe6Viet9WbFHOuOngJuYnK8dY4GjTQ-DDuP-rcY16H-1g9mxJyRWs7OJTRW3WVCC7wRd4QWjDer5fQ7d6orl7USWm-JxQ%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=eeb20d5a&sv=2) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXfpoJ_KiBg3rrh6tArKenQpzlJUhKrR2uQAQRZgPUHNKHD2XmHriRcUCIzDTx1uaZ7zeGC9attTLXQ5pEsm4lAXKlT5nkprAlXoj7BOCD2xsg5V95_gXnElMMGcc0TzciJin-O2uw%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=69a20dfa&sv=2) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdVrdOkNi4YjCZvSAHtCvKCLyKRXCk3qXDBcy93eLUM-qVRfPuRPBT8WrhmZY58unoSGcLJ1SycjYZVhBF3iqyx31PnOON1LOIDaaDGb8337bcTwSTwB_LFjtjLDlKQxOUEaANt%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=7679ee61&sv=2) [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#please-pay-attention-to-protecting-your-mnemonic-phrase-and-your-assets) !!! Please pay attention to protecting your mnemonic phrase and your assets. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#sui-trading) **Sui Trading** --------------------------------------------------------------------------------------------------------------------------- 1.Enter the open token address on any page, and the bot will automatically identify the contract and jump to the buying and selling panel. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdEAGxexerQ5QFv1eKQCxqcXnJAuyPlJ_oH0vnHAT4HDIvCUIt_pA1EIpTzJ6lanJrhXtt7nZIhjh76CPa-nLpOmEj5z3UAqkIhFmD6iUk4_aMC3SJorrCKWhqKURCGbRku2usEqQ%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=dec755d3&sv=2) 2.You can also enter / start ,then press the buy/sell button that appears on the bot to trade ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXfCz4vSJ5qAyDuOySuZRUsvp7pO4f2wfwYV7tjUrCals4WWPWYxcZOT4hIOpBockJp7N922j30UxFsIYilJDDMjtm4R5WHyfIKXM5mMCfrbqKcCcOguT7xSAgdOCYEhqyTh2O6Diw%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=916268af&sv=2) 3.You can also press "Menu" at the bottom and select Buy/Sell ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcy1LrtZiSYAuVgjfbSzLAMFL-SbL7st3YTul4dTuVp0JgQDTDa9_RlAAIH_eY6JPRYhE1cK9JeHX49NcysZK-KJzSlWODSpX1vmAKpwPzOZbHMGrHNzbnI4D3u2rjHhcMdPzFJ%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=e23d7a58&sv=2) * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-buy) Quick Buy ------------------------------------------------------------------------------------------------------------------- Click the system-preset amount, or click the "**Buy X SUI**" button to customize the purchase amount to execute the purchase. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXeBvjhwHhKX_MRslRZvdXwhpVLtK7gzHhyw5rYdfnaLF-Dx580effET22aWAGaeaGmTcVEQvHBPp9frHhIfniC7tdHK5pQbhDpjxNqmPBbcPQiBx8WeXall349m8plgrT4Dc1c9YQ%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=c7bc33e7&sv=2) You can also change the slippage at the marked point below ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdLLKbW9dgTtpTK8XKpaCbMtOt2RJ-2Id1xE3AUI6egK0NGZtC1c4dV140sSJuItIklQPdsc33wtblTbMka_NYeAMbdsL-XnVfo2D-l6szvOXIlB3Uimc1io0bIV7gg2ZfR1jl6yw%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=569fb0f4&sv=2) Once your purchase is successful, the system will automatically display the **selling panel** and pre-select the wallet holding the purchased token. You can click the **Refresh** button to update the latest token value and decide whether to proceed with a sale. * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-sell) **Quick Sell** ------------------------------------------------------------------------------------------------------------------------- In the token selling panel, you can: 1. Select the system’s **preset ratios**, or 2. Use the **"Sell X%"** or **"Sell X"** buttons to customize the quantity or ratio of tokens to sell. The sale will be executed immediately upon confirmation. After the transaction is successful, the system will generate an automatic **PnL (Profit and Loss) report**, providing a clear overview of your token income. * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#trading-fees-and-referral-rewards) **Trading Fees & Referral Rewards** --------------------------------------------------------------------------------------------------------------------------------------------------------------------- **Trading Fee** * A **1% transaction fee** applies to all trades. * Invited users can enjoy a **10% discount** on fees. **Referral Rewards** 1️⃣ **Earn 35% cashback**: Rewards are claimable once they reach **0.0005 SUI**—no delays! 2️⃣ **Inviter Discounts**: New users who sign up through your invitation link receive a **10% discount** on service fees. * * * [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#how-to-share-your-referral-link) **How to Share Your Referral Link?** -------------------------------------------------------------------------------------------------------------------------------------------------------------------- You can easily share your referral link by copying it from the **Home Panel** or the **Referral Rewards Page**, and sending it to your friends. ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXfjHc4a7RJ2W20O-KrkRSuTzExlNU_8JZN0orYDj8eREmuWV6as9t5FsKXSr-zL-UvhtndmjCYs9MzW2e-itbgkfp1JIW4ef2WWKqA6WSh0ntGpptn65-58u_PWuERPuebFcYgnPw%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=f59996a6&sv=2) ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXeGeQoz_LpLi3HoNpMfr59NWM5h-dha9xuQCkCmWK_M-IlwyD8u7KKEa4d5irjHQY74VTxM0rJsn80MqE8_O3yPt5npIWiky5-tsb5wb00HVAq764PF3_C0glQeXB1k6Fi31F86-g%3Fkey%3DijOb0QaZe7nHka4c_PpP80sn&width=768&dpr=4&quality=100&sign=55e53685&sv=2) * * * [PreviousAstros DEX Aggregator](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/astros-dex-aggregator) [Next$xBTC Campaign FAQ](https://naviprotocol.gitbook.io/navi-protocol-docs/campaign-detail/usdxbtc-campaign-faq) Last updated 11 months ago * [✨ Why Choose NAVI?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#why-choose-navi) * [🔰 Ready to Begin?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#ready-to-begin) * [🔗 Useful Links](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#useful-links) * [✈️ Quick Start Guide](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-start-guide) * [!!! Please pay attention to protecting your mnemonic phrase and your assets.](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#please-pay-attention-to-protecting-your-mnemonic-phrase-and-your-assets) * [Sui Trading](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#sui-trading) * [Quick Buy](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-buy) * [Quick Sell](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#quick-sell) * [Trading Fees & Referral Rewards](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#trading-fees-and-referral-rewards) * [How to Share Your Referral Link?](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot#how-to-share-your-referral-link) --- # Astros DEX Aggregator | Navi Protocol - docs The [Astros](https://naviprotocol.gitbook.io/astros/) DEX Aggregator is a core part of the NAVI Ecosystem, providing seamless integration for high-performance decentralized trading with optimized execution, security, and a smooth user experie #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/astros-dex-aggregator#key-features) Key Features 1. **High-Performance Trading**: The NAVI DEX Aggregator offers fast and low-latency trading through optimized smart contracts and algorithms, ensuring stable and efficient transactions even during peak trading periods. 2. **Order Splitting**: For large trades, the NAVI DEX Aggregator automatically splits orders across multiple liquidity pools, helping users achieve the best prices for their transactions. 3. **Multi-Hop Trading**: To further optimize trading costs and liquidity, the aggregator supports multi-hop trades, finding the best transaction paths across multiple routes to maximize value for users. 4. **Security and Reliability**: Security is NAVI's top priority. The DEX Aggregator employs multi-layered security protocols to ensure user funds are safe and trades execute smoothly. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/astros-dex-aggregator#supported-exchanges) Supported Exchanges Currently, NAVI DEX Aggregator supports multiple DEXs, including Cetus, Turbos, Bluefin, Aftermath and more. We are actively expanding integrations with more exchanges and working toward future integration with NAVI Protocol, aiming to provide users with an unmatched trading experience. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/astros-dex-aggregator#sdk-for-developers) SDK for Developers For developers looking to integrate NAVI DEX Aggregator functionality into their applications, we offer an SDK: [NAVI Aggregator SDK](https://sdk.naviprotocol.io/swap) . This SDK provides easy-to-use tools and resources to enable seamless access to NAVI's aggregation features. [PreviousNAVI Pro](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-pro) [NextNAVI AI Trading Bot](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot) Last updated 4 months ago --- # 💰 Integrating Fees | Astros ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#astros-aggregator-fee-sharing-scheme) **Astros Aggregator Fee Sharing Scheme** Astros does not charge users any trading fees. Instead, we share revenue collected by integrators to promote ecosystem growth and improve trading efficiency. Below is our standard fee-sharing structure: * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#id-1.-revenue-share-structure) **1\. Revenue Share Structure** * **Major Tokens** (e.g., SUI, USDC, USDT) Astros takes **30%** of the integrator's applied fee. * **Minor Tokens** (e.g., meme tokens, low-liquidity assets) Astros takes **50%** of the integrator's applied fee. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#id-2.-tiered-rebate-scheme) **2\. Tiered Rebate Scheme** Astros' share can be reduced based on monthly trading volume to encourage scaling: Weekly Volume Major Token Share Minor Token Share <$1M 30% 50% ≥$1M 25% 40% ≥$5M 20% 30% * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#id-3.-whitelisted-partner-policy) **3\. Whitelisted Partner Policy** Custom benefits for long-term partners: * **Negotiable Fee Share**: Initial rates can be customized based on project size and contribution potential. * **Reverse Incentives**: Eligible partners may receive additional rewards or ecosystem support (e.g., marketing, tech integration) based on trading volume. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#id-4.-settlement-and-transparency) **4\. Settlement & Transparency** * **Settlement Cycle**: Monthly. Trading source must be trackable via API Key or referral tag. * **Settlement Tokens**: Default in vSUI or USDC (negotiable). * **Transparent Reporting**: Astros provides trading volume and fee share reports for partner verification. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees#id-5.-anti-cheating-and-compliance) **5\. Anti-Cheating & Compliance** * **Wash trading is strictly prohibited**—violators will forfeit all fee shares. * **Partners must implement safeguards**, including minimum trade amounts and abuse prevention logic. * Astros reserves the right to interpret and arbitrate abnormal activity. [PreviousAggregator API](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/aggregator-api) [NextSlippage](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage) Last updated 5 months ago --- # Getting Started | Astros For developers looking to integrate Astros DEX Aggregator functionality into their applications, we offer an SDK available on GitHub: [Aggregator SDK](https://github.com/naviprotocol/navi-sdk) . This SDK provides easy-to-use tools and resources to enable seamless access to Astros‘s aggregation features. ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#installation) Installation Start an easy integration of react project with [Astros UI SDK](https://github.com/naviprotocol/navi-web-component) . Install it via npm: Copy npm i navi-web-component [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#usage) Usage ------------------------------------------------------------------------------------------------------------------ Import the `SwapPanelClient`, a client-side interface for managing the `SwapPanel` web component, designed for token swap functionality in browser environments: Copy import { SwapPanelClient } from 'navi-web-component' [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#demo) Demo ---------------------------------------------------------------------------------------------------------------- This demo leverages **Next.js**, a modern framework for building fast, scalable web applications. Whether you're a developer looking to explore Astros's features or integrate them into your app, this is the perfect starting point. [![Logo](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Fgithub.com%2Ffluidicon.png&width=20&dpr=4&quality=100&sign=ccc5b74a&sv=2)GitHub - naviprotocol/web-component-demoGitHub](https://github.com/naviprotocol/web-component-demo) Demo for UI SD ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#features) 🌟 Features **Seamless Setup**: Get started with minimal configuration. **Live Preview**: Auto-updating UI for instant feedback during development. **Customizable Components**: Integrate the Astros UI SDK and tailor it to match your app's branding. **API Exploration**: Experiment with pre-configured API routes for dynamic interactions ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#showcase-link) 🛠 Showcase Link [https://web-component-demo.vercel.app/](https://web-component-demo.vercel.app/) ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#get-started-today) 🚀 Get Started Today! Ready to dive in? Clone the repo, start the dev server, and bring the power of **Astros UI SDK** into your project in minutes. Happy coding! 💻✨ [PreviousAstros UI SDK](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media) [NextAggregator Components](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components) Last updated 9 months ago * [Installation](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#installation) * [Usage](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#usage) * [Demo](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#demo) * [🌟 Features](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#features) * [🛠 Showcase Link](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#showcase-link) * [🚀 Get Started Today!](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started#get-started-today) --- # Astros UI SDK | Astros #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#rapid-integration) 🚀 Rapid Integration Streamline your development process with: * **Pre-built components** for wallet management and swap functionality. * **Comprehensive documentation** to help you get started in no time. Focus on your app's unique features while we take care of the heavy lifting. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#trusted-by-decentralized-projects) 🛡️ Trusted by Decentralized Projects The Astros UI SDK is continually expanding its adoption: * Supported by multiple DApps, including: * [**NAVI Lending**](https://app.naviprotocol.io/) * [**Astros Aggregator**](https://www.navi.ag/) * More to be announced * Effortless handling of wallet connections and disconnections. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#support-for-all-sui-mainstream-wallets) 🛠️ Support for All Sui Mainstream Wallets Astros UI SDK fully supports a wide range of wallets to ensure seamless user experiences: * [**Suiet**](https://suiet.app/?ref=blog.sui.io) * [**Sui Wallet**](https://docs.suiwallet.com/?ref=blog.sui.io) * [**OKX Wallet**](https://chromewebstore.google.com/detail/okx-wallet/mcohilncbfahbmgdjkbpemcciiolgcge?pli=1) * [**Ethos Wallet**](https://ethoswallet.xyz/?ref=blog.sui.io) * [**Surf Wallet**](https://surf.tech/?ref=blog.sui.io) * [**Nightly**](https://nightly.app/?ref=blog.sui.io) * and more than 20+ Wallets * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#speed-and-responsiveness) ⚡ Speed and Responsiveness Achieve top-tier performance: * **Lightweight components** ensure fast load times. * **Real-time updates** and near-instant wallet interactions, even during high traffic. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#lazy-loading-for-enhanced-user-experience) 📦 Lazy Loading for Enhanced User Experience Optimize your app's performance: * Minimize initial load times. * Dynamically load assets and modules as users engage with your app. * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media#no-fees-for-all-integrations) 💸 No Fees for All Integrations Integrating with the Astros UI SDK comes at **zero cost**: * Use all features and components without any fees. * Focus your resources entirely on building and scaling your DApp. [PreviousIntroduction](https://naviprotocol.gitbook.io/astros) [NextGetting Started](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started) Last updated 9 months ago --- # Liquidation Mechanics | Navi Protocol - docs Reliable liquidation mechanics are enabled by tight integration with a variety of liquidity partners. We plan on leveraging the centralised liquidity of DeepBook to perform timely liquidations. Liquidators can purchase under-collateralized assets at a discount on the DEX, providing an incentive to maintain the health and stability of the lending pool. Liquidations are permissionless, thus effectively creating a market for discounted collateral. [PreviousGranular Asset Risk Management](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management) [NextAudit Report](https://naviprotocol.gitbook.io/navi-protocol-docs/security/audit-report) Last updated 1 year ago --- # Tutorial | Astros Welcome to Astros Perpetual - Visit [Perp](https://beta.astros.ag/perp) website to experience the trading journey. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2F3166231846-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FEagmjVMVJsuZQ0TvRYt7%252Fuploads%252F1vsKBlYHcSQTMVxhcagj%252FASTROS-Perp-Chart%2520Settings.png%3Falt%3Dmedia%26token%3D95765eda-1bad-48d3-a78d-30194a22c1e9&width=768&dpr=4&quality=100&sign=66e349c1&sv=2) [PreviousIntroduction](https://naviprotocol.gitbook.io/astros/astros-perpetual/editor) [NextDeposits and Withdrawals](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals) Last updated 9 months ago --- # Glossary | Navi Protocol - docs Some terms used throughout the documentation may be unfamiliar to developers. Below we list some common terms that will help with your understanding. Term Description APY Annual Percentage Yield (APY) represents the real rate of return on an investment account over a year, accounting for the effects of compounding interest. Unlike a simple interest rate, which calculates earnings only on the initial principal, APY includes interest earned on both the principal and the accumulated interest from previous periods. Conversely, the Borrow APY is the interest that the Borrower needs to pay. Loan To Value (LTV) The maximum borrowing power of a specific collateral. If a collateral has a Loan to Value of 75%, for every 1 ETH worth of collateral the user will be able to borrow 0.75 ETH worth of principal currency. The Loan To Value is specified per collateral and expressed in percentage points. Liquidation Threshold The threshold of a borrow position that will be considered undercollateralized and subject to liquidation. If a collateral has a liquidation threshold of 80%, it means that the loan will be liquidated when the debt value is worth 80% of the collateral value. The liquidation threshold is specified per collateral and expressed in percentage points. Liquidation Bonus The bonus received by liquidators to incentivise the purchase of specific collateral that has a health factor below 1. The Liquidation Bonus is specified per collateral and expressed in percentage points. Health Factor Represents the ratio between total collateral multiplied by the liquidation threshold, and the borrowed principal. When the Health Factor goes below 1, the loan is undercollateralized and can be liquidated. Also see `execute_liquidation`. Ray Units For internal calculations and to reduce the impact of rounding errors, the protocol uses the concept of Ray Math. A Ray is a unit with 27 decimals of precision. All the rates (liquidity/borrow/utilisation rates) as well as the cumulative indexes and the aTokens exchange rates are expressed in Ray. Please refer to the following [article](https://medium.com/dapphub/introducing-ds-math-an-innovative-safe-math-library-d58bc88313da) for further details about this concept. Market The address of the underlying asset. Lending Pool The smart contract with which users interact to perform funding operations Funding Operations Operations such as `borrow` , `repay`, `withdraw`, `deposit` Liquidity Rate The interest rate currently being earned by the reserve Liquidity Index The Interest cumulated by the reserve during the time interval since the last updated timestamp Automatic Leverage Vaults By borrowing and lending, you are longing or shorting an asset. You can technically use the asset you borrowed to repeat the process a few more times, making it equivalent to a "spot leverage". We apply the same idea to Automatic Leverage Vaults and make this process straightforward for users. [PreviousLending & Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) [NextGranular Asset Risk Management](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management) Last updated 2 months ago --- # Slippage | Astros [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#overview) Overview ------------------------------------------------------------------------------------------------ Slippage is the difference between the expected price of a trade and the actual executed price. Astros Aggregator provides slippage protection and positive slippage benefits to users. ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#slippage-configuration) Slippage Configuration #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#user-settings) User Settings * Configurable: Users can set their preferred slippage tolerance in the frontend * Recommendation: 0.5% - 1% for most trades #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#auto-slippage-setting) Auto Slippage Setting Auto Slippage Setting automatically adjusts slippage tolerance based on individual token characteristics. The system analyzes each token's specific properties such as volatility patterns, liquidity levels, and trading behavior to determine optimal slippage parameters, ensuring efficient transactions without manual configuration. ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#slippage-protection) Slippage Protection #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#negative-slippage-protection) Negative Slippage Protection * Automatic Revert: Transaction fails if slippage exceeds tolerance * No Hidden Fees: Users only pay what they agree to * Real-time Updates: Price updates before execution #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#smart-routing) Smart Routing * Best Prices: Aggregates multiple DEXs for optimal rates * Liquidity Analysis: Routes through pools with sufficient liquidity * MEV Protection: Protects against front-running and sandwich attacks ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#positive-slippage) Positive Slippage When the execution price is better than expected, users receive more tokens than the quoted amount. Astros Aggregator captures a small portion of positive slippage to support platform operations. #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#fee-structure) Fee Structure Trade Size Protocol Fee Description ≤ $1,000 ≤ 0.3% Small trades with minimal impact $1,001 - $10,000 ≤ 0.2% Medium trades with balanced approach $10,001 - $100,000 ≤ 0.15% Large trades with reduced fee rate \> $100,000 ≤ 0.1% Ultra-large trades with maximum protection [Previous💰 Integrating Fees](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees) [NextIntroduction](https://naviprotocol.gitbook.io/astros/astros-perpetual/editor) Last updated 3 months ago * [Overview](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#overview) * [Slippage Configuration](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#slippage-configuration) * [Slippage Protection](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#slippage-protection) * [Positive Slippage](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage#positive-slippage) --- # Supported Assets | Navi Protocol - docs One of the main selling points of our platform is the support for a variety of different assets that many traditional platforms won't support. Here, we outline what kind of assets we plan on allowing users to collateralise. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#blue-chip-assets) Blue Chip Assets The platform supports lending and borrowing of the following assets: 1. USD Coin bridged from Eth mainnet through Wormhole(USDCet) 2. Tether USD bridged through Wormhole from ETH mainnet(USDTeth) 3. Sui Token (SUI) 4. wETH Wrapped Eth 5. Cetus Token 6. voloSUI (LST Token) 7. haSUI (LST Token) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#yield-bearing-tokens) Yield-Bearing Tokens Yield-bearing tokens are tokens that have a value accrual mechanism. Examples of these are Liquid Staked Derivatives (e.g. $mSUI, $stETH, etc.), which accrue in value over time by earning staking fees, or automated Market Maker (AMM) LP Tokens, which accrue in value by capturing trading fees. The main interest in providing yield-bearing assets as collateral is their relative price stability, as well their appreciation mechanics. This enables users to unlock different low-cost, high yield strategies such as hedging, looping, long, short, and more. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#id-1.-lp-tokens) 1\. LP Tokens Automated Market Maker platforms enable users to deposit tokens in liquidity pools, giving back users an LP token. Historically, if a user wanted to provide liquidity to an AMM, the user had no access to the liquidity in the LP token. However, NAVI protocol enable users to borrow against these LP tokens so users can access the liquidity locked in their LP token and come up with a variety of strategies like leveraged yield farming, hedged positions, or delta-neutral. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#id-2.-liquid-staked-derivative-tokens) 2\. Liquid Staked Derivative Tokens The platform will accept Liquid Staked Derivative tokens as collateral for borrowing. These tokens represent staked assets and can be used to obtain loans while still earning staking rewards, further increasing the capital efficiency of the DeFi ecosystem. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#long-tail-and-exotic-asset-support) Long-tail and exotic asset support Traditional money markets such as AAVE and Compound make it hard for long-tail and exotic assets to get listed on the platforms due to extensive liquidity thresholds in order to shield the protocol TVL. However, by introducing innovations such as Isolation Mode and a variety of granular risk management improvements such as Debt Ceilings, Supply Limits and Borrow Limits, these assets can be gradually added to the protocol without having an effect on its solvency risk. This allows exotic and long-tail assets to participate in DeFi lending, which allows users to access the liquidity of these long-tail assets without the need to sell them. [PreviousHackathon - Overflow NAVI Bounty](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty) [NextLending & Borrowing](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) Last updated 1 year ago * [Blue Chip Assets](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#blue-chip-assets) * [Yield-Bearing Tokens](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#yield-bearing-tokens) * [Long-tail and exotic asset support](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets#long-tail-and-exotic-asset-support) --- # Aggregator Components | Astros [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#swap-panel) Swap Panel ---------------------------------------------------------------------------------------------------------------------------------- Provides a complete Swap transaction process, including pair selection, intelligent routing, constructing transactions, submitting transactions, and displaying transaction results. ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#usage) Usage * * * 1 Import the component Copy import { SwapPanelClient } from 'navi-web-component' 2 Instantiating Component Copy const swapPanelClient = SwapPanelClient.getInstance() The component uses the singleton pattern, so multiple calls to getInstance return the same instance. 3 Register the onSignTransaction method for transaction signing. The user executing swap needs the wallet to sign the transaction. the DApp needs to register a callback function to implement the wallet signing logic. Copy swapPanelClient.onSignTransaction = async (txb) => { // run sign transaction logic in your app // after signed, return the signature and bytes const resp = await signTransaction({ transaction: txb, }) return { signature: resp.signature, bytes: resp.bytes, } } 4 Listen connect event If the user uses the Swap component within the DApp without connecting to the wallet, the component displays a button to connect to the wallet. Clicking on the button by the user triggers the connect event, which the DApp needs to listen to and enter the wallet connection flow. Copy swapPanelClient.events.on('clickConnect', () => { // run connect wallet logic in your app // after connected, set user address in swap panel swapPanelClient.setUserAddress('0x1234567890123456789012345678901234567890') }) 5 Sync user address DApp needs to pass the address of the currently connected wallet to the component. Copy // wallet connected swapPanelClient.setUserAddress('0x1234567890123456789012345678901234567890') // wallet disconnected swapPanelClient.setUserAddress('') 6 Calling the methods of instance ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#methods) Methods * * * #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#show) show() Displays the swap panel. Copy swapPanelClient.show() #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#hide) hide() Hides the swap panel. Copy swapPanelClient.hide() #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#settokenfrom-cointype-string-promise-less-than-boolean-greater-than) setTokenFrom(coinType: string): Promise Sets the token to swap from. #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#settokento-cointype-string-promise-less-than-boolean-greater-than) setTokenTo(coinType: string): Promise Sets the token to swap to. #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#settokenfromamount-amount-string-promise-less-than-boolean-greater-than) setTokenFromAmount(amount: string): Promise Sets the amount for the token to swap from. #### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#changetheme-theme-dark-or-light-promise-less-than-boolean-greater-than) changeTheme(theme: 'dark' | 'light'): Promise Sets the UI theme. ### [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#events) Events Use the `events` property to listen for specific swap panel events. * * * Event name Description ready trigger when swap panel is ready clickConnect trigger when connect button is clicked. swapSuccess trigger when swap success show trigger when swap panel show hide trigger when swap panel hide [PreviousGetting Started](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/getting-started) [NextAggregator API](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/aggregator-api) Last updated 9 months ago * [Swap Panel](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#swap-panel) * [Usage](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#usage) * [Methods](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#methods) * [Events](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components#events) Copy swapPanelClient.setTokenFrom('0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX') Copy swapPanelClient.setTokenTo('0x02::sui::SUI') Copy swapPanelClient.setTokenFromAmount('1000') Copy swapPanelClient.changeTheme('dark') swapPanelClient.changeTheme('light') Copy swapPanelClient.events.on(eventName, callback) --- # Aggregator API | Astros [](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/aggregator-api#get-quote) Get Quote -------------------------------------------------------------------------------------------------------- **Base URL:** Copy https://open-aggregator-api.naviprotocol.io `Get` `/find_routes` The `find_routes` API endpoint identifies the optimal routes for swapping one token (`from`) to another (`target`) based on the specified amount and additional parameters. It determines the best swap paths by considering factors such as route depth and the input amount type. **Headers** Name Value Description x-navi-token String (optional) Serves the same function as `apiKey` in sdk, used to authenticate user requests. **Body** Name Type Description from String The token address you are swapping from (e.g., `Sui-0x2::sui::SUI`). target String The token address you want to swap to (e.g., `NAVX-0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX`). amount String The amount of the `fromCoinAddress` token to swap, specified with decimals (e.g., `1000000000`). by\_amount\_in Boolean Specifies whether the provided amount is the input amount for the swap. Please only use `True` depth String The maximum number of hops allowed in the route search, balancing performance and accuracy. Default: `3` dexList Enum List (optional) A comma-separated list of decentralized exchanges (DEXs) to include for routing the swap. If left empty, all available DEXs will be considered. (e.g., `['cetus', 'turbos']`) Supported DEXs: * Cetus * Turbos * Aftermath * Deepbook * Bluefin * Momentum * VSui * HaSui * Magma * Magma (ALMM) * FlowX version Integer Higher versions may unlock more features. Current version is `12` **Sample Request** Copy https://open-aggregator-api.naviprotocol.io/find_routes? from=0x2::sui::SUI& target=0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7%3A%3Ausdc%3A%3AUSDC &amount=100000000&by_amount_in=true&depth=3&version=12 **Sample Response** 200 400 [PreviousAggregator Components](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/images-and-media/aggregator-components) [Next💰 Integrating Fees](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/integrating-fees) Last updated 1 month ago Copy { "data": { "amount_in": "100000000", "amount_out": 223857, "routes": [\ {\ "path": [\ {\ "id": "0xa63347f0a3d79e36c629866d72d148403907088cca219d80bdd5461d79d34d46",\ "type": "0x3492c874c1e3b3e2984e8c41b589e642d4d0a5d6459e5a9cfc2d52fd7c89c267::pool::Pool<0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI, 0x2::sui::SUI>",\ "provider": "bluefin",\ "from": "0x2::sui::SUI",\ "target": "0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI",\ "a2b": false,\ "direction": false,\ "fee_rate": 100,\ "lot_size": 0,\ "amount_in": 100000000,\ "amount_out": 95226771,\ "extended_details": {\ "after_sqrt_price": 0\ },\ "info_for_ptb": {\ "packageId": "0x6c796c3ab3421a68158e0df18e4657b2827b1f8fed5ed4b82dba9c935988711b",\ "moduleName": "gateway",\ "functionName": "route_swap",\ "byAmountIn": true,\ "minSqrtPrice": "79226673515401279992447579055",\ "amountLimit": 0,\ "typeArguments": [\ "0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI",\ "0x2::sui::SUI"\ ]\ }\ },\ {\ "id": "0xaa020ad81e1621d98d4fb82c4acb80dc064722f24ef828ab633bef50fc28268b",\ "type": "0x1eabed72c53feb3805120a081dc15963c204dc8d091542592abaf7a35689b2fb::pool::Pool<0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC, 0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI>",\ "provider": "cetus",\ "from": "0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI",\ "target": "0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC",\ "a2b": false,\ "direction": false,\ "fee_rate": 500,\ "lot_size": 0,\ "amount_in": 95226771,\ "amount_out": 223857,\ "extended_details": {\ "after_sqrt_price": 0\ },\ "info_for_ptb": {\ "globalConfigId": "0xdaa46292632c3c4d8f31f23ea0f9b36a28ff3677e9684980e4438403a67a3d8f",\ "packageId": "0x6f5e582ede61fe5395b50c4a449ec11479a54d7ff8e0158247adfda60d98970b",\ "moduleName": "router",\ "functionName": "swap",\ "typeArguments": [\ "0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC",\ "0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI"\ ],\ "minSqrtPrice": "79226673515401279992447579055"\ }\ }\ ],\ "amount_in": 100000000,\ "amount_out": 223857,\ "initial_price": 0\ }\ ], "from_token": { "address": "0x2::sui::SUI", "decimals": 9, "price": 2.178773719491083 }, "to_token": { "address": "0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC", "decimals": 6, "price": 1.0002348920262438 }, "is_accurate": true } } Copy { "error": "not support" //Means this method is not supported yet } --- # Granular Asset Risk Management | Navi Protocol - docs ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management#supply-limits) **Supply Limits** These are limits to how much of the collateral asset can be used in the money market. This parameter is designed to protect the pool against specific, long-tail volatile assets to damage the pool integrity. For a variety of smaller capitalisation tokens with high fully-diluted valuations that are traded with thin liquidity, having the ability to supply an infinite amount of such token poses structural risks. Were the capitalisation of such token to vary significantly, it is likely that positions backed by such assets could no longer be liquidate-able, posing the risk of bad debt being incurred in the system. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management#debt-ceilings) Debt Ceilings These are limits on the total borrow amount of a market that is collaterized by another specific asset in the pool. The cap is measured as an amount of the borrowed markets underlying tokens. Similarly to Supply Limits, debt ceilings enable further granular risk management of certain collateral assets, by making sure that certain tail assets cannot be used to collateralise positions that are too large. [PreviousGlossary](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/glossary) [NextLiquidation Mechanics](https://naviprotocol.gitbook.io/navi-protocol-docs/security/liquidation-mechanics) Last updated 1 year ago * [Supply Limits](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management#supply-limits) * [Debt Ceilings](https://naviprotocol.gitbook.io/navi-protocol-docs/security/granular-asset-risk-management#debt-ceilings) --- # Introduction | Astros Astros perp is an innovative decentralized platform dedicated to financial derivatives, seamlessly operating on Sui Network。 Utilizing an advanced order book model, Astros collaborates with a wide network of market makers to deliver comprehensive asset exposure across a diverse range of markets. At the core of our innovation lies an unique "off-chain aggregation and on-chain settlement" approach, which combines the security and transparency of decentralized exchanges with the efficiency and intuitive user experience traditionally associated with centralized platforms. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/editor#quickly-start) Quickly Start [📚Tutorial](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations) [📈Perpetual Trading](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading) [PreviousSlippage](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/slippage) [NextTutorial](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations) Last updated 9 months ago --- # Liquidation Mechanics & Walkthrough | Navi Protocol - docs The health of the NAVI Protocol is dependent on the 'health' of the loans within the system, also known as the 'health factor'. When the 'health factor' of an account's total loans is below 1, anyone can call the `execute_liquidation` to the `LendingPool` contract, paying back part of the debt owed and receiving discounted collateral in return. This incentivizes third parties to participate in the health of the overall protocol, by acting in their own interest (to receive the discounted collateral) and as a result, ensure loans are sufficiently collateralised. There are multiple ways to participate in liquidations: 1. By calling the `execute_liquidation` directly in the LendingPool contract. 2. By creating your own automated bot or system to liquidate loans. For liquidation calls to be profitable, you must take into account the gas cost involved in liquidating the loan. If a high gas price is used, then the liquidation may be unprofitable for you. See the [Calculating profitability vs gas cost](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#calculating-profitability-vs-gas-cost) section for more details. [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#prerequisites) Prerequisites --------------------------------------------------------------------------------------------------------------------------------------------- When making a `execute_liquidation` call, you must: * Know the account (i.e. the Sui address: `user`) whose health factor is below 1. * Know the valid debt amount (`debt_to_cover`) and debt asset (`debt`) that can be paid. * The close factor is 0.35, which means that only a maximum of 35% of the debt can be liquidated per valid `execute_liquidation`. * You can set the `debt_to_cover` to `uint(-1)` and the protocol will proceed with the highest possible liquidation allowed by the close factor. * You must already have a sufficient balance of the debt asset, which will be used by the `execute_liquidation` to pay back the debts. * Know the collateral asset (`collateral`) you are closing. I.e. the collateral asset that the user has 'backing' their outstanding loan that you will partly receive as a 'bonus'. [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-1.-getting-accounts-to-liquidate) 1\. Getting accounts to liquidate --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Only user accounts that have a health factor below 1 can be liquidated. There are multiple ways you can get the health factor, with most of them involving 'user account data'. "Users" in the NAVI Protocol refer to a single Sui address that has interacted with the protocol. This can be an externally owned account or contract. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#on-chain) On-chain 1. To gather user account data from on-chain data, one way would be to monitor emitted events from the protocol and keep an up to date index of user data locally. 1. Events are emitted each time a user interacts with the protocol (deposit, repay, borrow, etc). See the contract source code for relevant events. 2. When you have the user's address, you can simply call `get_user_account_data` to read the user's current `health_factor`. If the `health_factor` is below 1, then the account can be liquidated. [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-2.-executing-the-liquidation-call) 2\. Executing the liquidation call ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once you have the account(s) to liquidate, you will need to calculate the amount of collateral that _can_ be liquidated: 1. Use `get_user_reserve_data` on the Lending Pool Lens contract with the relevant parameters. 2. Max debt that can be cleared by single liquidation call is given by the current close factor (which is 0.35 currently). debtToCover\=userVariableDebt∗LiquidationCloseFactorPercentdebtToCover = userVariableDebt \* LiquidationCloseFactorPercentdebtToCover\=userVariableDebt∗LiquidationCloseFactorPercent 3. For reserves that have `usage_as_collateral_enabled` as `true`, the `current_atoken_balance` and the current [liquidation bonus](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing) gives the max amount of collateral that can be liquidated maxAmountOfCollateralToLiquidate\=(debtAssetPrice∗currentATokenBalance∗liquidationBonus)/collateralPricemaxAmountOfCollateralToLiquidate = (debtAssetPrice \* currentATokenBalance \* liquidationBonus)/ collateralPrice maxAmountOfCollateralToLiquidate\=(debtAssetPrice∗currentATokenBalance∗liquidationBonus)/collateralPrice [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-3.-setting-up-a-bot) 3\. Setting up a bot ------------------------------------------------------------------------------------------------------------------------------------------------------------- Depending on your environment, preferred programming tools and languages, your bot should: * Ensure it has enough (or access to enough) funds when liquidating. * Calculate the profitability of liquidating loans vs gas costs, taking into account the most lucrative collateral to liquidate. * Ensure it has access to the latest protocol user data. * Have the usual fail safes and security you'd expect for any production service. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#calculating-profitability-vs-gas-cost) Calculating profitability vs gas cost One way to calculate the profitability is the following: 1. Store and retrieve each collateral's relevant details such as address, decimals used, and liquidation bonus as listed here. 2. Get the user's collateral balance (n`TokenBalance`). 3. Get the asset's price according to the Navi's [oracle contract](notion://www.notion.so/developers/the-core-protocol/price-oracle) (`getAssetPrice()`). 4. The maximum collateral bonus you can receive will be the collateral balance (2) multiplied by the liquidation bonus (1) multiplied by the collateral asset's price in Sui (3). Note that for assets such as USDC, the number of decimals are different from other assets. 5. The maximum cost of your transaction will be your gas price multiplied by the amount of gas used. You should be able to get a good estimation of the gas amount used by calling `estimateGas` via your web3 provider. 6. Your approximate profit will be the value of the collateral bonus (4) minus the cost of your transaction (5). ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#example-liquidation-scenario) **Example Liquidation Scenario** * A user deposits $100 worth of SUI (70% LTV), and borrows $50 worth of BTC. * Supply Balance: $100 * Borrow Balance: $50 * Health Factor = 100 \* 0,7 / 50 = 1.4 * wBTC price goes up by 50% * Supply Balance: $100 * Borrow Balance: $75 * Health Factor = 100 \* 0,7 / 75 = 0,9333 **User is now liquidate-able** Liquidate positions with a **health factor** below 1. When the health factor of a position is below 1, liquidators repay part or all of the outstanding borrowed amount on behalf of the borrower, while **receiving a discounted amount of collateral** in return (also known as a liquidation "bonus"). Liquidators can decide if they want to receive an equivalent amount of collateral aTokens, or the underlying asset directly. When the liquidation is completed successfully, the health factor of the position is increased, bringing the health factor above 1. Liquidators can only close a certain amount of collateral defined by a close factor. Currently the **close factor is 0.35**. In other words, liquidators can only liquidate a maximum of 35% of the amount pending to be repaid in a position. The liquidation discount applies to this amount. _In most scenarios_, profitable liquidators will choose to liquidate as much as they can (50% of the `user` position). To check a user's health factor, use [`get_user_account_data`](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#function-get_user_account_data) [Previous$xBTC Campaign FAQ](https://naviprotocol.gitbook.io/navi-protocol-docs/campaign-detail/usdxbtc-campaign-faq) [NextHackathon - Overflow NAVI Bounty](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty) Last updated 1 year ago * [Prerequisites](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#prerequisites) * [1\. Getting accounts to liquidate](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-1.-getting-accounts-to-liquidate) * [On-chain](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#on-chain) * [2\. Executing the liquidation call](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-2.-executing-the-liquidation-call) * [3\. Setting up a bot](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#id-3.-setting-up-a-bot) * [Calculating profitability vs gas cost](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#calculating-profitability-vs-gas-cost) * [Example Liquidation Scenario](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough#example-liquidation-scenario) --- # Deposits and Withdrawals | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#connect-your-wallet) **Connect Your Wallet** -------------------------------------------------------------------------------------------------------------------------------------------------- Once you're on Astros trading site, just go ahead and click on \[Connect Wallet\]. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXeSZpY6zP_W1rpCMLa4EA1bESVC9zSjwSR8zhjQZl17dWvUriLGXh6AuqtmFD2rHmAfHVMpijYKzheNNJ7zUMhgx86h7o1ewQtMc8ZcXhy4e1HJUt2mxlyj3_LOcsnbMbR-Wp4P9Q%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=7a5470a1&sv=2) * Select the wallet you are using and complete the connection process. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdqfQvZMx_PoIw-iqYjCAx5jCqlDDMJifWl6ZMutlKQcWI3fHJVBzCLol17hg-REm9HALwussgyUXixwZ0TSQPkJx2UXlORYCU0McISPHHu0JacxqTY4s5Ay14i0AOUwJYti-Mr0g%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=300&dpr=4&quality=100&sign=27d8b387&sv=2) * * * [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#deposits) Deposits ------------------------------------------------------------------------------------------------------------------------ Go to \[Account\] - \[Deposit\] and select the currency type and amount to deposit (currently only USDC is accepted). ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXeGBJJiYrN8J4VFSRjUlu8mpo095I5_qArkqmPWPkfvFWoR1foyh9dKP1igefsVWKGJ5KX7E577nqmY2AfGw-uFJoPDA3IuzhPcq6kfyQy8mBLm6YysuvsYdDSgVHaxCE0gdg7kNA%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=40332027&sv=2) ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXfryh113jl5dpp61014Cgy7W8jj9XzqtfAZXfxw4DrmzoDgKZ9YukHCTnQ49eXILuuXLBIGCHwmeNKxussxEWJcUPx1pJYRbQYd_V1iX3daTGgsXlWKo_V_KLsQdzf3moM6JghYgw%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=a10360fe&sv=2) If you don’t have available assets in your wallet, you may: * Transfer USDC on other chains to SUI through bridges. * Swap other assets for USDC. Deposit your USDC into the Astros contract to start trading. USDC will be exchanged USD at a 1:1 ratio after you depositing Confirm the transaction in your wallet. You can view your total balance under \[Account\]. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXd1kh4Jweh6kWtXu9-XSK2cVZwlBXbI04t7T6kS5r2GXAuSqbG8D3YQlFOUdx_0ahmkpFt0OiktxXn3npbnsunAFkvP6VcKjdduaVVkNKyyRCYSyeVGv7tt0-DrXzN4ANJGBDKbsQ%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=1273a41b&sv=2) To check your activity history, click \[Assets\] ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXfTMqsQk2xIkbEPnR0jCed55knqfO4S1usi5z42dEkmHiSOlwMPkaIu4x0TYr57AIZsbLrpAW-otfd1c6UhpMpmhOpY2lwV1jQrMyT3NlYHEqUjK_q8xOPLVuENN7sudJ2CD2un%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=3f39390c&sv=2) * * * [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#withdrawals) Withdrawals ------------------------------------------------------------------------------------------------------------------------------ 1. Navigate to \[Account\] - \[Withdraw\] and select the currency type and amount to withdraw. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdJ4p9lsGMmfMv7_mBDxuLFTIB4cv7mOjlu3yH5N8puVpsCJXAxYZogk-GjreGu-Ug-kjQk4FTu_8RmypbN_hR3JwyTRvm13t6DHaP2V11zwjl_7ZM8geZb23spECoRJF7m8fN-sw%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=edb406fc&sv=2) ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXcsNRgClLD1OyeMf56XL0ABWoKFPYRLPNvl6EsXwMTSjLDwFVn6873lLZQmT4lT9WelwIwhVdIlskafXj_alRlxgt3sEg3_mMi5WLMATdSjZZfbnHJtpt-9SbHfK_WRpwGdV3FnQQ%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=a98d42ac&sv=2) 2. Withdrawn USD will be converted back to USDC at a 1:1 ratio. 3. Note: 1. Margin allocated to open orders or active positions cannot be withdrawn. 2. If a withdrawal times out or is rejected by your wallet, the funds will be frozen for 10 minutes. You may retry after this period. 4. Confirm the transaction in your wallet. 5. Wait briefly; once confirmed, the funds will appear in your wallet. [PreviousTutorial](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations) [NextTrading](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading) Last updated 9 months ago * [Connect Your Wallet](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#connect-your-wallet) * [Deposits](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#deposits) * [Withdrawals](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals#withdrawals) --- # $xBTC Campaign FAQ | Navi Protocol - docs **xBTC Campaign Key Timeline** * **June 24:** NAVI $xBTC Supply Incentives go live on [OKX Earn](https://web3.okx.com/earn/product/navi-protocol-sui-xbtc-40510#source=activitypage&activitySourcePage=sui) * **June 27:** NAVI $xBTC [Borrow Campaign](https://app.naviprotocol.io/campaign/xbtc-okx-9) launches ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/campaign-detail/usdxbtc-campaign-faq#faq) FAQ * How does NAVI calculate the borrow limit? -Borrow Limit Definition: When a user supplies an asset, the borrowing limit represents the maximum amount they can borrow based on the asset's LTV and the user’s collateral capacity. Subsidies will only cover the borrowed amount released by supplying $xBTC. Here are two examples: * Example 1:\* User supplies 10,000 USDT (Max LTV 80%), $10,000 equivalent of $xBTC (Max LTV 60%) User's borrowing limit is $8,000 equivalent plus $6,000 equivalent tokens. Subsidies are calculated based on collateral weight. If a user borrows $7000, the borrowing fees for $3500 equivalent assets will be subsidized. * Example 2:\* If the user only holds $xBTC for collateral and has borrowed any other asset, the platform provides a 100% subsidy based on the collateral weight at the time of borrowing. * How do I calculate borrow fee subsidies? -Borrow fee subsidies will only apply to the available borrowing limit released after supplying $xBTC, based on a proportion of the user's collateral. * How do I claim the reward/subsidies? Reward distribution method • Rewards are distributed in real time in $NAVX, and the amount is converted according to the current market price • Users receive $NAVX on the NAVI platform, and OKX rewards ($SUI) are received through OKX Earn page * Will the $xBTC parameters change during the campaign period? NAVI will continuously monitor dynamic parameters such as LTV, and these are open for discussion after risks are properly evaluated. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/campaign-detail/usdxbtc-campaign-faq#campaign-1-borrow-fee-rebate-in-usdnavx) Campaign 1: Borrow Fee Rebate(In $NAVX) Section Details **Eligibility** Users who supply xBTC on OKX Earn or NAVI and Borrow USDC or SUI on NAVI **Reward Logic** Unlimited Fee Rebate calculated based on xBTC’s share in total supply when borrow is opened. * Fee Rebate for USDC Borrowers begin 27 June * Fee Rebate for USDC Borrowers begin 7 July **Example** Supply $4,000 USDT + $6,000 xBTC → 60% xBTC shareBorrow fees = $7,000Bonus = $7,000 × 60% = $4,200 NAVX **Example Flow** 1. Connect Wallet 2. Supply xBTC on OKX or NAVI 3. Borrow USDC/SUI 4. Enjoy the Fee Rebate #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/campaign-detail/usdxbtc-campaign-faq#campaign-2-borrow-apr-subsidy-navx--sui-rewards) Campaign 2: Borrow APR Subsidy (NAVX + SUI Rewards) Section Details **Eligibility** * Supply xBTC only- Borrow USDC or SUI * Only OKX Earn users eligible for SUI rewards **Reward Pool** \>$200,000 in $SUI (OKX Earn only)>$500,000 in $NAVX **Reward Logic** * Borrow APR Bonus will also be calculated based on xBTC’s share of the total supply. * Hourly APR subsidy based on xBTC’s share of supplied collateral * Borrow fee rebate for USDC begin on June 27, while borrow fee rebate for SUI starts from July 7. * The Borrow APR subsidy will continue to be issued in the form of a fixed amount every week. The $NAVX subsidy amount is 60% of the user's interest. If it is ran out for the week, NAVI will stop subsidizing but it will be refilled next week for the campaign period. **Claim Rules** * During Campaign: Real-time distribution on Campaign Page * Users will receive $NAVX rewards on the NAVI platform, while $SUI rewards will be claimed via OKX Earn. * After Campaign ends: Claim within 30 days * Unclaimed rewards are forfeited **Example Flow** 1. Supply on OKX or NAVI 2. Borrow USDC, SUI 3. Earn APR bonus 4. Claim rewards **👋 Want to stay in the loop?** Hop into our community for the latest updates, campaign tips, and real-time support: * [Twitter](https://x.com/navi_protocol) * [Telegram](https://t.me/navi_protocol) * [Discord](https://discord.com/invite/R6Xkbee8Xq) Let’s build together! [PreviousNAVI AI Trading Bot](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/navi-ai-trading-bot) [NextLiquidation Mechanics & Walkthrough](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough) Last updated 5 months ago --- # Trading | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#opening-positions) Opening Positions ------------------------------------------------------------------------------------------------------------------------- Users can open positions by choosing either \[Buy/Long\] or \[Sell/Short\], utilizing leverage to enhance trading potential. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdIT7oc6TOZckgTQatRdUA9ZSqW725e_nAz9ZvxsbVgxDs-8-x-LblAj-iiiX84qOPvLkDbOB5T7807fe9pUUlhMvndrSOjrocCv5PRg2F2vm1vKKFLhr0zR1o4GWjU1ZPOd-fzEw%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=ff431ba1&sv=2) * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#order-types) **Order Types** 1. Market Order: 1. Executes immediately at the current market price, prioritizing speed over price. 2. May experience slippage due to market volatility. 2. Limit Order: 1. Executes at a specified price or better. 2. For buy orders, the trade will execute at the limit price or lower. 3. For sell orders, the trade will execute at the limit price or higher. 4. Note: If the market price doesn’t reach the specified limit price, the order may not execute. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#estimated-position-profit-loss) **Estimated Position Profit/Loss** Long Position: * Profit: Gains are realized when the price rises. * Loss: Losses occur when the price falls. For example: * With 10x leverage, a 10% price increase results in a 100% profit. * If the maintenance margin is 1.5%, an 8.5% price decrease leads to a total loss of 100%, causing the position to be liquidated. Short Position: * Profit: Gains are realized when the price falls. * Loss: Losses occur when the price rises. For example: * With 1x leverage, a 10% price decrease results in a 10% profit. If the maintenance margin is 1.5%, a 98.5% price increase leads to a total loss of 100%, causing liquidation. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXd6cy5sNn3J160uFqlyw1sExvBi00qkbns2KrdUyIuTAhF2GmAQSav7fh5fdUFn56Gl-sePv9OGwf8xpNGzxl-a-6zNACpXj_ppVA9Hy9sAEqCeQypyD5Osp875CKp4ebaSLAqa6A%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=13adfcc8&sv=2) The examples focus on price movement impacts. Actual positions may incur **funding fees**, and the profit/loss figures are for reference only. Maintenance margin rates vary per cryptocurrency, reflecting different levels of trading risk. Review the token-specific parameters before trading. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#position-management) Position Management Users can manage their positions directly from the trading interface. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXefTL6tsQj1NDpb_nPv7LQYadyV3DIj797qQb-dOVW0XWtbISL6i830db5QACbduT2ZOaqSzifRh_fqbrAV3WaoaZxulZDIkxwEEBoa5wlYPMc2mVHKsEuE7lv7ZeLLKHqZknoJ3A%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=24656d0a&sv=2) 1. Adding Margin: 1. Isolated Margin: Add or reduce margin for a specific isolated position. 1. Click the margin adjustment button to modify the margin, managing your risk exposure. 2. Note: Initial margin cannot be reduced. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXecIiktsccLDRyINyumHA2Bkv3fmxZOA2ZpUCY90PUwmaYEcIG9cyC69FfsDSg1frVikhQ1NiaezHmNkNC1ycYbRZJDa9NjmVLzpams46fEcFi0FJZNA2TL1Wo_2EyXpMUnA3UB7w%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=d0df8adb&sv=2) 3. Cross Margin: Use available balance to supplement margin and lower position risk. 2. Liquidation Price and Margin Levels: 1. If the mark price reaches the liquidation price, the position will be liquidated, resulting in a total loss of associated margin. 2. Monitor margin levels to manage risk. If the margin level reaches or exceeds 100%, the position will be liquidated. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXe2pzsK0h6KQ6lRtWZv5y6RIrmW-QhmTGXmYUqr0CCSW7097U_UDHfQO6npsERWRZ8KbVJnDMlsn8TT4rcf2amECu6L6bFoCZLTtl2uy6IgI4whL59JMmebq4COihPq2jAsCoSu%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=3dea4ec0&sv=2) * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#stop-loss-and-take-profit) **Stop Loss and Take Profit** * Pre-set stop loss and take profit prices for your positions. * Orders execute automatically when the market price reaches the set levels. * Note: These are processed as market orders and may experience slippage. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXffFw35dbXFcPOQQd8wOlReatbwZVP5fMkLSlhP-_JdAYHDNz7ytyTE1sj3LwNrBglli36CbvVyxqUUxnt_JGBxoE-HhZ94Dn8lOVIhNra4z5gGmuAavfQqHbKhpbXsTd8-CpfB%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=16dcb5df&sv=2) ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXepqhifsFArbUAIdl6aZL_bLOjqRyKbFvhE86WFs-5_33CzQoSFcbK2uspQTKcwHdG9rQQ5WTKDnmyxjq-fKNcnDvFyBD4f6tgT0Yvge53GkvRnqWXp88bbnJBeZk7Slshg4RyMVA%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=32e21daa&sv=2) * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#closing-positions) **Closing Positions** 1. Click \[Close\] to close a position using either market or limit orders. 2. Alternatively, click \[Close All\] to cancel all open orders and close all positions at the current market price. ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Flh7-rt.googleusercontent.com%2Fdocsz%2FAD_4nXdfZYPp6cSwt9heq0X06CBWbaxo6LpWNcmu9WthNI2Fq-WzrpoIQMzwL68X4TyPPQnNwv4jcbveB4_4S_2q1i8wpAwuYn7IRlFWc4alyLFL1wC8cWnP0LZIJkYCf4Y9JDK97PwBXQ%3Fkey%3DDoQZ5Piz_l7a1tLlNidGQ4gB&width=768&dpr=4&quality=100&sign=78a4c67f&sv=2) [PreviousDeposits and Withdrawals](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/deposits-and-withdrawals) [NextPerpetual Trading](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading) Last updated 9 months ago * [Opening Positions](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#opening-positions) * [Order Types](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#order-types) * [Estimated Position Profit/Loss](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#estimated-position-profit-loss) * [Position Management](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#position-management) * [Stop Loss and Take Profit](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#stop-loss-and-take-profit) * [Closing Positions](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading#closing-positions) --- # Hackathon - Overflow NAVI Bounty | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#developer-prizes) Developer Prizes -------------------------------------------------------------------------------------------------------------------------------------------- **Total prize pool**: $10000 in $NAVX (SUI-native token with the most extensive use cases) by designing and deploying a meaningful and useful\* flashloan bot that commits the most calls to NAVI's flash loan feature, leveraging the [NAVI SDK](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/) ! First prize - most calls to flash loan - $5000 in $NAVX Second prize - 2nd most calls to flash loan - $3000 in $NAVX Third prize - 3rd most calls to flash loan - $2000 in $NAVX **Your Impact**: Design and deploy a meaningful and useful\* flash loan bot that maximizes the utilization of NAVI's flash loan feature, leveraging the NAVI SDK. Together, your submissions will help test and refine a robust flash loan mechanism that offers users efficient access to capital for various DeFi activities while ensuring security and reliability. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#meaningful-and-useful-assessment-criteria) \*Meaningful and Useful Assessment Criteria 1. Utility: The bot must provide tangible benefits to users and contribute to the overall growth and adoption of the NAVI ecosystem. 2. Security: The bot's code should prioritize security practices and follow industry standards to protect users' funds and maintain the integrity of the NAVI ecosystem. 3. Performance: The bot must demonstrate high performance and reliability during execution, with minimal latency and efficient use of resources. 4. Alignment with NAVI Ecosystem: The bot's design and functionality should contribute to the growth and success of the NAVI ecosystem, encouraging adoption and fostering community engagement. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#deliverables) Deliverables 1. A concise problem statement outlining the specific user needs or pain points addressed by the bot + demonstration of the bot's functionality and its impact 2. A well-documented flash loan bot codebase that showcases the effective use of NAVI's flash loan feature and NAVI SDK. 3. A detailed report outlining the bot's design choices, implementation process, and test cases to verify its performance and reliability. [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#why-build-together-with-navi-protocol) Why Build Together with NAVI Protocol? --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- **A Shared Vision for NAVI Flash Loan Innovation** Documentation: [NAVI Flash Loan Developer Doc](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan) Flash Loan Education Series: [Thread](https://x.com/navi_protocol/status/1710350795844014426?s=20) ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#summary-benefits-of-flash-loans-for-defi-users) Summary benefits of flash loans for DeFi users: 1. No need for collateral democratizes access 2. More arbitrage opportunities enable higher capital efficiency 3. Instant liquidity for participants improves overall ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#thorough-documentation-developer-tools-and-technical-support) Thorough Documentation, Developer Tools, and Technical Support Leverage [NAVI SDK](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/how-to-interact-with-the-contract/navi-sdk) to seamlessly integrate NAVI and SUI data into your applications, which is backed by our full team support to ensure smooth implementation and optimization. If you're a developer with a passion for innovation and a shared vision for the future, we want to work with you. Join us in expanding the utility of digital assets, proliferating seamless user experiences, and building the new era of digital finance. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#getting-started) Getting Started Step 1: Join our dedicated [developer channel](http://t.me/navi_protocol/147041) , supported by our experienced technical leads Step 2: Explore developer docs on integrating [Flash Loans](https://naviprotocol.gitbook.io/navi-protocol-docs/getting-started/flash-loan) and data via the [NAVI SDK](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/how-to-interact-with-the-contract/navi-sdk) Step 3: Follow SUI Overflow Hackathon and NAVI guidelines to submit your project [](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#about-navi-protocol) About NAVI Protocol -------------------------------------------------------------------------------------------------------------------------------------------------- [NAVI](https://naviprotocol.io/) is the first and most trusted Native One-Stop Liquidity Protocol on Sui. With over $180M in TVL and nearly 1M active users, it enables anyone to participate as liquidity providers or borrowers within the Sui Ecosystem. The protocol's innovative features, such as Flash Loans, Automatic Leverage Vaults, and Isolation Mode, enable users to leverage their assets and access novel trading opportunities with minimized risks. NAVI's design provides support for digital assets at different risk levels, while its advanced security features ensure the protection of user funds and the mitigation of systemic risks. NAVI’s innovation roadmap and tools are built by developers for developers. Core contributors of the protocol regularly sponsor and mentor feature-integration hackathons, product-led partnerships, and any aspiring builders in the move ecosystem. [PreviousLiquidation Mechanics & Walkthrough](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/liquidation-mechanics-and-walkthrough) [NextSupported Assets](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets) Last updated 1 year ago * [Developer Prizes](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#developer-prizes) * [\*Meaningful and Useful Assessment Criteria](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#meaningful-and-useful-assessment-criteria) * [Deliverables](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#deliverables) * [Why Build Together with NAVI Protocol?](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#why-build-together-with-navi-protocol) * [Summary benefits of flash loans for DeFi users:](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#summary-benefits-of-flash-loans-for-defi-users) * [Thorough Documentation, Developer Tools, and Technical Support](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#thorough-documentation-developer-tools-and-technical-support) * [Getting Started](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#getting-started) * [About NAVI Protocol](https://naviprotocol.gitbook.io/navi-protocol-docs/developers-docs/hackathon-overflow-navi-bounty#about-navi-protocol) --- # Bug Bounty Program | Navi Protocol - docs NAVI Protocol is committed to maintaining a secure and reliable platform for all users. To enhance our security measures, we invite researchers and developers to participate in our Bug Bounty Program. This program offers rewards for identifying and reporting vulnerabilities that could compromise the integrity, security, or functionality of the NAVI Protocol. [](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program#rewards) Rewards ------------------------------------------------------------------------------------------------------- Tier 1: Ability to Extract the TVL of any pool: Up to 2, 000, 000 NAVX Tier 2: Ability to permanently deny access to the TVL of one or many pools: Up to 1,000,000 NAVX Tier 3: Ability to attack or manipulate decentralized oracles used by NAVI: Up to 500, 000 NAVX Tier 4: Website design or logic flaws, bugs or frontend attack: Up to 100, 000 NAVX [](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program#to-submit-a-report) To Submit a Report ----------------------------------------------------------------------------------------------------------------------------- If you identify a vulnerability, please submit your report by emailing **bounty@naviprotocol.io**. Ensure your report includes detailed information about the vulnerability and steps to reproduce it. [PreviousAudit Report](https://naviprotocol.gitbook.io/navi-protocol-docs/security/audit-report) [Next2025 Roadmap](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap) Last updated 1 year ago * [Rewards](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program#rewards) * [To Submit a Report](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program#to-submit-a-report) --- # Audit Report | Navi Protocol - docs 2025 Auditing Report 307KB [movebit\_navi\_lending\_incentive\_2025\_01.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FCRilqvGAjGVHk2jQjunP%2Fmovebit_navi_lending_incentive_2025_01.pdf?alt=media&token=9407c325-256a-4cb0-b39d-3dea7edb5085) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FCRilqvGAjGVHk2jQjunP%2Fmovebit_navi_lending_incentive_2025_01.pdf?alt=media&token=9407c325-256a-4cb0-b39d-3dea7edb5085) 2024 Auditing Report 87KB [ottersec<> navi\_token\_2024\_01.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FlKpoD7sgSVgYKIgcuphY%2Fottersec%3C%3E%20navi_token_2024_01.pdf?alt=media&token=cce36162-7bb5-40aa-b52f-8236d9a9476f) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FlKpoD7sgSVgYKIgcuphY%2Fottersec%3C%3E%20navi_token_2024_01.pdf?alt=media&token=cce36162-7bb5-40aa-b52f-8236d9a9476f) 590KB [salus \_\_ navi\_penetration\_testing\_report\_2024\_01.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F8sT2EQSxGzDubbIRbePr%2Fsalus%20__%20navi_penetration_testing_report_2024_01.pdf?alt=media&token=300a1087-b9fc-4a1a-a291-3206f712b0f6) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F8sT2EQSxGzDubbIRbePr%2Fsalus%20__%20navi_penetration_testing_report_2024_01.pdf?alt=media&token=300a1087-b9fc-4a1a-a291-3206f712b0f6) 187KB [ottersec <> navi\_lending\_2024\_03\_follow\_up\_audit.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FQJXKf2HCBeJs0vev3eSs%2Fottersec%20%3C%3E%20navi_lending_2024_03_follow_up_audit.pdf?alt=media&token=bc8094cf-d4d0-4759-bbae-4e34e497eb3c) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FQJXKf2HCBeJs0vev3eSs%2Fottersec%20%3C%3E%20navi_lending_2024_03_follow_up_audit.pdf?alt=media&token=bc8094cf-d4d0-4759-bbae-4e34e497eb3c) 603KB [verdise<> navi\_oracle\_2024\_06\_audit.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F1vKf5VZ8e3sOLsC9Dtkg%2Fverdise%3C%3E%20navi_oracle_2024_06_audit.pdf?alt=media&token=f5002aa3-a834-4c46-8028-08e5bb04708e) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F1vKf5VZ8e3sOLsC9Dtkg%2Fverdise%3C%3E%20navi_oracle_2024_06_audit.pdf?alt=media&token=f5002aa3-a834-4c46-8028-08e5bb04708e) 2023 Auditing Report 168KB [Ottersec <> NAVI Final Audit Report.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FfCizb1wHSOKMqSPv6uBw%2FOttersec%20%3C%3E%20NAVI%20Final%20Audit%20Report.pdf?alt=media&token=03738aa8-9d38-4aaf-ba55-3fd0bde778a6) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FfCizb1wHSOKMqSPv6uBw%2FOttersec%20%3C%3E%20NAVI%20Final%20Audit%20Report.pdf?alt=media&token=03738aa8-9d38-4aaf-ba55-3fd0bde778a6) 925KB [Navi Smart Contract Audit Report.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2Fwolx9zIMMEEejTJx3nV3%2FNavi%20Smart%20Contract%20Audit%20Report.pdf?alt=media&token=1cb7f429-e1bd-44c0-916d-ed2ab3f46740) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2Fwolx9zIMMEEejTJx3nV3%2FNavi%20Smart%20Contract%20Audit%20Report.pdf?alt=media&token=1cb7f429-e1bd-44c0-916d-ed2ab3f46740) 590KB [Salus <> NAVI Penetration Testing Report.pdf](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F5ASrxr6zPhmcvXAr7NTt%2FSalus%20%3C%3E%20NAVI%20Penetration%20Testing%20Report.pdf?alt=media&token=c01e70e1-c338-4d24-8b20-721dcb7215b3) PDF Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2F5ASrxr6zPhmcvXAr7NTt%2FSalus%20%3C%3E%20NAVI%20Penetration%20Testing%20Report.pdf?alt=media&token=c01e70e1-c338-4d24-8b20-721dcb7215b3) [PreviousLiquidation Mechanics](https://naviprotocol.gitbook.io/navi-protocol-docs/security/liquidation-mechanics) [NextBug Bounty Program](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program) Last updated 9 months ago --- # Perpetual Trading | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading#order-matching-mechanism) Order Matching Mechanism ------------------------------------------------------------------------------------------------------------------------------------ Astros employs a **Price-Time Priority** system, utilizing a **First-In-First-Out (FIFO)** methodology for matching orders. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading#matching-criteria) Matching Criteria: Orders are matched when either of the following conditions is met: * A **buy (bid)** order price is **equal to or higher** than the best available **sell (ask)** order price. * A **sell (ask)** order price is **equal to or lower** than the best available **buy (bid)** order price. * A **market order** is submitted, and opposing limit orders already exist in the order book. In all cases, orders with earlier timestamps receive priority at the same price level. [PreviousTrading](https://naviprotocol.gitbook.io/astros/astros-perpetual/integrations/trading) [NextFunding](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding) Last updated 9 months ago --- # Referral | Astros ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#referral-types) Referral Types #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#referral-lite) Referral Lite Referral Lite is available to all users by default and is suitable for individual referrals. * Commission rate: 25% * Eligibility: Open to all users * Activation: No application required ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2F3166231846-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FEagmjVMVJsuZQ0TvRYt7%252Fuploads%252FEyb5mC0lETs65jOQs06Y%252FReferral%2520Lite.png%3Falt%3Dmedia%26token%3Da04f8521-bc77-4293-b764-12a3bc872752&width=768&dpr=4&quality=100&sign=f266d14a&sv=2) #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#referral-pro) Referral Pro Referral Pro is designed for KOLs, content creators, and community leaders with established communities. * Commission rate: Up to 40% * Adjustment: The commission rate can be manually adjusted up to 40% * Eligibility: Approval required * How to apply: * Submit an application via the [official application](http://forms.gle/W5qFv4XodZUHxRpJA) form on the Astros website, or * Contact the Astros team directly to request access ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2F3166231846-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FEagmjVMVJsuZQ0TvRYt7%252Fuploads%252FvkTTvVMSUKfEsjrECFaJ%252Funknown.png%3Falt%3Dmedia%26token%3D30364c7c-f731-49ad-8fd0-644fb6c237e6&width=768&dpr=4&quality=100&sign=5bf788ce&sv=2) ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#commission-settlement) Commission Settlement * Settlement frequency: Every 24 hours * Settlement method: Commissions are automatically credited to the user’s account Once settled, commissions become immediately available. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#commission-usage) Commission Usage Referral commissions can be used in the following ways: * Applied toward perpetual trading (Perps) on Astros * Withdrawn at any time to the user’s wallet There are no lock-up periods or usage restrictions on referral commissions. [PreviousTrading Fees](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees) [NextPoints](https://naviprotocol.gitbook.io/astros/astros-perpetual/points) Last updated 11 days ago * [Referral Types](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#referral-types) * [Commission Settlement](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#commission-settlement) * [Commission Usage](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral#commission-usage) --- # NAVI Media Kit (logos) | Navi Protocol - docs You may download from this: 397KB [NAVI Brand Assets.zip](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FVLzGBfz5PjPYinCvrm1R%2FNAVI%20Brand%20Assets.zip?alt=media&token=6e68dce8-21aa-4c67-9fcc-b137aba73396) archive Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FVLzGBfz5PjPYinCvrm1R%2FNAVI%20Brand%20Assets.zip?alt=media&token=6e68dce8-21aa-4c67-9fcc-b137aba73396) 309KB [Volo Brand Assets.zip](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FKvMlgydSDNVCwXKuYDGQ%2FVolo%20Brand%20Assets.zip?alt=media&token=7d7237ed-ca1e-435a-b024-7abf4d97c4d9) archive Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FKvMlgydSDNVCwXKuYDGQ%2FVolo%20Brand%20Assets.zip?alt=media&token=7d7237ed-ca1e-435a-b024-7abf4d97c4d9) 2MB [Astros Brand Assets.zip](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FiZbuhu6XGgAM2DyJxPuY%2FAstros%20Brand%20Assets.zip?alt=media&token=ed99a10f-65b1-42ee-9aeb-5a3a79afeb7d) archive Download[Open](https://757519164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYTRq6w3DGapKHxfqaA3Z%2Fuploads%2FiZbuhu6XGgAM2DyJxPuY%2FAstros%20Brand%20Assets.zip?alt=media&token=ed99a10f-65b1-42ee-9aeb-5a3a79afeb7d) [PreviousFAQ](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/faq) [NextTerms of Service](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service) Last updated 10 months ago --- # NAVX Tokenomics | Navi Protocol - docs $NAVX Token is a vital component of the NAVI Protocol ecosystem. This document outlines $NAVX token’s distribution, emission schedule, utilities, and governance role. [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-07b2) Token Overview ---------------------------------------------------------------------------------------------------------------- * **Name**: $NAVX Token * **Ticker**: $NAVX * **Chain**: Sui * **Total Supply (Max)**: 1,000,000,000 $NAVX * **Contract Address:** [**https://suivision.xyz/coin/0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX**](https://suivision.xyz/coin/0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX) [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-5ef6) Utility & Governance ---------------------------------------------------------------------------------------------------------------------- The $NAVX token has a wide range of use cases within NAVI Protocol. These use cases for $NAVX have been designed to promote growth and asset composability across the broader Sui DeFi ecosystem. They are part of the structured journey toward achieving decentralization, community governance, and vital protocol autonomy. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#ddf8) **| Governance**: Token holders can participate in the governance of the NAVI Protocol by voting on proposals and updates. This decentralized governance process ensures that the platform’s development and future direction are driven by its users. Governance proposals would include: * Money Markets * New Proposals for collateral & isolated market candidates. * Proposals for incentivized pools. * Major platform updates. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-2e71) **| Dynamic Liquidity (dLP) provision**: Users can provide liquidity to NAVX/SUI and NAVX/vSUI pairs in DEXes to get LP tokens. They can then lock their LP tokens for a period of time in proportion to their supply amount to activate eligibility to receive rewards within the money market. **dLP utilities include:** * **Boosted $NAVX Emission:** Users can earn additional $NAVX rewards on top of their basic supply/borrow APY. * **Revenue Sharing**: NAVI Protocol generates fees from borrowing within the platform. A portion of these fees is allocated to dLP holders, while the remaining fees are distributed to the platform’s treasury and other purposes as defined by the platform’s design. * **Voting**: Users who hold dLP tokens have more leveraged voting power than regular $NAVX token holders. * **Eligibility**: To trigger $NAVX emissions on both deposits and borrows, you must lock at least 2.5% of your deposit’s USD value in dLP tokens. Conclusively, $NAVX’s utility encourages users and token holders to actively participate in the protocol’s governance and liquidity activities in NAVI’s ecosystem. [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-59aa) Token distribution -------------------------------------------------------------------------------------------------------------------- The $NAVX token allocation is designed to support the growth, sustainability, and decentralization of the NAVI Protocol. Here’s how the tokens are distributed: ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A1400%2F1*5SpoYQScmgwjdN8H6CTeag.png&width=768&dpr=4&quality=100&sign=bdab9ff1&sv=2) NAVX Token Allocation **Each allocation has a specific use case:** * **Team**: 20% — Allocated for team members to align with long-term project success. * **Treasury**: 10% — Reserved for daily operations and strategic initiatives. * **Liquidity Provision**: 4% — To support market makers and secure liquidity. * [**Public Sale (IDO)**](https://medium.com/@navi.protocol/official-announcement-navx-ido-with-cetus-strategic-dex-partner-41cce9f06e96) : 1.2% — Allocated for the initial decentralized exchange offering. * **Marketing**: 3% — Used for promotional and outreach activities. * **Ecosystem & Airdrop**: 45.8% — Dedicated to incentivizing TVL growth, running campaigns and airdrops. Includes the initial early supporters incentive. * **Investors / Advisors**: 16% — Allocated for investors and advisors. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-778e) Token Emission The $NAVX Tokenomics endeavors to foster a shared vision of harmonization among stakeholders operating within the NAVI ecosystem, protocol functionality, and the $NAVX token, which forms a vital pillar of security for the NAVI Protocol. Below, you can find the vesting table and release schedule for $NAVX during, and post-IDO: ![](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A1400%2F0*ZxaSYpYVpj4CGhps&width=768&dpr=4&quality=100&sign=8656e7f0&sv=2) NAVX Emission Chart Conclusively, the NAVX token distribution perpetuates the community narrative, by reserving the largest allocation for ecosystem participants and community members. The main goal is to provide a sustainable and rewarding incentive model that drives growth and contributes to decentralization. [Previous2025 Roadmap](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap) [NextFAQ](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/faq) Last updated 1 year ago * [Token Overview](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-07b2) * [Utility & Governance](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-5ef6) * [| Governance:](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#ddf8) * [| Dynamic Liquidity (dLP) provision:](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-2e71) * [Token distribution](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-59aa) * [Token Emission](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics#id-778e) --- # 2025 Roadmap | Navi Protocol - docs ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q1-2025-foundation-for-ecosystem-growth) **Q1 2025 Foundation for Ecosystem Growth** * **SDK Open-Sourcing** * Release the NAVI SDK as an open-source project with comprehensive documentation. * Establish a developer portal with resources, guides, and tutorials. * **Migration Expansion** * Provide more capital flexibility to users. * Fully autopilot advanced lending strategies & take advantage of the shifting tides in liquidity. * **Multi-chain Expansion** * Strengthen interoperability with advanced bridge solutions. * Enhance cross-chain compatibility to expand market reach. * **Partnership Expansion** * Form strategic alliances with key projects to integrate NAVI solutions. * Collaborate with partners to enhance liquidity and user adoption. * **Platform Rebranding** * Launch a comprehensive rebranding initiative to refresh our visual identity, brand voice, and user experience * Strengthen user recognition, enhance market competitiveness, and support future growth. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q2-2025-ecosystem-diversification-and-adoption) **Q2 2025 Ecosystem Diversification & Adoption** * **Infrastructure Enhancements** * Optimize network efficiency and reduce latency in transactions. * Improve security measures and risk management protocols. * Continuous Optimization of Lending Product. * **Launch of New Ecosystem Products** * Introducing Diverse New Projects to the Ecosystem. * Partner with wallet providers and dApps to facilitate seamless integrations. * **User Growth & Incentives** * Deploy marketing and reward campaigns to onboard new users. * Expand educational content to drive adoption among non-technical users. * **Developer Engagement** * Launch hackathons and bounty programs to incentivize developer participation. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q3-2025-scaling-and-market-expansion) **Q3 2025 Scaling & Market Expansion** * **Adoption Growth** * Develop innovative solutions utilizing the NAVI SDK. * Forge strategic partnerships to drive DeFi integrations. * **Advanced Feature Development** * Implement optimized order execution strategies for NAVI Aggregator. * Explore new possibilities for AI-driven trading tools and analytics. * **Community Governance & Decentralization** * Introduce Vetoken mechanisms to empower the community in decision-making. * Initiate governance discussions on future upgrades and feature prioritization. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q4-2025-maturity-and-long-term-vision) **Q4 2025 Maturity & Long-Term Vision** * **Sustainable Ecosystem Growth** * Strengthen DAO governance with more community-driven initiatives. * Expand developer grant programs for long-term innovation. * **Mainstream Adoption Strategies** * Build user-friendly interfaces and integrations for non-crypto-native users. * Strengthen regulatory compliance to facilitate broader adoption. * **Future Roadmap Planning** * Assess ecosystem performance and iterate on key growth areas. * Define strategic objectives for 2026 and beyond. [PreviousBug Bounty Program](https://naviprotocol.gitbook.io/navi-protocol-docs/security/bug-bounty-program) [NextNAVX Tokenomics](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics) Last updated 9 months ago * [Q1 2025 Foundation for Ecosystem Growth](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q1-2025-foundation-for-ecosystem-growth) * [Q2 2025 Ecosystem Diversification & Adoption](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q2-2025-ecosystem-diversification-and-adoption) * [Q3 2025 Scaling & Market Expansion](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q3-2025-scaling-and-market-expansion) * [Q4 2025 Maturity & Long-Term Vision](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/2025-roadmap#q4-2025-maturity-and-long-term-vision) --- # Insurance Funds | Astros **Liquidation Mechanism** When a position is liquidated, the forced liquidation system automatically triggers. If the perpetual contract’s price reaches the bankruptcy price before the liquidation is fully executed, resulting losses are absorbed by the platform’s **insurance fund** — a dedicated reserve pool. **Insurance Fund Structure** The insurance fund is currently funded and managed by the Astros. Future iterations of the fund will transition to sustained through trading fee allocations. [PreviousLiquidation Process](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process) [NextADL](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl) Last updated 9 months ago --- # Margin | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-requirements) Margin Requirements --------------------------------------------------------------------------------------------------------------------------------- Astros enforces specific margin requirements for traders to effectively manage risk and maintain trading stability. Users must fulfill two types of margin requirements: * **Initial Margin** to open or increase positions. * **Maintenance Margin** to keep positions open and prevent liquidation. Traders can freely adjust their margin balance above these requirements according to their risk tolerance and market conditions. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#initial-margin) Initial Margin The **Initial Margin** is the collateral required to open or expand a position, calculated as follows: Initial Margin\=Initial Margin Fraction×Order Price×Order Size\\text{Initial Margin} = \\text{Initial Margin Fraction} \\times \\text{Order Price} \\times \\text{Order Size}Initial Margin\=Initial Margin Fraction×Order Price×Order Size The **maximum leverage** offered on Astros perpetual contracts is **25x**, which implies that traders must deposit at least **4%** of the position value as collateral when initiating a new position. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#example) Example: If a trader deposits $100 collateral and applies the maximum leverage (25x), the maximum position size can be calculated as: * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#maintenance-margin) Maintenance Margin The **Maintenance Margin** is the minimum collateral required to maintain an open position and prevent liquidation. The calculation formula is: Maintenance Margin Amount\=Maintenance Margin Fraction×Entry Price×Position Size\\text{Maintenance Margin Amount} = \\text{Maintenance Margin Fraction} \\times \\text{Entry Price} \\times \\text{Position Size}Maintenance Margin Amount\=Maintenance Margin Fraction×Entry Price×Position Size Positions falling below this maintenance margin threshold risk automatic liquidation. **Note:** Maintenance margin rates vary according to specific token pairs. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-modes) Margin Modes Astros offers two distinct margin modes to accommodate traders' different risk management preferences: #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#id-1.-isolated-margin-mode-default-mode) 1\. **Isolated Margin Mode** _(Default Mode)_ In **Isolated Margin Mode**, each position's margin is independent of the trader's overall account balance. Losses from liquidation are limited strictly to the margin allocated to that individual position, effectively capping the trader's maximum potential loss. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#id-2.-cross-margin-mode) 2\. **Cross Margin Mode** **Cross Margin Mode** allows positions to utilize the total available balance of the trading pair account as collateral. This approach helps prevent liquidation by dynamically allocating funds across positions within the same trading pair. However, liquidation under cross margin mode carries a higher risk, potentially resulting in the total loss of all collateral allocated within the all trading pair. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-mode-selection-and-restrictions) Margin Mode Selection and Restrictions * Users may select **only one margin mode per perpetual trading pair**. * To switch between margin modes or adjust existing orders: * All open positions and orders related to the trading pair must first be **closed or canceled**. This constraint ensures clear risk management and consistent collateralization. Astros [PreviousFunding](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding) [NextIndex and Mark Price](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price) Last updated 9 months ago * [Margin Requirements](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-requirements) * [Initial Margin](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#initial-margin) * [Maintenance Margin](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#maintenance-margin) * [Margin Modes](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-modes) * [Margin Mode Selection and Restrictions](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin#margin-mode-selection-and-restrictions) --- # Liquidation Process | Astros Astros utilizes **Mark Price** to minimize liquidation risks due to market manipulation or low liquidity. Liquidation occurs when the margin balance of a position reaches or falls below the **maintenance margin** threshold. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#liquidation-price-calculations) Liquidation Price Calculations The liquidation price is calculated differently based on the direction of the position: #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#for-long-positions) For **Long Positions**: Liquidation Price\=(Average Entry Price)×(1+Maintenance Margin Fraction)−Position Margin BalanceContract Size\\text{Liquidation Price} = (\\text{Average Entry Price}) \\times (1 + \\text{Maintenance Margin Fraction}) - \\frac{\\text{Position Margin Balance}}{\\text{Contract Size}}Liquidation Price\=(Average Entry Price)×(1+Maintenance Margin Fraction)−Contract SizePosition Margin Balance​ #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#for-short-positions) For **Short Positions**: Liquidation Price\=(Average Entry Price)×(1−Maintenance Margin Fraction)+Position Margin BalanceContract Size\\text{Liquidation Price} = (\\text{Average Entry Price}) \\times (1 - \\text{Maintenance Margin Fraction}) + \\frac{\\text{Position Margin Balance}}{\\text{Contract Size}}Liquidation Price\=(Average Entry Price)×(1−Maintenance Margin Fraction)+Contract SizePosition Margin Balance​ * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#perpetual-margin-level-calculation) Perpetual Margin Level Calculation To assess the current margin health of a perpetual contract position, Astros computes the margin level as follows: A margin level approaching or falling below 100% indicates an imminent liquidation risk. Astros ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#margin-modes-and-liquidation-impact) Margin Modes and Liquidation Impact Astros provides two distinct margin modes, each with different liquidation implications: #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#id-1.-isolated-margin-mode) **1\. Isolated Margin Mode** In isolated margin mode, liquidation risk and consequences are confined strictly to the margin and funding fees associated with the particular position being liquidated. Other positions and balances remain unaffected. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#id-2.-cross-margin-mode) **2\. Cross Margin Mode** In cross margin mode, liquidation impacts are broader. When liquidation occurs, the trader risks losing: * All collateral allocated. * Accrued funding fees associated with open positions. * Margins reserved for active orders (frozen margin). * The entirety of the available account balance. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#liquidation-outcomes-at-bankruptcy-price) Liquidation Outcomes at Bankruptcy Price During liquidation at the **Bankruptcy Price**, two possible outcomes emerge: * **Surplus Scenario**: If liquidation occurs at a price more favorable than the bankruptcy price, excess collateral is automatically transferred into the **Insurance Fund**. * **Deficit Scenario**: If liquidation cannot be executed above the bankruptcy price, the resulting deficit is first covered by the **Insurance Fund**. However, if the Insurance Fund balance is insufficient to cover this deficit, the liquidation is further managed through the **Automatic Deleveraging (ADL)** mechanism, which systematically reduces other positions to restore financial stability. [PreviousIndex and Mark Price](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price) [NextInsurance Funds](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/insurance-funds) Last updated 9 months ago * [Liquidation Price Calculations](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#liquidation-price-calculations) * [Perpetual Margin Level Calculation](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#perpetual-margin-level-calculation) * [Margin Modes and Liquidation Impact](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#margin-modes-and-liquidation-impact) * [Liquidation Outcomes at Bankruptcy Price](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process#liquidation-outcomes-at-bankruptcy-price) --- # Funding | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#perpetual-contract-pricing-mechanism) **Perpetual Contract Pricing Mechanism** ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Perpetual contract prices are anchored to the spot index price via the funding fee mechanism. * **Long positions** pay funding fees to **short positions** when contracts trade **at a premium** to the spot price. * **Short positions** pay funding fees to **long positions** when contracts trade **at a discount** to the spot price. _The platform retains none of these fees._ [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#funding-rates) **Funding Rates** -------------------------------------------------------------------------------------------------------------------------- Funding fees are charged hourly and determined by two components: 1. **Interest Rate (IR)** Daily rate: 0.03% _(_Variable_)_. Hourly rate: Hourly Interest Rate\=0.03%24\\text{Hourly Interest Rate} = \\frac{0.03\\%}{24}Hourly Interest Rate\=240.03%​ 2. **Premium Index (P)** Calculated at randomized intervals within each minute for each market: Premium Index\=max⁡(0, B−I)−max⁡(0, I−A)I\\text{Premium Index} = \\frac{\\max(0,\\,B - I) - \\max(0,\\,I - A)}{I}Premium Index\=Imax(0,B−I)−max(0,I−A)​ * B: Impact bid price (average execution price to close a long via market sell) * A: Impact ask price (average execution price to close a short via market buy) * I: Spot index price * **Impact Notional Value**: Impact Notional Value\=800 USDTInitial Margin Ratio\\text{Impact Notional Value} = \\frac{800\\,\\text{USDT}}{\\text{Initial Margin Ratio}}Impact Notional Value\=Initial Margin Ratio800USDT​ The hourly Premium Index is the average of all premium indices calculated within the hour. [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#hourly-funding-fee-rate-fr) **Hourly Funding Fee Rate (FR)** ------------------------------------------------------------------------------------------------------------------------------------------------------ **IF** then: Funding Fee Rate\=Hourly Interest Rate\\text{Funding Fee Rate} = \\text{Hourly Interest Rate}Funding Fee Rate\=Hourly Interest Rate Otherwise: Funding Fee Rate\=Hourly Interest Rate+Premium Index\\text{Funding Fee Rate} = \\text{Hourly Interest Rate} + \\text{Premium Index}Funding Fee Rate\=Hourly Interest Rate+Premium Index [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#funding-rate-cap) **Funding Rate Cap** -------------------------------------------------------------------------------------------------------------------------------- The absolute value of the funding rate is bounded by: ∣FR∣≤0.75%|FR| \\leq 0.75\\%∣FR∣≤0.75% [PreviousPerpetual Trading](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading) [NextMargin](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin) Last updated 9 months ago * [Perpetual Contract Pricing Mechanism](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#perpetual-contract-pricing-mechanism) * [Funding Rates](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#funding-rates) * [Hourly Funding Fee Rate (FR)](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#hourly-funding-fee-rate-fr) * [Funding Rate Cap](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding#funding-rate-cap) --- # Index and Mark Price | Astros [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#index-price) Index Price ------------------------------------------------------------------------------------------------------------------------------- The **Index Price** represents the real-time price of the underlying asset derived from aggregated spot market prices. Astros calculates this price every second by combining market data from multiple exchanges alongside the **Pyth Network oracle**. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#aggregation-sources) Aggregation Sources: * Exchanges: **Coinbase**, **Binance**, **OKX** * Oracle Protocol: **Pyth Network** **Note:** For BTC-denominated trading pairs, the price is converted to USD using the OKX BTC-USD index. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#index-price-validation-and-adjustment) Index Price Validation and Adjustment: To maintain price accuracy and stability, Astros applies two safeguards: * **Exchange Data Validity:** Prices from exchanges that have outdated trade data (no recent trades or insufficient trading volume within a predefined period) are excluded from calculations. * **Price Deviation Adjustment:** If an exchange's reported price deviates by more than **±3%** from the median price of all exchanges, the outlier price is adjusted as follows: * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#mark-price) Mark Price Astros adopts a **Mark Price** mechanism (Fair Price Marking) to mitigate liquidation risk due to temporary market manipulation, volatility, or illiquidity. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#calculation-formula) Calculation Formula: Mark Price\=Index Price+30-Minute Moving Average (Premium)\\text{Mark Price} = \\text{Index Price} + \\text{30-Minute Moving Average (Premium)}Mark Price\=Index Price+30-Minute Moving Average (Premium) Where the **30-Minute Moving Average (Premium)** is computed as: 30-Minute Moving Average\=Moving Average\[(Bid Price+Ask Price)2−Index Price\]\\text{30-Minute Moving Average} = \\text{Moving Average}\\left\[ \\frac{(\\text{Bid Price} + \\text{Ask Price})}{2} - \\text{Index Price} \\right\]30-Minute Moving Average\=Moving Average\[2(Bid Price+Ask Price)​−Index Price\] This moving average is continuously sampled every second over a rolling 30-minute window. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#unrealized-profit-and-loss-pnl-clarification) Unrealized Profit and Loss (PnL) Clarification After executing a trade, traders may observe positive or negative unrealized profits and losses (PnL) caused by temporary differences between the executed trade price and the Mark Price. * **Important**: Unrealized PnL fluctuations do **not** represent actual realized gains or losses unless the position is closed or liquidated. * It is crucial to monitor your **liquidation price** closely to avoid unintended liquidation due to short-term price discrepancies. [PreviousMargin](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/margin) [NextLiquidation Process](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process) Last updated 9 months ago * [Index Price](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#index-price) * [Mark Price](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#mark-price) * [Unrealized Profit and Loss (PnL) Clarification](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#unrealized-profit-and-loss-pnl-clarification) --- # Audit | Astros The Astros Perpetual Deposit Contract has been audited by Movebit. The latest audit reports below are as of February 2025. 311KB [20250311-Navi-Perp-Vault-Final-Audit-Report.pdf](https://3166231846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEagmjVMVJsuZQ0TvRYt7%2Fuploads%2Fg2IKp2ER5qhU3uX1Nr85%2F20250311-Navi-Perp-Vault-Final-Audit-Report.pdf?alt=media&token=34b676be-3da6-4be3-bce5-7a31bd214d5f) PDF Download[Open](https://3166231846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEagmjVMVJsuZQ0TvRYt7%2Fuploads%2Fg2IKp2ER5qhU3uX1Nr85%2F20250311-Navi-Perp-Vault-Final-Audit-Report.pdf?alt=media&token=34b676be-3da6-4be3-bce5-7a31bd214d5f) [PreviousAstros Vault FAQ Page 1](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1/astros-vault-faq-page-1) [NextContact Us](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations) Last updated 1 month ago --- # ADL | Astros Astros employs an **Automatic Deleveraging (ADL)** system to manage scenarios where the **Insurance Fund** lacks sufficient assets to cover liquidation losses. In such cases, the ADL mechanism automatically reduces the positions of traders holding opposite market positions to restore balance and protect market stability. [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#adl-priority-ranking) ADL Priority Ranking -------------------------------------------------------------------------------------------------------------------------------- The ADL system prioritizes trader positions for deleveraging based on two primary factors: * **Profitability** of the position * **Effective leverage** utilized Positions with **higher profitability** and **greater leverage** are prioritized and thus more susceptible to automatic position reduction. * * * [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#calculation-of-adl-ranking) Calculation of ADL Ranking -------------------------------------------------------------------------------------------------------------------------------------------- The ADL priority ranking is calculated using the following formulas and definitions: #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#effective-leverage) **Effective Leverage**: Effective Leverage\=Mark ValueMark Value−Bankruptcy Value\\text{Effective Leverage} = \\frac{\\text{Mark Value}}{\\text{Mark Value} - \\text{Bankruptcy Value}}Effective Leverage\=Mark Value−Bankruptcy ValueMark Value​ #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#percentage-profit-profit) **Percentage Profit** (% Profit): Profit\=Mark Value−Average Opening ValueAverage Opening Value×100%\\text{Profit} = \\frac{\\text{Mark Value} - \\text{Average Opening Value}}{\\text{Average Opening Value}} \\times 100\\%Profit\=Average Opening ValueMark Value−Average Opening Value​×100% Where: * **Mark Value**: The current value of the position calculated at the **Mark Price**. * **Bankruptcy Value**: The theoretical position value calculated at the **Bankruptcy Price**. * **Average Opening Value**: The position's value calculated using the **Average Entry Price**. * * * ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#importance-of-adl) Importance of ADL This structured ADL mechanism ensures: * Fairness in liquidation scenarios by targeting positions with higher risk profiles first. * Transparency through clear visual indicators and predictable calculations. * Market stability by promptly addressing deficit situations. Traders should regularly monitor their **ADL Ranking** indicator to proactively manage their positions and minimize risk exposure. Astros [PreviousInsurance Funds](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/insurance-funds) [NextTrading Fees](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees) Last updated 9 months ago * [ADL Priority Ranking](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#adl-priority-ranking) * [Calculation of ADL Ranking](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#calculation-of-adl-ranking) * [Importance of ADL](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl#importance-of-adl) --- # FAQ | Navi Protocol - docs Why was Navi Protocol created?[](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/faq#why-was-navi-protocol-created) Navi Protocol was created to build delightful user experiences on the fledgling Sui DeFi ecosystem and take advantage of the desirable features of the Move VM. Who is behind Navi Protocol?[](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/faq#who-is-behind-navi-protocol) The team behind Navi Protocol is a seasoned team of founders and builders from the blockchain development space with many collective years of experience building and running protocols across DeFi and Web3 infrastructure. What are the risks associated with Navi Protocol?[](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/faq#what-are-the-risks-associated-with-navi-protocol) The Navi team takes security very seriously and no code will be deployed without extensive reviews, testing, and audits. However there are risks inherent to participating in any Web3 DeFi platform, including: * Smart contract risk due to unforeseen bugs that are not caught by our stringent security policies. * Oracle risk due to oracle manipulation. * Blockchain risk. If the underlying blockchain is somehow compromised, Navi Protocol cannot protect user funds. Navi Protocol is to be treated as a Beta product as with any DeFi platform, so do not invest more than you are willing to lose! [PreviousNAVX Tokenomics](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navx-tokenomics) [NextNAVI Media Kit (logos)](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navi-media-kit-logos) Last updated 9 months ago --- # Trading Fees | Astros #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#id-1.-maker-orders) 1\. **Maker Orders** * Fee Rate: **0.02%** #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#id-2.-taker-orders) 2\. **Taker Orders** * Fee Rate: **0.04%** ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#fee-calculation-formula) Fee Calculation Formula Trading fees are calculated as follows: Trading Fee\=Position Value×Fee Rate\\text{Trading Fee} = \\text{Position Value} \\times \\text{Fee Rate}Trading Fee\=Position Value×Fee Rate ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#example-scenario) Example Scenario Consider a trader with the following parameters: * **Initial Capital**: 600 USD * **Leverage**: 100x * **Position Value**: The corresponding fee calculation would be: * **Opening Position** _(Taker Order)_: 60,000 USD×0.04%\=24 USD60,000 \\text{ USD} \\times 0.04\\% = 24 \\text{ USD}60,000 USD×0.04%\=24 USD * **Closing Position** _(Taker Order - Market)_: 60,000 USD×0.04%\=24 USD60,000 \\text{ USD} \\times 0.04\\% = 24 \\text{ USD}60,000 USD×0.04%\=24 USD * **Closing Position** _(Maker Order - Limit)_: 60,000 USD×0.02%\=12 USD60,000 \\text{ USD} \\times 0.02\\% = 12 \\text{ USD}60,000 USD×0.02%\=12 USD [PreviousADL](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl) [NextReferral](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral) Last updated 9 months ago * [Fee Calculation Formula](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#fee-calculation-formula) * [Example Scenario](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/trading-fees#example-scenario) --- # Points | Astros Astros uses a multi-dimensional points system to measure and reward user activity across trading performance, platform engagement, and ecosystem contribution. Your total points are calculated as the sum of six different point categories, each reflecting a distinct type of on-chain or platform behavior. The points system is designed to balance trading activity, performance quality, and ecosystem participation, rather than rewarding volume alone. Overview of Point Categories Astros points consist of the following six components: [Trading Volume Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/trading-volume-points) [Social Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/social-points) [Referral Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/referral-points) [Open Interest (OI) Points (Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/open-interest-oi-points-coming-soon) [PnL Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon) [Liquidation Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/liquidation-points-coming-soon) Each category has its own calculation logic and settlement frequency, which are outlined below. [PreviousReferral](https://naviprotocol.gitbook.io/astros/astros-perpetual/referral) [NextTrading Volume Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/trading-volume-points) Last updated 11 days ago --- # Trading Volume Points | Astros Key characteristics: * A minimum daily trading volume of 2,000 USDC is required to earn Trading Volume Points * Only executed trades are counted toward trading volume * Base Points are directly linked to a user’s executed trading volume * The Ranking Coefficient is derived from PnL-based ranking across all Perp traders. Higher-ranked users receive a higher ranking coefficient * Tier Boost Points are determined by a user’s daily trading volume tier. Higher trading volume results in a higher tier, which provides additional boost points [PreviousPoints](https://naviprotocol.gitbook.io/astros/astros-perpetual/points) [NextSocial Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/social-points) Last updated 10 days ago --- # Astros Vault FAQ Page 1 | Astros This FAQ is designed to help users better understand how Astros Vaults work, including deposits, rewards, lock-up periods, and redemption. 1. What is Astros Vaults? Astros Vaults is a limited-time yield campaign that allows users to deposit USDC into a Vault strategy and earn rewards in the form of USDC yield and Vault Points. 2. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1/astros-vault-faq-page-1#is-the-100-apy-guaranteed) Is the 100% APY guaranteed? #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1/astros-vault-faq-page-1#no) No. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1/astros-vault-faq-page-1#id-100-apy-is-a-baseline-target-not-a-guaranteed-return-or-hard-cap) 100% APY is a baseline target, not a guaranteed return or hard cap. * The Base Yield component has a minimum target, but actual returns depend on Vault performance * Total APY may be higher than 100% * Final rewards are calculated during the Locked Period 1. Can the APY be higher than 100%? Yes. * If the Base Yield exceeds its minimum target, the overall APY may exceed 100% * Vault Points are adjusted to reflect the final APY structure 1. When can I deposit funds? You can deposit USDC only during the Deposit Period. * Deposits are open for 7 days * Deposits are not accepted once the Earning Period begins 1. Can I withdraw or add funds during the Earning Period? **No.** * Deposits and withdrawals are paused during the Earning Period * Funds remain locked while the Vault strategy is running 1. What happens during the Locked Period? The Locked Period is used to: * Finalize Base Yield (USDC) * Calculate Vault Points * Prepare rewards for distribution **Funds cannot be withdrawn during this stage.** 1. When can I withdraw my funds? You may initiate Unstake starting from the Unstake Period. Once Unstake is initiated: * Principal * USDC Base Yield * Vault Points will be distributed automatically on T+7. 1. What does T+7 mean? T+7 means that your assets will be credited within 7 days after you initiate Unstake. No additional actions are required during this time. 2. What are Vault Points used for? Vault Points represent long-term ecosystem rewards and may be used for: * Token airdrops after TGE * Redemption on future Points exchange pages Final usage rules will be announced separately. 3. How are Vault Points calculated? Vault Points distribution rules are TBC. * Final calculations will be anchored to token FDV * Points will be used to derive token allocations consistent with the Vault’s APY structure 4. Is there a minimum or maximum deposit amount? Yes. * Minimum deposit: 5 USDC per address * Maximum deposit: 1,000,000 USDC per address * Total Vault cap: 5,000,000 USDC 5. What assets are supported? * Phase 1 supported asset: USDC * Additional stablecoins may be supported in future phases 6. Can I participate multiple times? During the Deposit Period, each address may deposit and withdraw multiple times. However, once the 7-day deposit period ends and the Vault enters the Earning Period, no additional deposits will be accepted. All participation is subject to: * Per-address deposit limits * Total Vault capacity Future Vault phases may allow additional participation. 7. What happens if there are no rewards? Astros Vaults is designed to distribute rewards based on Vault performance and allocation. However, rewards are not guaranteed and may vary by phase. 8. Is Astros Vaults a permanent product? No. Astros Vaults is a campaign-based Vault. Each phase may have different rules, durations, and reward structures. 9. Are there risks involved? Yes. * Vaults involve lock-up periods * Returns depend on Vault performance Users should evaluate their own risk tolerance before depositing [PreviousAstros Vault Campaign – Phase1](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1) [NextAudit](https://naviprotocol.gitbook.io/astros/astros-perpetual/audit) Last updated 10 days ago --- # Social Points | Astros Key characteristics: * Users can earn Social Points by sharing an official Astros Social Card on Twitter * Social Points = Fixed Points × (1 + PnL Ranking Coefficient) * Only one social task can be completed per day [PreviousTrading Volume Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/trading-volume-points) [NextReferral Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/referral-points) Last updated 10 days ago --- # Astros Vault Campaign – Phase1 | Astros For phase 1, Astros Vaults offers a target APY of 100% or higher, composed of: * Vault Points (target: 95%) * Base Yield in USDC (minimum: 5%) Actual returns may exceed the baseline target depending on Vault performance. Vault Overview * Campaign Type: Limited-time Vault * Total Duration: 6 weeks * Strategy: Stable USDC deposit * Target APY: ≥ 100% (Points + Yield) The Vault lifecycle consists of four stages: 1. Deposit 2. Earning 3. Locked (Reward Calculation) ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#timeline) Timeline 1. Deposit Period Dec 16, 8:00 AM – Dec 22, 23:59 PM PST Users can freely deposit USDC during this period. 2. Earning Period Dec 22, 23:59 PM – Jan 22, 23:59 PM PST Deposits and withdrawals are paused during this period. 3. Locked Period Jan 22, 23:59 PM – Jan 25, 23:59 PM PST Principal withdrawals are not allowed during this stage. 4. Unstake Period From Jan 25, 23:59 PM PST All assets will be transferred to the user’s wallet on T+7 after unstaking. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#pool-rules) Pool Rules * Pool Cap: 5,000,000 USDC * Minimum Deposit per Address: 5 USDC * Maximum Deposit per Address: 1,000,000 USDC * Supported Asset (Phase 1): USDC * Additional stablecoins may be supported in future phases ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#rewards-structure) Rewards Structure All deposited assets participate in a reward structure estimate 100% APY, composed of two components. Base Yield — USDC Yield * Base Yield paid in USDC * Actual Base Yield may be around 5%, depending on: * Vault performance * Reward allocation for the phase * Calculated based on deposited principal * Finalized and distributed after the Locked Period Base Yield represents the stable return component of the Vault and may vary across phases. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#vault-points) Vault Points Vault Points represent the remaining portion of the Vault’s APY target and provide long-term ecosystem rewards. Vault Points may be used for: * Token airdrops after TGE * Redemption on future Points exchange pages Vault Points will only be calculated and displayed after the earning period ends. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#apy-clarification) APY Clarification * 100% APY is a baseline target, not a hard cap * Total APY may be higher than 100% if Base Yield exceeds the minimum target * Final rewards are calculated during the Locked Period 100% APY is the baseline — actual returns may be higher. ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#rewards-distribution) Rewards Distribution * All Base Yield and Vault Points are finalized during the 3-day Locked Period * Users may initiate Unstake once the Unstake Period begins * After Unstake, principal + USDC yield + Vault Points will be credited automatically on T+7 ### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#notes) Notes * Astros Vaults is a limited-time campaign, not a permanent product * Reward structures may vary across future Vault phases * Please ensure you understand the full lock-up timeline before depositing [PreviousSettlement & Update Frequency Summary](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/settlement-and-update-frequency-summary) [NextAstros Vault FAQ Page 1](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1/astros-vault-faq-page-1) Last updated 11 days ago * [Timeline](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#timeline) * [Pool Rules](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#pool-rules) * [Rewards Structure](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#rewards-structure) * [Vault Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#vault-points) * [APY Clarification](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#apy-clarification) * [Rewards Distribution](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#rewards-distribution) * [Notes](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1#notes) --- # Open Interest (OI) Points (Coming Soon) | Astros Key characteristics: * Points are linked to open position size and holding duration * Daily OI Points are calculated based on the aggregate of all positions opened during the day * Larger position size and longer position holding time generally leads to higher OI contribution Anti-Farming Mechanisms for OI Points To ensure the integrity and fairness of the Open Interest (OI) Points system, Astros applies a set of anti-farming rules designed to discourage short-term, low-quality position manipulation. These rules are implemented through a combination of on-chain enforcement and off-chain monitoring, and may be adjusted over time as the system evolves. **Minimum Effective Position Size** * Only positions with a notional value of at least 10 USDC are considered valid for OI Points * Positions below this threshold do not generate OI Points **Minimum Holding Duration** * Positions must be held for a minimum of 3 minutes to be eligible for OI Points Positions closed before this duration do not generate OI Points **Per-Wallet Frequency Limit** * Each wallet is limited to a maximum of 10 effective position openings per hour * Any additional openings beyond this limit may be temporarily excluded from OI Point calculations **Liquidation Penalty** * If a position is liquidated, the OI Points associated with that position are penalized * Liquidated positions may receive: * A reduced OI score (e.g. a partial multiplier), or Partial invalidation of the corresponding OI Points [PreviousReferral Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/referral-points) [NextPnL Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon) Last updated 10 days ago --- # Referral Points | Astros This category consists of two components: #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/referral-points#one-time-referral-milestones) One-Time Referral Milestones Users can earn one-time bonus points by completing referral invitation milestones. * Each milestone can only be triggered once * Only qualified invited users (trading volume≥ $2000) are counted * The maximum total points obtainable from one-time referral tasks is 31 points The referral milestone structure is publicly disclosed to ensure transparency and clarity. Number of Qualified Invited Users One-Time Referral Points 3 +3 points 10 +5 points 30 +8 points 50 +15 points #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/referral-points#ongoing-referral-rewards) Ongoing Referral Rewards * Inviting users receive a percentage-based share of the daily points earned by all invited users * Ongoing referral points are calculated and settled daily [PreviousSocial Points](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/social-points) [NextOpen Interest (OI) Points (Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/open-interest-oi-points-coming-soon) Last updated 10 days ago --- # PnL Points(Coming Soon) | Astros This means that both profitable and unprofitable traders can earn PnL Points through continuous and active trading. PnL Points are calculated in two steps: hourly scoring and daily aggregation. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon#raw-pnl-score-hourly) Raw PnL Score (Hourly) A Raw PnL Score is calculated once every hour. The hourly Raw PnL Score is positively correlated with: * Absolute realized PnL for the hour * Based on realized PnL only * Funding fees are excluded * PnL Ranking Factor * Derived from the user’s PnL ranking among all Perp traders * Higher rankings result in a higher factor Raw PnL Score (Hourly) increases as either realized PnL magnitude or PnL ranking improves. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon#daily-aggregation) Daily Aggregation * Hourly Raw PnL Scores are summed across all hours within the same day * This produces the user’s Raw PnL Score (Daily) Raw PnL Score (Daily) = Σ Raw PnL Score (Hourly) #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon#final-daily-pnl-points) Final Daily PnL Points * PnL Points (Daily) = Raw PnL Score (Daily) [PreviousOpen Interest (OI) Points (Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/open-interest-oi-points-coming-soon) [NextLiquidation Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/liquidation-points-coming-soon) Last updated 11 days ago --- # Contact Us | Astros ![](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2F3166231846-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FEagmjVMVJsuZQ0TvRYt7%252Fuploads%252Fjm8ZBa1thLnqrZ0UZu7l%252Fimage.png%3Falt%3Dmedia%26token%3Db8da5f4e-d834-454d-9ee0-166a7c0d9500&width=768&dpr=4&quality=100&sign=7e26c452&sv=2) We're here to help! Whether you have questions about the Astros Aggregator, need technical support, or want to explore partnership opportunities, our team is ready to assist you. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#main) Main **Official Website:** [https://astros.ag/](https://astros.ag/) **Twitter (X):** [https://x.com/astros\_ag](https://x.com/astros_ag) **Discord Channel**: [https://discord.com/invite/R6Xkbee8Xq](https://discord.com/invite/R6Xkbee8Xq) **Telegram Channel:** [https://t.me/navi\_protocol](https://t.me/navi_protocol) ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#partnerships-coo-carl-carl-naviprotocol.io) Partnerships COO - Carl: [carl@naviprotocol.io](mailto:_carl@naviprotocol_) [![Logo](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Ftelegram.org%2Fimg%2Fapple-touch-icon.png&width=20&dpr=4&quality=100&sign=6e739424&sv=2)CarlTelegram](https://t.me/carlboi_eth) ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#integration-specialist-xiaodi-xiaodi-naviprotocol) Integration Specialist - Xiaodi: [_xiaodi@naviprotocol_](mailto:_xiaodi@naviprotocol_) [![Logo](https://naviprotocol.gitbook.io/astros/~gitbook/image?url=https%3A%2F%2Ftelegram.org%2Fimg%2Fapple-touch-icon.png&width=20&dpr=4&quality=100&sign=6e739424&sv=2)xiaodiTelegram](https://t.me/xiaodi008) [PreviousAudit](https://naviprotocol.gitbook.io/astros/astros-perpetual/audit) [NextTerms of Service](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service) Last updated 5 months ago * [Main](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#main) * [Partnerships COO - Carl: carl@naviprotocol.io](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#partnerships-coo-carl-carl-naviprotocol.io) * [Integration Specialist - Xiaodi: xiaodi@naviprotocol](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations#integration-specialist-xiaodi-xiaodi-naviprotocol) --- # Lending & Borrowing | Navi Protocol - docs [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#token-parameters) Token Parameters --------------------------------------------------------------------------------------------------------------------------------------- Asset Collateral/ Borrowable LTV Supply Cap Borrow Cap Ceiling SUI Yes/Yes 75% 55,000,000 80% USDT Yes/Yes 80% 10,000,000 90% Wormhole USDC Yes/Yes 80% 10,000,000 90% WETH Yes/Yes 75% 2,000 90% Cetus Yes/Yes 50% 12,000,00 60% vSUI Yes/Yes 75% 15,000,000 85% haSUI Yes/Yes 75% 40,000,000 80% NAVX Yes/Yes 45% 200,000,000 12% WBTC Yes/Yes 40% 30 70% AUSD Yes/Yes 80% 2,500,000 90% USDC Yes/Yes 80% 120,000,000 96% FDUSD Yes/Yes 70% 2,000,000 90% USDY Yes/Yes 70% 10,000,000 90% suiETH Yes/Yes 75% 8,500 90% NS Yes/Yes 47% 45,000,000 60% stBTC Yes/Yes 50% 10 50% BLUE Yes/Yes 40% 7,000,000 60% BUCK Yes/Yes 70% 25,000,000 85% suiUSDT Yes/Yes 80% 30,000,000 96% DEEP Yes/Yes 47% 350,000,000 70% stSUI Yes/Yes 70% 500,000 30% LBTC Yes/Yes 60% 750 70% suiBTC Yes/Yes 60% 650 20% WAL Yes/Yes 60% 120,000,000 50% SOL Yes/Yes 60% 10,000 60% HAEDAL Yes/Yes 50% 30,000,000 50% XBTC Yes/Yes 67% 600 70% IKA Yes/Yes 30% 200,000,000 60% EnzoBTC Yes/No 50% 550 0% MBTC Yes/No 55% 300 0% YBTC.B Yes/No 40% 70 0% XAUM Yes/Yes 50% 1,000 80% WBTC(Layer0) Yes/Yes 55% 100 60% ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#token-contract-address) Token Contract Address Asset Id: 0 SUI: 0x2::sui::SUI 1. USD Coin (Portal from Ethereum): 0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf:coin:COIN 2. USDT (Portal from Ethereum): 0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c:coin:COIN 3. WETH 0xaf8cd5edc19c4512f4259f0bee101a40d41ebed738ade5874359610ef8eeced5::coin::COIN 4. CETUS 0x06864a6f921804860930db6ddbe2e16acdf8504495ea7481637a1c8b9a8fe54b::cetus::CETUS 5. voloSUI 0x549e8b69270defbfafd4f94e17ec44cdbdd99820b33bda2278dea3b9a32d3f55::cert::CERT 6. haSUI 0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI 7. NAVX 0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX 8. WBTC 0x027792d9fed7f9844eb4839566001bb6f6cb4804f66aa2da6fe1ee242d896881:coin:COIN 9. AUSD 0x2053d08c1e2bd02791056171aab0fd12bd7cd7efad2ab8f6b9c8902f14df2ff2::ausd::AUSD 10. USDC 0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC 11. suiETH 0xd0e89b2af5e4910726fbcd8b8dd37bb79b29e5f83f7491bca830e94f7f226d29::eth::ETH 12. USDY 0x960b531667636f39e85867775f52f6b1f220a058c4de786905bdf761e06a56bb::usdy::USDY 13. NS 0x5145494a5f5100e645e4b0aa950fa6b68f614e8c59e17bc5ded3495123a79178::ns::NS 14. stBTC 0x5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6:coin:COIN 15. DEEP 0xdeeb7a4662eec9f2f3def03fb937a663dddaa2e215b8078a284d026b7946c270::deep::DEEP 16. FDUSD 0xf16e6b723f242ec745dfd7634ad072c42d5c1d9ac9d62a39c381303eaa57693a::fdusd::FDUSD 17. BLUE 0xe1b45a0e641b9955a20aa0ad1c1f4ad86aad8afb07296d4085e349a50e90bdca::blue::BLUE 18. BUCK 0xce7ff77a83ea0cb6fd39bd8748e2ec89a3f41e8efdc3f4eb123e0ca37b184db2::buck::BUCK 19. suiUSDT 0x375f70cf2ae4c00bf37117d0c85a2c71545e6ee05c4a5c7d282cd66a4504b068::usdt::USDT 20. stSUI 0xd1b72982e40348d069bb1ff701e634c117bb5f741f44dff91e472d3b01461e55::stsui::STSUI 21. suiBTC 0xaafb102dd0902f5055cadecd687fb5b71ca82ef0e0285d90afde828ec58ca96b::btc::BTC 22. SOL 0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8:coin:COIN 23. LBTC 0x3e8e9423d80e1774a7ca128fccd8bf5f1f7753be658c5e645929037f7c819040::lbtc::LBTC 24. WAL 0x356a26eb9e012a68958082340d4c4116e7f55615cf27affcff209cf0ae544f59::wal::WAL 25. HAEDAL 0x3a304c7feba2d819ea57c3542d68439ca2c386ba02159c740f7b406e592c62ea::haedal::HAEDAL 26. XBTC 0x876a4b7bce8aeaef60464c11f4026903e9afacab79b9b142686158aa86560b50::xbtc::XBTC 27. IKA 0x7262fb2f7a3a14c888c438a3cd9b912469a58cf60f367352c46584262e8299aa::ika::IKA 28. EnzoBTC 0x8f2b5eb696ed88b71fea398d330bccfa52f6e2a5a8e1ac6180fcb25c6de42ebc::coin:COIN 29. MBTC 0xd1a91b46bd6d966b62686263609074ad16cfdffc63c31a4775870a2d54d20c6b::mbtc::MBTC 30. YBTC.B 0xa03ab7eee2c8e97111977b77374eaf6324ba617e7027382228350db08469189e::ybtc::YBTC 31. XAUM 0x9d297676e7a4b771ab023291377b2adfaa4938fb9080b8d12430e4b108b836a9::xaum::XAUM 32. WBTC 0x0041f9f9344cac094454cd574e333c4fdb132d7bcc9379bcd4aab485b2a63942::wbtc::WBTC [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#borrow-apy) Borrow APY --------------------------------------------------------------------------------------------------------------------------- Asset Optimal Utilization Base Interest Multiplier Jump\_multiplier SUI 70% 0% 15% 300% USDT 85% 5% 9% 500% Wormhole USDC 85% 5% 9% 500% WETH 75% 0% 5.33% 320% Cetus 50% 0% 40% 320% vSUI 75% 0% 13.33% 320% haSUI 70% 0% 15% 320% NAVX 10% 0% 80% 1000% WBTC 50% 0% 8% 600% AUSD 80% 5% 10% 550% USDC 90% 4.5% 8% 450% FDUSD 85% 5% 9% 500% USDY 85% 5% 9% 500% suiETH 75% 0% 8% 320% NS 50% 10% 40% 300% stBTC 50% 0% 8% 600% BLUE 30% 0% 60% 800% BUCK 80% 5% 10% 550% suiUSDT 90% 4.5% 8% 450% DEEP 70% 10% 68% 1000% stSUI 75% 0% 13.33% 320% LBTC 50% 0% 8% 600% suiBTC 80% 0% 2% 600% WAL 70% 20% 54.3% 600% SOL 80% 6% 23.75% 1475% HAEDAL 20% 30% 80% 350% XBTC 80% 0% 2% 400% IKA 30% 10% 140% 1200% EnzoBTC 50% 0% 8% 600% MBTC 50% 0% 8% 600% YBTC.B 50% 0% 8% 600% XAUM 60% 8% 20% 600% WBTC(Layer0) 80% 0% 0.63% 600% [](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#risk-parameters) Risk parameters ------------------------------------------------------------------------------------------------------------------------------------- Asset Liq. Threshold Liquidation Bonus Reserve Factor SUI 80% 10% 20% USDT 75% 5% 20% Wormhole USDC 85% 8% 30% WETH 80% 10% 20% Cetus 55% 10% 30% vSUI 80% 10% 20% haSUI 80% 10% 20% NAVX 55% 5% 20% WBTC 45% 10% 20% AUSD 85% 10% 30% USDC 85% 8% 20% FDUSD 75% 10% 25% USDY 75% 8% 25% suiETH 80% 10% 20% NS 50% 10% 30% stBTC 60% 10% 98% BLUE 45% 10% 30% BUCK 75% 10% 30% suiUSDT 85% 8% 20% DEEP 50% 10% 30% stSUI 75% 10% 20% LBTC 65% 10% 30% suiBTC 65% 10% 30% WAL 65% 10% 30% SOL 65% 10% 30% HAEDAL 55% 10% 30% XBTC 70% 10% 30% IKA 35% 10% 50% EnzoBTC 60% 10% 30% MBTC 65% 10% 30% YBTC.B 45% 10% 30% XAUM 60% 10% 30% WBTC(Layer0) 65% 15% 50% **Plateform Fees Structure:** * 10% of liquidation incentives When a user has reached its liquidation threshold, **up to 35%** (in terms of market value) of the total supply asset is sold to the liquidator at a discounted price to repay a portion of the loan. [PreviousSupported Assets](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/supported-assets) [NextGlossary](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/glossary) Last updated 29 days ago * [Token Parameters](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#token-parameters) * [Token Contract Address](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#token-contract-address) * [Borrow APY](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#borrow-apy) * [Risk parameters](https://naviprotocol.gitbook.io/navi-protocol-docs/protocol-parameters/lending-and-borrowing#risk-parameters) --- # Privacy Policy | Navi Protocol - docs This Privacy Policy describes how Navi Protocol Labs, Inc. (“NAVI,” “we,” “our,” or “us”) may collect, use, and disclose personal information about you. This Privacy Policy applies to information collected when you interact with the products, services, technology, features, and software (collectively, the “Services”) we make available to you via our electronic platforms and applications (the “Platform”). Please read this Privacy Policy carefully so that you understand our policies and practices regarding your information. If you do not agree with our policies and practices then your choice is not to interact with the Services. By accessing or using the Services you agree to this Privacy Policy. We encourage you to check this Privacy Policy often so you stay informed about our practices and the choices available to you. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-1.-information-we-collect) **1\. Information We Collect** Depending on how you interact with the Services, we may collect information about you like: * Information You Directly Provide. You provide us with information directly when, for instance, you communicate with our customer support via support tickets. * Information Collected Automatically. We automatically collect information about you when you interact with certain content that we make available on the Platform or you connect your digital asset wallet to the Platform. * Information from Third Parties. We may also collect information about you from third parties. For example, we may collect information from risk-related service providers that help us verify your identify and detect potential misuse of the Services; or from public blockchain data and wallet addresses. In connection with using or accessing the Services, we may collect the following categories of information. * Communication Information. Information like communications with our customer support, responses to our surveys, and information submitted in connection with your registration for our events. * Transaction Data. Data like the sending or receiving blockchain address, transaction IDs, transaction amount, type, and other details of any transactions you enter into using the Services or the Platform. * Device Data. Device type and other data about your device like its software and hardware details, browser type and version, and operating system; IP address (internet address of your computer);location information; and mobile device ID. * Third Party Connections and Integrations. If you access the Services through a third party connection, you may allow us to have access to certain information from such third party. Please see the privacy policies and terms for these third parties for more information. * Other Information. Any other information that you choose to provide or that we request. We may aggregate or de-identify information so that the information can no longer identify you, as defined under applicable laws. We may use and/or disclose aggregated or de-identified information for any purpose unless an applicable law says otherwise. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-2.-how-we-use-your-information) **2\. How We Use Your Information** We may use the information we collect in connection with what we consider our Everyday Business Activities including using your information to: * Operate and Provide the Services. We may use the information we collect to provide and operate the Services like contacting you about technical notices or security alerts. * Monitor and Improve the Services. We may use the information we collect to analyze the effectiveness of the Services, review the Services, and improve the Services. * Conduct Research. We may use information you share with us or that we collect to conduct research, product testing, and troubleshooting to help us operate and improve the Services. * Communicate with you about the Services. We may use information we collect about you to communicate with you about the Services like offers, promotions, and providing other news and information that we think will be of interest to you. * Facilitate a Corporate Transaction. We may use information we collect during negotiations or in connection with the sale of part or all of our assets, the acquisition of part or all of another business or the businesses’ assets, or other transaction including but not limited to financing or bankruptcy. * Foster Safety and Security. We use the information we collect to provide for the safety and security of our users and the Services. This may include detecting and preventing against malicious, deceptive, fraudulent, or illegal activities; improving our security; exercising our legal rights; in compliance with any applicable law; and as permitted by law. * Other Expected Purposes. In connection with any purpose expressly described at the time of collection or any purpose that is reasonably expected based on the context or in light of a term in our agreements with you. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-3.-sharing-information) **3\. Sharing Information** You should know the ways that we share your information and why we share your information. In connection with our Everyday Business Activities, we may share information collected from or about you in the below circumstances. * Service Providers. We may share your information with services providers that perform functions or provide services on our behalf such as our business, professional, or technical support providers that help us with our business and the Services and/or administer activities in connection with the Services and our business. * Comply with Laws and Protect our Rights. We may share your information as we believe to be necessary or appropriate to comply with applicable law and legal processes; respond to requests from public and government authorities including authorities outside your country of residence; protect our rights, privacy, safety, or property, and/or that of our affiliates, you, or others; and allow us to pursue available remedies or limit the damages that we may sustain. * Investors and Acquirers. We may transfer your information to advisors, investors, potential transactional partners, or other third parties in connection with the initial actions or engagement of a merger, acquisition, sale of some or all of our stock or assets, change in control, financing, bankruptcy, or similar transaction. * With other Third Parties. There are situations when we may disclose your information to third parties in connection with our Everyday Business Activities and such sharing is in accordance with, or required by, any applicable law or legal process. * With Your Consent or at Your Direction. We may share your information with third parties when you direct us to do so or if you have consented to additional sharing of your information. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-4.-cookies-and-similar-technologies) **4\. Cookies and Similar Technologies** Like most other online services, we use cookies and similar technologies to collect some of the data discussed in this Privacy Policy. These help us provide certain features to you and analyze usage information. The Your Choices section below provides additional information about our use of cookies and similar technologies and your ability to manage cookies. Our use of cookies and similar technologies fall into the following general categories: * Essential. We may use cookies, web beacons, or other similar technologies necessary to provide the Services. This includes technologies that allow you to access our website, services, and applications, or are required to identify irregular site behavior and improve security. * Performance. We may use cookies, web beacons, or other similar technologies to assess the performance of the Services including as part of our analytic practices to help us understand how visitors use our websites; determine if you have interacted with our messaging; determine whether you have viewed an item or link; and/or to improve our website content, applications, or services. * Functionality. We may use cookies, web beacons, or other similar technologies that allow us to offer you enhanced functionality when accessing or using the Services. This may include delivering error messages and enhancing the presentation of content on the Services. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-5.-analytics-and-a-dvertising) **5\.** Analytics and Advertising We may engage others to provide analytics services and serve advertisements across the web and/or in mobile applications. These entities may use cookies and similar technologies to collect information about your use of the Services and your activities across other websites and online services which they may associate with persistent identifiers. These identifiers may be derived from a hashed or encrypted version of personal information such as your email address. Their activities and your choices regarding their use of your information to personalize ads to you are subject to and set out in their policies. We neither have access to, nor does this Privacy Policy govern, the use of cookies or other tacking technologies that may be placed on your computer, mobile phone, or other device by non-affiliated third party providers. As described below in the Your Choices section, these providers may offer you a way to opt-out of the collection of information used for certain advertising to you. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-6.-your-choices) **6\. Your Choices** You have certain choices about how to protect and limit the collection, use, and sharing of information about you including: A. Opt-out of Cookies and Tracking Technologies. You can often adjust your browser setting to remove or reject browser cookies. If you remove or reject cookies, the availability and functionality of the Services may be affected. B. Using Privacy Plug-Ins or Browsers. You can block websites from setting cookies used for interest-based ads by using a browser with privacy features or installing browser plugins and configuring them to block third party cookies or trackers. C. Opt-Out of Marketing Communications. You may opt-out of receiving marketing communication from us by following the instruction in those communications or submitting a request to [discord](https://discord.com/invite/R6Xkbee8Xq) . If you opt-out we may still send you non-promotional emails, such as those about your account or our ongoing business relations. D. Third Party Opt-Outs. You can also use opt-out tools offered by major online advertising industry groups to limit how cookies are used for advertising purposes by participating third parties. More information is available on these sites from the [Network Advertising Initiative](https://optout.networkadvertising.org/) and [Digital Advertising Alliance](https://optout.aboutads.info/) . E. Platform Opt-Outs. The following platform(s) offer opt-out features that let you opt-out of use of your information for interest-based advertising: [https://adssettings.google.com/](https://adssettings.google.com/) . ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-7.-international-transfers) **7\.** International Transfers Your information may be transferred to a country other than the country you are located. We comply with laws on the transfer of personal information between countries to help ensure your information is protected, wherever it may be. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-8.-how-we-protect-your-information) **8\. How We Protect Your Information** We use reasonable procedural, physical, and electronic safeguards to protect your information from unauthorized access or use including encryption at rest and during transit. Our measures are designed to protect against the accidental or unlawful destruction, loss, misuse, alteration, and unauthorized disclosure of, or access to, the information under our control. The safety and security of your information also depends on you, do not share your private cryptographic key with anyone. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-9.-information-storage) **9\. Information Storage** We retain your information for as long as necessary to provide the Services, fulfill our legal obligations, enforce our legal agreements, and resolve disputes. The retention periods for your information are determined on a case-by-case basis depending on the nature of information, why it was collected, and the applicable legal reason for the retention. We may also keep your information when necessary to protect the safety and security of the Services. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-10.-age-restrictions) **10\. Age Restrictions** The Services are not intended for anyone under the age of 18. We do not knowingly collect or solicit personal information from children. In the event that we encounter information from an individual under the age of 18, we will promptly take steps to delete such information. If you believe your child under the age of 18 uploaded information in connection with the Services, please contact us using the information in the Contact Us section below. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-11.-changes-to-this-privacy-policy) **11\. Changes to this Privacy Policy** We are always improving the Services and create new features regularly. These updates sometimes require us to collect new information or use what we already have differently. Further, the laws regarding personal information and privacy frequently change. We will notify you of any changes we make by revising the date at the top of this page. If you object to any change, you can stop using the Services. After we post any changes, your continued use of the Services is subject to the updated Privacy Policy. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-12.-third-party-links-and-features) **12\. Third Party Links and Features** The Services may contain links, banners, and/or widgets to third party sites, applications, or services. We may also incorporate third party software (including open source software) in the Services. These links and features are provided for your reference and convenience only and do not imply any endorsement of information provided through these third party links and features, nor any association with their operators. NAVI is not responsible for the practices of such third parties. Any information you provide to third parties on their sites or services is covered under their privacy and data collection practices and not covered by this Privacy Policy. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-13.-contact-us) **13\. Contact Us** If you have any questions, please contact us via [discord](https://discord.com/invite/R6Xkbee8Xq) or [telegram](https://t.me/navi_protocol) . [PreviousTerms of Service](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service) Last updated 3 months ago * [1\. Information We Collect](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-1.-information-we-collect) * [2\. How We Use Your Information](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-2.-how-we-use-your-information) * [3\. Sharing Information](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-3.-sharing-information) * [4\. Cookies and Similar Technologies](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-4.-cookies-and-similar-technologies) * [5\. Analytics and Advertising](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-5.-analytics-and-a-dvertising) * [6\. Your Choices](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-6.-your-choices) * [7\. International Transfers](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-7.-international-transfers) * [8\. How We Protect Your Information](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-8.-how-we-protect-your-information) * [9\. Information Storage](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-9.-information-storage) * [10\. Age Restrictions](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-10.-age-restrictions) * [11\. Changes to this Privacy Policy](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-11.-changes-to-this-privacy-policy) * [12\. Third Party Links and Features](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-12.-third-party-links-and-features) * [13\. Contact Us](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy#id-13.-contact-us) --- # Settlement & Update Frequency Summary | Astros Point Category Update Frequency Calculation Basis Trading Volume Points Daily Daily trading volume Social Points Daily Task completion Referral Points Daily Invited user activity OI Points Daily All positions opened that day PnL Points Hourly → Daily Hourly realized PnL Liquidation Points Event-based → Daily Largest daily liquidation [PreviousLiquidation Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/liquidation-points-coming-soon) [NextAstros Vault Campaign – Phase1](https://naviprotocol.gitbook.io/astros/astros-perpetual/astros-vault-campaign-phase1) Last updated 10 days ago --- # Privacy Policy | Astros This Privacy Policy describes how Navi Protocol Labs, Inc. (“ASTROS,” “we,” “our,” or “us”) may collect, use, and disclose personal information about you. This Privacy Policy applies to information collected when you interact with the products, services, technology, features, and software (collectively, the “Services”) we make available to you via our electronic platforms and applications (the “Platform”). Please read this Privacy Policy carefully so that you understand our policies and practices regarding your information. If you do not agree with our policies and practices then your choice is not to interact with the Services. By accessing or using the Services you agree to this Privacy Policy. We encourage you to check this Privacy Policy often so you stay informed about our practices and the choices available to you. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-1.-information-we-collect) 1\. Information We Collect Depending on how you interact with the Services, we may collect information about you like: * **Information You Directly Provide**. You provide us with information directly when, for instance, you communicate with our customer support via support tickets. * **Information Collected Automatically**. We automatically collect information about you when you interact with certain content that we make available on the Platform or you connect your digital asset wallet to the Platform. * **Information from Third Parties**. We may also collect information about you from third parties. For example, we may collect information from risk-related service providers that help us verify your identify and detect potential misuse of the Services; or from public blockchain data and wallet addresses. We may also collect information from advertising networks and/or data analytics providers. In connection with using or accessing the Services, we may collect the following categories of information. * **Identity Information**. Information like your full name, email address, usernames, and any other information we may need to collect and/or verify pursuant to our internal policies and regulatory obligations. * **Communication Information**. Information like communications with our customer support, responses to our surveys, and information submitted in connection with your registration for our events. * **Transaction Data.** Data like the sending or receiving blockchain address, transaction IDs, transaction amount, type, and other details of any transactions you enter into using the Services or the Platform. * **Device Data**. Device type and other data about your device like its software and hardware details, browser type and version, and operating system; IP address (internet address of your computer);location information; and mobile device ID. * **Third Party Connections and Integrations**. If you access the Services through a third party connection, you may allow us to have access to certain information from such third party. Please see the privacy policies and terms for these third parties for more information. * **Other Information**. Any other information that you choose to provide or that we request. We may aggregate or de-identify information so that the information can no longer identify you, as defined under applicable laws. We may use and/or disclose aggregated or de-identified information for any purpose unless an applicable law says otherwise. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-2.-how-we-use-your-information) 2\. How We Use Your Information We may use the information we collect in connection with what we consider our Everyday Business Activities including using your information to: * **Operate and Provide the Services**. We may use the information we collect to provide and operate the Services like contacting you about technical notices or security alerts. * **Monitor and Improve the Services**. We may use the information we collect to analyze the effectiveness of the Services, review the Services, and improve the Services. * **Conduct Research**. We may use information you share with us or that we collect to conduct research, product testing, and troubleshooting to help us operate and improve the Services. * **Communicate with you about the Services**. We may use information we collect about you to communicate with you about the Services like offers, promotions, and providing other news and information that we think will be of interest to you. * **Facilitate a Corporate Transaction**. We may use information we collect during negotiations or in connection with the sale of part or all of our assets, the acquisition of part or all of another business or the businesses’ assets, or other transaction including but not limited to financing or bankruptcy. * **Foster Safety and Security**. We use the information we collect to provide for the safety and security of our users and the Services. This may include detecting and preventing against malicious, deceptive, fraudulent, or illegal activities; improving our security; exercising our legal rights; in compliance with any applicable law; and as permitted by law. * **Other Expected Purposes**. In connection with any purpose expressly described at the time of collection or any purpose that is reasonably expected based on the context or in light of a term in our agreements with you. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-3.-sharing-information) 3\. Sharing Information You should know the ways that we share your information and why we share your information. In connection with our **Everyday Business Activities**, we may share information collected from or about you in the below circumstances. * **Service Providers**. We may share your information with services providers that perform functions or provide services on our behalf such as our business, professional, or technical support providers that help us with our business and the Services and/or administer activities in connection with the Services and our business. * **Comply with Laws and Protect our Rights**. We may share your information as we believe to be necessary or appropriate to comply with applicable law and legal processes; respond to requests from public and government authorities including authorities outside your country of residence; protect our rights, privacy, safety, or property, and/or that of our affiliates, you, or others; and allow us to pursue available remedies or limit the damages that we may sustain. * **Investors and Acquirers**. We may transfer your information to advisors, investors, potential transactional partners, or other third parties in connection with the initial actions or engagement of a merger, acquisition, sale of some or all of our stock or assets, change in control, financing, bankruptcy, or similar transaction. * **With other Third Parties**. There are situations when we may disclose your information to third parties in connection with our **Everyday Business Activities** and such sharing is in accordance with, or required by, any applicable law or legal process. * **With Your Consent or at Your Direction**. We may share your information with third parties when you direct us to do so or if you have consented to additional sharing of your information. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-4.-cookies-and-similar-technologies) 4\. Cookies and Similar Technologies Like most other online services, we use cookies and similar technologies to collect some of the data discussed in this Privacy Policy. These help us provide certain features to you and analyze usage information. The **Your Choices** section below provides additional information about our use of cookies and similar technologies and your ability to manage cookies. Our use of cookies and similar technologies fall into the following general categories: * **Essential**. We may use cookies, web beacons, or other similar technologies necessary to provide the Services. This includes technologies that allow you to access our website, services, and applications, or are required to identify irregular site behavior and improve security. * **Performance**. We may use cookies, web beacons, or other similar technologies to assess the performance of the Services including as part of our analytic practices to help us understand how visitors use our websites; determine if you have interacted with our messaging; determine whether you have viewed an item or link; and/or to improve our website content, applications, or services. * **Functionality**. We may use cookies, web beacons, or other similar technologies that allow us to offer you enhanced functionality when accessing or using the Services. This may include delivering error messages and enhancing the presentation of content on the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#analytics_and_advertising) 5\. Analytics and Advertising We may engage others to provide analytics services and serve advertisements across the web and/or in mobile applications. These entities may use cookies and similar technologies to collect information about your use of the Services and your activities across other websites and online services which they may associate with persistent identifiers. These identifiers may be derived from a hashed or encrypted version of personal information such as your email address. Their activities and your choices regarding their use of your information to personalize ads to you are subject to and set out in their policies. We neither have access to, nor does this Privacy Policy govern, the use of cookies or other tacking technologies that may be placed on your computer, mobile phone, or other device by non-affiliated third party providers. As described below in the **Your Choices** section, these providers may offer you a way to opt-out of the collection of information used for certain advertising to you. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-6.-your-choices) 6\. Your Choices You have certain choices about how to protect and limit the collection, use, and sharing of information about you including: 1. **Opt-out of Cookies and Tracking Technologies.** You can often adjust your browser setting to remove or reject browser cookies. If you remove or reject cookies, the availability and functionality of the Services may be affected. 2. **Using Privacy Plug-Ins or Browsers.** You can block websites from setting cookies used for interest-based ads by using a browser with privacy features or installing browser plugins and configuring them to block third party cookies or trackers. 3. **Opt-Out of Marketing Communications**. You may opt-out of receiving marketing communication from us by following the instruction in those communications. If you opt-out we may still send you non-promotional emails, such as those about your account or our ongoing business relations. 4. **Third Party Opt-Outs**. You can also use opt-out tools offered by major online advertising industry groups to limit how cookies are used for advertising purposes by participating third parties. More information is available on these sites from the [Network Advertising Initiative](https://optout.networkadvertising.org/) and [Digital Advertising Alliance](https://optout.aboutads.info/) . 5. **Platform Opt-Outs**. The following platform(s) offer opt-out features that let you opt-out of use of your information for interest-based advertising: [https://adssettings.google.com/](https://adssettings.google.com/) . ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-7.-international-transfers) 7\. International Transfers Your information may be transferred to a country other than the country you are located. We comply with laws on the transfer of personal information between countries to help ensure your information is protected, wherever it may be. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-8.-how-we-protect-your-information) 8\. How We Protect Your Information We use reasonable procedural, physical, and electronic safeguards to protect your information from unauthorized access or use including encryption at rest and during transit. Our measures are designed to protect against the accidental or unlawful destruction, loss, misuse, alteration, and unauthorized disclosure of, or access to, the information under our control. The safety and security of your information also depends on you, do not share your private cryptographic key with anyone. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-9.-information-storage) 9\. Information Storage We retain your information for as long as necessary to provide the Services, fulfill our legal obligations, enforce our legal agreements, and resolve disputes. The retention periods for your information are determined on a case-by-case basis depending on the nature of information, why it was collected, and the applicable legal reason for the retention. We may also keep your information when necessary to protect the safety and security of the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-10.-age-restrictions) 10\. Age Restrictions The Services are not intended for anyone under the age of 18. We do not knowingly collect or solicit personal information from children. In the event that we encounter information from an individual under the age of 18, we will promptly take steps to delete such information. If you believe your child under the age of 18 uploaded information in connection with the Services, please contact us using the information in the Contact Us section below. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-11.-changes-to-this-privacy-policy) 11\. Changes to this Privacy Policy We are always improving the Services and create new features regularly. These updates sometimes require us to collect new information or use what we already have differently. Further, the laws regarding personal information and privacy frequently change. We will notify you of any changes we make by revising the date at the top of this page. If you object to any change, you can stop using the Services. After we post any changes, your continued use of the Services is subject to the updated Privacy Policy. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-12.-third-party-links-and-features) 12\. Third Party Links and Features The Services may contain links, banners, and/or widgets to third party sites, applications, or services. We may also incorporate third party software (including open source software) in the Services. These links and features are provided for your reference and convenience only and do not imply any endorsement of information provided through these third party links and features, nor any association with their operators. ASTROS is not responsible for the practices of such third parties. Any information you provide to third parties on their sites or services is covered under their privacy and data collection practices and not covered by this Privacy Policy. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-13.-contact-us) 13\. Contact Us If you have any questions, please email us at \[ [team@naviprotocol.io](mailto:team@naviprotocol.io)\ \]. [PreviousTerms of Service](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service) Last updated 4 months ago * [1\. Information We Collect](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-1.-information-we-collect) * [2\. How We Use Your Information](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-2.-how-we-use-your-information) * [3\. Sharing Information](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-3.-sharing-information) * [4\. Cookies and Similar Technologies](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-4.-cookies-and-similar-technologies) * [5\. Analytics and Advertising](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#analytics_and_advertising) * [6\. Your Choices](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-6.-your-choices) * [7\. International Transfers](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-7.-international-transfers) * [8\. How We Protect Your Information](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-8.-how-we-protect-your-information) * [9\. Information Storage](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-9.-information-storage) * [10\. Age Restrictions](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-10.-age-restrictions) * [11\. Changes to this Privacy Policy](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-11.-changes-to-this-privacy-policy) * [12\. Third Party Links and Features](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-12.-third-party-links-and-features) * [13\. Contact Us](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy#id-13.-contact-us) --- # Liquidation Points(Coming Soon) | Astros * If no liquidation events occur on a given day, Liquidation Points for that day will be 0 * It is normal for users to have multiple days with no Liquidation Points The Raw Liquidation Score for a single liquidation event is determined by: * Liquidation Amount * The actual amount liquidated in that event * Liquidation Size Multiplier * A scaling factor that increases as the liquidation amount becomes larger Larger liquidation events result in a higher Raw Liquidation Score. #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/liquidation-points-coming-soon#daily-liquidation-score) Daily Liquidation Score * For each day, all liquidation events are evaluated * Only the largest Raw Liquidation Score from that day is counted Raw Liquidation Score (Daily) = Max(Raw Liquidation Score per liquidation event) #### [](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/liquidation-points-coming-soon#final-daily-liquidation-points) Final Daily Liquidation Points * Daily Liquidation Points are calculated as: Liquidation Points (Daily) = 2 × Raw Liquidation Score (Daily) [PreviousPnL Points(Coming Soon)](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/pnl-points-coming-soon) [NextSettlement & Update Frequency Summary](https://naviprotocol.gitbook.io/astros/astros-perpetual/points/settlement-and-update-frequency-summary) Last updated 10 days ago --- # Terms of Service | Astros These Terms of Service (this “Agreement” or these “Terms”) constitutes a binding legal agreement between you (“you” or “your”) and Navi Protocol Labs, Inc. (“ASTROS,” “we,” “our,” or “us”). This Agreement governs your access to and use of our electronic platforms and applications (collectively, the “Platform”) and all related products, services, programs, technologies, software, tools, features, information or data available or communicated via the Platform, and any other service provided by ASTROS from time to time (collectively, the “Services”). By accessing or using the Services through the Platform, you agree that you have read, understand, and accept this Agreement. If you do not agree to this Agreement then you must not use the Services and we do not grant, shall not grant, or be deemed to grant to you, the license to access or use the Services. THESE TERMS INCLUDE A WAIVER OF ANY RIGHT TO PARTICIPATE IN A CLASS ACTION, AS WELL AS A MANDATORY ARBITRATION CLAUSE THAT GOVERNS RESOLUTION OF CERTAIN DISPUTES AND WAIVES YOUR RIGHT TO SUE IN COURT OR HAVE A TRIAL BY JURY. **PLEASE READ SECTION 17 CAREFULLY.** [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.-who-may-use-the-services) 1\. WHO MAY USE THE SERVICES ---------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.1-eligibility) 1.1 Eligibility To be eligible to use the Services, you represent and warrant that you are at least 18 years old, capable of forming a binding contract with us, have not previously been suspended or removed from the Services, and will use the Services only for yourself. If you are accessing or using the Services on behalf of a company, organization, or other legal entity then you represent and warrant that you have the authority to bind such entity to these Terms and agree on behalf of such legal entity to be bound by these Terms. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.2-restrictions) 1.2 Restrictions Your use of the Services is subject to applicable law including, without limitation, export restrictions, end-user restrictions, anti-terrorism law, anti-money laundering law, trade embargo, and economic sanctions imposed, administered, or enforced by the European Union, the United Kingdom, the United Nations Security Council, the United States Department of Treasury’s Office of Foreign Asset Control, the United States Department of State, the United States Department of Commerce, the United Nations Security Council, and/or any other applicable national, regional, provincial, state, municipal, or local law or regulation (“collectively, “Sanctions”). You represent and warrant that you are not located in, organized under the laws of, or a resident in any country or territory subject to Sanctions, under the control of any person or entity located or a resident in any country or territory subject to Sanctions, or otherwise a citizen, resident, located in, or organized in a jurisdiction where your access or use of the Services would be illegal. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.3-verification) 1.3 Verification You may be required to provide us with certain information and/or documentation directly or through a third party. You hereby authorize us, directly or through a third party, to make inquires that we consider necessary to verify your identity, protect against the misuse of the Services, or for any other reason in connection with the Services. You further authorize us to take any such action that we deem necessary based on the results of such inquiries. You further authorize any third party to which our inquiries are directed, to fully respond to such requests. We will have no liability or responsibility for any permanent or temporary inability to access or use the Services as a result of our inquiries. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.-interacting-with-the-services) 2\. INTERACTING WITH THE SERVICES -------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.1-digital-asset-wallets) 2.1 Digital Asset Wallets To use certain functions of the Services, you must connect a compatible software application or other mechanism (“**Digital Asset Wallet**”). Your relationship with the third party that provides your Digital Asset Wallet is governed by the terms and conditions of that third party’s agreements. We assume no responsibility or liability in connection with your use of any Digital Asset Wallet connected to the Platform. We reserve the right, in our sole discretion, to prohibit certain Digital Asset Wallet’s from connecting to the Platform or from interacting with any part of the Platform or the Services. We do not make any representations or warranties regarding how the Services or the Platform will interact or operate with your Digital Asset Wallet. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.2-digital-assets) 2.2 Digital Assets We do not custody, possess, or control the virtual currency, cryptocurrency, stablecoins, liquid staking tokens, or other cryptographic tokens (collectively, “**Digital Assets**”) held, stored, sent, or transferred to or from your Digital Asset Wallet. As the owner of the Digital Assets stored in your Digital Asset Wallet, you acknowledge and agree that you bear all risk of loss related to the Digital Assets sent, received, or stored in your Digital Asset Wallet. You acknowledge and agree that you are solely responsible for the custody of the cryptographic private keys associated with your Digital Asset Wallet and will not share your Digital Asset Wallet credentials or seed phrase with any third party. We accept no responsibility for, or liability to you, in connection with your use of any Digital Asset Wallet. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.3-security) 2.3 Security You are responsible for maintaining adequate security and control of any and all IDs, passwords, hints, personal identification numbers (PINs), API keys, or other codes that you use to access the Services. Any loss or compromise of any of the foregoing can result in unauthorized access to your Digital Asset Wallet by third parties and the loss or theft of any Digital Assets. We assume no responsibility for any loss that you may sustain due to a compromise of your access credentials due to no fault of ours or your failure to follow up or act on any notices or alerts that we provide or send to you. In the event that we suspect that an unauthorized person is accessing the Services via your Digital Asset Wallet, we reserve the right to terminate, suspend, or restrict your access and use of the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.4-the-protocol) 2.4 The Protocol The Platform provides a web or mobile-based means to access the software protocols that govern the operation of Digital Assets (the “**Protocol**”). The Platform is one but not the exclusive means of accessing a Protocol. The Protocol is comprised of open-source or source-available self-executing smart contracts. We do not provide the services made available to you via the Protocol including, without limitation, staking, bridging, or swapping Digital Assets. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.5-aggregator-api) 2.5 Aggregator API Our Application Programming Interface (“**Aggregator API**”) made available to the public via our documentation found [here](https://naviprotocol.gitbook.io/astros/astros-dex-aggregator/aggregator-api) (“**API Docs**”) is subject to these Terms. You agree not to use the Aggregator API in breach of any applicable law or to infringe, directly or indirectly, the rights of any third party. You may not use the Aggregator API in any manner that accesses or uses information beyond what is permitted in the API Docs, this Agreement, and any other applicable documentation or agreement. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.-third-party-services-and-waiver) 3\. THIRD PARTY SERVICES AND WAIVER ------------------------------------------------------------------------------------------------------------------------------------------------------------ The Platform may enable you to access and transact futures contracts that are quoted, margined, and settled in supported Digital Assets (“Derivate Services”). Derivate Services are complex and may not be suitable for inexperienced users. BY TRANSACTING ON ASTROS, YOU CAN LOSE YOUR ENTIRE DEPOSIT IN A VERY SHORT TIME. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.1-margin) 3.1 Margin You agree to deposit and maintain Digital Assets in your Derivative Services account (“**Derivatives Account**”) in such form and amount that we may from time to time, in our sole discretion, require. The Digital Assets eligible to be deposited and maintained in your Derivatives Account for transactions like opening and maintaining a leveraged position (“**Margin**”) is subject to our sole and absolute discretion from time to time. The value of any Margin shall be, at all times, as determined by us at our sole discretion. We may, but shall not be obligated to, transfer all or any part of your Margin to any other Derivatives Account and/or utilize Margin for any other purposes except for the Derivate Services. We may, with or without notice to you, and at any time, with respect to any Derivative Services transaction, adjust the: (i) minimum amount of Margin required to be deposited into your Derivatives Account in order to open a leveraged position (“**Initial Margin**”); and/or (ii) Margin required to keep the applicable leveraged position open (“**Maintenance Margin**” and, collectively, with the Initial Margin, the “**Margin Requirements**”). You acknowledge and agree that we may, due to certain circumstances like market conditions, immediately or within such other time period, change Margin Requirements applicable to you or require additional Margin, and you hereby wave any right to object to any such change or requirement. You acknowledge and agree that all or any part of your Margin may be held by us, notwithstanding any provision or instruction to the contrary in this Agreement or otherwise: (i) for any purposes including, without limitation, to secure the performance of your obligations; (ii) as security granted by you to us subject to a general lien and right of set off in our favor for any and all of your obligations, liabilities, or monies whatsoever at any time now or hereafter owing, due, incurred or payable by you to under this Agreement, whether present or future, actual or contingent, solely or jointly, or principal or surety; and (iii) for any other purpose(s), subject to applicable law. You further acknowledge and agree that any Margin deposited or otherwise provided to your Derivatives Account will not constitute your property nor shall such transaction constitute a loan by you to us or a constructive trust in your favor when used by us for any purposes stated or related to this Agreement. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.2-margin-calls) 3.2 Margin Calls We may but shall not be required to make any request to you regarding increasing your Margin to satisfy any shortfall or approaching shortfall in your Initial Margin and/or Maintenance Margin (such request, a “Margin Call”). You acknowledge and agree that you are solely responsible, at all relevant times including volatile periods, for maintain and monitoring your Margin to satisfy applicable Margin Requirements regardless of whether a Margin Call has been made or not. We will have no liability to you or any third party, whether directly or indirectly in connection with requesting a Margin Call or any delay in the receipt by you of a Margin Call. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.3-liquidation) 3.3 Liquidation In connection with mitigating liquidations due to certain risks like market manipulation, volatility, or liquidity, we calculate certain values of Derivative Service contracts using the calculation set forth in our documents [here](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/index-and-mark-price#mark-price) (“Mark Price”). If, with respect to any open positions maintained in the Derivative Services reaches the price at which liquidation occurs, calculated by us in accordance with the calculations set forth in our documents [here](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/liquidation-process) (“**Liquidation Price**”) — all of your position(s) are subject to termination (such process, “**Liquidation Process**”). You acknowledge and agree that we are not required to provide any notice prior to commencing the Liquidation Process and any and all applicable charges and fees related to the Liquidation Process will be charged based on the amount of Digital Assets subject to the Liquidation Process . You acknowledge and agree that: (i) you will allocate, at any and all applicable times, the required Initial Margin to your Derivatives Account before entering any Derivate Services transaction; (ii) if your Margin balance falls below the require Maintenance Margin, you will transfer additional Margin to the Derivate Services ; (iii) you shall not have any claim with respect to any unrealized profit or loss and will not be entitled to request the withdrawal of any unrealized profit or loss; and (iv) it is your sole and absolute responsibility to monitor all applicable Maintenance Margin requirements including Mark Price at all times. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.4-insurance-funds-and-automatic-deleveraging) 3.4 Insurance Funds and Automatic Deleveraging In connection with the Liquidation Process, we will attempt to reduce the deficit between your Margin balance and the Maintenance Margin prior to fully liquidating any (or all) positions. If, after the Liquidation Process is complete, your Derivatives Account has a negative balance for any reason, the resulting deficit may be absorbed by our reserve pool (“**Insurance Fund**”). If the Insurance Fund is insufficient to cover a Liquidation Process that results in a deficit, the applicable counterparty positions will be liquidated in accordance of priority using the calculations for such liquidation priority found [here](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/adl) (such process, “Automatic Deleveraging” or “ADL”). ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.5-third-party-data) 3.5 Third Party Data We may rely on information and/or data like indices or market data provided by or obtained from third parties including third party exchanges and/or oracles (“**Third Party Data**”). You acknowledge and agree that we do not: (i) guarantee the accuracy, completeness, or availability of Third Party Data; (ii) warrant that any Third Party Data is up to date as at the time obtained; and (iii) have any liability to you for errors contained in Third Party Data or any losses you may incur from the use or reliance on Third Party Data. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.6-funding-fee-rates) 3.6 Funding Fee Rates In connection with the Derivative Services, you may enter into transactions without an expiration date and that will continue indefinitely unless and until the position is closed or liquidated (“**Perpetual Contracts**”). You will either be required to pay or be entitled to receive a fee during the time that the applicable Perpetual Contract is open based on the calculations of such fee and time intervals found [here](https://naviprotocol.gitbook.io/astros/astros-perpetual/perpetual-trading/funding) (“**Funding Fee Rate**”). You acknowledge and agree that the Funding Fee Rates are high at certain times due to reasons including extreme market conditions and, therefore, it may be expensive to maintain a long-term position during such times. Funding Fee Rates only apply to users who have an open Perpetual Contracts position (until such position is closed or terminated). We reserve the right to change the Funding Fee Rate (including the Funding Fee Rate time intervals) from time to time in our sole discretion. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.-third-party-services-and-waiver) 4\. THIRD PARTY SERVICES AND WAIVER ------------------------------------------------------------------------------------------------------------------------------------------------------------ The Platform may include, without limitation, links to sites, technology, applications, products, services, materials, or resources, provided or made available to you by third parties (“Third Party Services”).Your access and use of any Third Party Service are subject to the terms and policies of the applicable Third Party Service provider including, without limitation, [Mayan Finance](https://docs.mayan.finance/integration/swap-widget) and its terms and conditions. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.1-third-party-services) 4.1 Third Party Services You acknowledge and agree that you are solely responsible for any and all costs, charges, and fees associated with your use of any Third Party Service. Our integration or inclusion of any Third Party Service does not imply endorsement or recommendation. You acknowledge and agree that we are not responsible for the availability, reliability, accuracy, or legitimacy of any Third Party Service (including any related websites, resources, or links displayed therein). Any dispute you have involving a Third Party Service including, without limitation, your intellectual property rights, is between you and the provider of such Third Party Service. We will not be responsible or liable for any damage or loss caused or alleged to be caused by, or in connection with, your use of, or reliance on, any Third Party Service. If, to the extent we permit, you grant express permission to a Third Party Service to access or connect to the Services through such third party or the Platform, you acknowledge that granting permission to any third party to take specific actions on your behalf does not relieve you of any of your responsibilities under these Terms. You are fully responsible for any act or omission of any third party. You acknowledge and agree that you will not hold us responsible for, and will indemnify us from, any liability arising out of or related to any act or omission of any third party with access to your Digital Asset Wallet, decentralized application, software, or other mechanism that you use to interact with the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.2-waiver-of-claims) 4.2 Waiver of Claims To the maximum extent permitted by applicable law, you waive any and all claims, demands, and damages of every kind or nature, known or unknown, suspected or unsuspected, disclosed or undisclosed, against ASTROS and its affiliates, and each of their respective officers, employees, agents, and successors arising out of or in any way related to any of the risks set forth herein. You also waive application of Section 1542 of the Civil Code of the State of California, or any similar statue or law of any other jurisdiction. Section 1542 reads as follows: “a general release does not extend to claims which the creditor does not know or suspect to exist in his or her favor at the time of executing the release, which if known by him or her must have materially affected his or her settlement with the debtor.” [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.-rewards) 5\. REWARDS ------------------------------------------------------------------------------------------------------------ In connection with the Services, we may offer or make available certain incentives, prizes, points, or rewards for completing certain activities like user referrals, performing a certain number of transactions, participating in our or our business partners beta applications, or staking your Digital Assets (collectively, “**Rewards**”). Any Reward that we may offer or make available through the Platform or the Services, from time to time and at any time, is subject to these Terms and any other applicable term or provision directly or indirectly related to or in connection with the Reward. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.1-general-reward-terms) 5.1 General Reward Terms By accepting these Terms, you hereby unconditionally and irrevocably confirm that you understand and accept any and all risks directly related to or in connection with Rewards. You further agree and consent that you grant all necessary rights for using your Digital Assets that you directly use or in connection with any program, campaign, or other similar activity we offer or make available. We reserve the right to change, modify, discontinue, or cancel any Reward we offer at our sole discretion, at any time, and without notice to you. Any information regarding the potential amount of a Reward is an estimate only. ASTROS does not, in any way, represent, warrant, covenant, or guarantee the rate, multiplier, or other formula used to calculate Rewards (collectively, “**Reward Rates**”) will, at any time, remain the same and may fluctuate up or down from time to time. You acknowledge and agree that any representations, whether express or implied regarding any Reward Rate may be based on factors including but not limited to: (i) an estimate based on general market rates; (ii) special rates during promotional periods; and/or (iii) observations of available on-chain rates. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.2-slashing) 5.2 Slashing Some or all of the aggregate amount of the Rewards or other amounts may be programmatically destroyed as a penalty imposed by the applicable underlying blockchain network (“**Slashing Penalty**”). As a result, there may be non-payment of Rewards and the staked Digital Assets may be subject to a penalty. We will not be responsible or liable for any monetary or equitable damage you incur including any legal or monetary arising directly or in connection with your access, use, or unauthorized access of the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.3-no-guarantee-of-rewards) 5.3 No Guarantee of Rewards You understand and agree that we do not guarantee that you will earn or receive any Reward. We expressly disclaim all representations and warranties regarding any Reward including that any: (i) Reward will be received; (ii) Reward will occur on a continuous basis; (iii) Reward will be on an uninterrupted basis or error-free basis; and (iv) any particular Digital Asset will be available in connection with the Reward. ASTROS has no liability for and expressly disclaims any loss, liability, or damage that you may incur directly, indirectly, or in connection with Rewards including, without limitation, damages arising from or in connection with: (i) interruptions to the Service that you access or receive Rewards; (ii) the protocols of the applicable blockchain network distributing Rewards; and (iii) errors, defects, disruptions, discontinuances, and/or restrictions of Rewards. ASTROS, OUR AFFILIATES, AND/OR THIRD PARTY SERVICE PROVIDERS DO NOT GUARANTEE THAT YOU WILL RECEIVE ANY REWARD INCLUDING ANY VALIDATION REWARD OR STAKING REWARD. YOU ACKNOWLEDGE AND AGREE THAT ASTROS, OUR AFFILIATES, AND THIRD PARTY SERVICE PROVIDERS ARE NOT LIABLE FOR ANY FAILURE BY THE APPLICABLE BLOCKCHAIN NETWORK OR OTHER THIRD PARTY IN DISBURSING ANY REWARD. YOU ACKNOWLEDGE THAT PAST REWARDS ARE NOT INDICATIVE OF EXPECTED FUTURE REWARDS. ASTROS WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY REWARD OR SLASHING PENALTY THAT RESULTS FROM YOUR ACCESS OR USE OF THE SERVICES. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-6.-risk-disclosures) 6\. RISK DISCLOSURES ------------------------------------------------------------------------------------------------------------------------------ You understand, accept, and agree to assume all of the various risks involved in interacting with the Platform, the Services, Digital Assets, Rewards, and all other services, products, or features directly related to or in connection with this Agreement including all risks set forth below. (a) Digital Assets, the features, functions, characteristics, operations, use, and other properties and/or software, networks, protocols, systems, or other technology that Digital Assets interact with are complex; and the terms, features, or risks described herein are not a complete or exhaustive list of all such features, risks, or complexities and may not be readily or fully understood due to such complexities. (b) If you act as a liquidity provider to the Protocol through the Platform, you understand that your Digital Asset may lose some or all value while supplied to the Protocol due to fluctuations in Digital Asset prices in a trading pair or liquidity pool. (c) Staking rewards are not guaranteed and may be based on network performance, validator reliability, and other external factors. ASTROS does not assure any specific level of returns or profitability from staking activities. (d) You understand that we do not create, own, or operate cross-chain bridges and we do not make any representation or warranty about the safety or soundness of any cross-chain bridge. (e) Digital Assets will be irretrievably lost if sent to the wrong address. For instance, if the address is improperly formatted, contains an error, or for a different type of Digital Asset. (f) Blockchain networks and Digital Assets may be subject to forks or attacks on the security, integrity, and/or operation of the networks, including any network events. These events may affect features, functionality, operations, use, or properties of any Digital Asset or network and/or the value of any Digital Asset. (g) Any Digital Asset, the Services, the Platform, and/or the Protocol may be targeted by malicious persons or individuals who may attempt to disrupt the Services or steal Digital Assets including, without limitation, malware, hacking, phishing, double spending, smurfing, spoofing, sybil attacks, social engineering, majority mining, mining attacks, distributed denial of service, and blockchain forks. (h) The public nature of the Internet means that parts or the Internet may be unreliable or unavailable at any given time. Interruption, delay, corruption, loss of data, the loss of confidentiality or privacy through the course of data transmission, or malware transmission may occur when transmitting data via the Internet or other technology. This can result in your transaction(s) not being executed according to your instructions, at the requested time, and/or not at all. No technology is completely secure or safe. (i) Digital Assets may decrease in value or lose all value, in a short period of time or permanently, due to various factors including, without limitation, government or regulatory activity, the discovery of wrongful or illegal conduct, market manipulation, price distortion, insider dealing, market distortion, malicious wrongdoing or behaviors, changes to the Digital Asset’s nature or characteristics, suspension, or cessation of support for a Digital Asset by exchanges, public opinion, technical advancements, macroeconomic and political factors, and other factors outside of our control. (j) Digital Assets stored in a Digital Asset Wallet, on the Platform, through the Services (if applicable), or the Protocol are not protected deposits and may not be protected by any deposit protection scheme. Thus, Digital Assets have a reduced level and type of protection compared to fiat and other asset classes or types. (k) The creation of the Protocol may be abandoned for reasons including without limitation, lack of interest, funding, incapacitation of key developers or project members, lack of commercial success or prospects, or Force Majeure Event (defined below). You understand that there are no assurances regarding any benefit to interacting with the Services, even if the Protocol was partially or fully developed and launched. (l) The Services may undergo significant changes over time. We may also limit control over how other visitors and/or users can use the Services and what services are offered on or through the Platform. This could create the risk of the Services not meeting your expectations, for any number of reasons, including mistaken assumptions or analysis, a change in the design and/or implementation plans, or execution on or through the Services. (m) We currently rely on our service providers for certain aspects of our operations including cloud computing services and data centers that provide facilities, infrastructure, website functionality and access, components, and services, all of which are critical to our operations. Like most other online companies, because we rely on service providers, we face operational risk. Any interruption in the services provided by our service providers can impair our ability to provide the Services. (n) We do not directly manage the operation of the service providers we use including their data center facilities. Such third parties are vulnerable to financial, legal, regulatory, and labor issues, cybersecurity incidents, break-ins, computer viruses, denial-of-service attacks, sabotage, acts of vandalism, privacy breaches, service terminations, disruptions, interruptions, Force Majeure Events, and other events. (o) Blockchain transactions like Digital Asset transactions rely on smart contracts stored on various blockchains, cryptographic tokens generated by smart contracts, and other nascent software, applications, and systems that interact with blockchain-based networks. Such technologies are experimental, speculative, inherently risky, and subject to change. A defining feature of blockchain technology is its entries are immutable, which means, as a technical matter, they generally cannot be deleted or modified by anyone. You acknowledge and understand smart contracts dictate how funds and ownership of Digital Assets are distributed. (p) You acknowledge and understand that you may be subject to scams and/or other types of fraud perpetrated by parties outside of our control. It is your responsibility to be aware of and protect against such misconduct. In the event that you are subject to such fraud, there is a risk of loss of your Digital Assets. (q) All blockchain transactions include data and, in some circumstances, personal data about you. Many blockchain technologies store transaction data publicly and permanently. When you use such public blockchain technology, you intentionally make your transaction data public and acknowledge that this data cannot be deleted, removed, or reversed due to the nature of blockchain technology. (r) We are subject to an extensive and rapidly evolving regulatory landscape, and any changes to any law or regulation could adversely impact our ability to offer the Services and/or your use or access to the Services. Such regulatory change may also impact your legal obligations with respect to your use of the Services. (s) You understand that smart contract transactions automatically execute and settle, and blockchain-based transactions are irreversible when confirmed. You acknowledge and accept that the cost and speed of transacting with cryptographic and blockchain-based systems are variable and may increase dramatically at any time. (t) You understand that smart contract transactions automatically execute and settle, and blockchain-based transactions are irreversible when confirmed. You acknowledge and accept that the cost and speed of transacting with cryptographic and blockchain-based systems such as $SUI and $ETH are variable and may increase dramatically at any time. You further acknowledge and accept the risk, where applicable, of selecting your slippage rate which expose you to additional cost or fees by the underlying blockchain network. (u) We may run promotional campaigns from time to time that are sponsored by our business partners with higher annual percentage rates to benefit users. These higher rates may be temporary and you should consider whether the relevant offer still meets your needs once the interest rate reverts to its normal level after the promotional period. (v) When financing is used for trading, the loan carries risk if, among other things, the value of your Digital Assets drops. You acknowledge that you are responsible for increasing the applicable Digital Asset to satisfy this market circumstance. Failure to respond promptly can result in the forced liquidation of your Digital Assets. (w) The use of Derivative Services exposes you to market risk – the risk you can incur as a result of a Derivative Services position moving against you. If you are long a position and the Digital Asset price declines or if you are short a position and the Digital Asset price increase, you can lose all of your Digital Assets. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-7.-acknowledgements-and-covenants) 7\. ACKNOWLEDGEMENTS AND COVENANTS ---------------------------------------------------------------------------------------------------------------------------------------------------------- By accessing or using the Services, you acknowledge, agree, represent, and warrant, in each case as applicable, each of the items contained in this Section. (a) You represent and warrant that you have received a copy of, have carefully read, understand, accept, and agree to assume all of the risks involved with the Services and Digital Assets including without limitation, the risks specifically set forth in this Agreement. You agree that we will not be liable to you for any loss, damage, expense, or liability that is or may relate to any of the risks specifically set forth in this Agreement. You represent and agree that you are able to bear any financial or other loss associated with or that may otherwise relate to your access or use of the Services. (b) You represent and warrant that you are not relying on (and will not at any time rely on) our communication (written or oral) as advice or as a recommendation to engage in any transaction or interaction involving the Services. You agree that we have not: (i) given any guarantee or representation as to the potential success, return, effect, or benefit (either legal, regulatory, tax, financial, accounting, or otherwise) of transacting in Digital Assets, and/or using the Services; and (ii) made any representation to you regarding the legality of transacting in Digital Assets and/or the Services under applicable law. In deciding to use the Services you have made your own independent decision that using the Services is suitable and appropriate for you. (c) You acknowledge and agree that we do not provide investment advice and any content on the Services or other communication channel should not be considered as tailored investment advice. You must seek professional advice regarding your particular financial, legal, technical, and other conditions prior to commencing your use of the Services. You represent and warrant that you fully understand all risks associated with using the Services and you have the necessary experience, understanding, and risk tolerance for using the Services including the necessary experience and knowledge to enter into any use or transaction regarding the Services. You acknowledge and accept any and all risks regarding the Services and are responsible for conducting your own independent analysis of the risks specific to your access or use of the Services. (d) (a) We reserve the right to take any action we determine necessary, in our sole discretion, regarding your liabilities and collateral in one or more of your active collateral positions, including, without limitation, if the value of your Digital Assets drops below a certain level or your positions pose a serious threat to the proper functioning of the applicable market. You acknowledge that we may, at any time and in our sole discretion take any action we deem necessary, in our sole discretion if: (i) you have negative equity; (ii) we determine that you would likely fall below a certain maintenance requirement (negative equity) upon liquidation, in one or more of your positions through the Services or a combination of two or more of your positions; or (iii) we determine, in our sole discretion, that one or more of your positions, or a combination of two or more of your positions pose a serious threat to the proper functioning of the Digital Assets included in any Digital Asset market including any lending pool. (b) You acknowledge and understand that separate margin requirements may apply to certain Services like margin trading. You understand that cross margining between open orders and open positions by which reference to the net market risk across open orders and positions is not permitted. WE MAKE NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, AS TO THE LAWFULNESS OF YOUR PARTICIPATION IN THE SERVICES, PLATFORM, REWARDS, AND/OR ANY THIRD PARTY SERVICE, NOR SHALL ANY PERSON AFFILIATED, OR CLAIMING AFFILIATION, WITH US HAVE AUTHORITY TO MAKE ANY SUCH REPRESENTATIONS OR WARRANTIES. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.-prohibited-use-and-representations) 8\. PROHIBITED USE AND REPRESENTATIONS ------------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.1-prohibited-use) 8.1 Prohibited Use You may not use the Services to engage in the following categories of activity (each a “Prohibited Use”). The specific types of activities listed below are representative, but not exhaustive. (a) Unlawful Activity. Activity which, in any way, would violate, or assist in violation of, any law, statue, ordinance, or regulation, sanctions programs administered in the countries where we offer the Services, or which would involve proceeds of any unlawful activity; publish, distribute, or disseminate any unlawful material or information. (b) Abusive of Others. Interfere with another individual’s access to or use of the Services including but not limited to exploiting, harming, or attempting to exploit or harm minors in any way by exposing them to inappropriate content; defame, abuse, extort, harass, stalk, threaten, or otherwise violate or infringe the legal rights of others; ask for personally identifiable information, or otherwise; transmit, or procure the sending of, any advertising or promotional material, including any “junk mail,” “chain letter,” “spam,” or any other similar solicitation; to impersonate or attempt to impersonate ASTROS, an employee, another user, or any other person or entity (including, without limitation, by using email addresses, screen names, similarly named or commonly misspelled URLs, or associated blockchain identities); engage in any other conduct that restricts or inhibits anyone's use or enjoyment of the Services; incite, threaten, encourage, or promote hate, racial intolerance, or violent acts against others. (c) Fraud. Activity which operates to deceive or defraud, or attempt to deceive or defraud, us, any users or any other person, including without limitation providing any false, inaccurate, or misleading information whether directly through the Services or through an external means that affects the Services with the intent to unlawfully obtain the property of another or to provide knowingly or recklessly false information, including in any way that causes inaccuracy among the content on the Services. (d) Abusive Activity. To cause the Services, the Platform underlying blockchain network(s) or technologies, or any other functionality with which the Services interact, to work other than as intended; damage our reputation, or impair any of our legal rights or interests; engage in any activity or behavior that violates any applicable laws concerning, or otherwise damages, the integrity of the Services or any other service or software which relies on the Services; use the Services in any manner that could disable, overburden, damage, impair, or interfere with the Services, including the ability to engage in real time activities through the Services; use any robot, spider, or other automatic device, process, or means to access the Services for any purpose, including monitoring or copying any of the material on the Services; attempt to gain unauthorized access to, interfere with, damage, or disrupt any parts of the Services, the server on which the Services or information in connection with the Services is stored, or any server, computer, or database connected to the Services, including any underlying blockchain; through the use of a VPN software or any other privacy or anonymization tools or techniques intended to circumvent, or attempt to circumvent, any restrictions that apply to the Services. (e) Intellectual Property Infringement. Violate the legal rights (including the rights of publicity and privacy) of others or contain any material that could give rise to any civil or criminal liability under applicable law or regulation or that otherwise may be in conflict with these Terms; engage in transactions involving items that infringe or violate any copyright, trademark, right of publicity or privacy, or any other proprietary right under the law, including but not limited to sales, distribution, or access to counterfeit music, software, or other licensed materials without the appropriate authorization from the rights holder; use of our intellectual property, name, or logo, including use of any of our trade or service marks, without our express consent or in a manner that otherwise harms us or our brand; any action that implies an untrue endorsement by or affiliation with us. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.2-representations-and-warranties) 8.2 Representations and Warranties Without limitation to any other term or provision in this Agreement, you represent and warrant to us that: (a) You will not engage in any Prohibited Use; (b) you will abide by any and all applicable laws of the jurisdiction where you are located, all local, national, and international practices regarding Internet use, and all network agreements, rules, and procedures related to or in connection with the Services; (c) your interactions and transactions in connection with the Services will comply with applicable law and regulation in your jurisdiction; (d) you have obtained sufficient information about the Services, Digital Assets, Rewards, Digital Asset Wallets, the Platform, the Protocol, and all other services, applications, and features directly related to or in connection with the Services to make an informed decisions in regard to your use of the Services; (e) you will bear the full responsibility for any and all activities that occurs in connection with your use or access to the Services including, without limitation: (i) any transaction or interaction on the Platform or in connection with the Services; (ii) disclosing or publishing information; (iii) clicking to agree with various agreements; and (iv) uploading and submitting various documents or information; and (f) you are the legal and rightful owner of the Digital Assets in the Digital Asset Wallet, and any and all Digital Assets you use in connection with the Services. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.-changes-suspension-and-termination) 9\. CHANGES, SUSPENSION, AND TERMINATION -------------------------------------------------------------------------------------------------------------------------------------------------------------------- We may, at our sole discretion and without liability to you, with or without prior notice and at any time, modify or discontinue, temporarily or permanently, all or any part of the Services. You acknowledge that our decision to take certain actions including limiting, suspending, or terminating your access to the Services, may be based on our confidential criteria that are essential to our risk management and security protocols. You agree that we are under no obligation to disclose the details of our risk management and security procedures to you. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.1-no-liability) 9.1 No Liability We will not be liable for any losses suffered by you resulting from any modification of the Services or from any suspension or termination of your access to all or a portion of the Services. You acknowledge that Digital Asset values may fluctuate during any period during which the Services have been suspended and agree that we will have no liability for any such fluctuations. You also acknowledge that in the event of permanent suspension or termination of the Services, the Digital Assets associated with your account may be lost and that we will have no liability for any such losses. You waive and hold us and our affiliates, licensees, and service providers harmless from any claims resulting from any action taken by us and/or any of the foregoing parties during, or taken as a consequence of, investigations by us, such parties, or law enforcement authorities. We have the right and sole discretion to cooperate fully with any law enforcement authorities or court order requesting or directing us to disclose the identity or other information of anyone posting any materials on or through the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.2-effect-of-termination) 9.2 Effect of Termination In the event of the termination of your right to access or use any part or all of the Services, discontinuation of the Services, or other termination of your right to access any portion or all of the Services we may: (i) block your Digital Wallet Address from accessing the Services; (ii) delete or deactivate your profile and all related information and/or materials associated therewith, without liability to you; (iii) cancel any open transaction, or other use of the Services that are pending at the time of discontinuation or termination; (iv) in the event that your access is terminated due to a Prohibited Use, you will be subject to immediate sanction, including without limitation subjecting to disgorgement and/or recoupment any and all Rewards; and/or (v); any and all amounts payable by you to us will immediately become due. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.-intellectual-property-rights) 10\. INTELLECTUAL PROPERTY RIGHTS -------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.1-astros-materials) 10.1 ASTROS Materials The Services and its entire contents, features, and functionality including but not limited to all information, software, text, displays, images, video, and audio, the design, selection, and arrangement thereof, and the “look and feel” of the Services, except any open source software, are owned by us (“ASTROS Materials”), its licensors, or other providers of such material and are protected by applicable and/or international copyright, trademark, patent, trade secret, and other intellectual property or proprietary rights laws. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.2-limitations-on-use) 10.2 Limitations on Use In connection with your use of the Services, you may use the ASTROS Materials solely as authorized by us for as long as we permit you to continue accessing the Services. Without limiting the foregoing, you agree not to: (i) resell, lease, lend, share, distribute, or otherwise permit any third party to use the Services, ASTROS Materials; (ii) modify or create derivative works of the Services or ASTROS Materials, or any portion thereof, or any data or information received by you in connection therewith; (iii) frame, display, or incorporate the Services or ASTROS Materials in any website or any other work of authorship; (iv) decompile, disassemble, reverse engineer, or attempt to discover the source code of the Services or ASTROS Materials; (v) use the Services or ASTROS Materials to design, develop, or create any competing product or service; (vi) use the Services or ASTROS Materials for any commercial or noncommercial purpose other than their intended purposes determined at our sole discretion; (vii) suggest, imply, or misrepresent any affiliation, connection, or partnership with, or endorsement by, ASTROS; or (viii) use the Services or ASTROS Materials in any service bureau environment. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.3-rights-we-grant-you) 10.3 Rights We Grant You We hereby permit you to use and access the Services, provided that you comply with these Terms. If any software, content, or other materials owned or controlled by us are distributed to you as part of your use of the Services, we hereby grant you a non-sublicensable, non-transferable, and non-exclusive right and license to execute, access, and display such software, content, and materials provided to you as part of the Services, in each case for the sole purpose of enabling you to use the Services as permitted by these Terms. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.4-reservation-of-rights) 10.4 Reservation of Rights If your use or access to the Services is in breach of these Terms, your right to access the Services will stop immediately and you must, at our sole option, return or destroy any copies of the materials that you made directly or indirectly from the Services. No right, title, or interest in or to the Services is transferred to you, and all rights not expressly granted are reserved by us. You may freely use any open-source materials up to the limits provided, but in accordance with any requirements placed, by those materials’ open-source licenses. Any use of the Services not expressly permitted by these Terms is a breach of these Terms and may violate copyright, trademark, and other applicable laws. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.5-trademarks) 10.5 Trademarks Our legal name, the term “ASTROS,” and any and all other related names, logos, product and/or service names, designs, and slogans are trademarks of ASTROS, its affiliates, or licensors. You agree not to use such marks without our prior express written permission. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-11.-platform-content) 11\. PLATFORM CONTENT -------------------------------------------------------------------------------------------------------------------------------- We do not warrant the accuracy, completeness, or usefulness of any materials or information that we or a third party present on or through the Services and such information is made available solely for general information and education purposes. Any material, content, or information posted to the Services should not be construed as an intention to form a contract, and in no case should any information be construed as an offer from ASTROS to buy, sell, exchange, or otherwise transact with you using Digital Assets. We disclaim all liability and responsibility arising from any reliance placed on such information or materials by you, any other user or person who may be informed of any of the Services contents, or by the actions or omissions of others interacting with the Services. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-12.-feedback) 12\. FEEDBACK ---------------------------------------------------------------------------------------------------------------- Any questions, suggestions, ideas, feedback, reviews, or other information or materials regarding the Services that you provide us with (collectively, “Feedback”) are non-confidential. ASTROS will be entitled to the unrestricted use and dissemination of Feedback for any purpose, commercial or otherwise without acknowledgment, attribution, or compensation to you. You hereby assign to ASTROS all right, title, and interest to Feedback together with all associated intellectual property rights and waive any claim for, acknowledgement or compensation based on any Feedback or any modifications made based on any Feedback. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-13.-relationship) 13\. RELATIONSHIP ------------------------------------------------------------------------------------------------------------------------ ASTROS is not your broker, intermediary, agent, or advisor and has no fiduciary relationship or obligation to you in your use of the Services. ASTROS does not provide investment, tax, or legal advice, and you are solely responsible for any transaction, investment, strategy, decision, or other act that you make when using the Services. We may provide educational material or information on the Platform, through the Services, social media account, or other channel of communication. No communication or information provided to you by ASTROS is intended as, or shall be considered or construed as, advice. You acknowledge and agree to the fullest extent such duties or liabilities are afforded by law or by equity, such duties and liabilities are hereby irrevocably disclaimed, waived, and eliminated, and that we shall be held completely harmless in relation thereof. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.-charges-and-fees) 14\. CHARGES AND FEES -------------------------------------------------------------------------------------------------------------------------------- We may, in our sole discretion and at any time, set or modify the fees for any or all of the Services. Except as required by law, fees are non-refundable. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.1-our-fees) 14.1 Our Fees You agree to pay us all applicable fees associated with your use of the Services. We may change the fees and any fee schedule at any time, without notice. Any fee we charge may vary between Digital Assets or Digital Asset Pair. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.2-third-party-fees) 14.2 Third Party Fees You may be charged fees for your use or access to the Protocol through a third party interface. You are responsible for doing your own diligence on any third party interface to understand any applicable fee or charge that the third party interface provider may charge you. Under no circumstances will ASTROS incur any liability, of any kind, to you arising from or relating to fees charged to you by your access or use to the Protocol via a third party interface or any Third Party Service. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.3-asset-recovery) 14.3 Asset Recovery ASTROS has no legal, contractual, or other similar obligation or duty to recover, compensate, or refund any Digital Assets lost due to any reason including smart-contract bugs, blockchain malfunctions, cyber-attacks, or user errors. We reserve the right, in our sole discretion, to attempt to assist you with recovery or refund of your Digital Assets on a case-by-case basis. No prior assistance shall be binding or set a precedent for any future assistance by ASTROS. We may discontinue, refuse, or suspend our assistance at any time and in our sole and absolute discretion. In connection with our review of any request you make regarding the recovery of your Digital Assets, you agree to: (i) provide us with all relevant information and documentation related to your request within three (3) calendar days of the loss of your Digital Assets; and (ii) be responsible for any and all fees we incur in connection with the recovery of your Digital Assets. We make no promises, warrants, representations, or guarantees regarding the recovery of all or any amount of your lost Digital Assets. You agree that you will not hold us liable for: (i) any action or inaction we make in connection with the decision to recover or not recover your Digital Assets; (ii) any discrepancy between the amount of Digital Assets we recover and the amount you lost; and (iii) any loss you incur from using the Digital Assets we recovered. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.4-blockchain-fees) 14.4 Blockchain Fees Blockchain transactions require the payment of transaction fees to the appropriate network’s nodes, miners, validators, or operators (“**Blockchain Fees**”). You will be solely responsible to pay the Blockchain Fees for any transaction that you initiate via the Services. Blockchain Fees are neither levied directly by ASTROS nor paid to or shared with ASTROS in any way, but rather are determined by your use of the Services and the rules placed by corresponding blockchain communities at large. You acknowledge and agree that ASTROS has no control over Blockchain Fees (including without limitation their applicability, payment, amounts, transmission, intended operation, and effectiveness) whether related to your use of the Services or otherwise, and in no event will ASTROS be responsible to you or any other party for the payment, repayment, refund, disbursement, indemnity, or for any other aspect of your use or transmission of Blockchain Fees. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-15.-warranty-disclaimer) 15\. WARRANTY DISCLAIMER ASTROS has no oversight on or control over any particular Digital Asset, Protocol, or blockchain network. You are responsible for your use of the Services, the functionalities that you enable, transactions engaged on the Protocol through the Services, and access or use of the information derived thereof. You are also solely responsible for complying with all applicable laws related to transactions and activities that directly or indirectly incorporate our provision of the Services. You acknowledge and understand that we are not registered nor licensed with, nor have the Services or the software contained therein been reviewed by any securities, commodities, or other financial or banking regulator. You further acknowledge and understand that we cannot and do not guarantee or warrant that files available for download from the Services will be free of viruses or other destructive code. You are responsible for implementing sufficient procedures and checkpoints to satisfy your particular requirements for: (i) an appropriate blockchain based utility; (ii) anti-virus protection and accuracy of data input and output; (iii) your participation in and use of the Protocol and related technologies; and (iv) maintaining a means external to our site to reconstruct any lost data. TO THE FULLEST EXTENT PROVIDED BY LAW, IN NOT EVENT WILL ASTROS, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES BE LIABLE FOR ANY LOSS OR DAMAGE CAUSED BY A DISTRIBUTED DENIAL-OF-SERVICE ATTACK, MAN-IN-THE-MIDDLE ATTACK, VIRUS, OR OTHER TECHNOLOGICALLY HARMFUL MATERIAL THAT MAY INFECT YOUR COMPUTER EQUIPMENT, COMPUTER PROGRAMS, DATA, OR OTHER PROPRIETARY MATERIAL DUE TO YOUR USE OF THE SERVICES, PLATFORM, OR ASTROS MATERIALS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF ASTROS THROUGH THE SERVICES, OR YOUR DOWNLOADING OF ANY MATERIAL POSTED ON IT, OR ON ANY THIRD PARTY WEBSITE LINKED TO IT. YOUR USE OF THE SERVICES AND ANY SERVICE CONTENT IS AT YOUR SOLE RISK. THE SERVICES, ASTROS MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, PROVIDED BY OR ON BEHALF OF ASTROS ARE PROVIDED ON AN “AS IS’’ AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT LEGALLY PERMISSIBLE, IN NOT EVENT WILL ASTROS, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES BE LIABLE FOR, AND EXPLICITLY DISCLAIM, ANY AND ALL REPRESENTATIONS OR WARRANTIES OF ANY KIND RELATED THE SERVICES, ASTROS MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING (WITHOUT LIMITATION) THE WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. NEITHER ASTROS, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES MAKES ANY WARRANTY OR REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, ACCURACY, OR AVAILABILITY OF THE SERVICES, ASTROS MATERIALS, THE PROTOCOL, THE PLATFORM, AND/OR ANY PRODUCT, SERVICE, FEATURE, OR OTHER ITEM PROVIDED BY OR ON BEHALF OF ASTROS. ASTROS, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES DO NOT REPRESENT OR WARRANT THAT: (I) ACCESS TO THE SERVICES, ASTROS MATERIALS, THE PLATFORM, THE PROTOCOL, AND ANY OTHER PRODUCT, SERVICE, FEATURE, REWARD, OR ITEM PROVIDED BY OR ON BEHALF OF ASTROS WILL BE CONTINUOUS, UNINTERRUPTED, TIMELY, WITHOUT DELAY, ERROR-FREE, SECURE, OR FREE FROM DEFECTS; (II) THE INFORMATION CONTAINED OR PRESENTED ON THE SERVICES, ASTROS MATERIALS, THE PROTOCOL, OR THE PLATFORM IS ACCURATE, RELIABLE, COMPLETE, CONCISE, CURRENT, OR RELEVANT; (III) THE SERVICES, ASTROS MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, REWARD, OR ANY SOFTWARE CONTAINED THEREIN WILL BE FREE FROM DEFECTS, MALICIOUS SOFTWARE, ERRORS, OR ANY OTHER HARMFUL ELEMENTS, OR THAT ANY OF SUCH WILL BE CORRECTED; OR (III) THE SERVICES, ASTROS MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, WILL MEET ANY USER’S EXPECTATIONS. NO INFORMATION OR STATEMENT THAT WE MAKE, INCLUDING DOCUMENTATION OR PRIVATE COMMUNICATION, SHOULD BE TREATED AS OFFERING ANY WARRANTY CONCERNING THE SERVICES, ASTROS MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD PROVIDED BY OR ON BEHALF OF ASTROS. WE DO NOT ENDORSE, GUARANTEE, OR ASSUME ANY LIABILITY OR RESPONSIBILITY FOR ANY CONTENT, ADVERTISEMENTS, OFFERS, STATEMENTS, OR ACTIONS BY ANY THIRD PARTY EITHER REGARDING THE SERVICES, ASTROS MATERIALS, THE PLATFORM, THE PROTOCOL, REWARDS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF ASTROS. THE FOREGOING DOES NOT AFFECT ANY WARRANTIES THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-16.-indemnification) 16\. INDEMNIFICATION ------------------------------------------------------------------------------------------------------------------------------ You agree to defend, indemnify, and hold harmless ASTROS, its affiliates, licensors, and service providers, and their respective officers, directors, employees, contractors, agents, licensors, suppliers, successors, and assigns from and against any claims, liabilities, damages, judgments, awards, losses, costs, expenses, or fees (including reasonable attorneys’ fees) arising out of or relating to: (i) your violation of these Terms; (ii) your use of Services; (iii) your interactions or transaction with or on the Platform, through the Services, or the Protocol, and any other service, product, application, program, or feature accessible on or through the Services; (iv) your use of or reliance on the Platform’s content, the Services, ASTROS Materials, and/or any other services or products other than as expressly authorized in these Terms; (v) your access or use of a Third Party Service including any liquidity aggregator; (vi) engaging in any Prohibited Use, whether alone or in concert with others such as front-running; (vii) any third party’s access or use of the Services with or without your assistance, using any device, account, profile, Digital Asset Wallet, or other mechanism that you own or control; (viii) congestion in the SUI or other blockchain network available on the Platform; (ix) failed transactions when depositing multiple Digital Assets into a liquidity pool; (x) your use of any Software Development Kit (“SDK”), Command-Line Interface (“CLI”), or other software offered by us or provided through the Platform or Services; and/or (xi) any actions or inactions we directly or indirectly make in connection with recovery of your Digital Assets. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-17.-limitation-of-liability-disclaimer-of-damages) 17\. LIMITATION OF LIABILITY; DISCLAIMER OF DAMAGES ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- TO THE FULLEST EXTENT PROVIDED BY LAW, IN NO EVENT WILL ASTROS, ITS AFFILIATES, OR THEIR LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS, OR DIRECTORS BE LIABLE FOR DAMAGES OF ANY KIND, UNDER ANY LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH YOUR USE, OR INABILITY TO USE THE SERVICES, ASTROS MATERIALS, THE PLATFORM, THE PROTOCOL, AND/OR ANY PRODUCT, SERVICE, REWARD, DIGITAL ASSET, OR OTHER ITEM PROVIDED BY OR ON BEHALF OF ASTROS, INCLUDING ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES INCLUDING BUT NOT LIMITED TO, PERSONAL INJURY, PAIN AND SUFFERING, EMOTIONAL DISTRESS, LOSS OF REVENUE, LOSS OF PROFITS, LOSS OF BUSINESS OR ANTICIPATED SAVINGS, LOSS OF USE, LOSS OF GOODWILL, LOSS OF DATA, AND WHETHER CAUSED BY TORT (INCLUDING NEGLIGENCE), BREACH OF CONTRACT, OR OTHERWISE, EVEN IF FORESEEABLE. THIS DISCLAIMER OF LIABILITY EXTENDS TO ANY AND ALL DAMAGES CAUSED BY ANY THIRD PARTY (INCLUDING, WITHOUT LIMITATION, THOSE CAUSED BY FRAUD, DECEIT, OR MANIPULATION), WHETHER OR NOT A USER, OR ANY FAILURE, EXPLOIT, OR VULNERABILITY OF THE SERVICES, THE PLATFORM, THE PROTOCOL, ASTROS MATERIALS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF ASTROS. TO THE FULLEST EXTENT PROVIDED BY LAW, IN NO EVENT WILL THE COLLECTIVE LIABILITY OF ASTROS, AND ITS SUBSIDIARIES, AFFILIATES, LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS, AND DIRECTORS, TO ANY PARTY (REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, OR OTHERWISE) EXCEED THE GREATER OF $100 OR THE AMOUNT YOU HAVE PAID DIRECTLY TO ASTROS FOR THE SERVICES IN THE LAST SIX MONTHS OUT OF WHICH LIABILITY AROSE. THE FOREGOING DOES NOT AFFECT ANY LIABILITY THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.-dispute-resolution-and-mandatory-arbitration) 18\. DISPUTE RESOLUTION AND MANDATORY ARBITRATION ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Please read this section carefully because it waives any right to participate in any class action or other representative action or proceeding. This section requires you to arbitrate certain disputes and limits the ways in which you can seek relief, including by precluding you from suing in court or having a jury trial. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.1-waiver-of-class-actions-and-right-to-jury-trial) 18.1 Waiver of Class Actions and Right to Jury Trial To the extent permissible by law, any claim, controversy, or dispute arising out of or related to this Agreement, or any products or services provided in connection with the Services (each a “**Dispute**”) must be brought in your individual capacity, and not as a plaintiff or class member in any putative class, collective action, or representative proceeding (collectively “**Class Action Waiver**”). The arbitrator may not consolidate more than one person’s claims or engage in any arbitration on behalf of a class. You agree that, by entering into this Agreement, you are waiving the right to a trial by jury and the right to participate in a class action. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.2-informal-resolution) 18.2 Informal Resolution Before filing a claim against ASTROS, you agree to try to resolve the Dispute by first emailing \[ [team@naviprotocol.io](mailto:team@naviprotocol.io)\ \] with a description of your claim and proof of your relationship with ASTROS. If we can’t resolve the Dispute within sixty days of our receipt of your first email, you or ASTROS may then submit the Dispute to binding arbitration as provided herein. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.3-arbitration-agreement) 18.3 Arbitration Agreement All Disputes between you and ASTROS must be resolved by final and binding arbitration. By agreeing to binding arbitration, you and ASTROS expressly waive the right to formal court proceedings including without limitation trial by jury and class action. This Agreement affects interstate commerce, and the enforceability of this section will be substantively and procedurally governed by the Federal Arbitration Act 9 U.S.C. § 1, et. Seq. (“**FAA**”). ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.4-conducting-arbitration) 18.4 Conducting Arbitration The arbitration shall be conducted by the International Chamber of Commerce (“**ICC**”) under its Commercial Arbitration Rules (“**ICC Rules**”) then in effect. If you are a consumer, the most recent version of the ICC Rules can be accessed [here](https://iccwbo.org/dispute-resolution/dispute-resolution-services/arbitration/rules-procedure/2021-arbitration-rules/) . These Terms shall govern any conflict between the ICC Rules and these Terms. The location and type of hearing shall be determined in accordance with the ICC Rules. Further, a party’s right to request a hearing shall also be determined in accordance with the ICC Rules. Unless otherwise ordered by an arbitrator or pursuant to the ICC Rules, any in-person arbitration shall be in English and held remotely to the maximum extent and administered in New York, New York, or another mutually agreeable location. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.5-confidentiality) 18.5 Confidentiality ASTROS, the arbitrator, and you, will each maintain the confidentiality of any arbitration proceedings, judgments, and awards including information shared and produced during the arbitration. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.6-arbitration-time-for-filing) 18.6 Arbitration Time for Filing Any arbitration must be commenced by filing a demand for arbitration within one year after the date the party asserting the claim first knows or reasonably should know of the act, omission or default giving rise to the claim. If applicable law prohibits a one year limitation period for asserting claims, any claim must be asserted within the shortest time period permitted by applicable law. If a claim is not filed within such period, the Dispute is permanently barred. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.7-severability) 18.7 Severability If any portion of this section is found to be unenforceable or unlawful for any reason, the unenforceable or unlawful provision shall be severed from these Terms and such severance of the provision(s) shall have no impact whatsoever on the remainder of this section. Further, to the extent that any claims must therefore proceed on a class, collective, consolidated, or representative basis, such claims must be litigated in a civil court of competent jurisdiction and not in arbitration, and the parties agree that litigation of those claims shall be stayed pending the outcome of any individual claims in arbitration. Lastly, if any provision in this section is found to prohibit an individual claim seeking public injunctive relief, such provision shall have no effect to the extent relief is allowed to be sought outside of arbitration. The remainder of this section shall remain in full force and effect. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.8-modification) 18.8 Modification Notwithstanding any term or provision in this Agreement to the contrary, you and ASTROS agree that if ASTROS makes any future material change to this section, we will notify you. Your continued use of the Services including the acceptance of features and services offered following the posting of changes constitutes your acceptance of any such changes. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-19.-governing-law) 19\. GOVERNING LAW -------------------------------------------------------------------------------------------------------------------------- This Agreement shall be governed by, and construed and enforced in accordance with, the laws of Panama without regard to conflict of law rules or principles that would cause the application of the laws of any other jurisdiction. You agree that ASTROS may initiate a proceeding relating to the enforceability or validity of its intellectual property rights in any court of competent jurisdiction. With respect to any other proceeding not subject to arbitration under this Agreement, the courts of Panama will have exclusive jurisdiction. You waive any objection to venue in any such courts. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-20.-amendments-to-this-agreement) 20\. AMENDMENTS TO THIS AGREEMENT -------------------------------------------------------------------------------------------------------------------------------------------------------- We reserve the right to amend this Agreement, any other agreement or document incorporated or referenced in this Agreement, and any policy governing the use of the Services at any time and in our sole discretion. Any amendment will be effective immediately and you waive any right you may have to receive any specific notice of such amendment. Your continued use of the Services after posting of such amendment constitutes your agreement to be bound by all then-in-effect amendments to this Agreement, regardless of whether you have actually reviewed them. [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.-miscellaneous-terms) 21\. MISCELLANEOUS TERMS -------------------------------------------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.1-assignment) 21.1 Assignment These Terms, and any other document, material, or information referenced herein is particular to you and any attempt that you make to assign, novate, or transfer your rights, interests, liabilities, and/or obligations is null and void, unless you have received ASTROS’s prior written consent. ASTROS reserves the right to assign our rights without restriction, including without limitation to any of our affiliates or subsidiaries, or to any successor in interest of any business associated with the Services. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties and their successors and permitted assigns. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.2-term-and-survival) 21.2 Term and Survival We reserve the right to change, suspend or discontinue, or terminate, restrict, or disable your use of or access to, parts or all of the Services or their functionality at any time at our sole discretion and without notice. All sections of this Agreement that by their nature should survive termination shall survive termination. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.3-nonwaiver-of-rights) 21.3 Nonwaiver of Rights Our failure or delay in exercising any right, power, or privilege under these Terms shall not operate as a waiver thereof. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.4-severability) 21.4 Severability If any provision of this Agreement shall be determined to be invalid or unenforceable under any rule, law, or regulation, or any governmental agency whether local, state, or federal, such provision shall be interpreted to accomplish the objectives of the provision to the greatest extent possible under any applicable law, and the validity or enforceability of any other provision of the Terms shall not be affected. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.5-headings) 21.5 Headings Headings of sections are for convenience only and shall not be used to limit or construe such sections. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.6-force-majeure) 21.6 Force Majeure You acknowledge and consent that the Services are provided by us according to our current technological capability and other business conditions. While we have made every effort to ensure continuity and security of the Services, we are unable to completely foresee and hedge against all legal, technological, and other risks. ASTROS will not be held liable for delays, failure in performance, or interruption of Services that result directly or indirectly from any cause or condition beyond our reasonable control. Such instances include: (i) acts of God such as earth earthquakes, fires, cyclones, explosions, typhoons, monsoons, landslides, lightning, storms, tempests, pandemics, droughts or meteors; (ii) acts of war, whether declared or undeclared, including invasion, act of a foreign enemy, hostilities between nations, civil insurrection, or militarily usurped power; and acts of terrorism; (iii) civil disorder, such as acts of a public enemy, malicious damage, terrorism, sabotage, or civil unrest; (iv) embargoes or sanctions (such as confiscation, nationalization, requisition, expropriation, prohibition, restraint or damage to property by or under the order of any government or governmental authority; (v) unnatural disasters, such as ionizing radiation or contamination by radioactivity from any nuclear waste or from combustion of nuclear fuel; (vi) labor disputes, including strikes, blockades, lock-outs, or other industrial disputes; (vii) failure of telecommunication outlets, including the internet, communications networks and facilities, or other infrastructure, systems, operations or of equipment relevant to the provision or use of the Services; (viii) data breaches or data-processing failure or incomplete processing; and/or (ix) changes in laws or regulations that may materially affect the Digital Assets and/or blockchain industries (collectively, “Force Majeure Events”). ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.7-taxes) 21.7 Taxes It is your sole responsibility to determine whether and to what extent any taxes apply to activity you conduct through the Services; and to withhold, collect, report, and remit the correct amounts of taxes to the appropriate tax authorities. No communication or information provided to you by ASTROS is intended as, or considered or construed as, legal or tax advice. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.8-notice) 21.8 Notice Any notices or other communications provided by us under these Terms including those regarding modifications to these Terms will be posted online, in the Services, or through other electronic communication. You agree and consent to receive electronically all communications, agreements, documents, notices, and disclosures that we provide in connection with your use of the Services. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.9-privacy) 21.9 Privacy To understand how ASTROS collects, uses, and shares information about you, please review our \[[Privacy Policy](https://app.gitbook.com/o/dcxQ7e5pivSbceCjCqQ8/s/EagmjVMVJsuZQ0TvRYt7/~/changes/14/legal-and-support/privacy-policy)\ \]. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.10-third-party-beneficiaries) 21.10 Third Party Beneficiaries Nothing in this Agreement, expressed or implied, is intended to confer upon any person, other than the parties and their successors and permitted assigns, any of the rights hereunder. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.11-entire-agreement) 21.11 Entire Agreement These Terms and every other term or provision applicable to you, including any document incorporated by reference herein, constitute the entire agreement and understanding between you and ASTROS as to the subject matter hereof, and supersede any and all prior discussions, agreements, and understandings of any kind (including any prior versions of these Terms). Unless otherwise specifically stated, these Terms govern and control any conflict between these Terms and any other agreement you may have with ASTROS. ### [](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.12-translation) 21.12 Translation These Terms are set forth in the English language and all communications including any notices or information being transmitted shall be in English. In the event that these Terms or any part of it is translated (for any proceedings, for your convenience, or otherwise) into any other language, the English language text of these Terms shall prevail. [PreviousContact Us](https://naviprotocol.gitbook.io/astros/legal-and-support/integrations) [NextPrivacy Policy](https://naviprotocol.gitbook.io/astros/legal-and-support/privacy-policy) Last updated 4 months ago * [1\. WHO MAY USE THE SERVICES](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.-who-may-use-the-services) * [1.1 Eligibility](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.1-eligibility) * [1.2 Restrictions](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.2-restrictions) * [1.3 Verification](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-1.3-verification) * [2\. INTERACTING WITH THE SERVICES](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.-interacting-with-the-services) * [2.1 Digital Asset Wallets](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.1-digital-asset-wallets) * [2.2 Digital Assets](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.2-digital-assets) * [2.3 Security](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.3-security) * [2.4 The Protocol](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.4-the-protocol) * [2.5 Aggregator API](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-2.5-aggregator-api) * [3\. THIRD PARTY SERVICES AND WAIVER](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.-third-party-services-and-waiver) * [3.1 Margin](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.1-margin) * [3.2 Margin Calls](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.2-margin-calls) * [3.3 Liquidation](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.3-liquidation) * [3.4 Insurance Funds and Automatic Deleveraging](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.4-insurance-funds-and-automatic-deleveraging) * [3.5 Third Party Data](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.5-third-party-data) * [3.6 Funding Fee Rates](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-3.6-funding-fee-rates) * [4\. THIRD PARTY SERVICES AND WAIVER](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.-third-party-services-and-waiver) * [4.1 Third Party Services](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.1-third-party-services) * [4.2 Waiver of Claims](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-4.2-waiver-of-claims) * [5\. REWARDS](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.-rewards) * [5.1 General Reward Terms](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.1-general-reward-terms) * [5.2 Slashing](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.2-slashing) * [5.3 No Guarantee of Rewards](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-5.3-no-guarantee-of-rewards) * [6\. RISK DISCLOSURES](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-6.-risk-disclosures) * [7\. ACKNOWLEDGEMENTS AND COVENANTS](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-7.-acknowledgements-and-covenants) * [8\. PROHIBITED USE AND REPRESENTATIONS](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.-prohibited-use-and-representations) * [8.1 Prohibited Use](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.1-prohibited-use) * [8.2 Representations and Warranties](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-8.2-representations-and-warranties) * [9\. CHANGES, SUSPENSION, AND TERMINATION](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.-changes-suspension-and-termination) * [9.1 No Liability](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.1-no-liability) * [9.2 Effect of Termination](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-9.2-effect-of-termination) * [10\. INTELLECTUAL PROPERTY RIGHTS](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.-intellectual-property-rights) * [10.1 ASTROS Materials](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.1-astros-materials) * [10.2 Limitations on Use](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.2-limitations-on-use) * [10.3 Rights We Grant You](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.3-rights-we-grant-you) * [10.4 Reservation of Rights](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.4-reservation-of-rights) * [10.5 Trademarks](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-10.5-trademarks) * [11\. PLATFORM CONTENT](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-11.-platform-content) * [12\. FEEDBACK](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-12.-feedback) * [13\. RELATIONSHIP](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-13.-relationship) * [14\. CHARGES AND FEES](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.-charges-and-fees) * [14.1 Our Fees](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.1-our-fees) * [14.2 Third Party Fees](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.2-third-party-fees) * [14.3 Asset Recovery](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.3-asset-recovery) * [14.4 Blockchain Fees](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-14.4-blockchain-fees) * [15\. WARRANTY DISCLAIMER](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-15.-warranty-disclaimer) * [16\. INDEMNIFICATION](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-16.-indemnification) * [17\. LIMITATION OF LIABILITY; DISCLAIMER OF DAMAGES](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-17.-limitation-of-liability-disclaimer-of-damages) * [18\. DISPUTE RESOLUTION AND MANDATORY ARBITRATION](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.-dispute-resolution-and-mandatory-arbitration) * [18.1 Waiver of Class Actions and Right to Jury Trial](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.1-waiver-of-class-actions-and-right-to-jury-trial) * [18.2 Informal Resolution](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.2-informal-resolution) * [18.3 Arbitration Agreement](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.3-arbitration-agreement) * [18.4 Conducting Arbitration](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.4-conducting-arbitration) * [18.5 Confidentiality](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.5-confidentiality) * [18.6 Arbitration Time for Filing](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.6-arbitration-time-for-filing) * [18.7 Severability](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.7-severability) * [18.8 Modification](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-18.8-modification) * [19\. GOVERNING LAW](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-19.-governing-law) * [20\. AMENDMENTS TO THIS AGREEMENT](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-20.-amendments-to-this-agreement) * [21\. MISCELLANEOUS TERMS](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.-miscellaneous-terms) * [21.1 Assignment](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.1-assignment) * [21.2 Term and Survival](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.2-term-and-survival) * [21.3 Nonwaiver of Rights](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.3-nonwaiver-of-rights) * [21.4 Severability](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.4-severability) * [21.5 Headings](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.5-headings) * [21.6 Force Majeure](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.6-force-majeure) * [21.7 Taxes](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.7-taxes) * [21.8 Notice](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.8-notice) * [21.9 Privacy](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.9-privacy) * [21.10 Third Party Beneficiaries](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.10-third-party-beneficiaries) * [21.11 Entire Agreement](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.11-entire-agreement) * [21.12 Translation](https://naviprotocol.gitbook.io/astros/legal-and-support/terms-of-service#id-21.12-translation) --- # Terms of Service | Navi Protocol - docs These Terms of Service (this “Agreement” or these “Terms”) constitutes a binding legal agreement between you (“you” or “your”) and Navi Protocol Labs, Inc. (“NAVI,” “we,” “our,” or “us”). This Agreement governs your access to and use of our electronic platforms and applications (collectively, the “Platform”) and all related products, services, programs, technologies, software, tools, features, information or data available or communicated via the Platform, and any other service provided by NAVI from time to time (collectively, the “Services”). By accessing or using the Services through the Platform, you agree that you have read, understand, and accept this Agreement. If you do not agree to this Agreement then you must not use the Services and we do not grant, shall not grant, or be deemed to grant to you, the license to access or use the Services. THESE TERMS INCLUDE A WAIVER OF ANY RIGHT TO PARTICIPATE IN A CLASS ACTION, AS WELL AS A MANDATORY ARBITRATION CLAUSE THAT GOVERNS RESOLUTION OF CERTAIN DISPUTES AND WAIVES YOUR RIGHT TO SUE IN COURT OR HAVE A TRIAL BY JURY. PLEASE READ SECTION 17 CAREFULLY. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-1.-who-may-use-the-services) **1\. WHO MAY USE THE SERVICES** #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-1.1-eligibility) 1.1 Eligibility To be eligible to use the Services, you represent and warrant that you are at least 18 years old, capable of forming a binding contract with us, have not previously been suspended or removed from the Services, and will use the Services only for yourself. If you are accessing or using the Services on behalf of a company, organization, or other legal entity then you represent and warrant that you have the authority to bind such entity to these Terms and agree on behalf of such legal entity to be bound by these Terms. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-1.2-restictions) 1.2 Restictions Your use of the Services is subject to applicable law including, without limitation, export restrictions, end-user restrictions, anti-terrorism law, anti-money laundering law, trade embargo, and economic sanctions imposed, administered, or enforced by the European Union, the United Kingdom, the United Nations Security Council, the United States Department of Treasury’s Office of Foreign Asset Control, the United States Department of State, the United States Department of Commerce, the United Nations Security Council, and/or any other applicable national, regional, provincial, state, municipal, or local law or regulation (“collectively, “Sanctions”). You represent and warrant that you are not located in, organized under the laws of, or a resident in any country or territory subject to Sanctions, under the control of any person or entity located or a resident in any country or territory subject to Sanctions, or otherwise a citizen, resident, located in, or organized in a jurisdiction where your access or use of the Services would be illegal. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-1.3-verification) 1.3 Verification You may be required to provide us with certain information and/or documentation directly or through a third party. You hereby authorize us, directly or through a third party, to make inquires that we consider necessary to verify your identity, protect against the misuse of the Services, or for any other reason in connection with the Services. You further authorize us to take any such action that we deem necessary based on the results of such inquiries. You further authorize any third party to which our inquiries are directed, to fully respond to such requests. We will have no liability or responsibility for any permanent or temporary inability to access or use the Services as a result of our inquiries. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.-interacting-with-the-services) **2\.** INTERACTING WITH THE SERVICES #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.1-digital-asset-wallets) 2.1 Digital Asset Wallets To use certain functions of the Services, you must connect a compatible software application or other mechanism (“Digital Asset Wallet”). Your relationship with the third party that provides your Digital Asset Wallet is governed by the terms and conditions of that third party’s agreements. We assume no responsibility or liability in connection with your use of any Digital Asset Wallet connected to the Platform. We reserve the right, in our sole discretion, to prohibit certain Digital Asset Wallet’s from connecting to the Platform or from interacting with any part of the Platform or the Services. We do not make any representations or warranties regarding how the Services or the Platform will interact or operate with your Digital Asset Wallet. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.2-digital-assets) 2.2 Digital Assets We do not custody, possess, or control the virtual currency, cryptocurrency, stablecoins, liquid staking tokens, or other cryptographic tokens (collectively, “Digital Assets”) held, stored, sent, or transferred to or from your Digital Asset Wallet. As the owner of the Digital Assets stored in your Digital Asset Wallet, you acknowledge and agree that you bear all risk of loss related to the Digital Assets sent, received, or stored in your Digital Asset Wallet. You acknowledge and agree that you are solely responsible for the custody of the cryptographic private keys associated with your Digital Asset Wallet and will not share your Digital Asset Wallet credentials or seed phrase with any third party. We accept no responsibility for, or liability to you, in connection with your use of any Digital Asset Wallet. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.3-security) 2.3 Security You are responsible for maintaining adequate security and control of any and all IDs, passwords, hints, personal identification numbers (PINs), API keys, or other codes that you use to access the Services. Any loss or compromise of any of the foregoing can result in unauthorized access to your Digital Asset Wallet by third parties and the loss or theft of any Digital Assets. We assume no responsibility for any loss that you may sustain due to a compromise of your access credentials due to no fault of ours or your failure to follow up or act on any notices or alerts that we provide or send to you. In the event that we suspect that an unauthorized person is accessing the Services via your Digital Asset Wallet, we reserve the right to terminate, suspend, or restrict your access and use of the Services. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.4-the-protocol) 2.4 The Protocol The Platform provides a web or mobile-based means to access the software protocols that govern the operation of Digital Assets (the “Protocol”). The Platform is one but not the exclusive means of accessing a Protocol. The Protocol is comprised of open-source or source-available self-executing smart contracts. We do not provide the services made available to you via the Protocol including, without limitation, staking, lending, bridging, or swapping Digital Assets You acknowledge and agree that the Platform is distinct from the Protocol, the Platform is one but not the exclusive means of accessing the Protocol, and your Protocol interactions or transactions are not interactions or transactions with us. You further understand and agree that we do not operate, own, or control the Protocol’s liquidity pools or control trade execution on the Protocol. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-3.-third-party-services-and-waiver) **3\. THIRD PARTY SERVICES AND WAIVER** The Platform may include, without limitation, links to sites, technology, applications, products, services, materials, or resources, provided or made available to you by third parties (“Third Party Services”). Your access and use of any Third Party Service are subject to the terms and policies of the applicable Third Party Service provider including without limitation W7, LLC d/b/a Wormhole Labs and its terms and conditions currently located at [http://www.portalbridge.com/](http://www.portalbridge.com/) and Alchemy Pay and its terms and conditions currently located at [http://www.alchemypay.org/terms-of-use/](http://www.alchemypay.org/terms-of-use/) . #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-3.1-third-party-services) 3.1 Third Party Services You acknowledge and agree that you are solely responsible for any and all costs, charges, and fees associated with your use of any Third Party Service. Our integration or inclusion of any Third Party Service does not imply endorsement or recommendation. You acknowledge and agree that we are not responsible for the availability, reliability, accuracy, or legitimacy of any Third Party Service (including any related websites, resources, or links displayed therein). Any dispute you have involving a Third Party Service including, without limitation, your intellectual property rights, is between you and the provider of such Third Party Service. We will not be responsible or liable for any damage or loss caused or alleged to be caused by, or in connection with, your use of, or reliance on, any Third Party Service. If, to the extent we permit, you grant express permission to a Third Party Service to access or connect to the Services through such third party or the Platform, you acknowledge that granting permission to any third party to take specific actions on your behalf does not relieve you of any of your responsibilities under these Terms. You are fully responsible for any act or omission of any third party. You acknowledge and agree that you will not hold us responsible for, and will indemnify us from, any liability arising out of or related to any act or omission of any third party with access to your Digital Asset Wallet, decentralized application, software, or other mechanism that you use to interact with the Services. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-3.2-waiver-of-claims) 3.2 Waiver of Claims To the maximum extent permitted by applicable law, you waive any and all claims, demands, and damages of every kind or nature, known or unknown, suspected or unsuspected, disclosed or undisclosed, against NAVI and its affiliates, and each of their respective officers, employees, agents, and successors arising out of or in any way related to any of the risks set forth herein. You also waive application of Section 1542 of the Civil Code of the State of California, or any similar statue or law of any other jurisdiction. Section 1542 reads as follows: “a general release does not extend to claims which the creditor does not know or suspect to exist in his or her favor at the time of executing the release, which if known by him or her must have materially affected his or her settlement with the debtor.” ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-4.-rewards) **4\. Rewards** In connection with the Services, you may earn or receive incentives, prizes, points, or rewards (collectively, “Rewards”). Any Reward that we may offer or make available through the Platform or the Services, from time to time and at any time, is subject to these Terms and any other applicable term or provision directly or indirectly related to or in connection with the Reward. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-4.1-general-reward-terms) 4.1 General Reward Terms By accepting these Terms, you hereby unconditionally and irrevocably confirm that you understand and accept any and all risks directly related to or in connection with Rewards. You further agree and consent that you grant all necessary rights for using your Digital Assets that you directly use or in connection with any program, campaign, or other similar activity we offer or make available. We reserve the right to change, modify, discontinue, or cancel any Reward we offer at our sole discretion, at any time, and without notice to you. Any information regarding the potential amount of a Reward is an estimate only. NAVI does not, in any way, represent, warrant, covenant, or guarantee the rate, multiplier, or other formula used to calculate Rewards (collectively, “Reward Rates”) will, at any time, remain the same and may fluctuate up or down from time to time. You acknowledge and agree that any representations, whether express or implied regarding any Reward Rate may be based on factors including but not limited to: (i) an estimate based on general market rates; (ii) special rates during promotional periods; and/or (iii) observations of available on-chain rates. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-4.2-slashing) 4.2 Slashing Some or all of the aggregate amount of the Rewards or other amounts may be programmatically destroyed as a penalty imposed by the applicable underlying blockchain network (“Slashing Penalty”). As a result, there may be non-payment of Rewards and the staked Digital Assets may be subject to a penalty. We will not be responsible or liable for any monetary or equitable damage you incur, including any legal or monetary loss arising directly or in connection with your access, use, or unauthorized access of the Services. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-4.3-no-guarantee-of-rewards) 4.3 No Guarantee of Rewards You understand and agree that we do not guarantee that you will earn or receive any Reward. We expressly disclaim all representations and warranties regarding any Reward including that any: (i) Reward will be received; (ii) Reward will occur on a continuous basis; (iii) Reward will be on an uninterrupted or error-free basis; and (iv) any particular Digital Asset will be available in connection with the Reward. NAVI has no liability for and expressly disclaims any loss, liability, or damage that you may incur directly, indirectly, or in connection with Rewards, including without limitation damages arising from or in connection with: (i) interruptions to the Services that you access or receive Rewards; (ii) the protocols of the applicable blockchain network distributing Rewards; and (iii) errors, defects, disruptions, discontinuances, and/or restrictions of Rewards. NAVI, our affiliates, and/or third-party service providers do not guarantee that you will receive any Reward. You acknowledge and agree that NAVI, our affiliates, and third-party service providers are not liable for any failure by the applicable blockchain network or other third party in disbursing any Reward. You acknowledge that past Rewards are not indicative of expected future Rewards. NAVI will not be responsible or liable for any Reward or Slashing Penalty that results from your access or use of the Services. NAVI, OUR AFFILIATES, AND/OR THIRD PARTY SERVICE PROVIDERS DO NOT GUARANTEE THAT YOU WILL RECEIVE ANY REWARD INCLUDING ANY VALIDATION REWARD OR STAKING REWARD. YOU ACKNOWLEDGE AND AGREE THAT NAVI, OUR AFFILIATES, AND THIRD PARTY SERVICE PROVIDERS ARE NOT LIABLE FOR ANY FAILURE BY THE APPLICABLE BLOCKCHAIN NETWORK OR OTHER THIRD PARTY IN DISBURSING ANY REWARD. YOU ACKNOWLEDGE THAT PAST REWARDS ARE NOT INDICATIVE OF EXPECTED FUTURE REWARDS. NAVI WILL NOT BE RESPONSIBLE OR LIABLE FOR ANY REWARD OR SLASHING PENALTY THAT RESULTS FROM YOUR ACCESS OR USE OF THE SERVICES. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-5.-risk-disclosures) **5\.** RISK DISCLOSURES You understand, accept, and agree to assume all of the various risks involved in interacting with the Platform, the Services, Digital Assets, Rewards, and all other services, products, or features directly related to or in connection with this Agreement including all risks set forth below. (a) Digital Assets, the features, functions, characteristics, operations, use, and other properties and/or software, networks, protocols, systems, or other technology that Digital Assets interact with are complex; and the terms, features, or risks described herein are not a complete or exhaustive list of all such features, risks, or complexities and may not be readily or fully understood due to such complexities. (b) If you act as a liquidity provider to the Protocol through the Platform, you understand that your Digital Asset may lose some or all value while supplied to the Protocol due to fluctuations in Digital Asset prices in a trading pair or liquidity pool. (c) Collateral for decentralized finance protocols and projects may be higher than similar centralized protocols and projects. (d) Staking rewards are not guaranteed and may be based on network performance, validator reliability, and other external factors. NAVI does not assure any specific level of returns or profitability from staking activities. (e) You understand that we do not create, own, or operate cross-chain bridges and we do not make any representation or warranty about the safety or soundness of any cross-chain bridge. (f) If you supply Digital Asset to a liquidity pool in an automated market maker (“AMM”), your deposited assets may lose relative value as the ratio of the Digital Assets in the liquidity pool fluctuate (“Impermanent Loss”). An AMM functions by allowing market forces to rebalance the ratio of Digital Assets in a liquidity pool. Once this rebalancing or Digital Assets occurs, you may end up withdrawing a different ratio of Digital Assets than when you deposited your Digital Assets into the liquidity pool. As such, you may perceive a “loss” in value in U.S. dollar terms due to the rebalancing of the Digital Assets in the liquidity pool. You represent that you understand the risk of Impermanent Loss. You further represent that you have carefully considered the likelihood of price divergence in a liquidity pool, and that you understand that we cannot control the amount of loss you incur. (g) Digital Assets will be irretrievably lost if sent to the wrong address. For instance, if the address is improperly formatted, contains an error, or for a different type of Digital Asset. (h) Blockchain networks and Digital Assets may be subject to forks or attacks on the security, integrity, and/or operation of the networks, including any network events. These events may affect features, functionality, operations, use, or properties of any Digital Asset or network and/or the value of any Digital Asset. (i) Any Digital Asset, the Services, the Platform, and/or the Protocol may be targeted by malicious persons or individuals who may attempt to disrupt the Services or steal Digital Assets including, without limitation, malware, hacking, phishing, double spending, smurfing, spoofing, sybil attacks, social engineering, majority mining, mining attacks, distributed denial of service, and blockchain forks. (j) The public nature of the Internet means that parts or the Internet may be unreliable or unavailable at any given time. Interruption, delay, corruption, loss of data, the loss of confidentiality or privacy through the course of data transmission, or malware transmission may occur when transmitting data via the Internet or other technology. This can result in your transaction(s) not being executed according to your instructions, at the requested time, and/or not at all. No technology is completely secure or safe. (k) Digital Assets may decrease in value or lose all value, in a short period of time or permanently, due to various factors including, without limitation, government or regulatory activity, the discovery of wrongful or illegal conduct, market manipulation, price distortion, insider dealing, market distortion, malicious wrongdoing or behaviors, changes to the Digital Asset’s nature or characteristics, suspension, or cessation of support for a Digital Asset by exchanges, public opinion, technical advancements, macroeconomic and political factors, and other factors outside of our control. (l) Digital Assets stored in a Digital Asset Wallet, on the Platform, through the Services (if applicable), or the Protocol are not protected deposits and may not be protected by any deposit protection scheme. Thus, Digital Assets have a reduced level and type of protection compared to fiat and other asset classes or types. (m) The creation of the Protocol may be abandoned for reasons including without limitation, lack of interest, funding, incapacitation of key developers or project members, lack of commercial success or prospects, or Force Majeure Event (defined below). You understand that there are no assurances regarding any benefit to interacting with the Services, even if the Protocol was partially or fully developed and launched. (n) The Services may undergo significant changes over time. We may also limit control over how other visitors and/or users can use the Services and what services are offered on or through the Platform. This could create the risk of the Services not meeting your expectations, for any number of reasons, including mistaken assumptions or analysis, a change in the design and/or implementation plans, or execution on or through the Services. (o) We currently rely on our service providers for certain aspects of our operations including cloud computing services and data centers that provide facilities, infrastructure, website functionality and access, components, and services, all of which are critical to our operations. Like most other online companies, because we rely on service providers, we face operational risk. Any interruption in the services provided by our service providers can impair our ability to provide the Services. (p) We do not directly manage the operation of the service providers we use including their data center facilities. Such third parties are vulnerable to financial, legal, regulatory, and labor issues, cybersecurity incidents, break-ins, computer viruses, denial-of-service attacks, sabotage, acts of vandalism, privacy breaches, service terminations, disruptions, interruptions, Force Majeure Events, and other events. (q) Blockchain transactions like Digital Asset transactions rely on smart contracts stored on various blockchains, cryptographic tokens generated by smart contracts, and other nascent software, applications, and systems that interact with blockchain-based networks. Such technologies are experimental, speculative, inherently risky, and subject to change. A defining feature of blockchain technology is its entries are immutable, which means, as a technical matter, they generally cannot be deleted or modified by anyone. You acknowledge and understand smart contracts dictate how funds and ownership of Digital Assets are distributed. (r) You acknowledge and understand that you may be subject to scams and/or other types of fraud perpetrated by parties outside of our control. It is your responsibility to be aware of and protect against such misconduct. In the event that you are subject to such fraud, there is a risk of loss of your Digital Assets. (s) All blockchain transactions include data and, in some circumstances, personal data about you. Many blockchain technologies store transaction data publicly and permanently. When you use such public blockchain technology, you intentionally make your transaction data public and acknowledge that this data cannot be deleted, removed, or reversed due to the nature of blockchain technology. (t) We are subject to an extensive and rapidly evolving regulatory landscape, and any changes to any law or regulation could adversely impact our ability to offer the Services and/or your use or access to the Services. Such regulatory change may also impact your legal obligations with respect to your use of the Services. (u) You understand that smart contract transactions automatically execute and settle, and blockchain-based transactions are irreversible when confirmed. You acknowledge and accept that the cost and speed of transacting with cryptographic and blockchain-based systems are variable and may increase dramatically at any time. (v) You understand that smart contract transactions automatically execute and settle, and blockchain-based transactions are irreversible when confirmed. You acknowledge and accept that the cost and speed of transacting with cryptographic and blockchain-based systems such as $SUI are variable and may increase dramatically at any time. You further acknowledge and accept the risk, where applicable, of selecting your slippage rate which expose you to additional cost or fees by the underlying blockchain network. (w) We may run promotional campaigns from time to time that are sponsored by our business partners with higher annual percentage rates to benefit users. These higher rates may be temporary and you should consider whether the relevant offer still meets your needs once the interest rate reverts to its normal level after the promotional period. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-6.-acknowledgements-and-covenants) **6\. ACKNOWLEDGEMENTS AND COVENANTS** By accessing or using the Services, you acknowledge, agree, represent, and warrant, in each case as applicable, each of the items contained in this Section. (a) You represent and warrant that you have received a copy of, have carefully read, understand, accept, and agree to assume all of the risks involved with the Services and Digital Assets including without limitation, the risks specifically set forth in this Agreement. You agree that we will not be liable to you for any loss, damage, expense, or liability that is or may relate to any of the risks specifically set forth in this Agreement. You represent and agree that you are able to bear any financial or other loss associated with or that may otherwise relate to your access or use of the Services. (b) You represent and warrant that you are not relying on (and will not at any time rely on) our communication (written or oral) as advice or as a recommendation to engage in any transaction or interaction involving the Services. You agree that we have not: (i) given any guarantee or representation as to the potential success, return, effect, or benefit (either legal, regulatory, tax, financial, accounting, or otherwise) of transacting in Digital Assets, and/or using the Services; and (ii) made any representation to you regarding the legality of transacting in Digital Assets and/or the Services under applicable law. In deciding to use the Services you have made your own independent decision that using the Services is suitable and appropriate for you. (c) You acknowledge and agree that we do not provide investment advice and any content on the Services or other communication channel should not be considered as tailored investment advice. You must seek professional advice regarding your particular financial, legal, technical, and other conditions prior to commencing your use of the Services. You represent and warrant that you fully understand all risks associated with using the Services and you have the necessary experience, understanding, and risk tolerance for using the Services including the necessary experience and knowledge to enter into any use or transaction regarding the Services. You acknowledge and accept any and all risks regarding the Services and are responsible for conducting your own independent analysis of the risks specific to your access or use of the Services. WE MAKE NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, AS TO THE LAWFULNESS OF YOUR PARTICIPATION IN THE SERVICES, PLATFORM, REWARDS, AND/OR ANY THIRD PARTY SERVICE, NOR SHALL ANY PERSON AFFILIATED, OR CLAIMING AFFILIATION, WITH US HAVE AUTHORITY TO MAKE ANY SUCH REPRESENTATIONS OR WARRANTIES. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-7.-prohibited-use-and-representations) **7\. PROHIBITED USE AND REPRESENTATIONS** #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-7.1-prohibited-use) 7.1 Prohibited Use You may not use the Services to engage in the following categories of activity (each a “Prohibited Use”). The specific types of activities listed below are representative, but not exhaustive. (a) Unlawful Activity. Activity which, in any way, would violate, or assist in violation of, any law, statue, ordinance, or regulation, sanctions programs administered in the countries where we offer the Services, or which would involve proceeds of any unlawful activity; publish, distribute, or disseminate any unlawful material or information. (b) Abusive of Others. Interfere with another individual’s access to or use of the Services including but not limited to exploiting, harming, or attempting to exploit or harm minors in any way by exposing them to inappropriate content; defame, abuse, extort, harass, stalk, threaten, or otherwise violate or infringe the legal rights of others; ask for personally identifiable information, or otherwise; transmit, or procure the sending of, any advertising or promotional material, including any “junk mail,” “chain letter,” “spam,” or any other similar solicitation; to impersonate or attempt to impersonate NAVI, an employee, another user, or any other person or entity (including, without limitation, by using email addresses, screen names, similarly named or commonly misspelled URLs, or associated blockchain identities); engage in any other conduct that restricts or inhibits anyone's use or enjoyment of the Services; incite, threaten, encourage, or promote hate, racial intolerance, or violent acts against others. (c) Fraud. Activity which operates to deceive or defraud, or attempt to deceive or defraud, us, any users or any other person, including without limitation providing any false, inaccurate, or misleading information whether directly through the Services or through an external means that affects the Services with the intent to unlawfully obtain the property of another or to provide knowingly or recklessly false information, including in any way that causes inaccuracy among the content on the Services. (d) Abusive Activity. To cause the Services, the Platform underlying blockchain network(s) or technologies, or any other functionality with which the Services interact, to work other than as intended; damage our reputation, or impair any of our legal rights or interests; engage in any activity or behavior that violates any applicable laws concerning, or otherwise damages, the integrity of the Services or any other service or software which relies on the Services; use the Services in any manner that could disable, overburden, damage, impair, or interfere with the Services, including the ability to engage in real time activities through the Services; use any robot, spider, or other automatic device, process, or means to access the Services for any purpose, including monitoring or copying any of the material on the Services; attempt to gain unauthorized access to, interfere with, damage, or disrupt any parts of the Services, the server on which the Services or information in connection with the Services is stored, or any server, computer, or database connected to the Services, including any underlying blockchain; through the use of a VPN software or any other privacy or anonymization tools or techniques intended to circumvent, or attempt to circumvent, any restrictions that apply to the Services. (e) Intellectual Property Infringement. Violate the legal rights (including the rights of publicity and privacy) of others or contain any material that could give rise to any civil or criminal liability under applicable law or regulation or that otherwise may be in conflict with these Terms; engage in transactions involving items that infringe or violate any copyright, trademark, right of publicity or privacy, or any other proprietary right under the law, including but not limited to sales, distribution, or access to counterfeit music, software, or other licensed materials without the appropriate authorization from the rights holder; use of our intellectual property, name, or logo, including use of any of our trade or service marks, without our express consent or in a manner that otherwise harms us or our brand; any action that implies an untrue endorsement by or affiliation with us. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-7.2-representations-and-warranties) 7.2 Representations and Warranties Without limitation to any other term or provision in this Agreement, you represent and warrant to us that: (a) You will not engage in any Prohibited Use; (b) you will abide by any and all applicable laws of the jurisdiction where you are located, all local, national, and international practices regarding Internet use, and all network agreements, rules, and procedures related to or in connection with the Services; (c) your interactions and transactions in connection with the Services will comply with applicable law and regulation in your jurisdiction; (d) you have obtained sufficient information about the Services, Digital Assets, Rewards, Digital Asset Wallets, the Platform, the Protocol, and all other services, applications, and features directly related to or in connection with the Services to make an informed decisions in regard to your use of the Services; (e) you will bear the full responsibility for any and all activities that occurs in connection with your use or access to the Services including, without limitation: (i) any transaction or interaction on the Platform or in connection with the Services; (ii) disclosing or publishing information; (iii) clicking to agree with various agreements; and (iv) uploading and submitting various documents or information; and (f) you are the legal and rightful owner of the Digital Assets in the Digital Asset Wallet, and any and all Digital Assets you use in connection with the Services. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-8.-changes-suspension-and-termination) **8\. CHANGES, SUSPENSION, AND TERMINATION** We may, at our sole discretion and without liability to you, with or without prior notice and at any time, modify or discontinue, temporarily or permanently, all or any part of the Services. You acknowledge that our decision to take certain actions including limiting, suspending, or terminating your access to the Services, may be based on our confidential criteria that are essential to our risk management and security protocols. You agree that we are under no obligation to disclose the details of our risk management and security procedures to you. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-8.1-no-liability) 8.1 No Liability We will not be liable for any losses suffered by you resulting from any modification of the Services or from any suspension or termination of your access to all or a portion of the Services. You acknowledge that Digital Asset values may fluctuate during any period during which the Services have been suspended and agree that we will have no liability for any such fluctuations. You also acknowledge that in the event of permanent suspension or termination of the Services, the Digital Assets associated with your account may be lost and that we will have no liability for any such losses. You waive and hold us and our affiliates, licensees, and service providers harmless from any claims resulting from any action taken by us and/or any of the foregoing parties during, or taken as a consequence of, investigations by us, such parties, or law enforcement authorities. We have the right and sole discretion to cooperate fully with any law enforcement authorities or court order requesting or directing us to disclose the identity or other information of anyone posting any materials on or through the Services. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-8.2-effect-of-termination) 8.2 Effect of Termination In the event of the termination of your right to access or use any part or all of the Services, discontinuation of the Services, or other termination of your right to access any portion or all of the Services we may: (i) block your Digital Wallet Address from accessing the Services; (ii) delete or deactivate your profile and all related information and/or materials associated therewith, without liability to you; (iii) cancel any open transaction, or other use of the Services that are pending at the time of discontinuation or termination; (iv) in the event that your access is terminated due to a Prohibited Use, you will be subject to immediate sanction, including without limitation subjecting to disgorgement and/or recoupment any and all Rewards; and/or (v); any and all amounts payable by you to us will immediately become due. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.-intellectual-property-rights) **9\. INTELLECTUAL PROPERTY RIGHTS** #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.1-navi-materials) 9.1 NAVI Materials The Services and its entire contents, features, and functionality including but not limited to all information, software, text, displays, images, video, and audio, the design, selection, and arrangement thereof, and the “look and feel” of the Services, except any open source software, are owned by us (“NAVI Materials”), its licensors, or other providers of such material and are protected by applicable and/or international copyright, trademark, patent, trade secret, and other intellectual property or proprietary rights laws. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.2-limitations-on-use) 9.2 Limitations on Use In connection with your use of the Services, you may use the NAVI Materials solely as authorized by us for as long as we permit you to continue accessing the Services. Without limiting the foregoing, you agree not to: (i) resell, lease, lend, share, distribute, or otherwise permit any third party to use the Services, NAVI Materials; (ii) modify or create derivative works of the Services or NAVI Materials, or any portion thereof, or any data or information received by you in connection therewith; (iii) frame, display, or incorporate the Services or NAVI Materials in any website or any other work of authorship; (iv) decompile, disassemble, reverse engineer, or attempt to discover the source code of the Services or NAVI Materials; (v) use the Services or NAVI Materials to design, develop, or create any competing product or service; (vi) use the Services or NAVI Materials for any commercial or noncommercial purpose other than their intended purposes determined at our sole discretion; (vii) suggest, imply, or misrepresent any affiliation, connection, or partnership with, or endorsement by, NAVI; or (viii) use the Services or NAVI Materials in any service bureau environment. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.3-rights-we-grant-you) 9.3 Rights We Grant You We hereby permit you to use and access the Services, provided that you comply with these Terms. If any software, content, or other materials owned or controlled by us are distributed to you as part of your use of the Services, we hereby grant you a non-sublicensable, non-transferable, and non-exclusive right and license to execute, access, and display such software, content, and materials provided to you as part of the Services, in each case for the sole purpose of enabling you to use the Services as permitted by these Terms. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.4-reservation-of-rights) 9.4 Reservation of Rights If your use or access to the Services is in breach of these Terms, your right to access the Services will stop immediately and you must, at our sole option, return or destroy any copies of the materials that you made directly or indirectly from the Services. No right, title, or interest in or to the Services is transferred to you, and all rights not expressly granted are reserved by us. You may freely use any open-source materials up to the limits provided, but in accordance with any requirements placed, by those materials’ open-source licenses. Any use of the Services not expressly permitted by these Terms is a breach of these Terms and may violate copyright, trademark, and other applicable laws. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.5-trademarks) 9.5 Trademarks Our legal name, the terms “NAVI,” “NAVI Protocol,” and any and all other related names, logos, product and/or service names, designs, and slogans are trademarks of NAVI, its affiliates, or licensors. You agree not to use such marks without our prior express written permission. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-10.-platform-content) **10\. PLATFORM CONTENT** We do not warrant the accuracy, completeness, or usefulness of any materials or information that we or a third party present on or through the Services and such information is made available solely for general information and education purposes. Any material, content, or information posted to the Services should not be construed as an intention to form a contract, and in no case should any information be construed as an offer from NAVI to buy, sell, exchange, or otherwise transact with you using Digital Assets. We disclaim all liability and responsibility arising from any reliance placed on such information or materials by you, any other user or person who may be informed of any of the Services contents, or by the actions or omissions of others interacting with the Services. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-11.-feedback) **11\. FEEDBACK** Any questions, suggestions, ideas, feedback, reviews, or other information or materials regarding the Services that you provide us with (collectively, “Feedback”) are non-confidential. NAVI will be entitled to the unrestricted use and dissemination of Feedback for any purpose, commercial or otherwise without acknowledgment, attribution, or compensation to you. You hereby assign to NAVI all right, title, and interest to Feedback together with all associated intellectual property rights and waive any claim for, acknowledgement or compensation based on any Feedback or any modifications made based on any Feedback. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-12.-relationship) **12\. RELATIONSHIP** NAVI is not your broker, intermediary, agent, or advisor and has no fiduciary relationship or obligation to you in your use of the Services. NAVI does not provide investment, tax, or legal advice, and you are solely responsible for any transaction, investment, strategy, decision, or other act that you make when using the Services. We may provide educational material or information on the Platform, through the Services, social media account, or other channel of communication. No communication or information provided to you by NAVI is intended as, or shall be considered or construed as, advice. You acknowledge and agree to the fullest extent such duties or liabilities are afforded by law or by equity, such duties and liabilities are hereby irrevocably disclaimed, waived, and eliminated, and that we shall be held completely harmless in relation thereof. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-13.-charges-and-fees) **13\. CHARGES AND FEES** We may, in our sole discretion and at any time, set or modify the fees for any or all of the Services. Except as required by law, fees are non-refundable. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-13.1-our-fees) 13.1 Our Fees You agree to pay us all applicable fees associated with your use of the Services. We may change the fees and any fee schedule at any time, without notice. Any fee we charge may vary between Digital Assets or Digital Asset Pair. We charge a fee when you borrow Digital Assets through the Services. You are presented with all fees we charge when borrowing Digital Assets before entering into the transaction. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-13.2-third-party-fees) 13.2 Third Party Fees You may be charged fees for your use or access to the Protocol through a third party interface. You are responsible for doing your own diligence on any third party interface to understand any applicable fee or charge that the third party interface provider may charge you. Under no circumstances will NAVI incur any liability, of any kind, to you arising from or relating to fees charged to you by your access or use to the Protocol via a third party interface or any Third Party Service. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-13.3-blockchain-fees) 13.3 Blockchain Fees Blockchain transactions require the payment of transaction fees to the appropriate network’s nodes, miners, validators, or operators (“Blockchain Fees”). You will be solely responsible to pay the Blockchain Fees for any transaction that you initiate via the Services. Blockchain Fees are neither levied directly by NAVI nor paid to or shared with NAVI in any way, but rather are determined by your use of the Services and the rules placed by corresponding blockchain communities at large. You acknowledge and agree that NAVI has no control over Blockchain Fees (including without limitation their applicability, payment, amounts, transmission, intended operation, and effectiveness) whether related to your use of the Services or otherwise, and in no event will NAVI be responsible to you or any other party for the payment, repayment, refund, disbursement, indemnity, or for any other aspect of your use or transmission of Blockchain Fees. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-14.-warranty-disclaimer) **14\. WARRANTY DISCLAIMER** NAVI has no oversight on or control over any particular Digital Asset, Protocol, or blockchain network. You are responsible for your use of the Services, the functionalities that you enable, transactions engaged on the Protocol through the Services, and access or use of the information derived thereof. You are also solely responsible for complying with all applicable laws related to transactions and activities that directly or indirectly incorporate our provision of the Services. You acknowledge and understand that we are not registered nor licensed with, nor have the Services or the software contained therein been reviewed by any securities, commodities, or other financial or banking regulator. You further acknowledge and understand that we cannot and do not guarantee or warrant that files available for download from the Services will be free of viruses or other destructive code. You are responsible for implementing sufficient procedures and checkpoints to satisfy your particular requirements for: (i) an appropriate blockchain based utility; (ii) anti-virus protection and accuracy of data input and output; (iii) your participation in and use of the Protocol and related technologies; and (iv) maintaining a means external to our site to reconstruct any lost data. TO THE FULLEST EXTENT PROVIDED BY LAW, IN NOT EVENT WILL NAVI, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES BE LIABLE FOR ANY LOSS OR DAMAGE CAUSED BY A DISTRIBUTED DENIAL-OF-SERVICE ATTACK, MAN-IN-THE-MIDDLE ATTACK, VIRUS, OR OTHER TECHNOLOGICALLY HARMFUL MATERIAL THAT MAY INFECT YOUR COMPUTER EQUIPMENT, COMPUTER PROGRAMS, DATA, OR OTHER PROPRIETARY MATERIAL DUE TO YOUR USE OF THE SERVICES, PLATFORM, OR NAVI MATERIALS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF NAVI THROUGH THE SERVICES, OR YOUR DOWNLOADING OF ANY MATERIAL POSTED ON IT, OR ON ANY THIRD PARTY WEBSITE LINKED TO IT. YOUR USE OF THE SERVICES AND ANY SERVICE CONTENT IS AT YOUR SOLE RISK. THE SERVICES, NAVI MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, PROVIDED BY OR ON BEHALF OF NAVI ARE PROVIDED ON AN “AS IS’’ AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT LEGALLY PERMISSIBLE, IN NOT EVENT WILL NAVI, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES BE LIABLE FOR, AND EXPLICITLY DISCLAIM, ANY AND ALL REPRESENTATIONS OR WARRANTIES OF ANY KIND RELATED THE SERVICES, NAVI MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING (WITHOUT LIMITATION) THE WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. NEITHER NAVI, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES MAKES ANY WARRANTY OR REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, ACCURACY, OR AVAILABILITY OF THE SERVICES, NAVI MATERIALS, THE PROTOCOL, THE PLATFORM, AND/OR ANY PRODUCT, SERVICE, FEATURE, OR OTHER ITEM PROVIDED BY OR ON BEHALF OF NAVI. NAVI, ITS AFFILIATES, AND SERVICE PROVIDERS, OR ANY OF THEIR RESPECTIVE OFFICERS, DIRECTORS, AGENTS, JOINT VENTURERS, EMPLOYEES, OR REPRESENTATIVES DO NOT REPRESENT OR WARRANT THAT: (I) ACCESS TO THE SERVICES, NAVI MATERIALS, THE PLATFORM, THE PROTOCOL, AND ANY OTHER PRODUCT, SERVICE, FEATURE, REWARD, OR ITEM PROVIDED BY OR ON BEHALF OF NAVI WILL BE CONTINUOUS, UNINTERRUPTED, TIMELY, WITHOUT DELAY, ERROR-FREE, SECURE, OR FREE FROM DEFECTS; (II) THE INFORMATION CONTAINED OR PRESENTED ON THE SERVICES, NAVI MATERIALS, THE PROTOCOL, OR THE PLATFORM IS ACCURATE, RELIABLE, COMPLETE, CONCISE, CURRENT, OR RELEVANT; (III) THE SERVICES, NAVI MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, REWARD, OR ANY SOFTWARE CONTAINED THEREIN WILL BE FREE FROM DEFECTS, MALICIOUS SOFTWARE, ERRORS, OR ANY OTHER HARMFUL ELEMENTS, OR THAT ANY OF SUCH WILL BE CORRECTED; OR (III) THE SERVICES, NAVI MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD, WILL MEET ANY USER’S EXPECTATIONS. NO INFORMATION OR STATEMENT THAT WE MAKE, INCLUDING DOCUMENTATION OR PRIVATE COMMUNICATION, SHOULD BE TREATED AS OFFERING ANY WARRANTY CONCERNING THE SERVICES, NAVI MATERIALS, PLATFORM, PROTOCOL, REWARDS, AND ANY OTHER SERVICE, PRODUCT, FEATURE, OR REWARD PROVIDED BY OR ON BEHALF OF NAVI. WE DO NOT ENDORSE, GUARANTEE, OR ASSUME ANY LIABILITY OR RESPONSIBILITY FOR ANY CONTENT, ADVERTISEMENTS, OFFERS, STATEMENTS, OR ACTIONS BY ANY THIRD PARTY EITHER REGARDING THE SERVICES, NAVI MATERIALS, THE PLATFORM, THE PROTOCOL, REWARDS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF NAVI. THE FOREGOING DOES NOT AFFECT ANY WARRANTIES THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-15.-indemnification) 15\. INDEMNIFICATION You agrees to defend, indemnify, and hold harmless NAVI, its affiliates, licensors, and service providers, and their respective officers, directors, employees, contractors, agents, licensors, suppliers, successors, and assigns from and against any claims, liabilities, damages, judgments, awards, losses, costs, expenses, or fees (including reasonable attorneys’ fees) arising out of or relating to: (i) your violation of these Terms; (ii) your use of Services; (iii) your interactions or transaction with or on the Platform, through the Services, or the Protocol, and any other service, product, application, program, or feature accessible on or through the Services; (iv) your use of or reliance on the Platform’s content, the Services, NAVI Materials, and/or any other services or products other than as expressly authorized in these Terms; (v) your access or use of a Third Party Service including any liquidity aggregator; (vi) engaging in any Prohibited Use, whether alone or in concert with others such as front-running; (vii) any third party’s access or use of the Services with or without your assistance, using any device, account, profile, Digital Asset Wallet, or other mechanism that you own or control; (viii) congestion in the SUI or other blockchain network available on the Platform; (ix) failed transactions when depositing multiple Digital Assets into a liquidity pool; and/or (x) your use of any Software Development Kit (“SDK”), Command-Line Interface (“CLI”), or other software offered by us or provided through the Platform or Services. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-16.-limitation-of-liability-disclaimer-of-damages) **16\. LIMITATION OF LIABILITY; DISCLAIMER OF DAMAGES** TO THE FULLEST EXTENT PROVIDED BY LAW, IN NO EVENT WILL NAVI, ITS AFFILIATES, OR THEIR LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS, OR DIRECTORS BE LIABLE FOR DAMAGES OF ANY KIND, UNDER ANY LEGAL THEORY, ARISING OUT OF OR IN CONNECTION WITH YOUR USE, OR INABILITY TO USE THE SERVICES, NAVI MATERIALS, THE PLATFORM, THE PROTOCOL, AND/OR ANY PRODUCT, SERVICE, REWARD, DIGITAL ASSET, OR OTHER ITEM PROVIDED BY OR ON BEHALF OF NAVI, INCLUDING ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES INCLUDING BUT NOT LIMITED TO, PERSONAL INJURY, PAIN AND SUFFERING, EMOTIONAL DISTRESS, LOSS OF REVENUE, LOSS OF PROFITS, LOSS OF BUSINESS OR ANTICIPATED SAVINGS, LOSS OF USE, LOSS OF GOODWILL, LOSS OF DATA, AND WHETHER CAUSED BY TORT (INCLUDING NEGLIGENCE), BREACH OF CONTRACT, OR OTHERWISE, EVEN IF FORESEEABLE. THIS DISCLAIMER OF LIABILITY EXTENDS TO ANY AND ALL DAMAGES CAUSED BY ANY THIRD PARTY (INCLUDING, WITHOUT LIMITATION, THOSE CAUSED BY FRAUD, DECEIT, OR MANIPULATION), WHETHER OR NOT A USER, OR ANY FAILURE, EXPLOIT, OR VULNERABILITY OF THE SERVICES, THE PLATFORM, THE PROTOCOL, NAVI MATERIALS, AND ANY PRODUCT, SERVICE OR OTHER ITEM PROVIDED BY OR ON BEHALF OF NAVI. TO THE FULLEST EXTENT PROVIDED BY LAW, IN NO EVENT WILL THE COLLECTIVE LIABILITY OF NAVI, AND ITS SUBSIDIARIES, AFFILIATES, LICENSORS, SERVICE PROVIDERS, EMPLOYEES, AGENTS, OFFICERS, AND DIRECTORS, TO ANY PARTY (REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, OR OTHERWISE) EXCEED THE GREATER OF $100 OR THE AMOUNT YOU HAVE PAID DIRECTLY TO NAVI FOR THE SERVICES IN THE LAST SIX MONTHS OUT OF WHICH LIABILITY AROSE. THE FOREGOING DOES NOT AFFECT ANY LIABILITY THAT CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.-dispute-resolution-and-mandatory-arbitration) **17\. DISPUTE RESOLUTION AND MANDATORY ARBITRATION** Please read this section carefully because it waives any right to participate in any class action or other representative action or proceeding. This section requires you to arbitrate certain disputes and limits the ways in which you can seek relief, including by precluding you from suing in court or having a jury trial. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.1-waiver-of-class-actions-and-right-to-jury-trial) 17.1 Waiver of Class Actions and Right to Jury Trial To the extent permissible by law, any claim, controversy, or dispute arising out of or related to this Agreement, or any products or services provided in connection with the Services (each a “Dispute”) must be brought in your individual capacity, and not as a plaintiff or class member in any putative class, collective action, or representative proceeding (collectively “Class Action Waiver”). The arbitrator may not consolidate more than one person’s claims or engage in any arbitration on behalf of a class. You agree that, by entering into this Agreement, you are waiving the right to a trial by jury and the right to participate in a class action. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.2-informal-resolution) 17.2 Informal Resolution Before filing a claim against NAVI, you agree to try to resolve the Dispute by first contact [discord](https://discord.com/invite/R6Xkbee8Xq) with a description of your claim and proof of your relationship with NAVI. If we can’t resolve the Dispute within sixty days of our receipt of your first request, you or NAVI may then submit the Dispute to binding arbitration as provided herein. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.3-arbitration-agreement) 17.3 Arbitration Agreement All Disputes between you and NAVI must be resolved by final and binding arbitration. By agreeing to binding arbitration, you and NAVI expressly waive the right to formal court proceedings including without limitation trial by jury and class action. This Agreement affects interstate commerce, and the enforceability of this section will be substantively and procedurally governed by the Federal Arbitration Act 9 U.S.C. § 1, et. Seq. (“FAA”). #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.4-conducting-arbitration) 17.4 Conducting Arbitration The arbitration shall be conducted by the International Chamber of Commerce (“ICC”) under its Commercial Arbitration Rules (“ICC Rules”) then in effect. If you are a consumer, the most recent version of the ICC Rules can be accessed [here](https://iccwbo.org/dispute-resolution/dispute-resolution-services/arbitration/rules-procedure/2021-arbitration-rules/) . These Terms shall govern any conflict between the ICC Rules and these Terms. The location and type of hearing shall be determined in accordance with the ICC Rules. Further, a party’s right to request a hearing shall also be determined in accordance with the ICC Rules. Unless otherwise ordered by an arbitrator or pursuant to the ICC Rules, any in-person arbitration shall be in English and held remotely to the maximum extent and administered in New York, New York, or another mutually agreeable location. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.5-confidentiality) 17.5 Confidentiality NAVI, the arbitrator, and you, will each maintain the confidentiality of any arbitration proceedings, judgments, and awards including information shared and produced during the arbitration. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.6-arbitration-time-for-filing) 17.6 Arbitration Time for Filing Any arbitration must be commenced by filing a demand for arbitration within one year after the date the party asserting the claim first knows or reasonably should know of the act, omission or default giving rise to the claim. If applicable law prohibits a one year limitation period for asserting claims, any claim must be asserted within the shortest time period permitted by applicable law. If a claim is not filed within such period, the Dispute is permanently barred. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.7-severability) 17.7 Severability If any portion of this section is found to be unenforceable or unlawful for any reason, the unenforceable or unlawful provision shall be severed from these Terms and such severance of the provision(s) shall have no impact whatsoever on the remainder of this section. Further, to the extent that any claims must therefore proceed on a class, collective, consolidated, or representative basis, such claims must be litigated in a civil court of competent jurisdiction and not in arbitration, and the parties agree that litigation of those claims shall be stayed pending the outcome of any individual claims in arbitration. Lastly, if any provision in this section is found to prohibit an individual claim seeking public injunctive relief, such provision shall have no effect to the extent relief is allowed to be sought outside of arbitration. The remainder of this section shall remain in full force and effect. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.8-modification) 17.8 Modification Notwithstanding any term or provision in this Agreement to the contrary, you and NAVI agree that if NAVI makes any future material change to this section, we will notify you. Your continued use of the Services including the acceptance of features and services offered following the posting of changes constitutes your acceptance of any such changes. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-18.-governing-law) **18\. GOVERNING LAW** This Agreement shall be governed by and construed in accordance with the laws of Panama. Any disputes not subject to arbitration under this Agreement shall be resolved exclusively by the courts of Panama. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-19.-amendments-to-this-agreement) **19\. AMENDMENTS TO THIS AGREEMENT** We reserve the right to amend this Agreement, any other agreement or document incorporated or referenced in this Agreement, and any policy governing the use of the Services at any time and in our sole discretion. Any amendment will be effective immediately and you waive any right you may have to receive any specific notice of such amendment. Your continued use of the Services after posting of such amendment constitutes your agreement to be bound by all then-in-effect amendments to this Agreement, regardless of whether you have actually reviewed them. ### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.-miscellaneous-terms) **20\. MISCELLANEOUS TERMS** #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.1-assignment) 20.1 Assignment These Terms, and any other document, material, or information referenced herein is particular to you and any attempt that you make to assign, novate, or transfer your rights, interests, liabilities, and/or obligations is null and void, unless you have received NAVI’s prior written consent. NAVI reserves the right to assign our rights without restriction, including without limitation to any of our affiliates or subsidiaries, or to any successor in interest of any business associated with the Services. Subject to the foregoing, these Terms will bind and inure to the benefit of the parties and their successors and permitted assigns. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.2-term-and-survival) 20.2 Term and Survival We reserve the right to change, suspend or discontinue, or terminate, restrict, or disable your use of or access to, parts or all of the Services or their functionality at any time at our sole discretion and without notice. All sections of this Agreement that by their nature should survive termination shall survive termination. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.3-nonwaiver-of-rights) 20.3 Nonwaiver of Rights Our failure or delay in exercising any right, power, or privilege under these Terms shall not operate as a waiver thereof. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.4-severability) 20.4 Severability If any provision of this Agreement shall be determined to be invalid or unenforceable under any rule, law, or regulation, or any governmental agency whether local, state, or federal, such provision shall be interpreted to accomplish the objectives of the provision to the greatest extent possible under any applicable law, and the validity or enforceability of any other provision of the Terms shall not be affected. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.5-headings) 20.5 Headings Headings of sections are for convenience only and shall not be used to limit or construe such sections. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.6-force-majeure) 20.6 Force Majeure You acknowledge and consent that the Services are provided by us according to our current technological capability and other business conditions. While we have made every effort to ensure continuity and security of the Services, we are unable to completely foresee and hedge against all legal, technological, and other risks. NAVI will not be held liable for delays, failure in performance, or interruption of Services that result directly or indirectly from any cause or condition beyond our reasonable control. Such instances include: (i) acts of God such as earth earthquakes, fires, cyclones, explosions, typhoons, monsoons, landslides, lightning, storms, tempests, pandemics, droughts or meteors; (ii) acts of war, whether declared or undeclared, including invasion, act of a foreign enemy, hostilities between nations, civil insurrection, or militarily usurped power; and acts of terrorism; (iii) civil disorder, such as acts of a public enemy, malicious damage, terrorism, sabotage, or civil unrest; (iv) embargoes or sanctions (such as confiscation, nationalization, requisition, expropriation, prohibition, restraint or damage to property by or under the order of any government or governmental authority; (v) unnatural disasters, such as ionizing radiation or contamination by radioactivity from any nuclear waste or from combustion of nuclear fuel; (vi) labor disputes, including strikes, blockades, lock-outs, or other industrial disputes; (vii) failure of telecommunication outlets, including the internet, communications networks and facilities, or other infrastructure, systems, operations or of equipment relevant to the provision or use of the Services; (viii) data breaches or data-processing failure or incomplete processing; and/or (ix) changes in laws or regulations that may materially affect the Digital Assets and/or blockchain industries (collectively, “Force Majeure Events”). #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.7-taxes) 20.7 Taxes It is your sole responsibility to determine whether and to what extent any taxes apply to activity you conduct through the Services; and to withhold, collect, report, and remit the correct amounts of taxes to the appropriate tax authorities. No communication or information provided to you by NAVI is intended as, or considered or construed as, legal or tax advice. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.8-notice) 20.8 Notice Any notices or other communications provided by us under these Terms including those regarding modifications to these Terms will be posted online, in the Services, or through other electronic communication. You agree and consent to receive electronically all communications, agreements, documents, notices, and disclosures that we provide in connection with your use of the Services. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.9-privacy) 20.9 Privacy To understand how NAVI collects, uses, and shares information about you, please review our \[[Privacy Policy](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy)\ \]. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.10-third-party-beneficiaries) 20.10 Third Party Beneficiaries Nothing in this Agreement, expressed or implied, is intended to confer upon any person, other than the parties and their successors and permitted assigns, any of the rights hereunder. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.11-entire-agreement) 20.11 Entire Agreement These Terms and every other term or provision applicable to you, including any document incorporated by reference herein, constitute the entire agreement and understanding between you and NAVI as to the subject matter hereof, and supersede any and all prior discussions, agreements, and understandings of any kind (including any prior versions of these Terms). Unless otherwise specifically stated, these Terms govern and control any conflict between these Terms and any other agreement you may have with NAVI. #### [](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.12-translation) 20.12 Translation These Terms are set forth in the English language and all communications including any notices or information being transmitted shall be in English. In the event that these Terms or any part of it is translated (for any proceedings, for your convenience, or otherwise) into any other language, the English language text of these Terms shall prevail. [PreviousNAVI Media Kit (logos)](https://naviprotocol.gitbook.io/navi-protocol-docs/dao-and-token/navi-media-kit-logos) [NextPrivacy Policy](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/privacy-policy) Last updated 3 months ago * [1\. WHO MAY USE THE SERVICES](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-1.-who-may-use-the-services) * [2\. INTERACTING WITH THE SERVICES](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-2.-interacting-with-the-services) * [3\. THIRD PARTY SERVICES AND WAIVER](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-3.-third-party-services-and-waiver) * [4\. Rewards](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-4.-rewards) * [5\. RISK DISCLOSURES](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-5.-risk-disclosures) * [6\. ACKNOWLEDGEMENTS AND COVENANTS](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-6.-acknowledgements-and-covenants) * [7\. PROHIBITED USE AND REPRESENTATIONS](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-7.-prohibited-use-and-representations) * [8\. CHANGES, SUSPENSION, AND TERMINATION](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-8.-changes-suspension-and-termination) * [9\. INTELLECTUAL PROPERTY RIGHTS](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-9.-intellectual-property-rights) * [10\. PLATFORM CONTENT](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-10.-platform-content) * [11\. FEEDBACK](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-11.-feedback) * [12\. RELATIONSHIP](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-12.-relationship) * [13\. CHARGES AND FEES](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-13.-charges-and-fees) * [14\. WARRANTY DISCLAIMER](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-14.-warranty-disclaimer) * [15\. INDEMNIFICATION](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-15.-indemnification) * [16\. LIMITATION OF LIABILITY; DISCLAIMER OF DAMAGES](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-16.-limitation-of-liability-disclaimer-of-damages) * [17\. DISPUTE RESOLUTION AND MANDATORY ARBITRATION](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-17.-dispute-resolution-and-mandatory-arbitration) * [18\. GOVERNING LAW](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-18.-governing-law) * [19\. AMENDMENTS TO THIS AGREEMENT](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-19.-amendments-to-this-agreement) * [20\. MISCELLANEOUS TERMS](https://naviprotocol.gitbook.io/navi-protocol-docs/legal-and-support/terms-of-service#id-20.-miscellaneous-terms) --- # Build with NAVI Protocol | NAVI Protocol Developer Docs **Build with NAVI Protocol** is a comprehensive guide for developers looking to integrate and interact with NAVI’s smart contracts. This guide offers in-depth explanations of key modules such as `lending_core`, `flashloan`, and `oracles`, detailing their functionalities and use cases. Additionally, the documentation includes step-by-step instructions for: * Retrieving Pool data and Oracle Price Feeds * Interacting with NAVI Protocol through the SDK * Managing user-specific data, including account caps and rewards This guide aims to streamline the development process, designed with developers in mind, enabling efficient and seamless integration with NAVI’s decentralized financial infrastructure. [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/#getting-started) Getting started ------------------------------------------------------------------------------------------------------ [📖Smart Contract Overview](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview) [🕓Decentralized Oracle](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle) [🗺️Contract Configuration](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration) [🎧Contract Integration with NAVI](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi) [❓FAQ](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq) All NAVI Smart Contract and SDK below are fully audited by Sui's official auditing firm partner OtterSec. Audit Report: [![Logo](https://naviprotocol.gitbook.io/navi-protocol-docs/~gitbook/image?url=https%3A%2F%2F1873373287-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Forganizations%252FdcxQ7e5pivSbceCjCqQ8%252Fsites%252Fsite_zXVRU%252Ficon%252FAdfnvhfqxmQMsWEnP65p%252Fnew_navi.png%3Falt%3Dmedia%26token%3Def7b7b4b-3fca-4078-826f-4fd9f9f4655e&width=48&height=48&sign=66a076d&sv=2)Audit Report | Navi Protocol - docsnaviprotocol.gitbook.io](https://naviprotocol.gitbook.io/navi-protocol-docs/security/audit-report) [NextSmart Contract Overview](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview) Last updated 10 months ago --- # Decentralized Oracle | NAVI Protocol Developer Docs [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#overview) Overview ------------------------------------------------------------------------------------------------------------ The NAVI decentralized oracle consistently produces stable and reliable prices by integrating data from multiple trusted oracle providers on Sui. Currently, we have selected Pyth and Supra as our price providers. To learn more, please refer to our [medium post](https://medium.com/@navi.protocol/navi-protocols-upgraded-decentralized-oracle-enhancing-security-and-robustness-with-pyth-and-248740c55f7b) . The Oracle operates on a **PUSH** model, allowing anyone to trigger updates. To ensure the protocol's security, we enforce a valid price interval of 15 seconds, meaning that any price older than 15 seconds is considered stale and not allowed. It is always recommended to update the price before using the NAVI lending protocol. [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#faq) FAQ -------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#what-happens-if-i-call-functions-from-lending_core-without-updating-prices) **What happens if I call functions from** `**lending_core**` **without updating prices?** The oracle's price can be updated by anyone. If a price update occurs within 15 seconds, everything should function as expected. However, if the price isn't updated within this interval, you will encounter an error with code **1502** due to stale prices. To avoid this, we recommend updating the price before performing any operations to ensure accuracy and timeliness. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#how-is-the-oracle-used-in-the-lending-protocol) **How is the oracle used in the lending protocol?** The oracle provides real-time price feeds, which are essential for maintaining users' health factors. It ensures assets remain healthy by triggering liquidations only when necessary, protecting both users and the protocol from undercollateralized loans. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#which-prices-should-i-update) **Which prices should I update?** We recommend updating all prices since the price update function is gas-efficient. However, you can opt to update only the prices of assets relevant to your account. For example, if you deposit **USDC** and **SUI** as collateral and want to borrow **USDT**, you only need to update the prices of **USDC**, **SUI**, and **USDT**. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#what-is-the-gas-cost-for-updating-prices) **What is the gas cost for updating prices?** The average gas cost for updating all prices is approximately **0.0013 SUI**. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#how-can-i-read-the-latest-price-from-the-oracle-and-check-its-validity) **How can I read the latest price from the oracle and check its validity?** You can retrieve price information using the following function in the `oracle::oracle` module: The returned values are as follows: * `**price_validity**`: A boolean indicating whether the price is fresh and valid. * `**price_value**`: The price itself. * `**price_decimal**`: The number of decimals in the price. **Why are prices not updated after calling** `**update_single_price**`**?** Although rare, this can occur due to the oracle's safety mechanisms. Here are some potential reasons and troubleshooting steps: * `**OracleUnavailable**`: Prices from providers are considered stale and are not applied. To resolve this, update prices via [**Pyth**](https://docs.pyth.network/price-feeds/use-real-time-data/sui) , then call `update_single_price` again. * `**InvalidOraclePrice**`: The final price is deemed invalid due to extreme fluctuations or abnormal values. * `**PriceRegulation**`: The price difference from providers exceeds acceptable limits. Check the emitted events for more details when encountering these issues. [PreviousNAVI Lending Protocol Upgrade Announcement (2025/11/17)](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17) [NextOracle Interface](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface) Last updated 1 year ago * [Overview](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#overview) * [FAQ](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#faq) * [What happens if I call functions from lending\_core without updating prices?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#what-happens-if-i-call-functions-from-lending_core-without-updating-prices) * [How is the oracle used in the lending protocol?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#how-is-the-oracle-used-in-the-lending-protocol) * [Which prices should I update?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#which-prices-should-i-update) * [What is the gas cost for updating prices?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#what-is-the-gas-cost-for-updating-prices) * [How can I read the latest price from the oracle and check its validity?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle#how-can-i-read-the-latest-price-from-the-oracle-and-check-its-validity) Copy native public fun get_token_price(clock: &Clock, price_oracle: &PriceOracle, oracle_id: u8): (bool, u256, u8); --- # NAVI Uptime Status Page | NAVI Protocol Developer Docs NAVI ensures continuous monitoring of its key services to maintain top-tier performance and reliability. Below are the status and metrics for **NAVI Lending** and **NAVI Aggregator.** **You can find the status page at:** [![Logo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/~gitbook/image?url=https%3A%2F%2Fnavi-protocol.betteruptime.com%2Fassets%2Fstatus_pages_v2%2Ffavicons%2Foperational-5a610d11.png&width=20&dpr=4&quality=100&sign=90752d04&sv=2)NAVI statusnavi-protocol.betteruptime.com](https://navi-protocol.betteruptime.com/) * * * ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#monitors) **🔗 Monitors** * **NAVI Aggregator Website:** [navi.ag](https://navi.ag/) * Operational Status**:** ✅ Operational / ❌ Error * Last Updated**:** MM/DD/YYYY HH:MM (UTC) * **NAVI Lending Website:** [app.naviprotocol.io](https://app.naviprotocol.io/) * Operational Status: ✅ Operational / ❌ Error * Last Updated: MM/DD/YYYY HH:MM (UTC) * **NAVI Aggregator API:** [open-aggregator-api.naviprotocol.io](https://open-aggregator-api.naviprotocol.io/) * Operational Status: ✅ Operational / ❌ Error * Last Updated: MM/DD/YYYY HH:MM (UTC) * **NAVI Package API:** [open-api.naviprotocol.io/api/package](https://open-api.naviprotocol.io/api/package) * Operational Status: ✅ Operational / ❌ Error * Last Updated: MM/DD/YYYY HH:MM (UTC) * **NAVI Pool API:** [open-api.naviprotocol.io/api/pool](https://open-api.naviprotocol.io/api/pool) * Operational Status: ✅ Operational / ❌ Error * Last Updated: MM/DD/YYYY HH:MM (UTC) #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#uptime-last-90-days) **📊 Uptime (Last 90 Days)** * **Uptime Percentage**: **100%** 🟢 * Reflects the service's availability over the past 90 days. #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#response-times-performance) **⏱ Response Times Performance** * **Performance Chart**: Displays response times for the **last 24 hours**, measured every minute for precision ![](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/~gitbook/image?url=https%3A%2F%2F2230654657-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FWcKfs3vWiDuhitgCkBQQ%252Fuploads%252FxMfgKN7m2n4vsNWdazRX%252FScreenshot%25202024-11-25%2520at%252017.38.01.png%3Falt%3Dmedia%26token%3D99daacbf-9459-44fb-ab2a-cc4939c69928&width=768&dpr=4&quality=100&sign=15ee878d&sv=2) * * * ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#maintenance-schedule) **Maintenance Schedule** Stay updated on any planned maintenance that may affect services. * Upcoming maintenance schedules will be listed here along with timelines, scope, and expected downtime. > **Contract Upgrade** **Date**: MM/DD/YYYY **Time**: Start - End (UTC) **Affected Services**: Website **Purpose**: Brief description of the reason for the maintenance * * * ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#incident-history) **Incident History** A transparent log of past incidents for accountability and reference. #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#previous-incidents-sample) **Previous Incidents Sample** **Date** **Service** **Issue** **Resolution** **Duration** MM/DD/YYYY navi.ag API response delay Restarted server X mins/hours * * * [PreviousDemo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/demo) [NextNAVI API Collection](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection) Last updated 1 year ago * [🔗 Monitors](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#monitors) * [Maintenance Schedule](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#maintenance-schedule) * [Incident History](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page#incident-history) --- # Contract Configuration | NAVI Protocol Developer Docs Contract configuration is a key step in setting up and integrating with the NAVI protocol. This process involves defining and customizing essential parameters that control the behavior of smart contracts, ensuring they function optimally within the ecosystem. **Key Elements of Contract Configuration:** * **Contract Address Setup:** Configure the latest upgradable contract address. This address is crucial for routing transactions to the appropriate contract. * **Pool Settings:** Define supply and borrow pools, including pool addresses, supported tokens, and specific parameters like fees, limits, and incentives. * **Oracle Integration:** Connect smart contracts to oracles for real-time data, such as asset prices, which are vital for operations like liquidations and collateral management. Proper configuration ensures seamless interactions between smart contracts, oracles, and other ecosystem components, enabling smooth processes like supplying, borrowing, and distributing rewards. [1️⃣Get the Latest Package ID](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id) [2️⃣Get Pools Config and Oracle Price Feeds](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds) [3️⃣Get Flashloan Config](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-flashloan-config) [PreviousOracle Interface](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface) [NextGet the Latest Package ID](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id) Last updated 1 year ago --- # Contract Integration with NAVI | NAVI Protocol Developer Docs To interact with the **NAVI Protocol**, external contracts must use a specific mechanism called the **Account Cap**. This mechanism allows contracts to seamlessly integrate with NAVI’s ecosystem, enabling operations such as supplying and borrowing assets, checking rewards, and more. #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi#key-interaction-components) Key Interaction Components: * **Account Cap**: The Account Cap is a **non-fungible token (NFT)** that serves as a key, granting external contracts the ability to interact with NAVI’s smart contracts. It must be stored within the external contract as a wrapped object and passed into relevant functions (e.g., supplying tokens) for transactions to occur. * **Oracle Update**: Oracle data ensures that NAVI maintains accurate and up-to-date asset prices, which are critical for external contracts to perform correct valuations and liquidations. By using the Account Cap, external contracts can fully access and interact with NAVI’s core functionalities, allowing them to participate in and benefit from NAVI's lending, borrowing, and reward systems. The **contract integration** page provides detailed guidance for writing logic in smart contracts. [1️⃣Retrieve Pools Info inside Contract](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract) [2️⃣Integration with Account Cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap) [3️⃣Demo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/demo) [PreviousGet Flashloan Config](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-flashloan-config) [NextRetrieve Pools Info inside Contract](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract) Last updated 1 year ago --- # NAVI API Collection | NAVI Protocol Developer Docs **List of APIs Provided by NAVI and Their Primary Functionalities:** 1. **NAVI Pool API** * Returns reserve information for all assets. [https://open-api.naviprotocol.io/api/navi/pools](https://open-api.naviprotocol.io/api/navi/pools) 2. **NAVI Aggregator** * Returns a swap quote fetched from DEXes. [https://open-aggregator-api.naviprotocol.io/find\_routes](https://open-aggregator-api.naviprotocol.io/find_routes) 3. **NAVI Contract API** * Returns the current NAVI package ID and outdated versions. [https://open-api.naviprotocol.io/api/package](https://open-api.naviprotocol.io/api/package) * Provides contract configurations and utilization details for all pools. [https://open-api.naviprotocol.io/api/navi/contract/configs](https://open-api.naviprotocol.io/api/navi/contract/configs) * Provides NAVI's fee and revenue information. https://open-api.naviprotocol.io/api/navi/fee?fromTimestamp={fromTimestamp} * Provides NAVI's flashloan configurations and settings. [https://open-api.naviprotocol.io/api/navi/flashloan](https://open-api.naviprotocol.io/api/navi/flashloan) * Provides NAVI's latest oracle price feeds. [https://open-api.naviprotocol.io/api/navi/oracle](https://open-api.naviprotocol.io/api/navi/oracle) * Retrieves a user's claimed rewards history. https://open-api.naviprotocol.io/api/navi/user/rewards?userAddress={userAddress} 4. **Volo Sui** * Provides detailed statistics about Volo, including staking information and validator details. [https://open-api.naviprotocol.io/api/volo/stats](https://open-api.naviprotocol.io/api/volo/stats) 5. **Aftermath Sui** * Returns the APY of afSui. [https://open-api.naviprotocol.io/api/afsui/stats](https://open-api.naviprotocol.io/api/afsui/stats) 6. **Haedal Sui** * Returns the APY of haSui. [https://open-api.naviprotocol.io/api/haedal/stats](https://open-api.naviprotocol.io/api/haedal/stats) [PreviousNAVI Uptime Status Page](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page) [NextNAVI API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api) Last updated 1 year ago --- # FAQ | NAVI Protocol Developer Docs ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-get-pool-data) How to get pool data? Pools' data can be retrieved through the NAVI public API, SDK, or via RPC calls. Please refer to [Contract Configuration](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration) ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-check-pool-supply-borrow-cap) How to check pool supply/borrow cap? You may get the data from [Get Pools Config and Oracle Price Feeds](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds) ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-does-the-package-id-always-change) Why does the Package ID always change? NAVI smart contracts are immutable, but upgrades are implemented via new Package IDs, allowing for new features and improvements. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#is-there-a-reward-for-supplying-and-borrowing) Is there a reward for supplying and borrowing? Yes, we provide incentives for both supplying and borrowing assets through NAVI. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-do-we-need-to-update-navis-oracle) Why do we need to update NAVI’s oracle? Oracle updates ensure the system uses the most accurate asset prices, which is critical for accurate liquidations and valuations. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-is-the-sui-price-the-same-as-the-vsui-price-inside-contract) Why is the Sui price the same as the vSui price inside contract? This is a security measure embedded in the contract design. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-can-users-check-their-available-rewards) How can users check their available rewards? You can check through the NAVI Lending SDK using `getUserAvailableLendingRewards()` ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-can-another-contract-interact-with-navi) How can another contract interact with NAVI? We developed the [**Account Cap**](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap) , which allows any other contract to freely interact with NAVI. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-do-i-use-the-navi-sdk) How do I use the NAVI SDK? Refer to the documentation here: [NAVI SDK Documentation](https://sdk.naviprotocol.io/) . ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-do-i-manage-the-account-cap-nft) How do I manage the Account Cap NFT? The Account Cap NFT can be held by any address or wrapped within a smart contract object. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#can-the-account-cap-be-transferred) Can the Account Cap be transferred? Yes, Account Cap NFTs can be transferred to any address. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#can-the-account-cap-be-transferred-1) Can the Account Cap be transferred? Yes, Account Cap NFTs can be transferred to any address. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-fix-function-call-error-version-pre_check_version) How to fix Function Call error version::pre\_check\_version? Call upgrade command to update the contract like: ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#dev-community) Dev Community Regarding any questions, please reach out to support at NAVI Dev [PreviousafSui, haSui, vSui API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api) Last updated 4 months ago * [How to get pool data?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-get-pool-data) * [How to check pool supply/borrow cap?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-check-pool-supply-borrow-cap) * [Why does the Package ID always change?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-does-the-package-id-always-change) * [Is there a reward for supplying and borrowing?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#is-there-a-reward-for-supplying-and-borrowing) * [Why do we need to update NAVI’s oracle?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-do-we-need-to-update-navis-oracle) * [Why is the Sui price the same as the vSui price inside contract?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#why-is-the-sui-price-the-same-as-the-vsui-price-inside-contract) * [How can users check their available rewards?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-can-users-check-their-available-rewards) * [How can another contract interact with NAVI?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-can-another-contract-interact-with-navi) * [How do I use the NAVI SDK?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-do-i-use-the-navi-sdk) * [How do I manage the Account Cap NFT?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-do-i-manage-the-account-cap-nft) * [Can the Account Cap be transferred?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#can-the-account-cap-be-transferred) * [Can the Account Cap be transferred?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#can-the-account-cap-be-transferred-1) * [How to fix Function Call error version::pre\_check\_version?](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#how-to-fix-function-call-error-version-pre_check_version) * [Dev Community](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq#dev-community) Copy sui client upgrade --gas-budget 500000000 --upgrade-capability ur-upgrade-cap-id --- # Smart Contract Overview | NAVI Protocol Developer Docs This guide outlines key modules that support essential functions such as lending, borrowing, repaying, rewards distribution, and flashloan. Each module is broken down with detailed descriptions of its use cases and key functions, providing developers a clear understanding of how NAVI’s system operates. The functions within this module are categorized into two types: **entry** and **non-entry functions**. * **Entry Functions**: * Directly invoke the underlying base function. * Automatically return the token object to the function sender. * **Non-Entry Functions**: * Also invoke the underlying base function. * Return the coin object without handling it. * Require the caller—typically a developer or transaction builder—to manage the token object manually. Failure to do so will result in a reverted transaction. Non-entry functions provide greater flexibility, enabling developers to improve interoperability and compatibility with other protocols. [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview#modules-covered-include) Modules covered include: ---------------------------------------------------------------------------------------------------------------------------------------------- [1️Lending Core](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core) [2️Flash Loan](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan) [3️Calculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator) [4️Dynamic Calculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator) [5️Storage](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage) [6️Release History](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history) [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview#github-repo-of-navi-interfaces) Github Repo of NAVI Interfaces: ------------------------------------------------------------------------------------------------------------------------------------------------------------ [![Logo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/~gitbook/image?url=https%3A%2F%2Fgithub.com%2Ffluidicon.png&width=20&dpr=4&quality=100&sign=ccc5b74a&sv=2)GitHub - naviprotocol/protocol-interfaceGitHub](https://github.com/naviprotocol/protocol-interface) NAVI Interface Repo [PreviousBuild with NAVI Protocol](https://naviprotocol.gitbook.io/navi-protocol-developer-docs) [NextLending Core](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core) Last updated 2 months ago * [Modules covered include:](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview#modules-covered-include) * [Github Repo of NAVI Interfaces:](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview#github-repo-of-navi-interfaces) --- # Flash Loan | NAVI Protocol Developer Docs The following functions provide users the ability to take out and repay flash loans from a specified pool. A flash loan allows users to borrow assets with the condition that the loan must be repaid within the same Sui transaction. If the loan is not fully repaid, the transaction reverts, ensuring that no loss occurs for the pool. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_loan_with_ctx_v2) **flash\_loan\_with\_ctx\_v2** This function allows a user to take out a flash loan of a specified amount of a certain coin type from a pool. The loan must be repaid within the same transaction. A `FlashLoanReceipt` is generated to keep track of the loan details. Copy public fun flash_loan_with_ctx_v2( config: &FlashLoanConfig, pool: &mut Pool, amount: u64, system_state: &mut SuiSystemState, ctx: &mut TxContext ): (Balance, FlashLoanReceipt) ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_repay_with_ctx) flash\_repay\_with\_ctx This function handles the repayment of a flash loan. It takes in the loan receipt, the repayment balance object, and updates the pool's balance accordingly. If the loan is not repaid in full, the transaction will revert. The rest will be returned as a balance object. Copy public fun flash_repay_with_ctx( clock: &Clock, storage: &mut Storage, pool: &mut Pool, receipt: FlashLoanReceipt, repay_balance: Balance, ctx: &mut TxContext ): Balance ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_repay_with_account_cap) flash\_repay\_with\_account\_cap This function allows a user to take out a flash loan while utilizing an `AccountCap`. The `AccountCap` serves as an agent layer during the loan process. The function returns both the loan balance and the receipt for tracking the loan. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#undefined) [PreviousLending Core](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core) [NextCalculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator) Last updated 1 month ago * [flash\_loan\_with\_ctx\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_loan_with_ctx_v2) * [flash\_repay\_with\_ctx](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_repay_with_ctx) * [flash\_repay\_with\_account\_cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#flash_repay_with_account_cap) * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan#undefined) Copy public fun flash_repay_with_account_cap( clock: &Clock, storage: &mut Storage, pool: &mut Pool, receipt: FlashLoanReceipt, repay_balance: Balance, account_cap: &AccountCap ): Balance {} --- # Lending Core | NAVI Protocol Developer Docs As a developer, your primary interactions with the NAVI Protocol will take place through the functions within the `**lending_core::incentive_v3**` module. This module serves as the entry point for all write transactions, including deposits, withdrawals, borrowing, repayment, liquidations, and reward claims [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry-functions) Entry Functions ------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_deposit) entry\_deposit This function allows a user to deposit a specified amount of a given coin type into a lending pool. The deposit amount is added to the pool's balance, and a deposit event is emitted. Copy public entry fun entry_deposit( clock: &Clock, storage: &mut Storage, pool: &mut Pool, asset: u8, deposit_coin: Coin, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ) {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_withdraw_v2) entry\_withdraw\_v2 This function allows a user to withdraw a specified amount from a lending pool. The withdrawal amount is deducted from the pool's balance, and a withdrawal event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_borrow_v2) entry\_borrow\_v2 This function allows a user to borrow a specified amount from a lending pool. The borrowed amount is deducted from the pool's balance, and a borrow event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_repay) entry\_repay This function allows a user to repay a specified loan amount. The repayment amount is added to the pool's balance, and a repay event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward_entry) claim\_reward\_entry This function allows users to claim rewards in a specified reward coin. Rewards are distributed from the bonus pool and a claim reward event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_liquidation_v2) entry\_liquidation\_v2 This function is used to liquidate a loan when a borrower's collateral is insufficient to cover their debt. The liquidation process repays the debt, returning any excess amount to the sender. A liquidation call event is emitted. [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#non-entry-functions) Non-entry Functions -------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#deposit_with_account_cap) deposit\_with\_account\_cap This function is similar to a standard deposit but includes an account cap limitation. The deposit amount is added to the pool's balance, and a deposit event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#withdraw_v2) withdraw\_v2 This function allows other contracts to withdraw a specified amount from a lending pool. The balance object is returned, and a withdrawal event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#withdraw_with_account_cap_v2) withdraw\_with\_account\_cap\_v2 This function is similar to a standard withdraw but includes an account cap limitation. The balance object is returned, and a withdrawal event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#borrow_v2) borrow\_v2 This function allows other contracts to borrow a specified amount from a lending pool. The balance object is returned, and a borrow event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#borrow_with_account_cap_v2) borrow\_with\_account\_cap\_v2 This function is similar to a standard borrow but includes an account cap limitation. The balance object is returned, and the borrow event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#repay) repay This function allows other contracts to repay a specified amount of a loan. The balance object is returned, and a repay event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#repay_with_account_cap) repay\_with\_account\_cap This function is similar to a standard repay but includes an account cap limitation. The balance object is returned, and a repay event is emitted. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward) claim\_reward Quick Reward Claiming Using the SDK We recommend using the SDK to claim rewards because the SDK will automatically claim all available rewards and perform off-chain indexing to optimize gas usage. #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#sdk-benefits) SDK Benefits: * **Off-chain indexing**: Retrieves relevant rules without incurring on-chain gas costs. * **Optimized filtering**: Selects only the necessary rule IDs before executing on-chain transactions. For users who want to implement customized and native reward claiming, we provide the following instructions: ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#step-by-step-process) Step-by-Step Process 1. **Retrieve Claimable Rewards** * Use `get_user_claimable_rewards` to fetch claimable reward information. * Parse the response using `parse_claimable_rewards`to determine RewardCoinType, coin\_types, and rule\_ids ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#get_user_claimable_rewards) get\_user\_claimable\_rewards This function retrieves the claimable rewards for a user, returning detailed reward information. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#parse_claimable_rewards) parse\_claimable\_rewards This function parses the claimable rewards to return the asset coin types, reward coin types, user total rewards, user claimed rewards, and rule ids. * The `coin_types` are derived from the asset tokens involved. * The `rule_ids` are extracted from the parsed claimable rewards. 1. **Execute** ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward-1) claim\_reward ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward_with_account_cap) claim\_reward\_with\_account\_cap This function is similar to a standard claim rewards but includes an account cap limitation. Rewards are distributed from the bonus pool, and a claim reward event is emitted. * Sample: Provide the appropriate parameters: ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#full-claim-contract-demo) Full Claim Contract Demo example: [https://suivision.xyz/txblock/5Nr7nkQg8GGLepEPVRmZ2CamkUgsSoNMqDyhNGbVqjjW](https://suivision.xyz/txblock/5Nr7nkQg8GGLepEPVRmZ2CamkUgsSoNMqDyhNGbVqjjW?tab=Overview) [PreviousSmart Contract Overview](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview) [NextFlash Loan](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan) Last updated 1 month ago * [Entry Functions](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry-functions) * [entry\_deposit](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_deposit) * [entry\_withdraw\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_withdraw_v2) * [entry\_borrow\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_borrow_v2) * [entry\_repay](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_repay) * [claim\_reward\_entry](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward_entry) * [entry\_liquidation\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#entry_liquidation_v2) * [Non-entry Functions](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#non-entry-functions) * [deposit\_with\_account\_cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#deposit_with_account_cap) * [withdraw\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#withdraw_v2) * [withdraw\_with\_account\_cap\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#withdraw_with_account_cap_v2) * [borrow\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#borrow_v2) * [borrow\_with\_account\_cap\_v2](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#borrow_with_account_cap_v2) * [repay](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#repay) * [repay\_with\_account\_cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#repay_with_account_cap) * [claim\_reward](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward) * [Step-by-Step Process](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#step-by-step-process) * [get\_user\_claimable\_rewards](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#get_user_claimable_rewards) * [parse\_claimable\_rewards](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#parse_claimable_rewards) * [claim\_reward](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward-1) * [claim\_reward\_with\_account\_cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#claim_reward_with_account_cap) * [Full Claim Contract Demo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/lending-core#full-claim-contract-demo) Copy public entry fun entry_withdraw_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) {} Copy public entry fun entry_borrow_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) {} Copy public entry fun entry_repay( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, repay_coin: Coin, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ) {} Copy public entry fun claim_reward_entry( clock: &Clock, incentive: &mut Incentive, storage: &mut Storage, reward_fund: &mut RewardFund, coin_types: vector, rule_ids: vector
, ctx: &mut TxContext ) {} Copy public entry fun entry_liquidation_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, debt_asset: u8, debt_pool: &mut Pool, debt_coin: Coin, collateral_asset: u8, collateral_pool: &mut Pool, liquidate_user: address, liquidate_amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) {} Copy public fun deposit_with_account_cap( clock: &Clock, storage: &mut Storage, pool: &mut Pool, asset: u8, deposit_coin: Coin, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap ) {} Copy public fun withdraw_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance {} Copy public fun withdraw_with_account_cap_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance {} Copy public fun borrow_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance {} Copy public fun borrow_with_account_cap_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance {} Copy public fun repay( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, repay_coin: Coin, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ): Balance {} Copy public fun repay_with_account_cap( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, repay_coin: Coin, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap ): Balance {} Copy struct ClaimableReward has copy, drop { asset_coin_type: String, reward_coin_type: String, user_claimable_reward: u256, user_claimed_reward: u256, rule_ids: vector
, } public fun get_user_claimable_rewards( clock: &Clock, storage: &mut Storage, incentive: &mut Incentive, user: address ) vector {} Copy public fun parse_claimable_rewards(claimable_rewards: vector) ( vector, // asset coin types vector, // reward coin types vector, // user total rewards vector, // user claimed rewards vector> // rule ids ) Copy // Reward Fund IDs VSUI: 0x7093cf7549d5e5b35bfde2177223d1050f71655c7f676a5e610ee70eb4d93b5c NAVX: 0x1a3f9fcfdfac10e92c99220203f7c4bb502558692f0be0f2cb5f788b4e12a6b5 SUINS: 0xc6b14b4eda9015ca69ec5f6a9688faa4f760259ce285dafe902ebe6700f5838f DEEP: 0xc889d78b634f954979e80e622a2ae0fece824c0f6d9590044378a2563035f32f FDUSD: 0x958dd7ad70755b10f96693bcd591d7a2cb9830a6c523baf43b3b5897664aa788 Copy public entry fun claim_reward( clock: &Clock, incentive: &mut Incentive, storage: &mut Storage, reward_fund: &mut RewardFund, coin_types: vector, rule_ids: vector
, ctx: &mut TxContext ) {} Copy public fun claim_reward_with_account_cap( clock: &Clock, incentive: &mut Incentive, storage: &mut Storage, reward_fund: &mut RewardFund, coin_types: vector, rule_ids: vector
, account_cap: &AccountCap ) Balance {} Copy // To claim rewards, we need to gather the same reward coin types // and then pass the corresponding asset coin types and rule IDs. // The expected function call should look like this: claim_reward( ..., // Additional parameters (e.g., clock, incentive, storage, etc.) coin_types: , // Expand asset types to match rule mappings rule_ids: // Flattened list of rule IDs ); Copy let user_a_rewards = incentive_v3::get_user_claimable_rewards( &clock, &mut storage, &mut incentive, USER_A ); ​ // Parse the retrieved claimable rewards into structured vectors let ( asset_coin_types, // List of asset coin types reward_coin_types, // List of corresponding reward coin types user_claimable_rewards, // Total claimable rewards per asset user_claimed_rewards, // Already claimed rewards per asset rule_ids // Associated rule IDs for each asset ) = incentive_v3::parse_claimable_rewards(user_a_rewards); // Parse the retrieved claimable rewards into structured vectors // Example output structure after parsing: // ( // , // Unique asset coin types // , // Corresponding reward coin types // , // Claimable rewards amounts // , // Already claimed amounts // <, > // Rule IDs grouped by asset type // ) Copy use lending_core::incentive_v3::{Self, Incentive as IncentiveV3, RewardFund}; use lending_core::storage::Storage; use std::ascii::String; use std::type_name; use std::vector; use sui::balance::{Balance}; use sui::coin::{Self}; use sui::clock::{Clock}; use sui::transfer::{Self}; use sui::tx_context::{Self, TxContext}; /// This function is used to claim reward with one coin type /// It runs fully onchain without offchain indexing. /// This practice is not gas optimized, and claiming reward though SDK with is recommended. /// Params objectIds will be available on the gitbook. public fun claim_reward( clock: &Clock, incentive: &mut IncentiveV3, storage: &mut Storage, reward_fund: &mut RewardFund, ctx: &mut TxContext, ): Balance { let ( asset_coin_types, reward_coin_types, user_total_rewards, user_claimed_rewards, rule_ids, ) = incentive_v3::parse_claimable_rewards( incentive_v3::get_user_claimable_rewards( clock, storage, incentive, tx_context::sender(ctx), ), ); let target_coin_type = &type_name::into_string(type_name::get()); let input_coin_types = vector::empty(); let input_rule_ids = vector::empty
(); let i = 0; while (i < vector::length(&asset_coin_types)) { let asset_coin_type = vector::borrow(&asset_coin_types, i); let reward_coin_type = vector::borrow(&reward_coin_types, i); let user_total_reward = *vector::borrow(&user_total_rewards, i); let user_claimed_reward = *vector::borrow(&user_claimed_rewards, i); let rule_id = vector::borrow(&rule_ids, i); if (user_total_reward > user_claimed_reward && reward_coin_type == target_coin_type) { vector::push_back(&mut input_coin_types, *asset_coin_type); vector::append(&mut input_rule_ids, *rule_id); }; i = i + 1; }; incentive_v3::claim_reward( clock, incentive, storage, reward_fund, input_coin_types, input_rule_ids, ctx, ) } public entry fun claim_reward_entry( clock: &Clock, incentive: &mut IncentiveV3, storage: &mut Storage, reward_fund: &mut RewardFund, recipient: address, ctx: &mut TxContext, ) { let ( asset_coin_types, reward_coin_types, user_total_rewards, user_claimed_rewards, rule_ids, ) = incentive_v3::parse_claimable_rewards( incentive_v3::get_user_claimable_rewards( clock, storage, incentive, tx_context::sender(ctx), ), ); let target_coin_type = &type_name::into_string(type_name::get()); let input_coin_types = vector::empty(); let input_rule_ids = vector::empty
(); let i = 0; while (i < vector::length(&asset_coin_types)) { let asset_coin_type = vector::borrow(&asset_coin_types, i); let reward_coin_type = vector::borrow(&reward_coin_types, i); let user_total_reward = *vector::borrow(&user_total_rewards, i); let user_claimed_reward = *vector::borrow(&user_claimed_rewards, i); let rule_id = vector::borrow(&rule_ids, i); if (user_total_reward > user_claimed_reward && reward_coin_type == target_coin_type) { vector::push_back(&mut input_coin_types, *asset_coin_type); vector::append(&mut input_rule_ids, *rule_id); }; i = i + 1; }; let balance = incentive_v3::claim_reward( clock, incentive, storage, reward_fund, input_coin_types, input_rule_ids, ctx, ); transfer::public_transfer(coin::from_balance(balance, ctx), recipient) } --- # Retrieve Pools Info inside Contract | NAVI Protocol Developer Docs With the provided link, you can access all the interactable interfaces within the NAVI protocol's smart contracts. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract#code-sample-retrieving-reserve-pool-dynamic-fields) Code Sample: Retrieving Reserve Pool Dynamic Fields Here’s a sample struct that defines the dynamic fields of a reserve pool: Copy struct ReserveData has store { id: u8, oracle_id: u8, coin_type: String, is_isolated: bool, supply_cap_ceiling: u256, borrow_cap_ceiling: u256, current_supply_rate: u256, current_borrow_rate: u256, current_supply_index: u256, current_borrow_index: u256, supply_balance: TokenBalance, borrow_balance: TokenBalance, last_update_timestamp: u64, ltv: u256, treasury_factor: u256, treasury_balance: u256, borrow_rate_factors: BorrowRateFactors, liquidation_factors: LiquidationFactors, reserve_field_a: u256, reserve_field_b: u256, reserve_field_c: u256, } ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract#function-example-retrieving-borrow-cap-ceiling) Function Example: Retrieving Borrow Cap Ceiling This function retrieves the `borrow_cap_ceiling` field from the `ReserveData` struct: This sample demonstrates how to access dynamic reserve pool fields such as the borrowing cap, which plays a crucial role in the risk management and lending/borrowing logic within the protocol. [PreviousContract Integration with NAVI](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi) [NextIntegration with Account Cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap) Last updated 1 year ago * [Code Sample: Retrieving Reserve Pool Dynamic Fields](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract#code-sample-retrieving-reserve-pool-dynamic-fields) * [Function Example: Retrieving Borrow Cap Ceiling](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract#function-example-retrieving-borrow-cap-ceiling) Copy public fun borrow_cap( object: &mut ReserveData, ): u256 { &object.borrow_cap_ceiling } --- # Get the Latest Package ID | NAVI Protocol Developer Docs [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#getpackageid-navi-api) **getPackageId - NAVI API** ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ The `getPackageId` API is publicly accessible and retrieves the latest package information for the NAVI Protocol. This endpoint provides the current `packageId` in use, along with a list of outdated package IDs for reference. It helps developers ensure they are working with the most up-to-date package when interacting with NAVI's smart contracts. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#get-api-package) Get the latest package information get https://open-api.naviprotocol.io/api/package Responses 200 Successful response with the latest package and outdated packages application/json Responseobject Show properties 404 Package not found get /api/package HTTP HTTPcURLJavaScriptPython Test it 200 Successful response with the latest package and outdated packages [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#getpackageid-navi-sdk) **getPackageId - NAVI SDK** ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ The `getLatestProtocolPackageId` function in the NAVI SDK retrieves the most recent `packageId` used in the NAVI Protocol. This function is essential for PTB developers to ensure they are interacting with the latest version of NAVI’s smart contracts in their JavaScript-based code. [PreviousContract Configuration](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration) [NextGet Pools Config and Oracle Price Feeds](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds) Last updated 1 year ago * [getPackageId - NAVI API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#getpackageid-navi-api) * [GETGet the latest package information](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#get-api-package) * [getPackageId - NAVI SDK](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id#getpackageid-navi-sdk) Copy GET /api/package HTTP/1.1 Host: open-api.naviprotocol.io Accept: */* Copy { "packageId": "0x834a86970ae93a73faf4fff16ae40bdb72b91c47be585fff19a2af60a19ddca3", "outdated": [\ {\ "packageId": "0x66aa3335901ce7e04b85ed6597ee42d4b479f7110bf98e8ebd474fa32a0027e1",\ "version": 19\ },\ {\ "packageId": "0xc6374c7da60746002bfee93014aeb607e023b2d6b25c9e55a152b826dbc8c1ce",\ "version": 18\ },\ {\ "packageId": "0x2c256d2ae030db12c7015aa1617ad928e60cc99d460b279fe76bbb9f82fa7063",\ "version": 17\ },\ {\ "packageId": "0x7c9b90b3fda0fa4aa8ee88ae6c4a0b83c773f74936b5354448cb94662e94442d",\ "version": 16\ },\ {\ "packageId": "0x9b3f433217c2bbfd13368b264653fc9989fcf8daab1144fa4b44a9fc168c243e",\ "version": 15\ },\ {\ "packageId": "0x06007a2d0ddd3ef4844c6d19c83f71475d6d3ac2d139188d6b62c052e6965edd",\ "version": 14\ },\ {\ "packageId": "0xd92d9db3ae5e2e932eda336b15f97e02255d152201d0cf29a29ca0c4fb0205f3",\ "version": 13\ },\ {\ "packageId": "0xdd01308cf0b874407dcfcae8d769090421111567954139083c776261c5f0e2b0",\ "version": 12\ },\ {\ "packageId": "0x3e8e806c3028adfffec57e380bb458f8286b73f1bf9b8906f89a2bb6b817616c",\ "version": 11\ },\ {\ "packageId": "0x66c91a8560cd64d73d93dd1ec7b61f3f21ad2f66553dd3d7038ca69255479bb7",\ "version": 10\ },\ {\ "packageId": "0xe66f07e2a8d9cf793da1e0bca98ff312b3ffba57228d97cf23a0613fddf31b65",\ "version": 9\ },\ {\ "packageId": "0x461364d0dc7edb74d73f8366605c63a3f67c37fc1dabf0c31780b37cc77820f6",\ "version": 8\ },\ {\ "packageId": "0xf5f8e3dc0252b22c61f24cbcaefba49bf6ccfff4ce7159e34d9aec0ba5112105",\ "version": 7\ },\ {\ "packageId": "0x81be491340a6964eb9903141c3068db55704b5892072eb9e372cc98f4b04639c",\ "version": 6\ },\ {\ "packageId": "0x0440aedc27c9a57ea357bd8fe1525a00d60d7f442a380924a7e7c1d79853bb8b",\ "version": 5\ },\ {\ "packageId": "0xb2345915de1f9bd661e9ab27eb27e376cdf6391359ea64fbfdb4550b092c1aa0",\ "version": 4\ },\ {\ "packageId": "0xd92bc457b42d48924087ea3f22d35fd2fe9afdf5bdfe38cc51c0f14f3282f6d5",\ "version": 3\ },\ {\ "packageId": "0xcd265ef828babd6d6b78693218d377aab349b3b2319bca1a3b4d614f91156d33",\ "version": 2\ },\ {\ "packageId": "0xd899cf7d2b5db716bd2cf55599fb0d5ee38a3061e7b6bb6eebf73fa5bc4c81ca",\ "version": 1\ }\ ] } Copy import { getLatestProtocolPackageId } from 'navi-sdk/dist/libs/PoolInfo'; const id = await getLatestProtocolPackageId(); --- # Calculator | NAVI Protocol Developer Docs This section contains functions for `calculating utilization`, `borrow rates`,`supply rates`, and `interest`, as well as for converting between asset amounts and values using oracle price data. This module is essential for performing calculations such as determining the current state of a lending pool, applying interest to loans or deposits, and converting between different tokens based on their price. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_utilization) calculate\_utilization > **Description:** This function calculates the utilization ratio of an asset in a lending pool. The utilization ratio is the ratio of total borrowed assets to the total available assets. > **Use Cases:** This function is used when determining the demand for an asset in the lending pool, which can influence the interest rates applied to borrowing and lending transactions. Copy public fun caculate_utilization( storage: &mut Storage, asset: u8 ): u256 {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_borrow_rate) calculate\_borrow\_rate > **Description:** This function calculates the borrowing interest rate for an asset based on its utilization ratio. > **Use Cases:** This function is used when a user wishes to borrow an asset from the lending pool. The interest rate calculated will be applied to the loan. Copy public fun calculate_borrow_rate( storage: &mut Storage, asset: u8 ): u256 {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_supply_rate) calculate\_supply\_rate > **Description:** This function calculates the supply (or deposit) interest rate for an asset based on its borrowing rate and utilization ratio. > **Use Cases:** This function is used when a user deposits an asset into the lending pool. The interest rate calculated will be the rate at which their deposit accrues interest. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_compounded_interest) calculate\_compounded\_interest > **Description:** This function calculates the compounded interest over a period of time based on a given rate. > **Use Cases:** This function can be used when calculating the interest accrued on a deposit or loan over a period of time. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_linear_interest) calculate\_linear\_interest > **Description:** This function calculates the linear interest over a period of time based on a given rate. > **Use Cases:** This function can be used when calculating the interest accrued on a deposit or loan over a period of time. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_value) calculate\_value > **Description:** This function converts an amount of an asset to its value in a base currency using the price data from a price oracle. > **Use Cases:** This function can be used when displaying the value of an asset to a user, or when performing calculations that require the value of an asset in the base currency. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_amount) calculate\_amount > **Description:** This function converts a value in a base currency to an amount of an asset using the price data from a price oracle. [PreviousFlash Loan](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/flash-loan) [NextDynamic Calculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator) Last updated 1 year ago * [calculate\_utilization](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_utilization) * [calculate\_borrow\_rate](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_borrow_rate) * [calculate\_supply\_rate](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_supply_rate) * [calculate\_compounded\_interest](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_compounded_interest) * [calculate\_linear\_interest](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_linear_interest) * [calculate\_value](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_value) * [calculate\_amount](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator#calculate_amount) Copy public fun calculate_supply_rate( storage: &mut Storage, asset: u8, borrow_rate: u256 ): u256 {} Copy public fun calculate_compounded_interest( timestamp_difference: u256, rate: u256 ): u256 {} Copy public fun calculate_linear_interest( timestamp_difference: u256, rate: u256 ): u256 {} Copy public fun calculate_value( clock: &Clock, oracle: &PriceOracle, amount: u256, oracle_id: u8 ): u256 {} Copy public fun calculate_amount( clock: &Clock, oracle: &PriceOracle, value: u256, oracle_id: u8 ): u256 {} --- # Get Pools Config and Oracle Price Feeds | NAVI Protocol Developer Docs NAVI offers essential data about specific lending and borrowing pools, as well as oracle price feeds, through its public **API** and **NAVI SDK**. This data includes key details like pool ID, reserve ID, borrow and supply balances, caps, interest rates, and **oracle prices**. It enables developers and users to understand the current state of a pool, its limitations, and potential opportunities for interaction, such as borrowing, supplying, and calculating rewards. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds#get-api-navi-pools) Get Pool Configuration get https://open-api.naviprotocol.io/api/navi/pools Responses 200 Successful response with pool configuration data application/json Responseobject Show properties 404 Pool configuration not found get /api/navi/pools HTTP HTTPcURLJavaScriptPython Test it 200 Successful response with pool configuration data ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds#oracles-in-the-navi-protocol) **Oracles in the NAVI Protocol** In the NAVI protocol, each oracle is associated with a specific `poolId`, enabling developers to efficiently access and interact with oracle data. The oracle provides essential fields for accurate financial operations: * **Decimal**: Defines the decimal precision of the pool's coin, ensuring calculations are accurate. * **OracleID**: The unique identifier for the oracle, specifying its asset ID. * **Value**: The current data point provided by the oracle, typically a numeric metric such as an asset price or exchange rate. * **Price**: The market price retrieved from the oracle, ensuring real-time accuracy in financial computations. * **Valid**: A boolean that indicates whether the oracle’s data is reliable and up-to-date. If `valid` is true, the data can be used safely for calculations. If false, the data may be outdated or unreliable. To query an oracle, use the API to retrieve the oracle object linked to each pool and ensure you are accessing the correct data. **Sample Data of Sui Price from API**: [**Sample Tx**](https://suivision.xyz/txblock/2jeVCjdfkUm4J6vMNVZtVne1o4NpdUFuJdvtuQyb8UgU?tab=Events) **and on-chain event of NAVI Orace Sui Price:** [PreviousGet the Latest Package ID](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-the-latest-package-id) [NextGet Flashloan Config](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-flashloan-config) Last updated 1 year ago * [GETGet Pool Configuration](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds#get-api-navi-pools) * [Oracles in the NAVI Protocol](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds#oracles-in-the-navi-protocol) Copy GET /api/navi/pools HTTP/1.1 Host: open-api.naviprotocol.io Accept: */* Copy { "data": [\ {\ "poolId": "text",\ "reserveId": "text",\ "borrowBalanceParentId": "text",\ "supplyBalanceParentId": "text",\ "borrowCapCeiling": "text",\ "coinType": "text",\ "currentBorrowIndex": "text",\ "currentBorrowRate": "text",\ "currentSupplyIndex": "text",\ "currentSupplyRate": "text",\ "id": 1,\ "isIsolated": true,\ "lastUpdateTimestamp": "text",\ "ltv": "text",\ "oracleId": 1,\ "reserveFieldA": "text",\ "reserveFieldB": "text",\ "reserveFieldC": "text",\ "supplyCapCeiling": "text",\ "treasuryBalance": "text",\ "treasuryFactor": "text",\ "totalSupplyAmount": "text",\ "minimumAmount": "text",\ "leftSupply": "text",\ "validBorrowAmount": "text",\ "borrowedAmount": "text",\ "leftBorrowAmount": "text",\ "availableBorrow": "text",\ "oracle": {\ "decimal": 1,\ "value": "text",\ "price": "text",\ "oracleId": 1,\ "valid": true\ },\ "supplyIncentiveApyInfo": {\ "vaultApr": "text",\ "boostedApr": "text",\ "rewardCoin": [\ "text"\ ],\ "apy": "text"\ },\ "borrowIncentiveApyInfo": {\ "vaultApr": "text",\ "boostedApr": "text",\ "rewardCoin": [\ "text"\ ],\ "apy": "text"\ }\ }\ ] } Copy "oracle": { "decimal": 9, "value": "1830516540", "price": "1.83051654", "oracleId": 0, "valid": true } Copy { "id": { "txDigest": "2jeVCjdfkUm4J6vMNVZtVne1o4NpdUFuJdvtuQyb8UgU", "eventSeq": "0" }, "packageId": "0xca441b44943c16be0e6e23c5a955bb971537ea3289ae8016fbf33fffe1fd210f", "transactionModule": "oracle_pro", "sender": "0xa2fe7a0d7bd70fe76d32065ec7b3c604cd90016a560bf2f01b68f3b5bbd2d3aa", "type": "0xc2d49bf5e75d2258ee5563efa527feb6155de7ac6f6bf025a23ee88cd12d5a83::oracle::PriceUpdated", "parsedJson": { "id": 0, "last_price": "1831480060", "last_update_at": "1728614555256", "price": "1831268400", "price_oracle": "0x1568865ed9a0b5ec414220e8f79b3d04c77acc82358f6e5ae4635687392ffbef", "update_at": "1728614565290" }, "bcs": "JjyLckUe7fhfVBPVwtNSNQKzVDkDMyjF92CYAsXDhUsTU28T1qeNR7r8GttQZ14V5yvEv4YQZW4XYRiMWLtt41NRhgxjCCvw5DwYEn3eFAaM3Bu4zYJBM24nFbCk2mXdnM2UkUNF3wEkUWZo4X23moGnzB" } --- # Integration with Account Cap | NAVI Protocol Developer Docs If an external contract wants to interact with the NAVI protocol, an account cap is required for the interaction. The account cap must be stored within the contract as a wrapped object. When calling functions—such as the supply token function—the account cap object must be passed as a parameter to enable the transaction. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap#code-snippet-account-cap-integration) Code Snippet: Account Cap Integration Copy public struct Vault has key, store { id: UID, account_cap: AccountCap, sui_index: u8, usdc_index: u8 } lending_core::incentive_v2::deposit_with_account_cap( clock, storage, pool_a, vault.sui_index, deposit_coin, inc_v1, inc_v2, &vault.account_cap ) In this example, the `Vault` struct includes an `account_cap` field that is passed into the `deposit_with_account_cap` function to enable token deposits. [PreviousRetrieve Pools Info inside Contract](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/retrieve-pools-info-inside-contract) [NextDemo](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/demo) Last updated 1 year ago --- # Get Flashloan Config | NAVI Protocol Developer Docs ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-flashloan-config#get-flashloan-config-from-navi-lending-sdk) Get Flashloan Config from NAVI Lending SDK This code snippet demonstrates how to retrieve the configuration for a flashloan using the NAVI Lending SDK, focusing on the pool configuration for the USDC coin. Copy import { getAllFlashLoanAssets } from '@naviprotocol/lending' const flashLoanAssets = await getAllFlashLoanAssets() const usdcAsset = flashLoanAssets.filter((asset) => { return asset.coinType === '0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC' }) [PreviousGet Pools Config and Oracle Price Feeds](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration/get-pools-config-and-oracle-price-feeds) [NextContract Integration with NAVI](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi) Last updated 4 months ago --- # Oracle Interface | NAVI Protocol Developer Docs [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface#oracle-integration-guide-for-developers) Oracle Integration Guide for Developers ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To ensure accurate and up-to-date price information for your operations, you can trigger a manual price update using the `oracle::oracle_pro::update_single_price` function. This must be integrated into a PTB (Programmable Transaction Block) before invoking any functions from `lending_core`. * * * **Oracle Interface Example** Copy moveCopy codemodule oracle::oracle_pro { use sui::clock::{Clock}; use oracle::oracle_provider::{OracleProviderConfig}; use oracle::oracle::{PriceOracle}; use oracle::config::{OracleConfig}; use SupraOracle::SupraSValueFeed::{OracleHolder}; use pyth::price_info::{PriceInfoObject}; native 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 ); native public fun get_price_from_adaptor( oracle_provider_config: &OracleProviderConfig, target_decimal: u8, supra_oracle_holder: &OracleHolder, pyth_price_info: &PriceInfoObject ): (u256, u64); } * * * **Example: Triggering a Price Update** **Sample Transaction** [View Transaction](https://suivision.xyz/txblock/QLGhGPczp7Y3XA1er5ovdXJuDRjpaHWSNRGLjN2SXiq?tab=Overview) * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface#oracle-configuration) **Oracle Configuration** Below is the configuration data for different tokens: * * * ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface#data-sources) **Data Sources** * **Supra Data Feeds**: [Supra Docs](https://supra.com/docs/data-feeds/data-feeds-index) * **Pyth Price Feed IDs**: [Pyth Docs](https://pyth.network/developers/price-feed-ids) [PreviousDecentralized Oracle](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle) [NextContract Configuration](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-configuration) Last updated 1 month ago * [Oracle Integration Guide for Developers](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface#oracle-integration-guide-for-developers) * [Data Sources](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle/oracle-interface#data-sources) Copy typescriptCopy codethis.txb.moveCall({ target: `${oracle.PackageId}::oracle_pro::update_single_price`, arguments: [\ this.txb.object('0x6'),\ this.txb.object(oracle.OracleConfig),\ this.txb.object(oracle.PriceOracle),\ this.txb.object(oracle.SupraOracleHolder),\ this.txb.object(asset.pythPriceInfoObject),\ this.txb.pure(asset.feedAddress),\ ], }); Copy OracleProConfig = { PackageId: '0xc2d49bf5e75d2258ee5563efa527feb6155de7ac6f6bf025a23ee88cd12d5a83', PriceOracle: '0x1568865ed9a0b5ec414220e8f79b3d04c77acc82358f6e5ae4635687392ffbef', OracleConfig: '0x1afe1cb83634f581606cc73c4487ddd8cc39a944b951283af23f7d69d5589478', SupraOracleHolder: '0xaa0315f0748c1f24ddb2b45f7939cff40f7a8104af5ccbc4a1d32f870c0b4105', }; SUI: { oracleId: 0, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 10000000000, // 10 = 10 * 1e9 = 10000000000 minimumEffectivePrice: 100000000, // 0.1 = 0.1 * 1e9 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x0000000000000000000000000000000000000000000000000000000000000002::sui::SUI', feedId: '0x2cab9b151ca1721624b09b421cc57d0bb26a1feb5da1f821492204b098ec35c9', // TODO: value supraPairId: 90, // SUI_USDT -> 90, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Under%20Supervision-,SUI_USDT,-90 pythPriceFeedId: '0x23d7315113f5b1d3ba7a83604c44b94d79f4fd69af77f804fc7f920a6dc65744', // **fixed value: Crypto.SUI/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x801dbc2f0053d34734814b2d6df491ce7807a725fe9a01ad74a07e9c51396c37', priceDecimal: 9, expiration: 30, }, USDC: { oracleId: 1, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 100000, // 0.1 = 0.1 * 1e6 = 100000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::COIN', feedId: '0x70a79226dda5c080378b639d1bb540ddea64761629aa4ad7355d79266d55af61', // TODO: value supraPairId: 47, // USDC_USDT -> 47, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Standard-,USDC_USDT,-47 pythPriceFeedId: '0xeaa020c61cc479712813461ce153894a96a6c00b21ed0cfc2798d1f9a9e9c94a', // **fixed value: Crypto.USDC/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x5dec622733a204ca27f5a90d8c2fad453cc6665186fd5dff13a83d0b6c9027ab', priceDecimal: 6, expiration: 30, }, USDT: { oracleId: 2, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 100000, // 0.1 = 0.1 * 1e6 = 100000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c::coin::COIN', feedId: '0xf72d8933873bb4e5bfa1edbfa9ff6443ec5fac25c1d99ba2ef37f50a125826f3', // TODO: value supraPairId: 48, // USDT_USD -> 48, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Premium-,USDT_USD,-48 pythPriceFeedId: '0x2b89b9dc8fdf9f34709a5b106b472f0f39bb6ca9ce04b0fd7f2e971688e2e53b', // **fixed value: Crypto.USDT/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x985e3db9f93f76ee8bace7c3dd5cc676a096accd5d9e09e9ae0fb6e492b14572', priceDecimal: 6, expiration: 30, }, WETH: { oracleId: 3, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 600000000000, // 6000 = 6000 * 1e8 = 600000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xaf8cd5edc19c4512f4259f0bee101a40d41ebed738ade5874359610ef8eeced5::coin::COIN', feedId: '0x44d92366eba1f1652ec81f34585406726bef267565a2db1664ffd5ef18e21693', // TODO: value supraPairId: 1, // ETH_USDT -> 1, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Premium-,ETH_USDT,-1 pythPriceFeedId: '0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace', // **fixed value: Crypto.ETH/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x9193fd47f9a0ab99b6e365a464c8a9ae30e6150fc37ed2a89c1586631f6fc4ab', priceDecimal: 8, expiration: 30, }, CETUS: { oracleId: 4, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 200, // x1: 2% = 0.02 * 10000 = 200 priceDiffThreshold2: 400, // x2: 4% = 0.04 * 10000 = 400 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 1500000000, // 1.5 = 1.5 * 1e9 = 1500000000 minimumEffectivePrice: 1000000, // 0.001 = 0.001 * 1e9 = 1000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x6864a6f921804860930db6ddbe2e16acdf8504495ea7481637a1c8b9a8fe54b::cetus::CETUS', feedId: '0x5ac98fc1e6723af2a6d9a68a5d771654a6043f9c4d2b836b2d5fb4832a3be4f2', // TODO: value supraPairId: 93, // CETUS_USDT -> 93, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Premium-,CETUS_USDT,-93 pythPriceFeedId: '0xe5b274b2611143df055d6e7cd8d93fe1961716bcd4dca1cad87a83bc1e78c1ef', // **fixed value: Crypto.CETUS/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x24c0247fb22457a719efac7f670cdc79be321b521460bd6bd2ccfa9f80713b14', priceDecimal: 9, expiration: 30, }, CERT: { oracleId: 5, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 10000000000, // 10 = 10 * 1e9 = 10000000000 minimumEffectivePrice: 100000000, // 0.1 = 0.1 * 1e9 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x549e8b69270defbfafd4f94e17ec44cdbdd99820b33bda2278dea3b9a32d3f55::cert::CERT', feedId: '0x086bb5540047b3c77ae5e2f9b811c7ef085517a73510f776753c8ee83d19e62c', // TODO: value supraPairId: 90, // SUI_USDT -> 90, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Under%20Supervision-,SUI_USDT,-90 pythPriceFeedId: '0x23d7315113f5b1d3ba7a83604c44b94d79f4fd69af77f804fc7f920a6dc65744', // **fixed value: Crypto.SUI/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x801dbc2f0053d34734814b2d6df491ce7807a725fe9a01ad74a07e9c51396c37', priceDecimal: 9, expiration: 30, }, HASUI: { oracleId: 6, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 10000000000, // 10 = 10 * 1e9 = 10000000000 minimumEffectivePrice: 100000000, // 0.1 = 0.1 * 1e9 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xbde4ba4c2e274a60ce15c1cfff9e5c42e41654ac8b6d906a57efa4bd3c29f47d::hasui::HASUI', feedId: '0xac934a2a2d406085e7f73b460221fe1b11935864605ba58cdbb8e21c15f12acd', // TODO: value supraPairId: 90, // SUI_USDT -> 90, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Under%20Supervision-,SUI_USDT,-90 pythPriceFeedId: '0x23d7315113f5b1d3ba7a83604c44b94d79f4fd69af77f804fc7f920a6dc65744', // **fixed value: Crypto.SUI/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x801dbc2f0053d34734814b2d6df491ce7807a725fe9a01ad74a07e9c51396c37', priceDecimal: 9, expiration: 30, }, NAVX: { oracleId: 7, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 200, // x1: 2% = 0.02 * 10000 = 200 priceDiffThreshold2: 400, // x2: 4% = 0.04 * 10000 = 400 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 1000000000, // 1 = 1 * 1e9 = 1000000000 minimumEffectivePrice: 1000000, // 0.001 = 0.001 * 1e9 = 1000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xa99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX', feedId: '0x4324c797d2f19eff517c24adec8b92aa2d282e44f3a5cafb36d6c4b30d7f2dca', // TODO: value supraPairId: 408, // NAVX_USDT -> 408, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Premium-,NAVX_USDT,-408 pythPriceFeedId: '0x88250f854c019ef4f88a5c073d52a18bb1c6ac437033f5932cd017d24917ab46', // **fixed value: Crypto.NAVX/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x5b117a6a2de70796bffe36495bad576b788a34c33ca0648bd57852ead3f41e32', priceDecimal: 9, expiration: 30, }, WBTC: { oracleId: 8, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 20000000000000, // 200000 = 200000 * 1e8 = 20000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x027792d9fed7f9844eb4839566001bb6f6cb4804f66aa2da6fe1ee242d896881::coin::COIN', feedId: '0x1bf4727242a61d892feef6616d3e40a3bd24b64b5deb884054e86cb9360556c4', // TODO: value supraPairId: 0, // BTC_USDT -> 0, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Pair%20Category-,BTC_USDT,-0 pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', // Crypto.BTC/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 30, }, AUSD: { oracleId: 9, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 10000, // 0.01 = 0.01 * 1e6 = 10000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x2053d08c1e2bd02791056171aab0fd12bd7cd7efad2ab8f6b9c8902f14df2ff2::ausd::AUSD', feedId: '0x9a0656e1e10a0cdf3f03dce9db9ad931f51dc6eac2e52ebfbf535dfbcf8100ef', // TODO: values supraPairId: 99999, pythPriceFeedId: '0xd9912df360b5b7f21a122f15bdd5e27f62ce5e72bd316c291f7c86620e07fb2a', pythPriceInfoObject: '0x94ef89923e7beccd4a52043a9451a87c614684b847426fb5fd76faa8cb1e907f', priceDecimal: 6, expiration: 30, }, NUSDC: { oracleId: 10, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 100000, // 0.1 = 0.1 * 1e6 = 100000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xdba34672e30cb065b1f93e3ab55318768fd6fef66c15942c9f7cb846e2f900e7::usdc::USDC', feedId: '0xe120611435395f144b4bcc4466a00b6b26d7a27318f96e148648852a9dd6b31c', // TODO: value supraPairId: 47, // USDC_USDT -> 47, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Standard-,USDC_USDT,-47 pythPriceFeedId: '0xeaa020c61cc479712813461ce153894a96a6c00b21ed0cfc2798d1f9a9e9c94a', // **fixed value: Crypto.USDC/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x5dec622733a204ca27f5a90d8c2fad453cc6665186fd5dff13a83d0b6c9027ab', priceDecimal: 6, expiration: 30, }, ETH: { oracleId: 11, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 600000000000, // 6000 = 6000 * 1e8 = 600000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xd0e89b2af5e4910726fbcd8b8dd37bb79b29e5f83f7491bca830e94f7f226d29::eth::ETH', feedId: '0x9a6ffc707270286e98e8d0f654ce38f69efbc302ac98e2deb11fbad2211600f0', // TODO: value supraPairId: 1, // ETH_USDT -> 1, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Supra%20Premium-,ETH_USDT,-1 pythPriceFeedId: '0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace', // **fixed value: Crypto.ETH/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x9193fd47f9a0ab99b6e365a464c8a9ae30e6150fc37ed2a89c1586631f6fc4ab', priceDecimal: 8, expiration: 30, }, USDY: { oracleId: 12, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 10000, // 0.01 = 0.01 * 1e6 = 10000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x960b531667636f39e85867775f52f6b1f220a058c4de786905bdf761e06a56bb::usdy::USDY', feedId: '0x11ddf2ac1868d493e2487deeb2a0c2791bb7ca69632c8c5fefe85e09390be093', // TODO: values supraPairId: 185, pythPriceFeedId: '0xe393449f6aff8a4b6d3e1165a7c9ebec103685f3b41e60db4277b5b6d10e7326', pythPriceInfoObject: '0x62e15c2fd1437a4d0e111dbd8a193f244878ba25cc7caa9120d0ee41ac151ea5', priceDecimal: 6, expiration: 30, }, NS: { oracleId: 13, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 100000, // 0.01 = 0.01 * 1e6 = 10000 historicalPriceTTL: 300000, // 5min(millisecond) coinType: '0x5145494a5f5100e645e4b0aa950fa6b68f614e8c59e17bc5ded3495123a79178::ns::NS', feedId: '0xc771ec0ca245857f30195ce05197a7b3ab41c58c1e8abe0661919d90675ad63d', supraPairId: 99999, // ignore for now pythPriceFeedId: '0xbb5ff26e47a3a6cc7ec2fce1db996c2a145300edc5acaabe43bf9ff7c5dd5d32', pythPriceInfoObject: '0xc6352e1ea55d7b5acc3ed690cc3cdf8007978071d7bfd6a189445018cfb366e0', priceDecimal: 6, expiration: 30, }, LorenzoBTC: { oracleId: 14, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 20000000000000, // 20000000000000 = 200000 * 1e8 = 20000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 300000, // 5min(millisecond) coinType: '0x5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6::coin::COIN', feedId: '0xdf9b254a7a64742e1edf8c48bd2a1f182b52f020de2ab070ae0e3f9228d05280', supraPairId: 0, pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 30, }, DEEP: { oracleId: 15, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 200, // x1: 2% = 0.02 * 10000 = 200 priceDiffThreshold2: 400, // x2: 4% = 0.04 * 10000 = 400 maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 400000, // 0.4 = 0.4 * 1e6 = 400000 minimumEffectivePrice: 1000, // 0.001 = 0.001 * 1e6 = 1000 historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0xdeeb7a4662eec9f2f3def03fb937a663dddaa2e215b8078a284d026b7946c270::deep::DEEP", feedId: "0x4558092b08ad1b33b0eb536f91a4655693c2390ac568f06de6f6fad827888600", supraPairId: 491, pythPriceFeedId: "0x29bdd5248234e33bd93d3b81100b5fa32eaa5997843847e2c2cb16d7c6d9f7ff", pythPriceInfoObject: "0x8c7f3a322b94cc69db2a2ac575cbd94bf5766113324c3a3eceac91e3e88a51ed", priceDecimal: 6, expiration: 30, }, FDUSD: { oracleId: 16, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 80, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 150, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 10000, // 0.01 = 0.01 * 1e6 = 10000 historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0xf16e6b723f242ec745dfd7634ad072c42d5c1d9ac9d62a39c381303eaa57693a::fdusd::FDUSD", feedId: "0x843b39829166bd97d61843b8967405f13d443e066ce2f4fa0685f187974d34bd", supraPairId: 474, pythPriceFeedId: "0xccdc1a08923e2e4f4b1e6ea89de6acbc5fe1948e9706f5604b8cb50bc1ed3979", pythPriceInfoObject: "0x5f6583b2b0fe1ecf94aaffeaab8a838794693960cea48c0da282d5f4a24be027", priceDecimal: 6, expiration: 30, }, BLUE: { oracleId: 17, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 200, // x1: 0.8% = 0.008 * 10000 = 80 priceDiffThreshold2: 400, // x2: 1.5% = 0.015 * 10000 = 150 maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000000, // 2 = 2 * 1e6 = 2000000 minimumEffectivePrice: 1000000, // 0.01 = 0.01 * 1e6 = 10000 historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0xe1b45a0e641b9955a20aa0ad1c1f4ad86aad8afb07296d4085e349a50e90bdca::blue::BLUE", feedId: "0xd8286c11df7e49496ee75622ae4132c56385c30b4bedb392e36c0699a52a1d52", supraPairId: 99999, pythPriceFeedId: "0x04cfeb7b143eb9c48e9b074125c1a3447b85f59c31164dc20c1beaa6f21f2b6b", pythPriceInfoObject: "0x5515a34fc610bba6b601575ed1d2535b2f9df1f339fd0d435fef487c1ee3df9c", priceDecimal: 9, expiration: 30, }, BUCK: { oracleId: 18, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 80, priceDiffThreshold2: 150, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000000, minimumEffectivePrice: 1000000, historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0xce7ff77a83ea0cb6fd39bd8748e2ec89a3f41e8efdc3f4eb123e0ca37b184db2::buck::BUCK", feedId: "0x93c1b815f64ef7c4311d74ff7c0ca1e47739c3ac31fdee0068c30887633ba2fb", supraPairId: 161, pythPriceFeedId: "0xfdf28a46570252b25fd31cb257973f865afc5ca2f320439e45d95e0394bc7382", pythPriceInfoObject: "0x3ef821a54dbdfe3f211b2ff7261dea0f0330c72fd292422ce586e21f43809a56", priceDecimal: 9, expiration: 30, }, SUIUSDT: { oracleId: 19, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 80, priceDiffThreshold2: 150, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 2000000, minimumEffectivePrice: 100000, historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0x375f70cf2ae4c00bf37117d0c85a2c71545e6ee05c4a5c7d282cd66a4504b068::usdt::USDT", feedId: "0xdeba21105ff41300f8829aaeba45fdec25d1533a64d504ef0348ff005da3fbe5", supraPairId: 48, pythPriceFeedId: "0x2b89b9dc8fdf9f34709a5b106b472f0f39bb6ca9ce04b0fd7f2e971688e2e53b", pythPriceInfoObject: "0x985e3db9f93f76ee8bace7c3dd5cc676a096accd5d9e09e9ae0fb6e492b14572", priceDecimal: 6, expiration: 30, }, STSUI: { oracleId: 20, maxTimestampDiff: 30000, // 30s(millisecond) priceDiffThreshold1: 100, priceDiffThreshold2: 300, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 10000000000, minimumEffectivePrice: 100000000, historicalPriceTTL: 300000, // 5min(millisecond) coinType: "0xd1b72982e40348d069bb1ff701e634c117bb5f741f44dff91e472d3b01461e55::stsui::STSUI", feedId: "0xd7a8c920db9f8b5c3c300307d88fca53684fd15b760977dbf8f0adc6e55783bd", supraPairId: 90, pythPriceFeedId: "0x23d7315113f5b1d3ba7a83604c44b94d79f4fd69af77f804fc7f920a6dc65744", pythPriceInfoObject: "0x801dbc2f0053d34734814b2d6df491ce7807a725fe9a01ad74a07e9c51396c37", priceDecimal: 9, expiration: 30, }, SUIBTC: { oracleId: 21, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 20000000000000, // 200000 = 200000 * 1e8 = 20000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: "0xaafb102dd0902f5055cadecd687fb5b71ca82ef0e0285d90afde828ec58ca96b::btc::BTC", feedId: "0x4e4666c82c476f0b51b27c5ed8c77ab960aa5e4c3a48796e179d721b471e3b7e", // TODO: value supraPairId: 0, // BTC_USDT -> 0, https://supra.com/docs/data-feeds/data-feeds-index/#:~:text=Pair%20Category-,BTC_USDT,-0 pythPriceFeedId: "0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43", // Crypto.BTC/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: "0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2", priceDecimal: 8, expiration: 30, }, WSOL: { oracleId: 22, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 100000000000, // 1000 * 1e8 = 100000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0xb7844e289a8410e50fb3ca48d69eb9cf29e27d223ef90353fe1bd8e27ff8f3f8::coin::COIN', feedId: '0x2611dff736233a6855e28ae95f8e5f62a6bf80653ddb118bf012fd783d530fa1', supraPairId: 10, // SOL_USDT -> 10 pythPriceFeedId: '0xef0d8b6fda2ceba41da15d4095d1da392a0d2f8ed0c6c7bc0f4cfac8c280b56d', // **fixed value: Crypto.SOL/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0x9d0d275efbd37d8a8855f6f2c761fa5983293dd8ce202ee5196626de8fcd4469', priceDecimal: 8, expiration: 30, } LBTC: { oracleId: 23, maxTimestampDiff: 30 * 1000, // 30s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 20000000000000, // 200000 = 200000 * 1e8 = 20000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 5 * 60 * 1000, // 5min(millisecond) coinType: '0x3e8e9423d80e1774a7ca128fccd8bf5f1f7753be658c5e645929037f7c819040::lbtc::LBTC', feedId: '0x8ee4d9d61d0bfa342cdb3ee8b7f047c91f0b586e0ff66fd6e8fc761e235e5409', // TODO: value supraPairId: 99999, // none pythPriceFeedId: '0x8f257aab6e7698bb92b15511915e593d6f8eae914452f781874754b03d0c612b', // Crypto.LBTC/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0xeba15840ddf425dacb5ff0990334fc03d034487f4ad416280859b96bf2af89f8', priceDecimal: 8, expiration: 30, }, WAL: { oracleId: 24, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, priceDiffThreshold2: 300, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 3000, // 30% = 0.3 * 10000 = 3000 maximumEffectivePrice: 10000000000, // 10 * 1e9 = 10000000000 minimumEffectivePrice: 1000000, // 0.001 * 1e9 = 1000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x356a26eb9e012a68958082340d4c4116e7f55615cf27affcff209cf0ae544f59::wal::WAL', // Mainnet verison feedId: '0x924bf9f715d857605f9f4146537fffc0414809c85845ce9d695f3645a22a5426', // TODO: value supraPairId: 99999, // none pythPriceFeedId: '0xeba0732395fae9dec4bae12e52760b35fc1c5671e2da8b449c9af4efe5d54341', // Crypto.WAL/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0xeb7e669f74d976c0b99b6ef9801e3a77716a95f1a15754e0f1399ce3fb60973d', priceDecimal: 9, expiration: 60, }, HAEDAL: { oracleId: 25, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, priceDiffThreshold2: 300, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 3000, // 30% = 0.3 * 10000 = 3000 maximumEffectivePrice: 10000000000, // 10 * 1e9 = 10000000000 minimumEffectivePrice: 1000000, // 0.001 * 1e9 = 1000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x3a304c7feba2d819ea57c3542d68439ca2c386ba02159c740f7b406e592c62ea::haedal::HAEDAL', // feedId: '0xe8a90eed4e6de66e114e6d00802852a9529054a33de0e8460ec37109f0d09d5e', // TODO: value supraPairId: 99999, // none pythPriceFeedId: '0xe67d98cc1fbd94f569d5ba6c3c3c759eb3ffc5d2b28e64538a53ae13efad8fd1', // **fixed value: Crypto.SUI/USD -> https://pyth.network/developers/price-feed-ids pythPriceInfoObject: '0xbc98681c15de1ca1b80a8e26500d43c77f7113368b024de1bf490afcb0387109', priceDecimal: 9, expiration: 60, }, XBTC: { oracleId: 26, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 50000000000000, // 500000 = 500000 * 1e8 = 50000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x876a4b7bce8aeaef60464c11f4026903e9afacab79b9b142686158aa86560b50::xbtc::XBTC', feedId: '0xbe3a049bbbdc596cc6109fcff0bc2c968e7533bcc675e5718f7ecdf3c5dae506', // TODO: value supraPairId: 0, pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 60, }, IKA: { oracleId: 27, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 4000, // 40% = 0.4 * 10000 = 4000 maximumEffectivePrice: 2000000000, // 2 = 2 * 1e9 = 2000000000 minimumEffectivePrice: 10000000, // 0.01 = 0.01 * 1e9 = 10000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x7262fb2f7a3a14c888c438a3cd9b912469a58cf60f367352c46584262e8299aa::ika::IKA', feedId: '0xebe4e84fd1b1e28622274640c1bce7f4d79f43e95c6f54bec3880781b88a0d92', // TODO: value supraPairId: 99999, // none pythPriceFeedId: '0x2b529621fa6e2c8429f623ba705572aa64175d7768365ef829df6a12c9f365f4', pythPriceInfoObject: '0x06c6b9e6eb87da329189e713b7fb319cc7990cf5abf192862a443f939eedc43b', priceDecimal: 9, expiration: 60, }, EnzoBTC: { oracleId: 28, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 50000000000000, // 500000 = 500000 * 1e8 = 50000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x8f2b5eb696ed88b71fea398d330bccfa52f6e2a5a8e1ac6180fcb25c6de42ebc::coin::COIN', feedId: '0xc7f87ba22d24e8ce5764f05f775c10f87fc04e2a411c6ad7922fc936e8f7b8e3', // TODO: value supraPairId: 99999, pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 60, }, MBTC: { oracleId: 29, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 50000000000000, // 500000 = 500000 * 1e8 = 50000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0xd1a91b46bd6d966b62686263609074ad16cfdffc63c31a4775870a2d54d20c6b::mbtc::MBTC', feedId: '0x1d7e07f8fcc6a51d55d69f425cdc84c23807aeac6516dc5d909fe537d7c6eeb1', // TODO: value supraPairId: 99999, pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 60, }, YBTC: { oracleId: 30, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 100, // x1: 1% = 0.01 * 10000 = 100 priceDiffThreshold2: 300, // x2: 3% = 0.03 * 10000 = 300 maxDurationWithinThresholds: 30 * 1000, // 30s(millisecond) maximumAllowedSpanPercentage: 700, // 7% = 0.07 * 10000 = 700 maximumEffectivePrice: 50000000000000, // 500000 = 500000 * 1e8 = 50000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e8 = 100000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0xa03ab7eee2c8e97111977b77374eaf6324ba617e7027382228350db08469189e::ybtc::YBTC', feedId: '0x9efc82d7786261800fa78fa347e1b39bf3d3808e4a3e192fb3677fa78a324928', // TODO: value supraPairId: 99999, pythPriceFeedId: '0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43', pythPriceInfoObject: '0x9a62b4863bdeaabdc9500fce769cf7e72d5585eeb28a6d26e4cafadc13f76ab2', priceDecimal: 8, expiration: 60, }, XAUM: { oracleId: 31, maxTimestampDiff: 60 * 1000, // 60s(millisecond) priceDiffThreshold1: 200, priceDiffThreshold2: 400, maxDurationWithinThresholds: 30000, // 30s(millisecond) maximumAllowedSpanPercentage: 3000, // 30% = 0.3 * 10000 = 3000 maximumEffectivePrice: 50000000000000, // 500000 = 500000 * 1e9 = 500000000000000 minimumEffectivePrice: 100000000, // 1 = 1 * 1e9 = 1000000000 historicalPriceTTL: 2 * 60 * 1000, // 2min(millisecond) coinType: '0x9d297676e7a4b771ab023291377b2adfaa4938fb9080b8d12430e4b108b836a9::xaum::XAUM', feedId: '0x5fc8ae7618a0c1551d0e5f5879d144ae5862a070f6a87c6c21c18dae3cb0645b', supraPairId: 99999, pythPriceFeedId: '0xd7db067954e28f51a96fd50c6d51775094025ced2d60af61ec9803e553471c88', pythPriceInfoObject: '0x2731a8e3e9bc69b2d6af6f4c032fcd4856c77e2c21f839134d1ebcc3a16e4b1b', priceDecimal: 9, expiration: 60, } --- # afSui, haSui, vSui API | NAVI Protocol Developer Docs [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-1.-afsui-apy) **1\. afSui APY** ------------------------------------------------------------------------------------------------------------------------------------------------ * **Base URL**: [https://open-api.naviprotocol.io/api/afsui/stats](https://open-api.naviprotocol.io/api/afsui/stats) * **Method**: `GET` * **Description**: This API retrieves the Annual Percentage Yield (APY) for afSui. * **Sample Response**: Copy { "data": { "apy": 0.027322659610035993 }, "code": 0 } * * * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-2.-hasui-apy) **2\. haSui APY** ------------------------------------------------------------------------------------------------------------------------------------------------ * **Base URL**: [https://open-api.naviprotocol.io/api/haedal/stats](https://open-api.naviprotocol.io/api/haedal/stats) * **Method**: `GET` * **Description**: This API retrieves the Annual Percentage Yield (APY) for haSui. * **Sample Response**: Copy { "data": { "apy": 0.025893894780826487 }, "code": 0 } * * * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-3.-vsui-statistics-api) **3\. vSui Statistics API** -------------------------------------------------------------------------------------------------------------------------------------------------------------------- * **Base URL**: [https://open-api.naviprotocol.io/api/volo/stats](https://open-api.naviprotocol.io/api/volo/stats) * **Method**: `GET` * **Description**: This API provides detailed statistical data for vSui. * **Sample Response**: [PreviousNAVI API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api) [NextFAQ](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/faq) Last updated 1 year ago * [1\. afSui APY](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-1.-afsui-apy) * [2\. haSui APY](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-2.-hasui-apy) * [3\. vSui Statistics API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api#id-3.-vsui-statistics-api) Copy { "data": { "operatorBalance": "39.413912684", "collectableFee": "131605.869947584", "pendingStakes": "1.009636323", "poolTotalRewards": "228631.715301755", "unstakeTicketSupply": "1.009636323", "totalStaked": "53263060.295093152", "activeStake": "52817200.312146262", "calcTotalRewards": "205768.543742003", "currentEpoch": "603", "validators": [\ {\ "address": "0xa92837bac51949cd6bac41dcec57d2a769f3c2cd2e8c0512f3eea0a2a2102b94",\ "totalStaked": "5704968.097185029",\ "priority": 0,\ "apy": "0.025869002321274353",\ "name": "P2P.ORG"\ },\ {\ "address": "0x4fffd0005522be4bc029724c7f0f6ed7093a6bf3a09b90e62f61dc15181e1a3e",\ "totalStaked": "2732652.145117887",\ "priority": 5,\ "apy": "0.02802546234307326",\ "name": "Mysten-1"\ },\ {\ "address": "0xd1d00bcc9661120fc6b0f233a2f6810f39e71b39fc637cb1b9e5635edb3b0c40",\ "totalStaked": "0",\ "priority": 1,\ "apy": "0.026324199442381593",\ "name": "stakefish"\ },\ {\ "address": "0x00ae78d3e5ba5d6b8de32455474f52811b95617cbad39ebf4f9e2daf67187407",\ "totalStaked": "34829854.384452006",\ "priority": 6,\ "apy": "0.029263662217253628",\ "name": "OKXEarn"\ },\ {\ "address": "0x184fbf9d6c2d2d3f27e27fe3ca2d3b4080bd406221e345e2d36633e638e988e1",\ "totalStaked": "0",\ "priority": 2,\ "apy": "0.027428769782009293",\ "name": "Cosmostation"\ },\ {\ "address": "0xcb7efe4253a0fe58df608d8a2d3c0eea94b4b40a8738c8daae4eb77830c16cd7",\ "totalStaked": "9995584.658701907",\ "priority": 7,\ "apy": "0.028026708009159452",\ "name": "Mysten-2"\ }\ ], "exchangeRate": 1.03538849964801, "totalSupply": "51641319.02892124", "apy": 0.0271, "sortedValidators": [\ "0xcb7efe4253a0fe58df608d8a2d3c0eea94b4b40a8738c8daae4eb77830c16cd7",\ "0x00ae78d3e5ba5d6b8de32455474f52811b95617cbad39ebf4f9e2daf67187407",\ "0x4fffd0005522be4bc029724c7f0f6ed7093a6bf3a09b90e62f61dc15181e1a3e",\ "0x3047b5258a4ba6d7a6bea9ada69cb336ecfb24fe1c3cea83094396665eba0de5",\ "0x184fbf9d6c2d2d3f27e27fe3ca2d3b4080bd406221e345e2d36633e638e988e1",\ "0x00ae78d3e5a5d6b8de32455474f52811b95617cbad39ebf4f9e2daf671874007",\ "0xd1d00bcc9661120fc6b0f233a2f6810f39e71b39fc637cb1b9e5635edb3b0c40",\ "0xa92837bac51949cd6bac41dcec57d2a769f3c2cd2e8c0512f3eea0a2a2102b94",\ "0xa2bf32db91ad54684cfd8a4e1d85f7672875d62421d40a8d993f601cff9b61ff",\ "0xc64e58562d424e248abce5b886b264209c23d05b7b75bc5a1a5e137700f0ddf8",\ "0x752b18cfa44304b9bbb110ba95211556f79c62bc2916c23eeb7aea959f5b3463"\ ], "maxInstantUnstake": "52817200.312146264", "maxNoFeeUnstake": "3125202.305753155" }, "code": 0 } --- # Dynamic Calculator | NAVI Protocol Developer Docs This module includes functions to dynamically calculate a user's health factor, collateral value, loan value, APY, and more, accounting for potential changes in the user's balances. It is utilized for risk management and user-interface purposes, such as determining whether a user's actions might put their account at risk of liquidation, or providing insights into the potential impact of a user's intended actions on their account. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator#dynamic_health_factor) dynamic\_health\_factor > **Description:** This function calculates a user's dynamic health factor, considering potential changes in their supply and borrow balances. It helps assess the user's risk level in relation to liquidation. > **Use Cases:** This function is used when estimating how a user's health factor would be affected by an increase or decrease in their supplied or borrowed assets. It is critical for risk management and liquidation prevention. Copy public fun dynamic_health_factor( clock: &Clock, storage: &mut Storage, oracle: &PriceOracle, pool: &mut Pool, user: address, asset: u8, estimate_supply_value: u64, estimate_borrow_value: u64, is_increase: bool ): u256 {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator#dynamic_calculate_apy) ~dynamic\_calculate\_apy~ Since the upgrade to V3 incentives, V2 is no longer in use, so its APY will remain at 0. Don't use this function to fetch APY data. > **Description:** This function calculates the dynamic APY for IncentiveV2 based on changes in a user's supply and borrow balances. It provides both the supply APY and borrow APY. > **Use Cases:** This function is used to estimate how changes in a user's supply and borrow amounts will impact their expected yield. It is essential for users deciding whether to adjust their positions in a lending pool. [PreviousCalculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/calculator) [NextStorage](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage) Last updated 10 months ago * [dynamic\_health\_factor](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator#dynamic_health_factor) * [dynamic\_calculate\_apy](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator#dynamic_calculate_apy) Copy public fun dynamic_calculate_apy( clock: &Clock, storage: &mut Storage, pool: &mut Pool, asset: u8, estimate_supply_value: u64, estimate_borrow_value: u64, is_increase: bool ): (u256, u256){} --- # Storage | NAVI Protocol Developer Docs This module provides key information related to the reserves in the lending pool and user-specific data, such as asset holdings and balances. They are crucial for tracking the state of the protocol and individual user interactions, helping developers and users manage their assets within the NAVI protocol. ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_reserves_count) get\_reserves\_count > **Description:** This function returns the number of reserve assets available in the storage pool. It provides an overview of how many different assets are being managed in the lending protocol. > **Use Cases:** This function is used when a developer or user needs to know the total number of asset reserves in the pool, typically for pool status checks or when initializing interactions with multiple reserves. Copy public fun get_reserves_count( storage: &Storage ): u8 {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_user_assets) get\_user\_assets > **Description:** This function retrieves the list of assets and their respective balances held by a specific user within the storage pool. It returns vectors representing the asset IDs and their corresponding values. > **Use Cases:** This function is used to get a comprehensive view of a user's asset holdings in the lending pool, useful for portfolio management or determining eligibility for borrowing and rewards. Copy public fun get_user_assets( storage: &Storage, user: address ): (vector, vector) {} ### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_user_balance) get\_user\_balance > **Description:** This function returns the balance of a specific asset for a given user, including both supply and borrow amounts. It is essential for tracking the user's positions within the lending protocol. > **Use Cases:** This function is used when a user or developer needs to check the current balance of an asset supplied or borrowed by a specific user, which is critical for monitoring positions and potential liquidation risks. [PreviousDynamic Calculator](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/dynamic-calculator) [NextRelease History](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history) Last updated 1 year ago * [get\_reserves\_count](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_reserves_count) * [get\_user\_assets](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_user_assets) * [get\_user\_balance](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage#get_user_balance) Copy public fun get_user_balance( storage: &mut Storage, asset: u8, user: address ): (u256, u256) {} --- # Demo | NAVI Protocol Developer Docs A comprehensive **vault demo** is available for developers, providing detailed instructions on building a Move project, the publishing process, integration with NAVI Account Cap and example transactions (TXs) to guide you through the integration. [Vault Demo - Move](https://github.com/naviprotocol/account-cap-demo) [PreviousIntegration with Account Cap](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/contract-integration-with-navi/integration-with-account-cap) [NextNAVI Uptime Status Page](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-uptime-status-page) Last updated 1 year ago --- # Release History | NAVI Protocol Developer Docs [NAVI Lending Protocol Upgrade Announcement (2025/11/17)](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17) [PreviousStorage](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/storage) [NextNAVI Lending Protocol Upgrade Announcement (2025/11/17)](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17) --- # NAVI API | NAVI Protocol Developer Docs [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-1.-navi-pools-api) **1\. NAVI Pools API** ---------------------------------------------------------------------------------------------------------------------------------------------- **Base URL:** `https://open-api.naviprotocol.io/api/navi/pools` **Method:** `GET` **Description:** Fetches detailed information about the NAVI Protocol Pools, including: 1. **Supply and Borrow Details:** * Current supply and borrow indexes: `currentSupplyIndex`, `currentBorrowIndex` * Total supply and borrowed amounts: `totalSupplyAmount`, `borrowedAmount` * Treasury details: `treasuryBalance` and more. 2. **Pool Parameters:** * Loan-to-Value (LTV): `ltv` * Supply and borrow caps: `supplyCapCeiling`, `borrowCapCeiling` 3. **Incentive Data:** * Supply and borrow incentives with APY details: `supplyIncentiveApyInfo`, `borrowIncentiveApyInfo` **Sample Response**: Copy { "borrowCapCeiling": "900000000000000000000000000", "coinType": "0000000000000000000000000000000000000000000000000000000000000002::sui::SUI", "currentBorrowIndex": "1116524042153776588547130964", "currentBorrowRate": "68416358820350495021185607", "currentSupplyIndex": "1039665797279616681092618808", "currentSupplyRate": "35127941119962108657922993", "id": 0, "isIsolated": false, "lastUpdateTimestamp": "1733450139160", "ltv": "750000000000000000000000000", "oracleId": 0, "reserveFieldA": "0", "reserveFieldB": "0", "reserveFieldC": "0", "supplyCapCeiling": "7.5e+34", "treasuryBalance": "2313971512229", "treasuryFactor": "100000000000000000000000000", "totalSupplyAmount": "52969686454591258", "minimumAmount": "7500000", "leftSupply": "22030313.54540874", "validBorrowAmount": "47672717809132132.2", "borrowedAmount": "33996182745883118", "leftBorrowAmount": "47672717775135949.2", "availableBorrow": "13676535063249014.2", "oracle": { "decimal": 9, "value": "4348335140", "price": "4.34833514", "oracleId": 0, "valid": true }, "supplyIncentiveApyInfo": { "vaultApr": "3.512", "boostedApr": "1.396", "stakingYieldApy": "0", "rewardCoin": [\ "549e8b69270defbfafd4f94e17ec44cdbdd99820b33bda2278dea3b9a32d3f55::cert::CERT",\ "a99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX"\ ], "apy": "4.908" }, "borrowIncentiveApyInfo": { "vaultApr": "6.841", "boostedApr": "6.353", "stakingYieldApy": "0", "rewardCoin": [\ "549e8b69270defbfafd4f94e17ec44cdbdd99820b33bda2278dea3b9a32d3f55::cert::CERT",\ "a99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX"\ ], "apy": "0.488" } } * * * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-2.-navi-package-api) **2\. NAVI Package API** -------------------------------------------------------------------------------------------------------------------------------------------------- **Base URL**: `https://open-api.naviprotocol.io/api/package` **Method**: `GET` **Description**: Returns the current NAVI package ID and details of outdated package versions for backward compatibility. **Sample Response**: * * * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-3.-navi-config-api) **3\. NAVI Config API** ------------------------------------------------------------------------------------------------------------------------------------------------ **Base URL**: `https://open-api.naviprotocol.io/api/navi/contract/configs` **Method**: `GET` **Description**: Provides detailed configuration data for NAVI Protocol, including reserve data, price feeds, and flash loan configurations: * **Reserve Data**: Supply and borrow caps, rates, LTV, treasury balance, and liquidation factors. * **Price Feed**: Oracle details, pricing thresholds, and historical price settings. * **Flash Loan Configurations**: Max/min amounts, supplier rates, and treasury rates. **Sample Response**: [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-4.-navi-fee-and-revenue-api) 4\. NAVI Fee and Revenue API -------------------------------------------------------------------------------------------------------------------------------------------------------------- **Base URL**: `https://open-api.naviprotocol.io/api/navi/fee?fromTimestamp={fromTimeStamp}` **Method**: `GET` **Description**: Fetches NAVI's fee and revenue data starting from a specified timestamp. The data is calculated for each 24-hour period. **Parameters**: * `**fromTimestamp**` (_integer_): The starting time in Unix timestamp format. **Sample Response**: [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-5.-navi-flashloan-config-api) 5\. NAVI Flashloan Config API ---------------------------------------------------------------------------------------------------------------------------------------------------------------- **Base URL**: `https://open-api.naviprotocol.io/api/navi/flashloan` **Method**: `GET` **Description**: Fetches the configuration details for NAVI's flashloan settings, including limits, fees, and pool information. **Explanation of Response Parameters:** 1. `**0x2::sui::SUI**`: * Represents the asset pool for which the flashloan configuration is provided. In this case, it is the **SUI** token. 2. `**max**`: * The maximum amount with token decimal of this asset available for a single flashloan transaction. * **Value in the example:** `"200000000000000"` (denoted in the smallest unit of the asset). 3. `**min**`: * The minimum amount with token decimal of this asset required to initiate a flashloan. * **Value in the example:** `"0"` (indicating no minimum amount is required). 4. `**assetId**`: * A unique asset id for the asset within the NAVI Protocol. * **Value in the example:** `0`. 5. `**poolId**`: * The unique id of the pool from which the flashloan will be provided. * **Value in the example:** `"0x96df0fce3c471489f4debaaa762cf960b3d97820bd1f3f025ff8190730e958c5"`. 6. `**supplierFee**`: * The fee charged to suppliers of the asset for participating in the flashloan mechanism. * **Value in the example:** `0` (indicating no supplier fee is charged). 7. `**flashloanFee**`: * The fee rate (percentage) charged for executing the flashloan. * **Value in the example:** `0.0006` (indicating a 0.06% fee for the loan amount). **Sample Response**: [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-6.-navi-oracle-api) 6\. NAVI Oracle API -------------------------------------------------------------------------------------------------------------------------------------------- **Base URL**: `https://open-api.naviprotocol.io/api/navi/oracle` **Method**: `GET` **Description**: Fetches oracle-related configuration and data for NAVI, including price feed settings, thresholds, and parameters for calculating effective prices. **Sample Response**: * * * [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-7.-navi-claimed-rewards-history) 7\. NAVI Claimed Rewards History ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- **Base URL**: `https://open-api.naviprotocol.io/api/navi/user/rewards?userAddress={userAddress}` **Method**: `GET` **Description**: Retrieves the transaction IDs of rewards claimed by a specific user, identified by their wallet address. **Parameters**: * `**userAddress**` (_string_): The user address string **Sample Response**: [PreviousNAVI API Collection](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection) [NextafSui, haSui, vSui API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/afsui-hasui-vsui-api) Last updated 1 year ago * [1\. NAVI Pools API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-1.-navi-pools-api) * [2\. NAVI Package API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-2.-navi-package-api) * [3\. NAVI Config API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-3.-navi-config-api) * [4\. NAVI Fee and Revenue API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-4.-navi-fee-and-revenue-api) * [5\. NAVI Flashloan Config API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-5.-navi-flashloan-config-api) * [6\. NAVI Oracle API](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-6.-navi-oracle-api) * [7\. NAVI Claimed Rewards History](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/navi-api-collection/navi-api#id-7.-navi-claimed-rewards-history) Copy { "packageId": "0x834a86970ae93a73faf4fff16ae40bdb72b91c47be585fff19a2af60a19ddca3", "outdated": [\ {\ "packageId": "0x66aa3335901ce7e04b85ed6597ee42d4b479f7110bf98e8ebd474fa32a0027e1",\ "version": 19\ },\ ...\ ] } Copy { "coin_type": "0x5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6::coin::COIN", "symbal": "stBTC", "reserve_data": { "id": 14, "oracle_id": 14, "is_solated": false, "coin_type": "5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6::coin::COIN", "supply_cap_ceiling": "580", "borrow_cap_ceiling": "0%", "current_supply_rate": "0", "current_borrow_rate": "0", "current_supply_index": "1", "current_borrow_index": "1", "borrow_balance": { "total_supply": "0" }, "supply_balance": { "total_supply": "5,501.08" }, "ltv": "35%", "treasury_factor": "10%", "treasury_balance": "0", "borrow_rate_factors": { "base_rate": "0%", "optimal_utilization": "50%", "multiplier": "8%", "jump_rate_multiplier": "600%", "reserve_factor": "20%" }, "liquidation_factors": { "bonus": "5%", "threshold": "45%", "ratio": "35%" }, "last_update_timestamp": "2024-12-06T00:10:18.832Z" }, "price_feed": { "id": "0xdf9b254a7a64742e1edf8c48bd2a1f182b52f020de2ab070ae0e3f9228d05280", "coin_type": "0x5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6::coin::COIN", "oracle_id": 14, "enable": true, "max_timestamp_diff": "30000", "price_diff_threshold1": "100", "price_diff_threshold2": "300", "max_duration_within_thresholds": "30000", "diff_threshold2_timer": "0", "historical_price_ttl": "300000", "primary": "PythOracleProvider", "secondary": "SupraOracleProvider", "maximum_allowed_span_percentage": "700", "maximum_effective_price": "200,000", "minimum_effective_price": "1" }, "flash_loan_config": { "id": "", "asset_id": 0, "pool_id": "", "coin_type": "0x5f496ed5d9d045c5b788dc1bb85f54100f2ede11e46f6a232c29daada4c5bdb6::coin::COIN", "max": 0, "min": 0, "rate_to_supplier": 0, "rate_to_treasury": 0 } }, Copy { "data": { "from": 1732587539, "to": 1732673939, "flashLoanRevenue": 47.8772023048398, "borrowInterestRevenue": 8856.9845984033, "borrowInterestFee": 35427.9383936132, "borrowRevenue": 8244.74392228731, "naviDailyRevenue": 17149.6057229954 }, "code": 0 } Copy { "0x0000000000000000000000000000000000000000000000000000000000000002::sui::SUI": { "max": "200000000000000", "min": "0", "assetId": 0, "poolId": "0x96df0fce3c471489f4debaaa762cf960b3d97820bd1f3f025ff8190730e958c5", "supplierFee": 0, "flashloanFee": 0.0006 } } Copy { "SUI": { "oracleId": 0, "maxTimestampDiff": 30000, "priceDiffThreshold1": 100, "priceDiffThreshold2": 300, "maxDurationWithinThresholds": 30000, "maximumAllowedSpanPercentage": 700, "maximumEffectivePrice": 10000000000, "minimumEffectivePrice": 100000000, "historicalPriceTTL": 300000, "coinType": "0x0000000000000000000000000000000000000000000000000000000000000002::sui::SUI", "feedId": "0x2cab9b151ca1721624b09b421cc57d0bb26a1feb5da1f821492204b098ec35c9", "supraPairId": 90, "pythPriceFeedId": "0x23d7315113f5b1d3ba7a83604c44b94d79f4fd69af77f804fc7f920a6dc65744", "pythPriceInfoObject": "0x801dbc2f0053d34734814b2d6df491ce7807a725fe9a01ad74a07e9c51396c37", "priceDecimal": 9, "expiration": 30 } } Copy { "amount": "1752445", "pool": "0x9b646906608b791a2fc65ec246d2a18e0d49e5fd0aae29dbfbaf0112885d93c9", "sender": "0x9f4c3feee7b70d6cf2d0c25296c4581bd4c281b11f45910c94bb8a962db0349d", "timestamp": "2024-12-06T01:02:59.512Z", "coin_type": "a99b8952d4f7d947ea77fe0ecdcc9e5fc0bcab2841d6e2a5aa00c3044e5544b5::navx::NAVX", "token_price": 0.144426003098488 } --- # NAVI Lending Protocol Upgrade Announcement (2025/11/17) | NAVI Protocol Developer Docs We are excited to announce that **NAVI Lending** will soon undergo a major upgrade! This update is designed to further enhance capital utilization, security, and flexibility, bringing a smoother and smarter DeFi experience to both ecosystem partners and end users. * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#launch-schedule) **Launch Schedule** * **Estimated Time:** * **PST:** 2025/11/17 4:00 PM * **EST:** 2025/11/17 7:00 PM * **SGT:** 2025/11/18 08:00 AM * **Package Id:** Copy 0xee0041239b89564ce870a7dec5ddc5d114367ab94a1137e90aa0633cb76518e0 * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#guideline-overview) **Guideline Overview** **NAVI Lending Core Smart Contract Upgrade** 1. Our package\_id will be updated due to a smart contract upgrade; the old package\_id will be deprecated immediately. 2. Breaking Change: For **SUI-asset** operations: **borrow, withdraw, flashloan, liquidation** need a **new interface** immediately after the upgrade. 3. For Non-SUI-Asset operations, **borrow, withdraw, flashloan**, **liquidation** are still functional for **30 days grace period**. After 30 days, the legacy interface will be deprecated. 4. No changes needed: **deposit, repay, claim\_reward** operations work as before 5. No changes needed: **getter&view** functions work as before #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#upgrade-overview) **Upgrade Overview** This NAVI upgrade covers two core areas: 1. **Launch of the Fund Manager Module** * Supplied SUI assets will be automatically staked via vSUI to increase protocol-wide yields. 2. **Flexible Borrow Fee Structure** * Allows assigning a special borrowing fee rate for users. * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#partner-notice-and-action-checklist) **Partner Notice & Action Checklist** * **Interface/Compatibility Changes:** 1. **Package Id will be upgraded** 2. **Module** names and paths remain unchanged. 3. **Function** **call** may introduce **extra arguments**—please review the updated API documents. 4. Interface migration requirements: * If you **withdraw/borrow/liquidate/flashloan** with a **non-SUI assets (asset id != 0)**, you can still use the original interface. But it's highly recommended to use the **new v2 interface**. The legacy interface will be deprecated in the future. * If you **withdraw/borrow/liquidate/flashloan** with **SUI asset (asset id = 0)**, you need to use the **new v2 interface**. * If you **deposit/repay/claim\_reward**, you don't need to change the interface * **Migration Tips:** 1. Update your packageId in your dependencies. Detailed guides for different user types: * **For Smart Contract Builders:** * You will need to update the NAVI lending\_core package\_id in your Move.toml. * If you use GitHub/MVR as a dependency, we will update the link after the upgrade. * Use the new interfaces in your smart contract. * **For Frontend/Backend Builders:** * Use the new package id in your move call. * Use the new interfaces in your move call. * If you use the MVR as a reference, we will update the link after the upgrade. 2. Pause any automated scripts before the maintenance; resume after verifying all integration points with the new contracts. * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#for-developers-major-user-facing-interface-changes) **【For Developers】Major User-facing Interface Changes** Below are all key user entry-points for fund operations. Partners are strongly encouraged to migrate to these new interfaces for the best compatibility and feature support: Firstly, please import the **SuiSystemState** to your module: **1\. entry\_withdraw (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * Added system\_state as a required on-chain argument. * * * **2\. entry\_borrow (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * Added system\_state as a required on-chain argument. * * * **3\. entry\_liquidation (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * Added system\_state as a required on-chain argument. * * * **4\. withdraw\_with\_account\_cap (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * v2 adds both system\_state and ctx arguments. * * * **5\. withdraw (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * v2 adds system\_state argument for advanced on-chain support. * * * **6\. borrow (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * v2 adds system\_state as a required on-chain argument. * * * **7\. borrow\_with\_account\_cap (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * v2 adds both system\_state and ctx arguments. * * * **8\. liquidation (incentive\_v3 module)** **Old (Legacy):** **New:** **Key change:** * v2 adds system\_state as a required on-chain argument. * * * **9\. flash\_loan\_with\_ctx (lending module)** **Old (Legacy):** **New:** **Key change:** * v2 adds system\_state as a required on-chain argument. * * * **10\. flash\_loan\_with\_account\_cap (lending module)** **Old (Legacy):** **New:** **Key change:** * v2 adds both system\_state and ctx arguments. * * * **Interface Upgrade Summary** * All major fund operation APIs (withdraw, borrow, liquidation, flash loan) now have corresponding \*\_v2 entry points. * The updated function signatures feature a more complete argument list; all partner integrations should migrate to the new interfaces. * Legacy versions WILL NOT support new reward, liquidation, flexible fee, or protected mode features. * * * #### [](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history/navi-lending-protocol-upgrade-announcement-2025-11-17#faq) **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 borrow/liquidation interfaces remain usable?** **A:** The legacy methods will still work for non-SUI asset operations, but migration to the new entry points is strongly recommended to enjoy all new features and maximum flexibility. * **Q3: How will the staking yield be used?** **A:** The staking yield generated from the fund manager module will be used to incentivize users in the future. * **Q4: Is the upgrade audited?** **A:** Yes. The upgrade is fully audited by OtterSec and Movebit. * * * **——NAVI Protocol Team** [PreviousRelease History](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/smart-contract-overview/release-history) [NextDecentralized Oracle](https://naviprotocol.gitbook.io/navi-protocol-developer-docs/decentralized-oracle) Last updated 1 month ago Copy use sui_system::sui_system::{SuiSystemState}; Copy public entry fun entry_withdraw( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ) Copy public entry fun entry_withdraw_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) Copy public entry fun entry_borrow( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ) Copy public entry fun entry_borrow_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) Copy public entry fun entry_liquidation( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, debt_asset: u8, debt_pool: &mut Pool, debt_coin: Coin, collateral_asset: u8, collateral_pool: &mut Pool, liquidate_user: address, liquidate_amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ) Copy public entry fun entry_liquidation_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, debt_asset: u8, debt_pool: &mut Pool, debt_coin: Coin, collateral_asset: u8, collateral_pool: &mut Pool, liquidate_user: address, liquidate_amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ) Copy public(friend) fun withdraw_with_account_cap( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, account_cap: &AccountCap ): Balance Copy public(friend) fun withdraw_with_account_cap_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, account_cap: &AccountCap, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance Copy public fun withdraw( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ): Balance Copy public fun withdraw_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance Copy public fun borrow( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ): Balance Copy public fun borrow_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance Copy public fun borrow_with_account_cap( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap ): Balance Copy public fun borrow_with_account_cap_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, pool: &mut Pool, asset: u8, amount: u64, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, account_cap: &AccountCap, system_state: &mut SuiSystemState, ctx: &mut TxContext ): Balance Copy public fun liquidation( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, debt_asset: u8, debt_pool: &mut Pool, debt_balance: Balance, collateral_asset: u8, collateral_pool: &mut Pool, liquidate_user: address, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, ctx: &mut TxContext ): (Balance, Balance) Copy public fun liquidation_v2( clock: &Clock, oracle: &PriceOracle, storage: &mut Storage, debt_asset: u8, debt_pool: &mut Pool, debt_balance: Balance, collateral_asset: u8, collateral_pool: &mut Pool, liquidate_user: address, incentive_v2: &mut IncentiveV2, incentive_v3: &mut Incentive, system_state: &mut SuiSystemState, ctx: &mut TxContext ): (Balance, Balance) Copy public fun flash_loan_with_ctx( config: &FlashLoanConfig, pool: &mut Pool, amount: u64, ctx: &mut TxContext ): (Balance, FlashLoanReceipt) Copy public fun flash_loan_with_ctx_v2( config: &FlashLoanConfig, pool: &mut Pool, amount: u64, system_state: &mut SuiSystemState, ctx: &mut TxContext ): (Balance, FlashLoanReceipt) Copy public fun flash_loan_with_account_cap( config: &FlashLoanConfig, pool: &mut Pool, amount: u64, account_cap: &AccountCap ): (Balance, FlashLoanReceipt) Copy public fun flash_loan_with_account_cap_v2( config: &FlashLoanConfig, pool: &mut Pool, amount: u64, account_cap: &AccountCap, system_state: &mut SuiSystemState, ctx: &mut TxContext ): (Balance, FlashLoanReceipt) ---