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

Fix hashes per tick discrepancy due to update_hashes_per_tick #1850

Closed
alpeng-jump opened this issue May 13, 2024 · 0 comments · Fixed by #1964
Closed

Fix hashes per tick discrepancy due to update_hashes_per_tick #1850

alpeng-jump opened this issue May 13, 2024 · 0 comments · Fixed by #1964
Assignees
@mmcgee-jump
Labels
consensus Priority: High runtime
Milestone
Frankendancer

Comments

@alpeng-jump
Copy link
Contributor

alpeng-jump commented May 13, 2024 •
edited

With update_hashes_per_tick6 FKu1qYwLQSiehz644H6Si65U5ZQ2cp9GxsyFUfYcuADv feature to update desired hashes per tick on an epoch boundary now being activated, testnet is running at 62500 hash rates per tick. We currently do not support this and run at 12500 hashes per tick, which causes an invalid tick hash count error and we don't produce any blocks confirmed by the network when we are leader.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmcgee-jump mmcgee-jump

Labels
consensus Priority: High runtime
Projects
None yet
Milestone
Frankendancer
Development

Successfully merging a pull request may close this issue.

poh: implement ticks_per_hash feature, fork skip fix firedancer-io/firedancer
2 participants
@alpeng-jump @mmcgee-jump