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.

Sign up for GitHub

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

Jump to bottom

Stream blocks #63

Open
jasny opened this issue Mar 10, 2021 · 1 comment
Open

Stream blocks #63

jasny opened this issue Mar 10, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@jasny
Copy link
Member

jasny commented Mar 10, 2021

With #62, the use of the public chain only is going to be pretty limited. Typically you'd want to use a secondary service like ltonetwork/indexer.

Rather than requiring a service to query data, which can be slow, the node could stream new blocks to the service of a unix or tcp socket.
@jasny jasny added the enhancement New feature or request label Mar 10, 2021
@jasny
Copy link
Member Author

jasny commented Mar 17, 2022

It's up to the (indexer) service to make sure it has received all blocks. If it notices a block is skipped, it should request it before continuing with the streamed blocks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jasny