Re: [Bitcoin-development] Bitcoind-in-background mode for SPV wallets

2014-05-04 Thread Tier Nolan
On Fri, Apr 11, 2014 at 5:54 PM, Gregory Maxwell wrote: > For the non-error-coded case I believe nodes > with random spans of blocks works out asymptotically to the same > failure rates as random. > If each "block" is really 512 blocks in sequence, then each "slot" is more likely to be hit. It

Re: [Bitcoin-development] Proposal for extra nonce in block header

2014-05-04 Thread Timo Hanke
On Sun, May 04, 2014 at 05:26:06PM +0200, Mike Hearn wrote: > Although I agree 32 bits for a version is overkill, I really don't like the > idea of you simply ignoring the protocol spec to try and reduce your own > costs. The purpose of the proposal is to change the protocol spec, not to ignore i

Re: [Bitcoin-development] Proposal for extra nonce in block header

2014-05-04 Thread Timo Hanke
On Sun, Apr 27, 2014 at 02:38:06AM -0700, Mark Friedenbach wrote: > I'm not convinced of the necessity of this idea in general, but if it > were to be implemented I would recommend serializing the nVersion field > as a VarInt (Pieter Wuille's multi-byte serialization format) and using > the remaini

Re: [Bitcoin-development] Proposal for extra nonce in block header

2014-05-04 Thread Mike Hearn
Although I agree 32 bits for a version is overkill, I really don't like the idea of you simply ignoring the protocol spec to try and reduce your own costs. Especially because in future we should make unknown versions a validation rule, so we can easily trigger hard forks. If this change was introd

Re: [Bitcoin-development] Proposal for extra nonce in block header

2014-05-04 Thread Timo Hanke
> If changing the structure of the block header, wouldnt you also need to > increment the version number to 3? No, in this case I don't think so. Incrementing the version number has two purposes: 1. inform old clients that something new is going on 2. be able to phase out old version numbers and

Re: [Bitcoin-development] "bits": Unit of account

2014-05-04 Thread Mike Caldwell
I will drink to that! Bitte ein Bit! (A Bit please - aka Bitburger Beer) Mike Sent from my iPhone > On May 4, 2014, at 12:17 AM, "Aaron Voisine" wrote: > > Bit by bit, it's become clear that it's a bit much to worry even a > little bit that overloading the word "bit" would be every bit as bad

Re: [Bitcoin-development] Bug with handing of OP_RETURN?

2014-05-04 Thread Jeff Garzik
On Sat, May 3, 2014 at 3:15 PM, Mark Friedenbach wrote: > Is it more complex? The current implementation using template matching > seems more complex than `if script.vch[0] == OP_RETURN && > script.vch.size() < 42` Not much more complex. The template matches a two-chunk script with OP_RETURN + o

Re: [Bitcoin-development] BIP70 implementation guidance

2014-05-04 Thread Mike Hearn
> > e.g. in the UK sole traders (that is, unincorporated businesses) can't > get EV certs because the UK doesn't maintain a trade register of such > businesses > Sole traders can just trade under their own name, or their email address, or their domain name, heck even their telephone number if some

Re: [Bitcoin-development] Bug with handing of OP_RETURN?

2014-05-04 Thread Sergio Lerner
El 03/05/2014 03:55 p.m., Mark Friedenbach escribió: > > On 05/03/2014 11:39 AM, Peter Todd wrote: >> The standard format ended up being exactly: >> >> OP_RETURN <0 to 40-byte PUSHDATA> >> Please remember that the code actually does not implement the "standard format" (at least the last time I

Re: [Bitcoin-development] Bug with handing of OP_RETURN?

2014-05-04 Thread Flavien Charlon
Thanks, that makes sense, just wanted to make sure this what the problem was. On Sun, May 4, 2014 at 6:15 AM, Jeff Garzik wrote: > On Sat, May 3, 2014 at 2:04 PM, Flavien Charlon > wrote: > > Outputs are above dust, inputs are not spent. OP_RETURN is supposed to be > > standard in 0.9.1 and th

Re: [Bitcoin-development] "bits": Unit of account

2014-05-04 Thread Wladimir
On Sun, May 4, 2014 at 8:36 AM, Tamas Blummer wrote: > Wladimir, > > what is missing is a decision to pull for the reference client. > Or did I missed that bit? No opinion - we'll follow whatever the rest does. Wladimir ---