-
Notifications
You must be signed in to change notification settings - Fork 47
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
Investigate stake contract inconsistency #1408
Comments
|
Rusk logs at the time of the inconsistency event.
|
This happened after a restart and during the sync process zgrep 'curr_h":52089' /var/log/dusk.log-20220522.gz -B310
|
As per printed provisioners, this is a result from Rusk service.
Missing provisioners:
|
Stake Contract method
|
As discussed, with regard to VM2 expected changes this issue can be put on hold for now. |
Another occurrence of the issue on devnet (node-53): {
"block_time": 13,
"cert_step": 3,
"curr_h": 142140,
"e_prov": 95,
"event": "accept_block",
"hash": "fb448f7cbf...e464064435",
"height": 142141,
"level": "info",
"msg": "run state transition",
"process": "chain",
"prov": 95,
"time": "2022-07-08T09:47:36Z",
"txs_count": 0
} {
"added": -4,
"block_time": 13,
"cert_step": 3,
"curr_h": 142140,
"e_prov": 91,
"event": "accept_block",
"hash": "fb448f7cbf...e464064435",
"height": 142141,
"level": "info",
"msg": "state transition completed",
"process": "chain",
"prov": 91,
"state_hash": "920d5534f9...b1e85a09be",
"time": "2022-07-07T04:50:10Z",
"txs_count": 0
} |
Describe the bug
Two nodes from a single devnet network reported same state_hash but different provisioners set after a successful
rusk.Finalize
call.node_1 accepted a block with
state_hash":"9102c6e0f6...ba694db0e8
at height52089
with 0 provisioners removed/addednode_11 accepted a block with
"state_hash":"9102c6e0f6...ba694db0e8"
at height52089
with 6 provisioners removedExpected behaviour
If no explicit withdraw transaction is accepted, we should not expect any modification to Provisioners set/Stake Contract state.
The text was updated successfully, but these errors were encountered: