Legal Disclaimer

Avana provides technical services, including a test environment, a web interface, and informational resources. The protocol consists of open-source smart contracts that can receive and hold supported crypto assets. Section 2 distinguishes those contracts from the Services and describes use of the contracts as being at the user's own risk. Avana does not control third-party applications built on the protocol or the activity of users interacting with it.

The interface does not hold private keys, control assets on a user's behalf, or modify or reverse submitted blockchain transactions. This is distinct from a deposit into a protocol contract, where the contract holds collateral according to its rules. Section 3.2 also reserves Avana's right to charge or modify interface fees. See Sections 2 and 3 for the full distinction between the protocol and the interface.

Access is subject to the eligibility and sanctions restrictions in Section 1. Users remain responsible for applicable legal and tax obligations, protecting wallet keys, and transactions signed with those keys. Sections 5 and 11 prohibit unauthorized access, disruption, abusive request volumes, and misleading integrations. Third-party wallets, protocols, and services have their own terms, fees, privacy practices, and risks, which also apply when they are used through an Avana integration.

Code availability does not give every part of the Services the same license. Section 6 describes the Services license, restrictions on Avana's marks, and the treatment of feedback. Where a software component has a separate open-source or business-source license, Section 6.2 provides that the component's license governs it. An integration therefore needs to account for the terms of each component it uses as well as the rules for accessing the Services.

The Terms describe the protocol and its dependencies as experimental technology. Contract vulnerabilities, upgrades, network failures, cyberattacks, and service interruptions can cause transactions to fail or assets to be lost. Compatible assets and networks can also change. The interface does not remove these risks, and an example or test result in the documentation does not establish that a later transaction will produce the same outcome.

LP-backed borrowing depends on the value recoverable from the underlying position. Market movement, pool inventory, oracle inputs, and liquidation liquidity can affect collateral value and account health. If an account crosses its liquidation threshold, its collateral may be settled to repay debt. These mechanics explain how protocol risk can affect an integration; they do not limit the broader risks and user responsibilities described in Section 8.

Section 9.2 excludes specified categories of damages, including consequential, indirect, incidental, and special damages, lost data, lost profits, and reductions in value. It also limits Avana's aggregate liability under the Terms to US$100. Section 9.3 explains that some exclusions or limits may not apply in jurisdictions that do not permit them. These provisions need to be read together with the conditions and exceptions in the Terms.

Section 9.4 sets out indemnification, defense, and reimbursement obligations for claims connected with use of the Services or third-party services, breaches of the Terms, submitted material, and unauthorized changes or use. The full scope, covered parties, and procedures are stated in Section 9. This summary does not expand or replace those obligations.