You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
I think providing fee per broker as a percentage of total volume per broker on the daily Broker Summary would make the data a bit more transparent to viewers.
It's only necessary for brokers that generate a fee. For Chainflip and other brokers who don't generate a fee, there wouldn't be a need for the breakdown of fee in percentage in the summary.
More Info
Since brokers can vary fees per swap, we can calculate the average fee per day and display this in the overview to give clarity to the user how brokers relate to each other fee wise.
Bounty
FLIP required for development: 150 FLIP
To start development, send the bounty to 0x2578f4fa0f36138c76389095bf74331a4f57bcc0 and comment with a link to the transaction.
The text was updated successfully, but these errors were encountered:
CumpsD
changed the title
Providing fee per broker as a percentage(%) on daily Broker Summary.
Providing fee per broker as a percentage on daily Broker Summary [150 FLIP]
Jul 22, 2024
Provide Broker Fee % on Broker Summary
Scope
I think providing fee per broker as a percentage of total volume per broker on the daily Broker Summary would make the data a bit more transparent to viewers.
It's only necessary for brokers that generate a fee. For Chainflip and other brokers who don't generate a fee, there wouldn't be a need for the breakdown of fee in percentage in the summary.
More Info
Since brokers can vary fees per swap, we can calculate the average fee per day and display this in the overview to give clarity to the user how brokers relate to each other fee wise.
Bounty
FLIP required for development: 150 FLIP
To start development, send the bounty to 0x2578f4fa0f36138c76389095bf74331a4f57bcc0 and comment with a link to the transaction.
The text was updated successfully, but these errors were encountered: