-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] 2.2 INVALID_BLOCK_COST and INVALID_TRANSACTIONS_FILTER_HASH Errors #17620
Comments
List of blocks that reported the INVALID_TRANSACTIONS_FILTER_HASH error: |
grep for
two of them in detail:
|
grep for
two of them in detail:
|
On my local server: I got them errors starting on 2024-02-28, with 2.2.0-rc3, but no more since 2024-03-02. On the big farm I'm still getting them with 2.2.0-rc3. So probably depends on the peers one is connected to. EDIT: I should clarify this is under normal operation, not while syncing. |
Thanks for the report. 2.2.0 did indeed have issues and has been pulled. 2.2.1 should resolve these. Please use 2.1.4 in the interim. |
What happened?
A number of users are reporting an error of INVALID BLOCK COST when their client is syncing various blocks (have not isolated specific recurring blocks as of yet).
Logs from one user are below and more can be acquired as needed.
error.txt
Version
2.2
What platform are you using?
Windows
What ui mode are you using?
GUI
Relevant log output
INVALID_BLOCK_COST:
INVALID_TRANSACTIONS_FILTER_HASH
The text was updated successfully, but these errors were encountered: