Skip to content
This repository has been archived by the owner on Aug 9, 2021. It is now read-only.

Move to paginated calls for Activity Feed #584

Open
oznekenzo opened this issue Dec 27, 2019 · 2 comments
Open

Move to paginated calls for Activity Feed #584

oznekenzo opened this issue Dec 27, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request Front End

Comments

@oznekenzo
Copy link
Contributor

This would require either updating the 3box activity library to use a different api from that of etherscan, waiting for etherscan to update their api, or bypassing the 3box activity library and using another api (alethio)

@oznekenzo oznekenzo added enhancement New feature or request Front End labels Dec 27, 2019
@oznekenzo oznekenzo self-assigned this Dec 27, 2019
@michaelsena
Copy link
Contributor

@oznekenzo it might make sense to move to Alethio for this, I think. I haven't researched all that many options, but their API seems good and performant based on very limited knowledge. Maybe the first step here is to do research on available solutions then implement the one that makes the most sense.

@michaelsena michaelsena added this to the Sprint 36 milestone Feb 19, 2020
@oznekenzo
Copy link
Contributor Author

Update on this: Alethio has three different endpoints for Txs, Internal, & Token transfers, requiring three different paginated calls (by # of transactions), so the very same people that were implementing this feature for (users with high # of transactions) are going to potentially run up against the confusing case where they'll get 50 Txs from yesterday (where 50 is the pagination cursor we decide to use) and 6 Internal transfers from over the course of two years, and in the next call (after scrolling to bottom), the user will get another 50 new Txs in the feed, though now appearing before the 6 internal transfers that were in the feed on the original call. We can work around this by doing multiple calls but we'd be making ~6+ paid api requests instead of 3 (or even 1). I emailed Lucian about somehow providing an aggregated endpoint where we don't have to sort all transactions ourselves, have yet to hear back

@michaelsena michaelsena removed this from the Sprint 36 milestone Mar 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request Front End
Projects
None yet
Development

No branches or pull requests

2 participants