Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YOPc9-0007u9-RJ for bitcoin-development@lists.sourceforge.net; Thu, 19 Feb 2015 11:49:53 +0000 Received: from nm41-vm4.bullet.mail.gq1.yahoo.com ([67.195.87.91]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YOPc7-0000bq-Ou for bitcoin-development@lists.sourceforge.net; Thu, 19 Feb 2015 11:49:53 +0000 Received: from [127.0.0.1] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 19 Feb 2015 11:36:00 -0000 Received: from [98.137.12.57] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 19 Feb 2015 11:33:14 -0000 Received: from [66.196.81.174] by tm2.bullet.mail.gq1.yahoo.com with NNFMP; 19 Feb 2015 11:33:13 -0000 Received: from [98.139.212.234] by tm20.bullet.mail.bf1.yahoo.com with NNFMP; 19 Feb 2015 11:33:13 -0000 Received: from [127.0.0.1] by omp1043.mail.bf1.yahoo.com with NNFMP; 19 Feb 2015 11:33:13 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 697799.45534.bm@omp1043.mail.bf1.yahoo.com X-YMail-OSG: GRy0sFEVM1nYUN..ebd4JDhkh4l5CxyrRYy.HbgTHTHU_YJHtDJ_VID32V_bAl3 .O5a1Ge2i2oPgFIWkwGo4I2G028CLMlj901Gv4gpLEkGOS.U4z442e1lnP_.I0BFhXS9Wfx7wM_a GpxGeLIseI4xbBAnb_1849rgAUjZjsuqDI.XZ5iV0tYNOze0a9C.pzwyK4gqW5jpUa2Xy_daWJj9 tWjJ5vENmFlADUHqtMj6RMAo.bL.y88tqNUVRCd2V2aZ0LFsNnEidBy9cuxBxHCzV2BrFaellZgb WVv5uLq_0NhAcMYopEogYZJF_3fL9bjJezUmebGReb.bbZjNrinSFATiq.YpWEjb0SK3UwrbDV5j 6.xFYpToA29hK.yJU2si4hU8l5Vpwf0OGHI7K.Nd1SUiYYVly6kjtdyt5m_gvepz2WGFwbthM52c Mbylq545uahF.ZfHKo8HsrEsVqenwwxRBDEgP_8kxvQrykAQOVGLTZceAmrnGLKv2JMHK9xYkuzV jL9KHZhB0JtRXm6nuhonV1fXb2zCNcjDs5aoOfj3d6hB.bhaFwBuvJFr2V.37qp93bKz8I_p3mhV Glp_yMyqj.kgk6UQDxoMNGhdyA6OJvL3xoHjIlJzZ0ETDzy9QrYwpSPJ31lR9_a99rsdW29FWw7T RGTrOVo46pNQjb4jqyfBgmlTNE8MXwsM2XIg_ubMsbwWVpgTp2CShaplcUzMxzOeGDUNbU5BWfJQ yhe3vd2_f2lOaAFy4dXMWkvbEMZnA__LHVg-- Received: by 66.196.80.113; Thu, 19 Feb 2015 11:33:13 +0000 Date: Thu, 19 Feb 2015 11:33:11 +0000 (UTC) From: Thy Shizzle To: "\"bitcoin-development@lists.sourceforge.net\" ; " Message-ID: <904753900.2475114.1424345591935.JavaMail.yahoo@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2475113_1213583842.1424345591924" 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 [67.195.87.91 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: 1YOPc7-0000bq-Ou Subject: [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:49:53 -0000 ------=_Part_2475113_1213583842.1424345591924 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, plugging away at my C# Bitcoin node "Lego.NET" Thashiznets/Lego.NET no= w 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 that seem to be wildly varyin= g. I mean the first one here Developer Reference - Bitcoin=C2=A0didn't ment= ion that version message now has the 4 byte checksum and no=C2=A0time in th= e net_addrs=C2=A0and I was getting reject malformed=C2=A0messages until I f= ound the other document which informed me we now use the 4 byte checksum in= 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 docu= ment said that the heartbeat AND disconnect were 30 minutes, but then in th= e other document I read that Heartbeat is 30 minutes and disconnect is 90 m= inutes which seems far more sensible so I went with that and modified my co= de. Is there any other variations between these two spec docos=C2=A0that pe= rhaps some of you devs know about that I need to look out for! Thanks! Shiz= zle. | =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 ------=_Part_2475113_1213583842.1424345591924 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, plugging away at my C# Bitcoin node "Lego.NET= " Tha= shiznets/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 that = 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 time in the net_addrs and I was getting reject ma= lformed messages until I found the other document which informed me we= now use the 4 byte checksum in version and no time in the net-addrs in ver= sion message. So I solved that and here is the other doco. I have foun= d other variances like one document said that the heartbeat AND disconnect = were 30 minutes, but then in the other document I read that Heartbeat is 30= minutes and disconnect is 90 minutes which seems far more sensible so I we= nt with that and modified my code. Is there any other variations between th= ese two spec docos that perhaps some of you devs know about that I nee= d to look out for! Thanks! Shizzle.
&nb= sp;
 
 
 
------=_Part_2475113_1213583842.1424345591924--