Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <kiwigb@yahoo.com>) id 1Yz3Kz-0005DW-5W for bitcoin-development@lists.sourceforge.net; Sun, 31 May 2015 13:31:37 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of yahoo.com designates 216.109.114.190 as permitted sender) client-ip=216.109.114.190; envelope-from=kiwigb@yahoo.com; helo=nm42-vm3.bullet.mail.bf1.yahoo.com; Received: from nm42-vm3.bullet.mail.bf1.yahoo.com ([216.109.114.190]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yz3Ky-0005UF-D7 for bitcoin-development@lists.sourceforge.net; Sun, 31 May 2015 13:31:37 +0000 Received: from [98.139.215.142] by nm42.bullet.mail.bf1.yahoo.com with NNFMP; 31 May 2015 13:31:31 -0000 Received: from [68.142.230.71] by tm13.bullet.mail.bf1.yahoo.com with NNFMP; 31 May 2015 13:31:31 -0000 Received: from [127.0.0.1] by smtp228.mail.bf1.yahoo.com with NNFMP; 31 May 2015 13:31:30 -0000 X-Yahoo-Newman-Id: 989392.78972.bm@smtp228.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 05Cr_VsVM1k4LkOEyPgapvJrEB2fdobaSexrRiG5jp53baG vjo_e_lH6YnmI6eCEIQrVdAx3l4rn3_YcvVwDoyxoqxvInEoopTc_innlo32 IqZ4OXUK4.YJEBo85M8MKBatagocCmpFHlTGVgd5.j0mVhvjV0neSTgzDcXm Ia4t_7KMG2CfDA_9jVqxFUlswdhHZECQr3BZZCEEONIsTW7Dn04961ZbLunb Zz4Twb93mArqGWWbxCgb2zm1D9cUB4B690qOttJSLJn7QXZbg1sVlYqhhNCN j4CU8deTz.Oi3MJ.8ztkfrmAKu1JUDkWXkDxW6Ovf5AjR_NojZWy.XKVVLDA 8W_Yf3fBDNIjzsCBq8fUQFfALbrWt2Do2NJ7nXEhEKjyDWuagEdLEqZVRQ83 uJPzNf8KhkHsNNBmn2LHrDJ8nz.Exd8.H1bHSgKQ4EpHYSwvN92jd0B2X.i2 nNyJCm74zcgSDZ3aKVuAryJrFm5aMiyUcYLocIVdta.SghtMUifKYiSSStl5 VIsywJCPJywL370egSZKLNejk_Tb9EeWj8EqE X-Yahoo-SMTP: kMAkG6uswBCBwEfDAoIbXivsMA-- Message-ID: <1433079085.5422.10.camel@yahoo.com> From: gb <kiwigb@yahoo.com> To: bitcoin-development@lists.sourceforge.net Date: Mon, 01 Jun 2015 01:31:25 +1200 In-Reply-To: <CABsx9T37jE3AtmUOOuW+emLGTparbS6OozPRL_hCrC+2JEzxgQ@mail.gmail.com> References: <554BE0E1.5030001@bluematt.me> <CAFzgq-xByQ1E_33_m3UpXQFUkGc78HKnA=7XXMshANDuTkNsvA@mail.gmail.com> <CABsx9T0kbRe31LMwk499MQUw225f5GGd67GfhXBezHmDqxkioA@mail.gmail.com> <CAFzgq-z5WCznGhbOexS0XESNGAVauw45ewEV-1eMij7yDT61=Q@mail.gmail.com> <CAFzgq-zTybEQyGz0nq90u5n5JZcJzxQS_XKaTpr5POJi-tHM6A@mail.gmail.com> <CABsx9T37jE3AtmUOOuW+emLGTparbS6OozPRL_hCrC+2JEzxgQ@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 (3.12.11-1.fc21) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kiwigb[at]yahoo.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [216.109.114.190 listed in list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record -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 X-Headers-End: 1Yz3Ky-0005UF-D7 Subject: Re: [Bitcoin-development] [Bulk] Re: Fwd: Block Size Increase Requirements X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Sun, 31 May 2015 13:31:37 -0000 Aren't you calculating bandwidth for a singly-connected node? A "highly connected" miner could have 30-100 node connections so you probably need to increase your traffic estimates by that factor. I.e. For 100MB blocks, 30-100 Mbps and $60-$100 per day data costs. > You should be able to handle 20MB blocks no problem; if I round up to > 100MB per block that works out to 1.3Mbps. > > > We also use Aliyun and Linode cloud services for block > propagation. As of May 2015, the price is 0.13 U.S. dollars > per GB for > 100Mbps connectivity at Aliyun. > > > That speed will handle 20MB blocks no problem. > > > If each 20MB block is 100MB of data up/down the wire (I'm vastly > over-estimating, after optimization it should be 40MB) then you'll be > paying...uhhh: > > > 0.1 GB / block-data-on-wire * 144 blocks/day * 30.5 days/month * 0.13 > $ / GB = $57 > > > Less than $2 per day in bandwidth. > > For a single cross-border TCP > connection, it would be certainly far slower than 12.5 MB/s. > > > That's OK, you'll 1.3Mbps or less > -- > -- > Gavin Andresen > > ------------------------------------------------------------------------------ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development