Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Jorge Timón
Now I get it. Thank you. You save space by having shorter scripts in transactions. -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It w

Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Pieter Wuille
On Sun, Dec 18, 2011 at 01:15:26PM +0100, Jorge Timón wrote: > But anyway, reading some comments I feel I'm missing something about > this proposal. How can you save space by putting the whole public key > instead of just the address (a hash of the public key) with each > output? > Is this what it'

Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Luke-Jr
On Sunday, December 18, 2011 9:28:36 AM Jorge Timón wrote: > Back on topic, is actually putting the whole pub key in each output > what you're proposing? Yes, just like is already done for generation, since it is more efficient *overall* for the block chain. sipa's key extraction is a MUCH better

Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Jorge Timón
I see it as a good start for POS payments. I don't know what flaw you're referring to. Back on topic, is actually putting the whole pub key in each output what you're proposing? 2011/12/18, Luke-Jr : > On Sunday, December 18, 2011 7:15:26 AM Jorge Timón wrote: >> I'm just saying is useful for th

Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Luke-Jr
On Sunday, December 18, 2011 7:15:26 AM Jorge Timón wrote: > I'm just saying is useful for the "green address" particular case. "Green addresses" are also a broken-by-design feature and should be discouraged. -- Learn Wi

Re: [Bitcoin-development] Pubkey addresses

2011-12-18 Thread Jorge Timón
2011/12/17, Jordan Mack : > While I think firstbits is an interesting idea, I agree with Matt on > this one. Firstbits, while being a clever idea, produces a less > desirable solution in comparison to the current alias proposals. I'm just saying is useful for the "green address" particular case. P

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Luke-Jr
On Saturday, December 17, 2011 7:28:12 PM Luke-Jr wrote: > On Saturday, December 17, 2011 6:46:34 PM Gregory Maxwell wrote: > > Sorry to be curt— I'm a little irritated that discussion on recovery > > in OP_EVAL was dropped because "input script size doesn't matter > > because of pruning" and now p

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Luke-Jr
On Saturday, December 17, 2011 6:46:34 PM Gregory Maxwell wrote: > Sorry to be curt— I'm a little irritated that discussion on recovery > in OP_EVAL was dropped because "input script size doesn't matter > because of pruning" and now people are talking about adding another > address type which creat

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Gregory Maxwell
On Sat, Dec 17, 2011 at 4:52 PM, Luke-Jr wrote: > I propose that full public key addresses be required to be "compact" (length > 33), and use version 21 (begins with '4', and is redundant with ver 20 for 20- > byte data). Any reason this wouldn't be workable? Would introduce yet another address t

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Luke-Jr
I propose that full public key addresses be required to be "compact" (length 33), and use version 21 (begins with '4', and is redundant with ver 20 for 20- byte data). Any reason this wouldn't be workable? -- Learn Window

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Jordan Mack
While I think firstbits is an interesting idea, I agree with Matt on this one. Firstbits, while being a clever idea, produces a less desirable solution in comparison to the current alias proposals. In addition to Matt's reasons, I would like to add that it is still a block of random characters,

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Matt Corallo
On Sat, 2011-12-17 at 12:14 +0100, Jorge Timón wrote: > Don't know much about QR codes, but I thought they have a length limitation. > Why jav wants to use not just addresses but firstbits then? Under no circumstances should the use of firstbits ever be supported. It doesn't scale, not even close,

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Wladimir
I don't see reason why not. It could just be another, longer, address type. The advantage being that it allows for shorter transactions in the block chain (right?). Wladimir On Sat, Dec 17, 2011 at 7:32 AM, Luke-Jr wrote: > IMO, we should standardize and support public key addresses. While not

Re: [Bitcoin-development] Pubkey addresses

2011-12-17 Thread Jorge Timón
Don't know much about QR codes, but I thought they have a length limitation. Why jav wants to use not just addresses but firstbits then? "Allow a field "green_address_list" (short "gal") to specify acceptable addresses in Firstbit format directly in the QR code and only use the "green_address_deta

[Bitcoin-development] Pubkey addresses

2011-12-16 Thread Luke-Jr
IMO, we should standardize and support public key addresses. While not ideal for humans, because of their length, it's a better fit for large QR Codes IMO. -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is