Open thesheepcat opened 2 years ago
The situation is now even trickier:
The balance between the two node is different by 30% .
I already tried to restart the node which seems to be not showing the complete balance, without the --utxoindex flag; then, i stopped the node once synced; then, i re-run the node with --utxoindex parameter.
Still, the balances are different.
To summarize:
Can you double-check please if dump-unencrypted-data
still gives you exact same error ? Cause I tried it, and it worked for me correctly.
My version is 0.11.6
This is probably a side effect of the bug that's fixed in the dev branch https://github.com/kaspanet/kaspad/pull/1859
Can you double-check please if
dump-unencrypted-data
still gives you exact same error ? Cause I tried it, and it worked for me correctly. My version is 0.11.6
Did you try to move your keys.json file (your wallet file) on a PC / VPS with a different number of cores (like from quad core PC to 6 core PC)?
No, I didn't - as far as I know, this was known issue and was fixed. Do you want me to try ? Does it related to current issue ?
From: thesheepcat @.> Sent: Saturday, December 18, 2021 12:34 AM To: kaspanet/kaspad @.> Cc: Ro Ma @.>; Comment @.> Subject: Re: [kaspanet/kaspad] "kaspawallet dump-encrypted-data" not working (Issue #1851)
Can you double-check please if dump-unencrypted-data still gives you exact same error ? Cause I tried it, and it worked for me correctly. My version is 0.11.6
Did you try to move your keys.json file (your wallet file) on a PC / VPS with a different number of cores (like from quad core PC to 6 core PC)?
— Reply to this email directly, view it on GitHubhttps://github.com/kaspanet/kaspad/issues/1851#issuecomment-997070214, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAXSR4VFLWS5QHTI2L737R3URO3GRANCNFSM5IADMPMA. You are receiving this because you commented.Message ID: @.***>
I have two servers (A and B) running Kaspa.
I need to migrate my wallet from A to B.
Server A:
Server B:
I need to be sure the dump also works on Server B, before shutting down Server A.