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
This should work for all of the current and future endpoints, in particular eth_Call
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
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
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
The text was updated successfully, but these errors were encountered: