From: Tim Ruffing <crypto@timruffing•de>
To: vjudeu <vjudeu@gazeta•pl>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] An alternative to BIP 32?
Date: Sat, 20 Mar 2021 11:08:30 +0100 [thread overview]
Message-ID: <62853a4db45c8c6a483fcb3ca05e0bb58e06a643.camel@timruffing.de> (raw)
In-Reply-To: <125859088-3f93e6aca40d5c3244243540270cdb84@pmq7v.m5r2.onet>
On Fri, 2021-03-19 at 20:46 +0100, vjudeu via bitcoin-dev wrote:
> is it safe enough to implement it and use in practice?
This may be harsh but I can assure you that a HD wallet scheme that can
be specified in 3 lines (without even specifying what the security
goals are) should not be assumed safe to implement.
Tim
next prev parent reply other threads:[~2021-03-20 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 19:46 vjudeu
2021-03-20 1:32 ` Erik Aronesty
2021-03-20 2:08 ` Arik Sosman
2021-03-22 12:05 ` Erik Aronesty
2021-03-20 10:08 ` Tim Ruffing [this message]
2021-03-20 20:25 vjudeu
2021-03-20 20:25 vjudeu
2021-03-21 21:45 ` Tim Ruffing
2021-03-22 7:51 vjudeu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62853a4db45c8c6a483fcb3ca05e0bb58e06a643.camel@timruffing.de \
--to=crypto@timruffing$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox