Re: [Bitcoin-development] Payment protocol and reliable Payment messages

Thanks for the explanation. On 01/13/2014 06:56 PM, Pieter Wuille wrote: >> As for you proposal, just be aware I'd like to use the payment protocol >> for face to face payments as well. That meant payment request via NFC or >> QR, payment message and payment confirmations via Bluetooth. I think i

Re: [Bitcoin-development] Stealth Addresses

> Uh while I'm responding again, what I'd discussed with Peter Todd in > IRC used two EC points in the stealth address. One for the payment and > one for the ECDH. The reason to use two is that it makes delegating > detection possible and so you don't have to have you spending keys > online to ev

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 04:15:01PM -0500, Alan Reiner wrote: > > I don't know if stealth addresses are the best solution to address > > this use case, but AFAIK the only current solution to this use case is > > to store a long-lived Bitcoin address in the addresss book. > > > > roy > > > > Fair en

Re: [Bitcoin-development] Stealth Addresses

On 01/13/2014 04:02 PM, Roy Badami wrote: >> It's not public. When I say "please pay me" I also say "use this >> multiplier". > Sending a "please pay me" message is really great for business > transactions. > > But I think the use case that Peter Todd mentions is actually *the* > most important cu

Re: [Bitcoin-development] Stealth Addresses

> It's not public. When I say "please pay me" I also say "use this > multiplier". Sending a "please pay me" message is really great for business transactions. But I think the use case that Peter Todd mentions is actually *the* most important currently under-addresesd use case: > With stealth ad

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 12:41 PM, Alan Reiner wrote: > It's not public. When I say "please pay me" I also say "use this > multiplier". The multiplier isn't published, and it's not publicly > discoverable without my wallet (or access to my email). If you have enough of a communications channel t

Re: [Bitcoin-development] Stealth Addresses

On 01/13/2014 03:14 PM, Peter Todd wrote: > On Mon, Jan 13, 2014 at 02:59:08PM -0500, Alan Reiner wrote: >> How is this different from the proposal I have made? >> >> You distribute the root public key (but not chaincode!) of a BIP32 >> branch. You can put your root key on a business card if you

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 12:10:56PM -0800, Gregory Maxwell wrote: > Uh while I'm responding again, what I'd discussed with Peter Todd in > IRC used two EC points in the stealth address. One for the payment and > one for the ECDH. The reason to use two is that it makes delegating > detection possibl

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 02:59:08PM -0500, Alan Reiner wrote: > How is this different from the proposal I have made? > > You distribute the root public key (but not chaincode!) of a BIP32 > branch. You can put your root key on a business card if you want. Then > when someone wants to pay you, you

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 04:58:01PM +0100, Mike Hearn wrote: > Signing a payment request for an individual is easy, anyway, depending on > the kind of ID you want. If you want to sign with an email address, just go > here with a browser like Chrome/Safari/IE that uses the system keystore: > >ht

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 11:59 AM, Alan Reiner wrote: > Then when someone > wants to pay you, you simply give them the multiplier and root key (they > already have the root key, but should verify). [...] > What > advantages does "stealth addresses" have over this scheme? You could extend > it usin

Re: [Bitcoin-development] Stealth Addresses

rOn Mon, Jan 13, 2014 at 08:57:33PM +0100, Mike Hearn wrote: > > > > On further reflection, I'm not sure I understand this use case of the > > payment protocol. Since a PaymentRequest currently contains the > > Outputs that specify the addresses to send to, reusing a > > PaymentRequest like this w

Re: [Bitcoin-development] Stealth Addresses

How is this different from the proposal I have made? You distribute the root public key (but not chaincode!) of a BIP32 branch. You can put your root key on a business card if you want. Then when someone wants to pay you, you simply give them the multiplier and root key (they already have the ro

Re: [Bitcoin-development] Stealth Addresses

> > On further reflection, I'm not sure I understand this use case of the > payment protocol. Since a PaymentRequest currently contains the > Outputs that specify the addresses to send to, reusing a > PaymentRequest like this without using stealth addresses implies > address reuse. Yes indeed ..

Re: [Bitcoin-development] Stealth Addresses

> > Likewise, I could attach a payment request to an email and send it to you, > > and now you can pay me whenever you want forever. > > That certainly sounds like a plausible use case. You do still have > the problem that e-mail is an insecure channel, but it's no worse than > exchanging Bitcoin

Re: [Bitcoin-development] Stealth Addresses

On 13 January 2014 19:40, Roy Badami wrote: > At the moment, I can give them a business card with a Bitcoin address. > Being able to give out a business card with a stealth address would be > a major advance. My thoughts exactly. Drak ---

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 01:52:25AM -0800, Gregory Maxwell wrote: > On Sun, Jan 12, 2014 at 1:18 PM, Gavin Andresen > wrote: > > No, please. Make it easy for non-geeks, extend the payment protocol, or > > we'll spend the next two years writing code that tries to ignore linebreaks > > and spaces an

Re: [Bitcoin-development] Payment protocol and reliable Payment messages

On Mon, Jan 13, 2014 at 6:44 PM, Andreas Schildbach wrote: > On 01/13/2014 05:43 PM, Pieter Wuille wrote: > >> As an optimization (and I believe this is what Mike plans to implement >> in BitcoinJ), if a payment_url is present, it should be encouraged to >> only send the payment there, and not bro

Re: [Bitcoin-development] Payment protocol and reliable Payment messages

On 01/13/2014 05:43 PM, Pieter Wuille wrote: > As an optimization (and I believe this is what Mike plans to implement > in BitcoinJ), if a payment_url is present, it should be encouraged to > only send the payment there, and not broadcast the transaction at all > on the P2P network (minimizing the

[Bitcoin-development] Payment protocol and reliable Payment messages

Hi all, while thinking about what use cases the stealth addresses covers, in particular in addition to the payment protocol, I found it useful to bring this up again. currently, BIP70 says for "payment_url": Secure (usually https) location where a Payment message (see below) may be sent to obtain

Re: [Bitcoin-development] Stealth Addresses

On Mon, Jan 13, 2014 at 2:37 PM, Roy Badami wrote: > That does require trusting the third party not to later tamper with > the payment request, though. You have to trust the billboard owner too. If you're relying on a third party to relay a payment instruction, that will always be an issue, hen

Re: [Bitcoin-development] Stealth Payments - Sample Code / Proof of Concept

On Mon, 13 Jan 2014 03:18:28 -0800, Mike Hearn wrote:Cool!On Mon, Jan 13, 2014 at 10:18 AM, Jeremy Spilman wrote: I spent 1BTC on TestNet to a stealth address...     TxID: df092896c1347b303da299bc84c92bef1946f455dbdc80ffdb01a18ea4ed8b4c... but can you redeem it?But of course!E

Re: [Bitcoin-development] Stealth Addresses

> I was thinking that people could upload a payment protocol file somewhere > once (like to their personal web page, or shared via dropbox or google > drive or some custom new pastebin style service), and then just encode a > regular bitcoin URI into the qrcode on the billboard. That does require

Re: [Bitcoin-development] Stealth Payments - Sample Code / Proof of Concept

Cool! On Mon, Jan 13, 2014 at 10:18 AM, Jeremy Spilman wrote: > I spent 1BTC on TestNet to a stealth address... > TxID: df092896c1347b303da299bc84c92bef1946f455dbdc80ffdb01a18ea4ed8b4c > ... but can you redeem it? > Code which generated this transaction is here: > https://gist.github.com/

Re: [Bitcoin-development] Stealth Addresses

> > However, if you're able to use the payment protocol then you probably > don't need stealth addresses to prevent reuse. > I was thinking that people could upload a payment protocol file somewhere once (like to their personal web page, or shared via dropbox or google drive or some custom new pas

Re: [Bitcoin-development] Stealth Addresses

On Sun, Jan 12, 2014 at 1:18 PM, Gavin Andresen wrote: > No, please. Make it easy for non-geeks, extend the payment protocol, or > we'll spend the next two years writing code that tries to ignore linebreaks > and spaces and changing elements in HTML forms to However, if you're able to use

[Bitcoin-development] Stealth Payments - Sample Code / Proof of Concept

* Transaction * I spent 1BTC on TestNet to a stealth address... TxID: df092896c1347b303da299bc84c92bef1946f455dbdc80ffdb01a18ea4ed8b4c http://blockexplorer.com/testnet/tx/df092896c1347b303da299bc84c92bef1946f455dbdc80ffdb01a18ea4ed8b4c#i8166574 * Code * Code which generated this transaction

Re: [Bitcoin-development] Stealth Addresses

On Sun, Jan 12, 2014 at 7:20 PM, Jeremy Spilman wrote: > > I think for displaying the payment in the UI after it's been made via > PP, we have to fully > > support sending to a new standard address type anyway. On Sun, 12 Jan 2014 10:26:18 -0800, Mike Hearn wrote: > Why? Showing an address is