Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching of etherscan.io transactions and/or block #->timestamp mappings #1

Open
JakubNer opened this issue Nov 25, 2018 · 0 comments
Open

Comments

@JakubNer
Copy link
Collaborator

https://github.com/JakubNer/overhide-ethereum/blob/77e54ebefdd19d23425d1b401308a98ee6f99cdb/main/js/glue/get-transactions.js#L13

At the moment all transactions are pulled down for the 'to' address from etherscan.io, processed, discarded.

Considering that most checks are for a limited number of 'to' addresses (broker & services are the 'to' addresses checking subscribers) and for some limited time frame ('since' parameter specified); it's likely worthwhile to cache.

If we don't want to cache specific transaction sets, we might want to cache Ethereum block #s to timestamps such that when asked for transactions 'since' some date, we can limit the etherscan.io API calls to start from a certain block #.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant