-
br-m<jpk68:matrix.org> Does the GUI not have one text input field for every word
-
br-m<jpk68:matrix.org> IMO it would likely be more straightforward to just ask the user if they have a 25-word or 16-word seed on restore. It's not like they wouldn't know how many words are in the seed
-
br-m<kayabanerve:matrix.org> If we're discussing the UI regarding seeds, I'd like to remind everyone that the user may _have_ to specify which language their seed is in.
-
br-m<kayabanerve:matrix.org> There's some seeds which are valid in multiple languages, as seed code I wrote started having test failures over and @jberman:monero.social: identified IIRC.
-
br-m<jpk68:matrix.org> Is this the same issue as in #9089?
-
br-m<rbrunner7> Yup, that's the #9089 case, and the discussion there shows how many angles this issue has.
-
br-m<rbrunner7> At the moment I don't think it's a good idea to put this problem on top of my already quite big Polyseed support story, but what I think is sensible is avoiding generating such ambigous seeds when creating a new wallet with a new random seed.
-
br-m<rbrunner7> That can be done with a few lines of code: Generate a new Polyseed at random, see whether the language can be decided automatically, if not generate a new Polyseed at random, until success.
-
br-m<rbrunner7> That will probably be code that will never ever execute in this universe even if Monero gets used for centuries, given how unlikely such ambigous seeds must be, but hey, as I said earlier, it's about seed, they are holy.
-
br-m<kayabanerve:matrix.org> I'm pretty sure that issue was found because it triggered a test failure, so that would mean it is observable. > <@rbrunner7> That will probably be code that will never ever execute in this universe even if Monero gets used for centuries, given how unlikely such ambigous seeds must be, but hey, as I said earlier, it's about seed, they are holy.