From: Wladimir <laanwj@gmail•com>
To: Melvin Carvalho <melvincarvalho@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin addresses -- opaque or not
Date: Tue, 11 Jun 2013 15:44:39 +0200 [thread overview]
Message-ID: <CA+s+GJAsmH_LVqV5qs5fPX8NSGyJtzOs6kyC7M27e8JdCLooEg@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhJ+v0NfbzVEDEUh69D-n_4=Nd544fsm0a++QwsqcS3RVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On Tue, Jun 11, 2013 at 3:11 PM, Melvin Carvalho
<melvincarvalho@gmail•com>wrote:
> There was some confusion on IRC as to whether bitcoin addresses are opaque
> or not.
>
> https://en.bitcoin.it/wiki/Address
>
> For the sake of argument let's say that opaque means that you can tell
> nothing about the address by examining the characters.
>
> My understanding was that they are NOT opaque, and that if that has
> changed, it will invalidate much at least some wiki page, for examples at
> least some of the following would now be false:
>
How do you define opaque? As far as humans are concerned the addresses are
opaque. They don't tell anything about your country or location, your bank,
your name, they don't even form some kind of hierarchy.
From the viewpoint of the code you could argue they have a meaning "address
type + hashed public key, base58 encoded" thus are not fully opaque. But
it's a long shot, as a hashed value is still very opaque.
> I also here that there is a LIKELY change from the base58 encoding ...
> when was this established?
>
No, there have been no changes to base58. The encoding is still exactly the
same as when Satoshi coined it. Can you show an example of what you mean?
Wladimir
[-- Attachment #2: Type: text/html, Size: 2146 bytes --]
next prev parent reply other threads:[~2013-06-11 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 13:11 Melvin Carvalho
2013-06-11 13:44 ` Wladimir [this message]
2013-06-11 14:12 ` Pieter Wuille
2013-06-11 15:29 ` Luke-Jr
2013-06-15 9:50 ` Melvin Carvalho
2013-06-22 11:48 ` 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=CA+s+GJAsmH_LVqV5qs5fPX8NSGyJtzOs6kyC7M27e8JdCLooEg@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=melvincarvalho@gmail$(echo .)com \
/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