Status-react: Wallet - Use web3 to fetch wallet transactions

[yenda]

User Story

As a developper, I want to to use web3 to fetch transactions so that Status does not depends on a centralized api (etherscan) for wallet transactions history.

Description

_Type_: Feature

_Summary_:
To reach MVP of the new wallet we used etherscan to fetch the transaction history of the wallet. This task will consist of implementing a new version of the transaction fetching logic using web3.

Expected behavior

Transactions are fetched using web3

Actual behavior

Transactions are fetched using etherscan and are limited to the 20 last transactions

Solution

_Summary_:

• [ ] implement and adapt this script in clojurescript https://ethereum.stackexchange.com/questions/2531/common-useful-javascript-snippets-for-geth/3478#3478 to get transactions for a given address from block X to Z in utils/transactions.cljs
• [ ] create an event that recursively calls the function for block n to n-step until the block when the wallet has been created is reached in ui.screens.wallet.events

Depending on the performance cost of this solution it might be worth it to keep the etherscan api call for the 20 first transactions, but use web3 as fallback in case it fails and fetch the rest of the transactions with web3.

[asemiankevich]

does this impact ERC tokens history? @goranjovic
also @yenda why we want to have it only 20 txns?

[yenda]

@asemiankevich the 20 first transaction would be fetched from etherscan if performances are not good enough in order to speed things up, while still being able to show them if etherscan is down.

[debragail]

Are perf tools a thing yet? Last I checked no one had a toolkit they were using.

[andytudhope]

@asemiankevich @goranjovic can we close here?

[pablanopete]

@yenda would this be appropriate for a new bounty still?

[yenda]

@pablanopete yes it is still relevant

[status-github-bot[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[status-github-bot[bot]]

This issue has been automatically closed. Please re-open if this issue is important to you.

[StatusSceptre]

@tbenr were you still wanting to work on this one? Are there any updates otherwise? I can add a bounty to it but wasn't sure of the context.

[debragail]

@StatusSceptre would be down to work on this if there's a bounty

[mandrigin]

@goranjovic what do you think about making it a bounty?

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 160.0 DAI (160.0 USD @ $1.0/DAI) attached to it as part of the Status-im fund.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  
  
  
  • Want to chip in? Add your own contribution here.
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $51,667.11 more funded OSS Work available on the Gitcoin Issue Explorer
  
  

[krisc]

Is anyone currently working on this?

[tbenr]

@krisc i had started experimenting #6144 . I planned to continue once I finish #6597

[krisc]

@tbenr Have you continued with this yet?

[tbenr]

@krisc no I didn't. do you want to jump in this? Btw consider this https://github.com/status-im/status-react/pull/6144#issuecomment-451978773

[krisc]

@tbenr I'll take a look at what you've done so far and see if I think I can take over.

[krisc]

@tbenr I think it is too advanced for me to move the PR forward. I'll be watching as this issue continues, however. Whenever that will be.

[StatusSceptre]

Should I stop work on @tbenr?

[tbenr]

@StatusSceptre sorry, i stopped my self.. definitely something I'm postponing too much.. maybe in the future we can go back on this...

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__The funding of 160.0 DAI (160.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $134,900.15 more funded OSS Work available on the Gitcoin Issue Explorer