-
Notifications
You must be signed in to change notification settings - Fork 107
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
Integration of Portal network / fluffy into Nimbus EL #2147
Labels
Comments
Location where to request over portal-history network instead of grabbing from db: nimbus-eth1/nimbus/sync/handlers/eth.nim Line 466 in 2891b9a
As PoC, can intially add Portal network to Eventually should probably have diffferent (for the different backends, e.g. also Era1) objects that can be selected from an Abstraction layer above this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PoC of the Portal network as backend for retrieving history data (EL block headers, bodies and receipts) before a certain (configurable) threshold (e.g. everything before TheMerge).
Basically, instead of grabbing the data from it database on incoming requests, it should request it over the Portal network. Or, it could first look into its database, and if the data is not there, move to requests over the network. TBD.
This might require adapting Fluffy to provide a better API.
The text was updated successfully, but these errors were encountered: