From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin addresses -- opaque or not
Date: Tue, 11 Jun 2013 15:29:11 +0000 [thread overview]
Message-ID: <201306111529.13657.luke@dashjr.org> (raw)
In-Reply-To: <CAKaEYhJ+v0NfbzVEDEUh69D-n_4=Nd544fsm0a++QwsqcS3RVw@mail.gmail.com>
On Tuesday, June 11, 2013 1:11:33 PM Melvin Carvalho wrote:
> For the sake of argument let's say that opaque means that you can tell
> nothing about the address by examining the characters.
This is true or false based on CONTEXT.
Obviously, an implementation of transaction handling (eg, wallets) needs to be
able to translate addresses to and from what they represent.
On the other hand, things like URI handlers do not (and should not) try to
interpret the address as anything other than an arbitrary word (\w+).
> 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:
The wiki goes into much detail on how addresses work, which is not the concern
of most software in the Bitcoin ecosystem, but may be of interest to humans
and developers working on the one component that operates the "black box" that
addresses are.
> --------
> <snip>
> --------
These aren't FALSE, they are "true at the moment, but subject to revision by
newer standards".
> I also here that there is a LIKELY change from the base58 encoding ... when
> was this established?
I stated (on IRC) that it was likely Bitcoin would change from the base58
encoding for addresses ... at some unspecified time in the future, to some
unspecified new encoding that addressed known limitations of base58. What
those changes will be, or when, are not all established at this time. The only
currently-planned change to addresses (very loosely defined) is inclusion of
the Payment Protocol URIs. But the point is that software developers shouldn't
assume that addresses will remain base58 forever.
Luke
next prev parent reply other threads:[~2013-06-11 15:29 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
2013-06-11 14:12 ` Pieter Wuille
2013-06-11 15:29 ` Luke-Jr [this message]
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=201306111529.13657.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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