From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXEOQ-0001PN-Hi for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 18:35:38 +0000 X-ACL-Warn: Received: from wp059.webpack.hosteurope.de ([80.237.132.66]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WXEOO-0006mL-JF for bitcoin-development@lists.sourceforge.net; Mon, 07 Apr 2014 18:35:38 +0000 Received: from [37.143.74.116] (helo=[192.168.2.2]); authenticated by wp059.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) id 1WXEOH-0004Wx-Qj; Mon, 07 Apr 2014 20:35:29 +0200 Content-Type: multipart/signed; boundary="Apple-Mail=_8712384A-25B6-4EF1-B70B-374CDFE4188D"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Tamas Blummer In-Reply-To: Date: Mon, 7 Apr 2014 20:35:40 +0200 Message-Id: <6D6E55CE-2F04-4C34-BEE6-98AEF1478346@bitsofproof.com> References: <5342C833.5030906@gmail.com> <6D430188-CE00-44B1-BD8C-B623CF04D466@icloudtools.net> To: Mike Hearn X-Mailer: Apple Mail (2.1874) X-bounce-key: webpack.hosteurope.de; tamas@bitsofproof.com; 1396895736; ce2b63e4; X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1WXEOO-0006mL-JF Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Why are we bleeding nodes? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 18:35:38 -0000 --Apple-Mail=_8712384A-25B6-4EF1-B70B-374CDFE4188D Content-Type: multipart/alternative; boundary="Apple-Mail=_68C47828-44F4-40B0-9829-D30929A7CF10" --Apple-Mail=_68C47828-44F4-40B0-9829-D30929A7CF10 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Headers first loading allows the node to run SPV from the very first = minutes and it can converge to full node by time. This is BTW how newest versions of BOP can work. Pruning however disqualifies the node as a source for bootstrapping an = other full node.=20 BTW, did we already agree on the service bits for an archive node? Tamas Blummer http://bitsofproof.com On 07.04.2014, at 20:23, Mike Hearn wrote: > * Sent 456.5 gb data >=20 > At my geographic service location (Singapore), this cost about $90 = last month for bandwidth alone. >=20 > One of the reasons I initiated the (now stalled) PayFile project was = in anticipation of this problem: >=20 > https://github.com/mikehearn/PayFile > http://www.youtube.com/watch?v=3Dr0BXnWlnIi4&feature=3Dyoutu.be >=20 > At some point if you want to actually download and validate the full = block chain from scratch, you will have to start paying for it I'm sure. >=20 > In the meantime: > Getting headers-first implemented and rolled out everywhere would = reduce the amount of redundant downloading and hopefully reduce transmit = traffic network-wide. > Implementing chain pruning would allow people to control upload = bandwidth consumption by reducing the amount of disk storage they allow. >=20 > = --------------------------------------------------------------------------= ---- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment=20 > Start a new project now. Try Jenkins in the cloud. > = http://p.sf.net/sfu/13600_Cloudbees_______________________________________= ________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --Apple-Mail=_68C47828-44F4-40B0-9829-D30929A7CF10 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Headers first loading allows the node to run SPV = from the very first minutes and it can converge to full node by = time.
This is BTW how newest versions of BOP can = work.

Pruning however disqualifies the node as a = source for bootstrapping an other full node. 
BTW, did we = already agree on the service bits for an archive node?


Tamas = Blummer
http://bitsofproof.com

On 07.04.2014, at 20:23, Mike Hearn <mike@plan99.net> wrote:

* Sent 456.5 gb data

At my geographic service location (Singapore), this cost about $90 last = month for bandwidth alone.

One of the = reasons I initiated the (now stalled) PayFile project was in = anticipation of this problem:


At some point if you want to actually download and = validate the full block chain from scratch, you will have to start = paying for it I'm sure.

In the = meantime:
  1. Getting headers-first implemented and rolled out everywhere would = reduce the amount of redundant downloading and hopefully reduce transmit = traffic network-wide.
  2. Implementing chain pruning would allow = people to control upload bandwidth consumption by reducing the amount of = disk storage they allow.

= --------------------------------------------------------------------------= ----
Put Bad Developers to Shame
Dominate Development with Jenkins = Continuous Integration
Continuously Automate Build, Test & = Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_____________________= __________________________
Bitcoin-development mailing = list
Bitcoin-development@lists.sourceforge.net
https://lists.sourcef= orge.net/lists/listinfo/bitcoin-development

= --Apple-Mail=_68C47828-44F4-40B0-9829-D30929A7CF10-- --Apple-Mail=_8712384A-25B6-4EF1-B70B-374CDFE4188D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJTQu/8AAoJEPZykcUXcTkcGqkH/0PiIuPN2+7niWdtrlRMzZcX m4GlEZfm/LU76H6qNw84SNJCDjdYfP212RoZkjnMAGyauNx1f/gkQ0KyhPg9Z3n6 lhJyQJn8hCGvMqNr/pNX6EYHx0PNtBGnSg+qj1wWR/PHgjThVcSha6t62Xh7iqFG cjqa/vHMda+eSsDknEGKQq0cp+H3koFyaMS4aMUsUsqSvKo6yRKqAs3/gaMrOZiB LlAIIN3e+tPhuP1iqaOkC17lTxebFMZkyIaqJgMnsy/7aJebQNghOZ0s18tlObeq hrPhSQj8qpbwbN1M8EtX4+N6LYdI5MNPBp8yv+WUDuPO1wMNo4TkEX03IxyLyPg= =3V2j -----END PGP SIGNATURE----- --Apple-Mail=_8712384A-25B6-4EF1-B70B-374CDFE4188D--