From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SfbTi-0007Gq-UQ for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 18:42:38 +0000 X-ACL-Warn: Received: from nm32-vm2.bullet.mail.ne1.yahoo.com ([98.138.229.50]) by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1SfbTh-0005bu-WC for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 18:42:38 +0000 Received: from [98.138.90.53] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 15 Jun 2012 18:42:32 -0000 Received: from [98.138.89.240] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 15 Jun 2012 18:42:32 -0000 Received: from [127.0.0.1] by omp1013.mail.ne1.yahoo.com with NNFMP; 15 Jun 2012 18:42:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 538466.73172.bm@omp1013.mail.ne1.yahoo.com Received: (qmail 10634 invoked by uid 60001); 15 Jun 2012 18:42:32 -0000 X-YMail-OSG: B7lTSEIVM1mfVuxTO9T9ocCIa99pDrz1uMLv.dEs44rIRSr yt7JOhADd7DJbCNrqLy1Wd0qG28rj5i2QfAkWo7kv_k2t50khZe8_1vmnbiN BUozbF94ymmFE7xVwdMa9prvMtT70nBm_R0lgDrQZ0ChLRmjxG45RrvrK5L6 8oWPPrD9wnFeOsAhqrMdFP01uYGXpflrK78szkYLKEKM0FkaP8IgQy64nsTj ej3xLzkGlcqKzSDs5jXQqEcJ8udcCbI0a4tM7M_KP0hXzcvs76RZ3SudD5oc budGlllYqcu9f0khMsrP4KdyJzXD0Rl7CQzVtr8bC17PcDP2iWG6tLXGBc5x _XBX0Utqbd_qeCSMYncAIPFiZKdnXt4c3JbQRcHSxWGsdt5zs4UtPymtrow0 N4.rMoouRfAAMBc.0xNTWCfo1NGBwANs_RcLf0vrKn8DvAzxKCG4bVeXfyZi zc8NKLGBLweSqKlTU_N407eidAMschIRIUY5bx6KnWP0SBZzq2FHHBlMVv8u 26vDxc7GA3Lao Received: from [213.129.230.10] by web121004.mail.ne1.yahoo.com via HTTP; Fri, 15 Jun 2012 11:42:32 PDT X-Mailer: YahooMailWebService/0.8.118.349524 References: Message-ID: <1339785752.91313.YahooMailNeo@web121004.mail.ne1.yahoo.com> Date: Fri, 15 Jun 2012 11:42:32 -0700 (PDT) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.229.50 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 FSL_FREEMAIL_2 FSL_FREEMAIL_2 0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1 X-Headers-End: 1SfbTh-0005bu-WC Subject: Re: [Bitcoin-development] New P2P commands for diagnostics, SPV clients X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 18:42:39 -0000 Why though? The bottleneck is not network traffic but disk space usage/bloc= kchain validation time.=0A=0A=0A=0A----- Original Message -----=0AFrom: Mik= e Hearn =0ATo: Jeff Garzik =0ACc: Bit= coin Development =0ASent: Friday= , June 15, 2012 3:43 PM=0ASubject: Re: [Bitcoin-development] New P2P comman= ds for diagnostics, SPV clients=0A=0A> Yes, the format is something that mu= st be hashed out (no pun=0A> intended). =A0Need input from potential users = about what information=0A> they might need.=0A=0AMatts point that a branch-= per-transaction may duplicate data is well=0Amade, that said, I suspect a f= ormat that tries to fix this would be=0Amuch more complicated.=0A=0AHow abo= ut see this project as a three part change?=0A=0AFirst step - add the mempo= ol command and make nodes sync up their=0Amempools on startup.=0A=0ASecond = step - if protocol version >=3D X, the "block" message consists=0Aof a head= er + num transactions + vector=A0 instead of the full=0Atransactions = themselves.=0A=0AOn receiving such a block, we go look to see which transac= tions we're=0Amissing from the mempool and request them with getdata. Each = time we=0Areceive a tx message we check to see if it was one we were missin= g=0Afrom a block. Once all transactions in the block message are in=0Amemor= y, we go ahead and assemble the block, then verify as per normal.=0AThis sh= ould speed up block propagation. Miners have an incentive to=0Aupgrade beca= use it should reduce wasted work.=0A=0AThird step - new message, getmerklet= x takes a vector and returns=0Aa merkletx message: "merkle branch mis= sing the root + transaction data=0Aitself" for each requested transaction. = The filtering commands are=0Aadded, so the block message now only lists tra= nsaction hashes that=0Amatch the filter which can then be requested with ge= tmerkletx.=0A=0A-----------------------------------------------------------= -------------------=0ALive Security Virtual Conference=0AExclusive live eve= nt will cover all the ways today's security and =0Athreat landscape has cha= nged and how IT managers can respond. Discussions =0Awill include endpoint = security, mobile security and the latest in malware =0Athreats. http://www.= accelacomm.com/jaw/sfrnl04242012/114/50122263/=0A__________________________= _____________________=0ABitcoin-development mailing list=0ABitcoin-developm= ent@lists.sourceforge.net=0Ahttps://lists.sourceforge.net/lists/listinfo/bi= tcoin-development=0A