In the previous page we have seen how to create the structure of our adapter. In this section we will focus on explaining the different dimensions that our adapters can return.
We call dimension to the attributes returned by the
fetchfunction of our adapters. Depending on where would you like to list your project, you should return one of the below dimensions.
All dimensions can be returned in USD value (
string) or as balance object (
// volume dimension in USD
// volume dimension in tokens object
In order to be listed your adapter would need to provide a minimum of one daily dimension. Providing all of them is not required but recommended in order to have better insights.
Dexs, dexs aggregators and derivatives dimensions:
dailyFees: All fees and value collected from all sources, this also includes liquid staking rewards, generated yields and possible mint and burn fees paid by LP (but not transaction or gas fees).
dailyUserFees: Fees paid by protocol users excluding gas fees. This includes swap fees to open/close positions, borrow fees and all fees user has to pay.
dailyRevenue: Revenue of the protocol governance, this includes treasury and gov token holders (
dailyHoldersRevenue + dailyProtocolRevenue)
dailyProtocolRevenue: Treasury revenue.
dailyHoldersRevenue: Value going to gov token holders, this includes burned coins.
dailySupplySideRevenue: Value earned by liquidity providers.
totalFees(Cumulative value of dailyFees)
totalRevenue(Cumulative value of dailyRevenue)
totalProtocolRevenue(Cumulative value of dailyProtocolRevenue)
totalSupplySideRevenue(Cumulative value of dailySupplySideRevenue)
totalDailyHoldersRevenue(Cumulative value of dailyHoldersRevenue)
If you are not sure how to fit the different fees and revenues generated in your protocol, take a look at the following table or ping us on Discord!
- Protocol governance includes trasury + gov token holders
- Revenue = HoldersRevenue + ProtocolRevenue