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
Ensure front ends can usefully summarise activity for users:
Rewards earned (and bost amount earned)
Fees paid
Fees saved due to referral / loyalty scheme
Gain or loss by type (fee/MTM/rewards/liquidaton/loss socialisatoin/deposit/withdraw/transfer)
Work over variety of period (day/week/month/?)
Validate requirements with FE teams
JR: It will be very hard for us to put together any sort of meaningful "portfolio" view without getting something like this. I believe such a view will be very strongly desired by users wanting to stay on top of their earnings / rewards etc so it is worth investing the time in. IMO limiting the scope of this to daily summaries, probably aligned to epochs, should keep the implementation acceptable to Core and would give us what we need to build something really nice.
The text was updated successfully, but these errors were encountered:
JR: It will be very hard for us to put together any sort of meaningful "portfolio" view without getting something like this. I believe such a view will be very strongly desired by users wanting to stay on top of their earnings / rewards etc so it is worth investing the time in. IMO limiting the scope of this to daily summaries, probably aligned to epochs, should keep the implementation acceptable to Core and would give us what we need to build something really nice.
The text was updated successfully, but these errors were encountered: