Re: [Bitcoin-development] Service bits for pruned nodes

2013-04-29 Thread Jay F
On 4/28/2013 8:55 PM, Peter Todd wrote: On Mon, Apr 29, 2013 at 03:48:18AM +, John Dillon wrote: We can build this stuff incrementally I'll agree. It won't be the case that one in a thousand nodes serve up the part of the chain you need overnight. So many I am over engineering the

Re: [Bitcoin-development] On-going data spam

2013-04-09 Thread Jay F
On 4/9/2013 4:09 AM, Peter Todd wrote: On Tue, Apr 09, 2013 at 12:42:12PM +0200, Mike Hearn wrote: hack by changing the protocol. Nodes can serve up blocks encrypted under a random key. You only get the key when you finish the download. A blacklist NAK Makes bringing up a new node dependent

Re: [Bitcoin-development] A bitcoin UDP P2P protocol extension

2013-03-23 Thread Jay F
My first concern was that I and about everyone else only has TCP/UDP port forwarding, but at least for the first: UDT uses UDP to transfer bulk data with its own reliability control and congestion control mechanisms. Multiple UDT flows can share a single UDP port, thus a firewall can open only

Re: [Bitcoin-development] Warning: many 0.7 nodes break on large number of tx/block; fork risk

2013-03-12 Thread Jay F
On 3/12/2013 5:18 AM, Jorge Timón wrote: A related question...some people mentioned yesterday on #bitcoin-dev that 0.5 appeared to be compatible with 0.8. Was that only for the fatal block and would have forked 0.8 later too or is it something else? I'm having a hard time understanding this