cerc-io/ipld-eth-server
18
0
Fork 1
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 37 Wiki Activity

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

New Issue
Closed
opened 2020-09-16 16:56:33 +00:00 by i-norden · 2 comments
i-norden commented 2020-09-16 16:56:33 +00:00
Member
Copy Link

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

  • Finish remaining eth 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

If an incoming request cannot be served from the Postgres cache, forward the request to a geth node - [x] Finish remaining eth JSON-RPC endpoints (#2) - [x] GraphQL integration - [x] Add and configure go-ethereum rpc.Client and ethclient.Client inside ipld-eth-server API backend - [x] If data for RPC result cannot be retrieved from Postgres (nil val or err returned), forward request to archival node
i-norden commented 2020-09-23 17:24:54 +00:00
Author
Member
Copy Link

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

This should work for all of the current and future endpoints, in particular eth_Call
i-norden commented 2020-11-02 14:06:29 +00:00
Author
Member
Copy Link

Satisfied in #19 and #2/#22

Satisfied in #19 and #2/#22
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working

  
critical

   
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
Epic

   
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
Integration tests

   
invalid

This doesn't seem right

  
question

Further information is requested

  
v5

   
wontfix

This will not be worked on

  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
critical
documentation
duplicate
enhancement
Epic
good first issue
help wanted
Integration tests
invalid
question
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/ipld-eth-server#9
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?