From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] address collision and undependability
Date: Thu, 6 Jun 2013 13:37:26 +0200 [thread overview]
Message-ID: <CAKaEYhKQ9vyis3X7PLDgFbYijWck-D_hVnp_xt+muhdzjyXeFQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
There was a discussion on #bitcon-dev yesterday
I stated that it would be impractical to generate two bitcoin addresses,
such that they differed in exactly one character (modulo different
checksums).
The corollary to this is that if you find an address with a verifiable
signature. Changing one character of that address would have no known
private key, and hence be normally undependable.
Does that sound correct?
[-- Attachment #2: Type: text/html, Size: 500 bytes --]
next reply other threads:[~2013-06-06 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 11:37 Melvin Carvalho [this message]
2013-06-06 12:00 Byte Coin
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=CAKaEYhKQ9vyis3X7PLDgFbYijWck-D_hVnp_xt+muhdzjyXeFQ@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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