<rbrunner7> With the seed command the CLI wallet gives out a legacy seed as 3 lines, like so:

<rbrunner7> nestle husband lemon smelting aglow five ozone abort

<rbrunner7> mobile sushi rising lopped amidst juvenile hairy evaluate

<rbrunner7> rotate dabbing island hurried taken gearbox upload wedge nestle

<rbrunner7> I think it's like that since seeds quite in general were introduced.

<rbrunner7> What do people think: Does this formatting have value? I would like to switch to giving out the seed as one long string.

<rbrunner7> Background is a problem with seed input when restoring: Before Polyseed, the CLI wallet allowed entering seeds on multiple lines. That job was easy: Just ask for line after line until all together there are at least 24 words.

<rbrunner7> Now, where we have the possibility that it's a Polyseed, seems to me that's no longer possible.

<rbrunner7> If a user enters 16 words on a first line, is this now a complete Polyseed, or only the first 16 words of a legacy seed?

<rbrunner7> What I want to prevent: That you can't take the seed as output with the seed command and directly restore with that.

<rbrunner7> Having to re-format 3 lines back into 1 would be a pain.

<rbrunner7> It's of course quite a small problem, but it somehow bugs me, and I don't want to break a decade of seed output tradition just like that :)

<ofrnxmr> They have different wordlists > <@rbrunner7> If a user enters 16 words on a first line, is this now a complete Polyseed, or only the first 16 words of a legacy seed?

<ofrnxmr> So it should be possible to detect based on the words alone

<sneedlewoods_xmr:matrix.org> IMO changing the formatting to a single line sounds good. > <@rbrunner7> What do people think: Does this formatting have value? I would like to switch to giving out the seed as one long string.

<sneedlewoods_xmr:matrix.org> Relying on the wordlists sounds more complex and only works if there are no words overlapping AFAICT (did not check if there are any).

<rbrunner7> Yes, that thought crossed my mind: Continuously check whether the words as of now would be a valid Polyseed, and if not stop, stop to ask for further output.

<rbrunner7> But this seems to be a bit the wrong question for me. Question is "Is that 3 line formatting important, is it useful in some aspect, so we do want to keep it".

<rbrunner7> Beside "It always was that" and "Never change a running system" I personally don't see any advantages. But other people may see it differently.

<rbrunner7> *and if yes, stop to ask for further input

AFAIK it was just to avoid clipping words neatly, not on random letters as the text hit the terminal width.

AFAIK it was just to clip words neatly, not on random letters as the text hit the terminal width.

<rbrunner7> I see. Yes, that's an argument to keep the multiple lines ...

I guess you could add "..." when continued, which the parser would interpret as "wait" if present when re-read.

<rbrunner7> Hmm, yes. But other apps like the GUI wallet would have to learn that as well, or they would probably tax "..." as invalid word.

Hmm. Clever. "Invalid seed, taxing next restored wallet at 0.001%" :D

<ofrnxmr> @sneedlewoods_xmr:matrix.org: Well.. you could just press "enter" after entering 16 words

<ofrnxmr> Or it can ask you to choose a seed