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

[VOC13] - Add internal geth client to API backend for forwarding cache misses #9

Closed
4 tasks done
i-norden opened this issue Sep 16, 2020 · 2 comments
Closed
4 tasks done
Assignees

Comments

@i-norden
Copy link
Collaborator

i-norden commented Sep 16, 2020

If an incoming request cannot be served from the Postgres cache, forward the request to a geth node

  • Finish remaining eth JSON-RPC endpoints (Finish eth standard JSON_RPC endpoints #2)

  • GraphQL integration

  • Add and configure go-ethereum rpc.Client and ethclient.Client inside ipld-eth-server API backend

  • If data for RPC result cannot be retrieved from Postgres (nil val or err returned), forward request to archival node

@i-norden
Copy link
Collaborator Author

This should work for all of the current and future endpoints, in particular eth_Call

@i-norden i-norden changed the title Add internal geth client to API backend for forwarding cache misses VOC13 - Add internal geth client to API backend for forwarding cache misses Oct 23, 2020
@i-norden i-norden changed the title VOC13 - Add internal geth client to API backend for forwarding cache misses [VOC13] - Add internal geth client to API backend for forwarding cache misses Oct 23, 2020
@i-norden
Copy link
Collaborator Author

i-norden commented Nov 2, 2020

Satisfied in #19 and #2/#22

@i-norden i-norden closed this as completed Nov 2, 2020
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