secinthenet

> I think we agree: there is no reason for anyone to choose non-HDM Glacier. And that's why I don't think there's any benefit in modifying my Glacier fork any...

> Is there any interest in attempting to deconstruct Glacier (via this repository) into modular pieces in a way that's compatible with Tordl? I would very much like to figure...

> > If non-HDM Glacier is not a sensible choice, it doesn't mean that modifying non-HDM Glacier to be HDM > > I was hoping he meant that he wanted...

I don't disagree, but can you really rely on that? There are scenarios where you clone on VMs or docker containers that are not configured

@andrewkozlik the idea above from @nioncode is exactly what I thought about and commented on in https://github.com/BlockchainCommons/bc-lethekit/issues/38#issuecomment-751904641 and https://github.com/oed/seedsplit/issues/6#issuecomment-751905751 Is there a reason why this shouldn't be done, other than...

@andrewkozlik I agree this can be a great source of confusion for users. I opened https://github.com/satoshilabs/slips/pull/1044 to specify that this is the only way SLIP39 can be used for backing...

@efnats I suggest adding a very loud and clear warning to seedhodler that this is not SLIP39 compatible. In fact, I would probably use a different word list to further...

@ChristopherA maybe you're already aware of it, but SLIP39 doesn't specify what secret you split. The doc only says "SSS splits a master secret, such as the master seed S...

@ksedgwic to confirm, you're using the exact same method with the exact same crypto, just on the BIP39 initial entropy (which can be converted to and from the mnemonic) instead...

I don't know how to fix this, I'll need to dig into this