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 1YOPfh-000897-0q for bitcoin-development@lists.sourceforge.net; Thu, 19 Feb 2015 11:53:33 +0000 Received: from nm40.bullet.mail.ne1.yahoo.com ([98.138.229.33]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YOPff-0007If-FL for bitcoin-development@lists.sourceforge.net; Thu, 19 Feb 2015 11:53:33 +0000 Received: from [127.0.0.1] by nm40.bullet.mail.ne1.yahoo.com with NNFMP; 19 Feb 2015 11:40:02 -0000 Received: from [98.138.100.111] by nm40.bullet.mail.ne1.yahoo.com with NNFMP; 19 Feb 2015 11:37:18 -0000 Received: from [98.139.215.143] by tm100.bullet.mail.ne1.yahoo.com with NNFMP; 19 Feb 2015 11:37:18 -0000 Received: from [98.139.212.199] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2015 11:37:18 -0000 Received: from [127.0.0.1] by omp1008.mail.bf1.yahoo.com with NNFMP; 19 Feb 2015 11:37:18 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 66823.69816.bm@omp1008.mail.bf1.yahoo.com X-YMail-OSG: CDPGONoVM1lpvGuYJfWbG.fsNNYZsZOuMrNhR7lZQ6baOb65m_mUDUfl1VxpQ9f VB_zjr5dS5A0T0ErzKkeUaPaYC.Et7i.hF5FVeiL.s.vsHef..AcWzVSSEBg6xxr6VrWMxqFmXYW BSzsTEIbvq2qhMzi75KWx9YdM2YcO1wZRsRt6tLfZTgmi6PyVEfxKN8fjhwMfElEL1ZgYAAhTzvF l2Rw04FPGwaSWd9GuVU6FnQPW0taSTpAi5OyW2YKnoVrp0WJiQtuXBmifwjiL433PdwbBYXda3BZ GJXVwBWecScQUF6bQG_skJyCFY5Ucp9uTlt5CiFcK7siZxDrf.OzlmPfUfIADh6VIb7b_pGKlywx xPrKVyb_MtR2qo162yqkmwONPCFksdfVrq.MGTkDX3CEApwlAMlXnQkELChnP2ztzT5qvU2xo4BV 7ATeF7H_isFvpuLOvxHi5EoW_bOnhLF_WbtaMn9930CAP94S.zswFJ84GvfHK4za9.WLh5_l9Txl r4Nmrx5G8X9xrCZwoVtrj0GDNom7fnf4LvNV32AqgjnfqiaHLhqn.wWYtnJoUw98mpj5hZ8b3fy3 FdVfrdIAvewIsUh3PZuqcMtrno9TKpYgilYevCTMP8cNBx4pK6fZAJS5qPwgLOy9FXcLLD6j_C1P v4PYGTotYQ7NcYOvEifFAxO4LGhdGeL3ilpXjRbRk3Zo1..AL1we7RyynN90Rne.rMY8sR14_dYL c0fBkg9tAaF8GEcZmDzfesogTbI.fb2VlnGDIjqOlJ_YRT_xhNYzgGeCdBhLGDHZT.A-- Received: by 66.196.81.117; Thu, 19 Feb 2015 11:37:17 +0000 Date: Thu, 19 Feb 2015 11:37:17 +0000 (UTC) From: Thy Shizzle To: "bitcoin-development@lists.sourceforge.net\" ; " Message-ID: <598724161.2420831.1424345837150.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <904753900.2475114.1424345591935.JavaMail.yahoo@mail.yahoo.com> References: <904753900.2475114.1424345591935.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2420830_2017125422.1424345837138" X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (harro84[at]yahoo.com.au) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.229.33 listed in list.dnswl.org] 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (harro84[at]yahoo.com.au) 1.0 HTML_MESSAGE BODY: HTML included in message -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 T_REMOTE_IMAGE Message contains an external image X-Headers-End: 1YOPff-0007If-FL Subject: Re: [Bitcoin-development] What's what with addr relaying? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Thy Shizzle List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 11:53:33 -0000 ------=_Part_2420830_2017125422.1424345837138 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Oh and I realised I stuffed up the subject and it talks about the addr rela= y but I actually answered my own question on the addr relaying, I had just = miss interpreted one document I thought it was talking about subtracting 2 = hours before relaying but I see we subtract 2 hours on receipt not relay=C2= =A0because the if it hadn't been seen for 60 minutes previously it now beco= mes 3 hours and we use but don't relay makes sense.=20 On Thursday, 19 February 2015, 22:33, Thy Shizzle wrote: =20 =20 Hi, plugging away at my C# Bitcoin node "Lego.NET" Thashiznets/Lego.NET n= ow I am currently working on addr relaying. I am as we speak wiring up my D= B in Azure, and ready to start plopping net_addrs in my DB, all good howeve= r I'm reading two different specification docs that seem to be wildly varyi= ng. I mean the first one here Developer Reference - Bitcoin=C2=A0didn't men= tion that version message now has the 4 byte checksum and no=C2=A0time in t= he net_addrs=C2=A0and I was getting reject malformed=C2=A0messages until I = found the other document which informed me we now use the 4 byte checksum i= n version and no time in the net-addrs in version message. So=C2=A0I solved= that and here is the other doco. I have found other variances like one doc= ument said that the heartbeat AND disconnect were 30 minutes, but then in t= he other document I read that Heartbeat is 30 minutes and disconnect is 90 = minutes which seems far more sensible so I went with that and modified my c= ode. Is there any other variations between these two spec docos=C2=A0that p= erhaps some of you devs know about that I need to look out for! Thanks! Shi= zzle. | =C2=A0 | | =C2=A0 | | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | | Thashiznets/Lego.NETLego.NET - A C# full node for processing the Bitcoin = block chain | | | | View on github.com | Preview by Yahoo | | | | =C2=A0 | =C2=A0 | =C2=A0 | | =C2=A0 | | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | | Developer Reference - BitcoinBETA: This documentation has not been extens= ively reviewed by Bitcoin experts and so likely contains numerous errors. P= lease use the Issue and Edit links on the bot... | | | | View on bitcoin.org | Preview by Yahoo | | | | =C2=A0 | =C2=A0 | =C2=A0 | | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | | Satoshi Client Node Discovery - BitcoinContents 1 Overview 2 Handling Mes= sage "getaddr" 3 Discovery Methods 3.1 Local Client's External Address 3.2 = Connect Callback Address 3.3 IRC Addresses 3.4 DNS Addresses | | | | View on en.bitcoin.it | Preview by Yahoo | | | | =C2=A0 | =C2=A0 =C2=A0 =20 ------=_Part_2420830_2017125422.1424345837138 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Oh and= I realised I stuffed up the subject and it talks about the addr relay but = I actually answered my own question on the addr relaying, I had just miss i= nterpreted one document I thought it was talking about subtracting 2 hours = before relaying but I see we subtract 2 hours on receipt not relay bec= ause the if it hadn't been seen for 60 minutes previously it now becomes 3 = hours and we use but don't relay makes sense.


On Thursday, 19 February 2015, 22:33, Thy Sh= izzle <thashiznets@yahoo.com.au> wrote:


Hi, plugging away a= t my C# Bitcoin node "Lego.NET" = Thashiznets/Lego.NET now I am currently working on addr relaying. I am = as we speak wiring up my DB in Azure, and ready to start plopping net_addrs= in my DB, all good however I'm reading two different specification docs th= at seem to be wildly varying. I mean the first one here Developer Reference - Bitcoin didn= 't mention that version message now has the 4 byte checksum and no tim= e in the net_addrs and I was getting reject malformed messages un= til I found the other document which informed me we now use the 4 byte chec= ksum in version and no time in the net-addrs in version message. So I = solved that and here is the other doco. I have found other variances like o= ne document said that the heartbeat AND disconnect were 30 minutes, but the= n in the other document I read that Heartbeat is 30 minutes and disconnect = is 90 minutes which seems far more sensible so I went with that and modifie= d my code. Is there any other variations between these two spec docos = that perhaps some of you devs know about that I need to look out for! Thank= s! Shizzle.
<= /table>
&nbs= p;
 
 
 
 
 
 
&nb= sp;
Satoshi Client Node Discovery - Bitcoin
View on en.bitco= in.it
Preview by Yahoo
 
 
 


=
------=_Part_2420830_2017125422.1424345837138--