-
Notifications
You must be signed in to change notification settings - Fork 95
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
Wrong "state" migrating from 3.1.0 to 3.2.0 #228
Comments
This is unrelated to the state files. I would avoid deleting the state files since that is a core part of horcrux' double sign protection. Waiting for blocks without signature is not always sufficient since an out of sync sentry could request a signature for an old block. This is due to the cosigner nonce cache, and I believe it is related to #226 and think it may also be fixed by #227 in v3.2.1. Can you please try v3.2.1? |
@agouin tested v3.2.1 with then same problem. Co-Signer 1 and 2:
Co-signer 3:
Sentry:
Version:
|
worked for me! |
Migrating from version 3.1.0 to 3.2.0 no signatures occur with this error
Cosigner failed to set nonces and sign chain_id=xxx-1 height=xxx round=0 type=prevote cosigner=1 err="unexpected state, metadata does not exist for U: xxxxx"
The steps performed:
The same in test with a stand-alone setup (--accept-risk) with a wrong state file.
In this last case I solved it increasing blocks without signatures and then by deleting
state/priv_validator_state.json
(it's a testnet)Some idea?
Thanks
The text was updated successfully, but these errors were encountered: