Waves icon indicating copy to clipboard operation
Waves copied to clipboard

Published 20 hours ago • verified publisher icon wavesplatform

Waves startup issue when there is a wallet issue.

Open Crypto2 opened this issue 4 years ago • 3 comments

I've noticed 2x over the years that Waves has a dangerous issue when it starts up if there is an issue loading the wallet. Instead of printing an error and refusing to run it just silently creates a new wallet with a new seed (even if the wallet seed is specified in the config file). It actually doesn't mention there was an issue at all and acts like nothing happened.

Crypto2 avatar Feb 08 '21 16:02 Crypto2

Any update on this? It seems to do it randomly even if it was shut down properly let alone if there was any error or crash or anything.

Crypto2 avatar May 15 '21 00:05 Crypto2

  1. If wallet file is corrapted, then node will not start.
  2. If you change seed and not delete wallet-file, node will start with old seed. Wallet seed has a priority to config-seed. It's not a bug, but we will change tis option in future releases
  3. If you delete wallet file, node will create new instead of deleted.

Or you have another issue?

DrBlast avatar May 17 '21 05:05 DrBlast

  1. This would be the expected behavior but in these cases I'm seeing it will start without printing any errors and with a new seed. It mainly happens if there is a crash while the node is running but it does it just randomly on startup as well.
  2. This would be the expected behavior but I haven't tested it so I can't comment on it.
  3. This is correct from my experience, every time I've seen it make a wallet from scratch it used the seed in the config file.

Crypto2 avatar May 19 '21 04:05 Crypto2