Hi

<rbrunner7> tobtoht: I tried today to open a wallet file created with Feather Wallet in the CLI wallet, and the seed command failed to display the seed. As far as I can see the problem is that wallet2::seed_language is not set.

<rbrunner7> A search through the Feather source for wallet2::set_seed_language did not return something, but it seems to use Wallet API setSeedLanguage in the seed display dialog to set the language if it's not set. Could it be, no seed display yet in Feather, language not set?

<rbrunner7> I think it would make sense to default to English if language not set also in the core software.

<rbrunner7> On the one hand, it's maybe an edge case that people copy around wallet files between apps, but on the other hand why not?

<rbrunner7> And quite in general, seeds can be your last hope and the difference between regaining access to your coins and the abyss, so better make them as robust as possible ...

<ofrnxmr> I'm wondering your feather wallet was created by restoring from seed? could potentially be a diff outcome for a restored wallet vs a newly generated one

<rbrunner7> Not sure anymore, I quickly check

<rbrunner7> Nope, also a wallet newly created in Feather Wallet has this issue. Well, it's maybe a case of not strictly enough defined semantics, nothing in wallet2 and the Wallet API forces you to set the seed language, and things work without it. Just the CLI wallet app is not in the mood to show the seed if there is no language set.

<rbrunner7> Which, as I said, would be easy to change.

.merge+ 10689

Added

rbrunner7: I can reproduce. The seed language is being set during creation in Feather, but the .keys file is never updated. Looking into why that is.

.merges

10309 10512 10531 10533 10543

.merge+ 10493 10495

...

.merge+ 10584

Added