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

Implement default max-block-count value #552

Open
kauri-hero opened this issue Nov 11, 2024 · 0 comments
Open

Implement default max-block-count value #552

kauri-hero opened this issue Nov 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kauri-hero
Copy link
Contributor

kauri-hero commented Nov 11, 2024

Most of the feedback from the RPC providers has indicated that not having a smaller max block count will be a regular timeout issue as the range of scans increases. This will occur if the user is offline for more that a few days.

Implement max_block_count value of 100,000 as default value.

if the RPC response provides another value, then the logic will handle adjusting for that anyways.

GH-606 has made good improvements with this aspect, allowing startBlock for new database to be brought in from head of chain.

This card will further reduce scanning issues in future for serving Nodes

@kauri-hero kauri-hero converted this from a draft issue Nov 11, 2024
@kauri-hero kauri-hero added the enhancement New feature or request label Nov 11, 2024
@kauri-hero kauri-hero moved this from 🆕 New to 🔖 Awaiting Development (Prioritized) in MASQ Node v2 Nov 17, 2024
@masqrauder masqrauder moved this from 🔖 Awaiting Development (Prioritized) to 🏗 Development In Progress in MASQ Node v2 Nov 19, 2024
@masqrauder masqrauder changed the title Implement default max-start-block value Implement default max-block-count value Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🏗 Development In Progress
Development

No branches or pull requests

2 participants