Indeed, and with things like BIP32 it would be pointless to use one address,
and I agree it is silly to reuse addresses, some for the privacy aspect, some
for the revealing the pubkey on a spend aspect. But just because it is silly,
doesn't mean it's necessarily required for devs to disallow
On Fri, Mar 27, 2015 at 1:51 AM, Thy Shizzle thyshiz...@outlook.com wrote:
Yes I agree, also there is talks about a government body I know of warming
to bitcoin by issuing addresses for use by a business and then all
transactions can be tracked for that business entity. This is one proposal I
On Thu, Mar 26, 2015 at 8:38 PM, Tom Harding t...@thinlink.com wrote:
I addressed that by limiting the duplicate check to an X-block segment. X
is hard-coded in this simple scheme (X=144 = 1-day addresses). You
could picture a selectable expiration duration too.
If its to be heuristic in
On Thu, Mar 26, 2015 at 9:26 PM, Tom Harding t...@thinlink.com wrote:
I should have been clearer that the motivation for address expiration is to
reduce the rate of increase of the massive pile of bitcoin addresses out
there which have to be monitored forever for future payments. It could make
If I understand correctly, transforming raw blocks to keyed blocks
takes 512x longer than transforming keyed blocks back to raw. The key
is public, like the IP, or some other value which perhaps changes less
frequently.
Yes. I was thinking that the IP could be part of a first layer of
This should not be enforced by default. There are some use cases where
address re-use is justified (a donation address spread on multiple
static pages or even printed on papers/books?). For example, I offer
some services on the internet for free, and I only have a bitcoin
address for donations
On Thu, Mar 26, 2015 at 10:28 PM, s7r s...@sky-ip.org wrote:
This should not be enforced by default.
No one suggested _anything_ like that. Please save the concern for
someplace its actually applicable.
I know it's not recommended to use the same pubkey more than once, but
the protocol was
Maybe I'm overlooking something, but I've been watching this thread with
increasing skepticism at the complexity of the offered solution. I don't
understand why it needs to be so complex. I'd like to offer an alternative for
your consideration...
Challenge:
Send me: SHA256(SHA256(concatenation
8 matches
Mail list logo
