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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1T2443-0008OB-Qf for bitcoin-development@lists.sourceforge.net; Thu, 16 Aug 2012 17:40:59 +0000 X-ACL-Warn: Received: from nm5-vm1.bullet.mail.ne1.yahoo.com ([98.138.91.32]) by sog-mx-1.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1T2442-0006np-Ui for bitcoin-development@lists.sourceforge.net; Thu, 16 Aug 2012 17:40:59 +0000 Received: from [98.138.90.51] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 16 Aug 2012 17:40:53 -0000 Received: from [98.138.89.162] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 16 Aug 2012 17:40:53 -0000 Received: from [127.0.0.1] by omp1018.mail.ne1.yahoo.com with NNFMP; 16 Aug 2012 17:40:53 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 590910.3608.bm@omp1018.mail.ne1.yahoo.com Received: (qmail 82195 invoked by uid 60001); 16 Aug 2012 17:40:53 -0000 X-YMail-OSG: aUWny9wVM1kKa4EiZKLbyFPiZn3H7pG2B_ED3vrErwRwP0_ bhITUW1ypBs3MvycfYaa7zoofk8DKx5vqs108nk3yl.v6bopl.GcboXkhhwZ zyQcb2I4rB7jW9hKxvIHQpkcnA_cFs2bca8AQS1CMHq86uyJfmeNb5pGYMiL _jwRBCp52MHIXK3ZaICEIK5H45kdUJguqt5R21GmA.JAROluerzy9VeQfLGB xV8fHLPZPG0puZP99u.Xvo0QDMPD44LUHEcsZt.Dgwn7FirUW1JZmVblzMFA VHE2rt8j9L2N_oAk29juWtvbK75uS.8pFp3U_DpgMPFSSQN3LBYQT.BGsnQY LDh4qFndBUncD5Q85jqiV1vMbPP98XNw7GDqhr_Ta6XFOXEQxg8CbRBERfuX k365s5k0PpJuATXwDt7JVnmEFHdLFloodQz6nazGJl0Uxj3PxryMETTsLte4 GV269L4eR6dK9SEXb5eLpT_1HmUDLJrGEL1SMmvb5CY0rG3f4s4tEwK6I5fM Vqd8TETEpQr64ukUe3x37wHJDD1UkpjN98ibDt5cl8eiIwONVl1iGFG9Y6dH hxT_hEktDtJ4gPz8sKUvuHqgcN6.WOdEtHBEIrcAlwUlqU0Q805W5s0ov54Y jLY9ETnIEhkoA0_XU1xACCMq_vhoUodcE7iw7Iac_VppUOQ-- Received: from [92.20.159.204] by web121006.mail.ne1.yahoo.com via HTTP; Thu, 16 Aug 2012 10:40:53 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: Message-ID: <1345138853.81509.YahooMailNeo@web121006.mail.ne1.yahoo.com> Date: Thu, 16 Aug 2012 10:40:53 -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.91.32 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) 0.0 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 AWL AWL: From: address is in the auto white-list X-Headers-End: 1T2442-0006np-Ui Subject: Re: [Bitcoin-development] BIP 35: add mempool message 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: Thu, 16 Aug 2012 17:40:59 -0000 The format for "mempool" packet is missing. I'm guessing that it is an empt= y message, right?=0A=0AMight be good to add that.=0A=0A=0A=0A----- Original= Message -----=0AFrom: Jeff Garzik =0ATo: Bitcoin Deve= lopment =0ACc: =0ASent: Thursday= , August 16, 2012 6:32 PM=0ASubject: [Bitcoin-development] BIP 35: add memp= ool message=0A=0AConsensus was we should do a BIP for all P2P changes, so h= ere it is...=0Afeedback requested.=0A=0Ahttps://en.bitcoin.it/wiki/BIP_0035= =0A=0AAbstract=0A-------------------------------------------=0AMake a netwo= rk node's transaction memory pool accessible via a new=0A"mempool" message.= =A0 Extend the existing "getdata" message behavior to permit=0Aaccessing th= e transaction memory pool.=0A=0A=0AMotivation=0A---------------------------= ----------------=0ASeveral use cases make it desireable to expore a network= node's transaction=0Amemory pool:=0A* SPV clients, wishing to obtain zero-= confirmation transactions sent or=0A=A0 received.=0A* Miners, downloading e= xisting network transactions after a restart.=0A* Remote network diagnostic= s.=0A=0A=0ASpecification=0A-------------------------------------------=0A1)= Upon receipt of a "mempool" message, the node will respond=0A=A0 with an = "inv" message containing MSG_TX hashes of all the=0A=A0 transactions in th= e node's transaction memory pool.=0A=0A=A0 An "inv" message is always retu= rned, even if empty.=0A=0A2) The typical node behavior in response to an "i= nv" is "getdata".=0A=0A=A0 However, the reference Satoshi implementation i= gnores requests=0A=A0 for transaction hashes outside that which is recentl= y relayed.=0A=0A=A0 To support "mempool", an implementation must extend it= s "getdata"=0A=A0 message support to querying the memory pool.=0A=0A3) Fea= ture discovery is enabled by checking two "version" message attributes:=0A= =0A=A0 a) Protocol version >=3D 60002=0A=A0 b) NODE_NETWORK bit set in nS= ervices=0A=0A=0ABackwards compatibility=0A---------------------------------= ----------=0AOlder clients remain 100% compatible and interoperable after t= his change.=0A=0A=0AImplementation=0A--------------------------------------= -----=0ASee https://github.com/bitcoin/bitcoin/pull/1641=0A=0A-- =0AJeff Ga= rzik=0AexMULTI, Inc.=0Ajgarzik@exmulti.com=0A=0A---------------------------= ---------------------------------------------------=0ALive Security Virtual= Conference=0AExclusive live event will cover all the ways today's security= and =0Athreat landscape has changed and how IT managers can respond. Discu= ssions =0Awill include endpoint security, mobile security and the latest in= malware =0Athreats. http://www.accelacomm.com/jaw/sfrnl04242012/114/501222= 63/=0A_______________________________________________=0ABitcoin-development= mailing list=0ABitcoin-development@lists.sourceforge.net=0Ahttps://lists.s= ourceforge.net/lists/listinfo/bitcoin-development=0A