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
It will require quite some work on both Atlas and Orion.
Atlas:
there is no support for header base sorting for table component (I don't expect it to be trivial)
mcap is a value calculated on the frontend, so there is no way to order it by it
total revenue is a value that is living on channel entity, so there is no way to order tokens by another entity property
Orion:
for mcap it would require some mapping changes, basically tracking the market cap as the supply and price changes, and then exposing it to the frontend as token property
for total revenue - this one is more tricky since there is no code-efficient way for a token to keep track of the channels' total revenue value. @zeeshanakram3 proposed one solution with using Views as a way to always have to most recent data without major work, but it introduces a performance overhead
there is no support for header base sorting for table component (I don't expect it to be trivial)
Why would this be difficult? What am I missing?
for mcap it would require some mapping changes
Yes, def. it should not be computed on front-end, and computing on backend is quite easy, we are proessing trades anyway, so with each trade the mcap is just recomputed, just 1-2 extra lines in that mapping.
for total revenue - this one is more tricky since there is no code-efficient way for a token to keep track of the channels' total revenue value.
Why would we not just add a new field that accumulates all channel account inflows, wich can come via member remarks with payment primarily, thats all we care about now really.
Seems most of the work is Orion here, are you able to do this Orion work?
Problem
Currently it looks like this
the problem is that
Proposal
The text was updated successfully, but these errors were encountered: