Re: [Bitcoin-development] Reusable payment codes

2015-06-16 Thread odinn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is very well done. Have you seen this discussion that I started regarding BIP 63? https://bitcointalk.org/index.php?topic=1083961.0 I have no response from Peter Todd back on it other than my time is better spent focusing on more fundemental

Re: [Bitcoin-development] Reusable payment codes

2015-06-16 Thread Peter Todd
On Tue, Jun 16, 2015 at 09:26:07AM -0700, odinn wrote: This is very well done. Have you seen this discussion that I started regarding BIP 63? https://bitcointalk.org/index.php?topic=1083961.0 I have no response from Peter Todd back on it other than my time is better spent focusing on

Re: [Bitcoin-development] Reusable payment codes

2015-06-16 Thread odinn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter, my response below On 06/16/2015 10:46 AM, Peter Todd wrote: On Tue, Jun 16, 2015 at 09:26:07AM -0700, odinn wrote: This is very well done. Have you seen this discussion that I started regarding BIP 63?

Re: [Bitcoin-development] Reusable payment codes

2015-04-29 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/27/2015 02:53 PM, Brian Deery wrote: 1. There will be a 1:1 relationship between a payment code owner and their identity. Presumably the payment code would be strongly and publicly tied to the identity. This makes the notification address

Re: [Bitcoin-development] Reusable payment codes

2015-04-28 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The notification transactions are a pain point when it comes to privacy, and yet they must exist in order to to ensure that nobody can lose their money as long as they back up their wallet seed. They could be treated as a backup, however, that

Re: [Bitcoin-development] Reusable payment codes

2015-04-27 Thread Brian Deery
Hi Justus: CC'ing mailing list because more bloom filter and HD wallet experts there can chime in for some of these thoughts. I refined some ideas we went over earlier. Here are some critiques/worries about the payment codes. With identities explicitly tied to a payment code, bloom filter

Re: [Bitcoin-development] Reusable payment codes

2015-04-27 Thread Mike Hearn
1. There will be a 1:1 relationship between a payment code owner and their identity. Bear in mind, the spec defines identity to mean: *Identity is a particular extended public/private key pair. * So that's not quite what is meant normally by identity. It's not a government / real name

Re: [Bitcoin-development] Reusable payment codes

2015-04-27 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/27/2015 04:46 PM, Mike Hearn wrote: So that's not quite what is meant normally by identity. It's not a government / real name identity or an email address or phone number kind of identity. I expect that mappings would begin to develop

Re: [Bitcoin-development] Reusable payment codes

2015-04-24 Thread Gregory Maxwell
On Fri, Apr 24, 2015 at 8:00 PM, Justus Ranvier justus.ranv...@monetas.net wrote: https://github.com/justusranvier/rfc/blob/payment_code/bips/bip-pc01.mediawiki This link contains an RFC for a new type of Bitcoin address called a payment code Payment codes are SPV-friendly alternatives to