Architecture
This illustration provides a high-level overview of the Athena protocol's core contracts and their interactions.
Core Contracts
ATEN Token
The ATEN token follows the standard ERC-20 specification with an added transferAndCall feature. This enables direct smart contract interactions without relying on the typical approve/transferFrom mechanism. You can review the details of this function here:
If you are looking for information about the tokenomics of the ATEN token, you can find them in the dedicated page.
AthenaPositionToken
The AthenaPositionToken tokens implements most of the ERC-721 (NFT) standard methods with slight modifications, as well as Athena specific methods including:
All Liquidity Position Tokens also implement ERC721Enumerable, which adds enumerability of all the token IDs in the contract as well as all token IDs owned by each account.
AthenaPositionTokenAthenaCoverToken
The AthenaCoverToken tokens implements most of the ERC-721 (NFT) standard methods with slight modifications, as well as Athena specific methods including:
All Cover Tokens also implement ERC721Enumerable, which adds enumerability of all the token IDs in the contract as well as all token IDs owned by each account.
AthenaCoverTokenLiquidityManager
The Liquidity Manager serves as the primary entry point for users interacting with the Athena protocol. It monitors the states of insurance pools, liquidity positions, and covers, facilitating core contract interactions.
Key functions of the Liquidity Manager include:
StrategyManager
The Strategy Manager functions as an abstraction layer between the Liquidity Manager and liquidity strategies. It ensures that deposits and withdrawals are processed uniformly across all strategies.
ClaimManager
The Claim Manager handles all claim-related interactions between users, the Liquidity Manager, and arbitration courts. It monitors the status of claims and manages the cover compensation process.
Key functions of the Liquidity Manager include:
External Contracts
The Athena protocol integrates with various external contracts to generate yield for its liquidity providers and facilitate claim dispute resolutions.
For a comprehensive list of these protocols, refer to the Markets section:
Markets OverviewLiquidity Strategies
When users provide liquidity to the Athena protocol, they can allocate their funds across a range of decentralized finance (DeFi) protocols to generate base yield. These protocols, known as strategies, are managed by the StrategyManager contract. Strategies may include lending protocols, yield farming, staking, or liquidity vaults.
Arbitration Courts
If a claim is contested by a prosecutor, it is escalated to an on-chain court for arbitration. Standard Athena liquidity pools utilize the decentralized Kleros court system to ensure impartial rulings. Certain specialized insurance pools may have their own dedicated courts. To determine which court is assigned to a specific pool, you can review the pool’s jurisdiction on its details page.
All courts use the ERC-792 Arbitration Standard as well as the ERC-1497 Evidence Standard.
You can learn more about Kleros and its arbitration system here:
Libraries
Athena integrates several libraries across the protocol. Below are some of the core libraries in use:
VirtualPool
Defines an internal interface for managing multiple pools within a single contract. This module is utilized by the LiquidityManager to streamline interactions with all pools.
AthenaDataProvider
Standardizes the protocol's key data structures. It is leveraged by the LiquidityManager to retrieve real-time data on pool states, liquidity positions, and active covers.
PoolMath
Performs essential computations related to pool states based on given parameters. The LiquidityManager relies on this module to determine the current conditions of the pools.
TickBitmap
Maintains a record of cover creation and expiration within the pools. It is employed by the LiquidityManager to efficiently track the lifecycle of covers.
A complete list of the libraries used in the Athena protocol can be found on our Github here.
Last updated
