pull down to refresh

seedless is safer

As in no derivation? Why is that safer?

That was a reference to Bitkey's design choice to not allow users to access their key/seed material.

I don't think it is safer.

reply

That post says 3 words "not your keys" in 300 words. But it doesn't even say how it solves it.

reply

Yes it made me so grumpy I got into it with Steve Lee

#1009501

Also I made a song about it:

I didn't like the idea that "no vendor lock in" was redefined as "you can send your coins to a new address" rather than "you can import your seed into another wallet software."

reply
104 sats \ 0 replies \ @optimism 22h

You: "You have to send a tx from their app to recover"
Steve: "That is not lock-in"

Steve is right though: this is not lock-in...

... it's slavery disguised as bulshytt.

(I really enjoyed re-reading Anathem, lol)

reply
71 sats \ 3 replies \ @ca 29 Apr
  • you don't need to select a physical place to hide it
  • you cannot lose it to memory, fire, flooding
  • guests cannot steal it from your home
  • you won't make mistakes transcribing the seed
  • you won't have to maintain the physical seed and check on it regularly
  • you don't have to explain the concept of keys to normies
  • et al.
reply

Okay?

  • What magic secret can live in the open?
  • What magic secret (container?) can sustain amnesia/wear, fire and flooding?
  • What magic secret cannot be stolen?
  • What magic secret is persistent and absolute in backup?
  • What magic secret is non-physical?
  • What magic secret is so magic that you don't have to explain it?
reply
173 sats \ 1 reply \ @ca 13h

Bitkey has a clean solution to the dilemma.

Certainly with tradeoffs, but only one I could gift to a normie and have a guarantee that they won't fail in custoding bitcoin.

reply
104 sats \ 0 replies \ @optimism 7h

I think that that's my bottom line point: tradeoffs. If you have secrets, they have to be kept safe. Whether or not you do it yourself or you outsource it, directly or indirectly, merely shifts the burden, but the burden is still there. You may just not be exposed to it in the same way and you'll have different friction.

You'll even probably still have a seed and key derivation as continuous secure random without wrapping is a security risk too that a normie won't be able to defend against.

I guess what they really mean is: we don't have a BIP-39 implementation.

reply