Re: [Bitcoin-development] BIP43 Purpose code for voting pool HD wallets

2014-09-25 Thread Gregory Maxwell
On Tue, Aug 19, 2014 at 10:11 AM, Justus Ranvier jus...@monetas.net wrote: Two draft information BIPs are attached. I've pinged some people privately but also pinging the list… no commentary on this proposal? -- Meet

Re: [Bitcoin-development] BIP43 Purpose code for voting pool HD wallets

2014-09-25 Thread Justus Ranvier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/26/2014 01:53 AM, Gregory Maxwell wrote: On Tue, Aug 19, 2014 at 10:11 AM, Justus Ranvier jus...@monetas.net wrote: Two draft information BIPs are attached. I've pinged some people privately but also pinging the list… no commentary on

Re: [Bitcoin-development] SPV clients and relaying double spends

2014-09-25 Thread Aaron Voisine
Something like that would be a great help for SPV clients that can't detect double spends on their own. (still limited of course to sybil attack concerns) Aaron Voisine breadwallet.com On Thu, Sep 25, 2014 at 7:07 PM, Matt Whitlock b...@mattwhitlock.name wrote: What's to stop an attacker from

Re: [Bitcoin-development] SPV clients and relaying double spends

2014-09-25 Thread Matt Whitlock
Probably the first double-spend attempt (i.e., the second transaction to spend the same output(s) as another tx already in the mempool) would still need to be relayed. A simple double-spend alert wouldn't work because it could be forged. But after there have been two attempts to spend the same

Re: [Bitcoin-development] SPV clients and relaying double spends

2014-09-25 Thread Matt Whitlock
What's to stop an attacker from broadcasting millions of spends of the same output(s) and overwhelming nodes with slower connections? Might it be a better strategy not to relay the actual transactions (after the first) but rather only propagate (once) some kind of double-spend alert? On

Re: [Bitcoin-development] BIP43 Purpose code for voting pool HD wallets

2014-09-25 Thread Alan Reiner
I'm in favor of BIP43. Adding a Purpose node can be used as an identifier for what kind of tree is in the wallet file we're reading. I can envision a few different, common tree structures. Perhaps using a non-hardened first-layer derivation (we have clients who want this). Similarly, my

Re: [Bitcoin-development] BIP43 Purpose code for voting pool HD wallets

2014-09-25 Thread Bryan Bishop
On Thu, Sep 25, 2014 at 8:53 PM, Gregory Maxwell gmaxw...@gmail.com wrote: I've pinged some people privately but also pinging the list… no commentary on this proposal? One possible reason is that non-subscribed users aren't able to access the file through sourceforge. The attachment through

Re: [Bitcoin-development] SPV clients and relaying double spends

2014-09-25 Thread Aaron Voisine
Of course you wouldn't want nodes to propagate alerts without independently verifying them, otherwise anyone could just issue alerts for every new transaction. Aaron Voisine breadwallet.com On Thu, Sep 25, 2014 at 7:16 PM, Matt Whitlock b...@mattwhitlock.name wrote: Probably the first

Re: [Bitcoin-development] SPV clients and relaying double spends

2014-09-25 Thread Christophe Biocca
A lot of this discussion has already occured. Some code was even merged into master, then reverted. See: https://github.com/bitcoin/bitcoin/issues/4550 https://github.com/bitcoin/bitcoin/pull/4570 It would probably be a good idea to start from that code, as it addresses many of the possible