Platform Fees

Overview

Avana may charge frontend or service fees on official interfaces. Those charges are separate from the protocol's collateral, oracle, and liquidation rules.

Fee rates, exemptions, and rollout status are operational settings. Verify them in the live interface or release materials before relying on them.

Interface vs Protocol

Core contracts govern LP admission, borrowing capacity, and liquidation. Interface fees, if enabled, sit on top as frontend business policy rather than as a change to the borrow or risk engine.

• Protocol economics determine debt accrual, collateral treatment, and liquidation outcomes
• Interface fees are tied to a specific frontend or service path
• Direct contract integrations may follow different fee assumptions than the official UI

Disclosure

Any interface fee should be shown clearly before signature so users can distinguish it from gas costs, swap fees, and protocol-level debt or liquidation effects.

Treasury Usage

If interface fees are collected, they typically fund product operations such as infrastructure, monitoring, security work, and support. Governance may formalize or revise those policies over time.

Integration Notes

• Verify current fee policy before quoting end-user costs
• Do not hard-code interface-fee assumptions into protocol integrations unless policy is formally versioned
• Keep fee policy separate from borrow capacity and liquidation logic in integration docs