Sean

Doing a quick edit to force the check for legacy keys to false allows for the services to startup. I didn't dig any deeper but it seems like the way...

Ok, learning as I go here. looks like the ~/.chia_keys/.checked_legacy_migration file is empty and if you put False in there it gets picked up for the config(ctx.obj["force_legacy_keyring_migration"]) and sets the...

@paninaro It seems like that chunk of code is the same in 1.5.0 and 1.5.1. In 1.5.0 it prompts for the keyring passphrase when starting up I assume it's working...

I'm also interested to know why it seems to be working just fine in 1.5.0. Seems like maybe that get_legacy_keyring_instance isn't getting called in the 1.5.0 version? Also I don't...

ok maybe I see what is happening. The code that is getting hit in 1.5.1 was not being used in 1.5.0 unless you tried to run chia keys migrate. So...

Yeah this is still a problem. Does anyone know how they are checking for legacy keys? I suspect the check is doing something incorrectly and causes this code to be...

Sure seems like it does the trick to me. I vote open a PR for this fix. @alvistar you want to give it a try? _ignore my bad naming of...

Is there a verification process for these issues or is just merging in the fix good enough?

@lfarrand do you mind sharing the dependencies you installed and the freebsd version?