From: "Byte Coin" <bytecoin@gmx.com>
To: "Bitcoin Dev" <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] address collision and undependability
Date: Thu, 06 Jun 2013 14:00:42 +0200 [thread overview]
Message-ID: <20130606120042.96680@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
From https://bitcointalk.org/index.php?topic=20955.msg264038#msg264038
This may be an appropriate thread to mention that the the "checksum" at the end of an address does not effectively prevent single character errors or transpositions.
For instance https://blockexplorer.com/search/1ByteCoin shows that
1ByteCoinAddressesMatch1kpCWNXmHKW 1ByteCoinAddressesMatch1kpCxNXmHKW
are both valid addresses even though they only differ by one character.
Similarly, the valid addresses
1ByteCoinAddressesMatchcNN781jjwLY 1ByteCoinAddressesMatchcNN718jjwLY
only differ by one transposition.
ByteCoin
----- Original Message -----
From: Melvin Carvalho
Sent: 06/06/13 12:37 PM
To: Bitcoin Dev
Subject: [Bitcoin-development] address collision and undependability
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: 2489 bytes --]
next reply other threads:[~2013-06-06 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 12:00 Byte Coin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 11:37 [Bitcoin-development] address collision and undependability Melvin Carvalho
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=20130606120042.96680@gmx.com \
--to=bytecoin@gmx.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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