Platform Fees
Interface-level fee policy and disclosure guidance for Avana frontends.
Overview
This page describes interface policy, not the core protocol borrowing model. Avana may charge frontend or service fees on official interfaces, but those operational charges should not be confused with the protocol's collateral, oracle, or liquidation rules.
Exact fee rates, exemptions, and rollout status are operational settings and should be verified in the live interface or release materials before relying on them.
Interface vs Protocol
Avana's core contracts govern LP admission, borrowing capacity, and liquidation behavior. Interface fees, if enabled, are layered on top of those contracts as a frontend business policy rather than as a change to the borrow or risk engine itself.
- • Protocol economics determine debt accrual, collateral treatment, and liquidation outcomes.
- • Interface fees are an operational choice 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 surfaced clearly before signature so builders and users can distinguish it from gas costs, swap fees, or protocol-level debt and liquidation effects.
Treasury Usage
If interface fees are collected, they typically fund product operations such as infrastructure, monitoring, security work, documentation, and support. Governance may choose to formalize or change these policies over time.
Treasury use should be published as operational reporting, not implied by the protocol's collateral architecture.
Integration Notes
- • Builders should verify current fee policy before quoting end-user costs.
- • Avoid hard-coding interface-fee assumptions into protocol integrations unless the policy is formally versioned.
- • When documenting integrations, keep fee policy separate from borrow capacity and liquidation logic.