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

Handle FindBlocks in the Inbound service #1078

Closed
4 tasks
hdevalence opened this issue Sep 20, 2020 · 1 comment · Fixed by #1347
Closed
4 tasks

Handle FindBlocks in the Inbound service #1078

hdevalence opened this issue Sep 20, 2020 · 1 comment · Fixed by #1347
Assignees
Labels
A-rust Area: Updates to Rust code C-enhancement Category: This is an improvement

Comments

@hdevalence
Copy link
Contributor

hdevalence commented Sep 20, 2020

Is your feature request related to a problem? Please describe.

The inbound network service should handle FindBlocks requests correctly.

Describe the solution you'd like

  • Compute the intersection between the chain specified in the request and the chain in the state service;
  • Query the state service for up to 500 following hashes;
  • Truncate those hashes at stop, if stop is Some;
  • Return the truncated list of hashes.

Additional context

Part of #889.

Response Size:

  • 500 hashes is zcashd's maximum response size.
  • >= 402 hashes is the most efficient response size for zebrad, see Reduce the size of checkpoints #1204. (zebrad uses 1 hash to verify the tip, and discards 1 hash to work around zcashd bugs.)
@oxarbitrage
Copy link
Contributor

Blocked on #1306

@oxarbitrage oxarbitrage added the S-blocked Status: Blocked on other tasks label Nov 16, 2020
@teor2345 teor2345 changed the title Handle FindBlocks in the Inbound service Handle FindBlocks in the Inbound service Nov 17, 2020
@mpguerra mpguerra removed the S-blocked Status: Blocked on other tasks label Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rust Area: Updates to Rust code C-enhancement Category: This is an improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants