📅 Original date posted:2014-04-07 📝 Original message:Headers first loading ...

Tamas Blummer [ARCHIVE] /

npub1cce…x8m8

2023-06-07 15:17:39

in reply to nevent1q…uhj4

📅 Original date posted:2014-04-07
📝 Original message: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 at 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:
>
> https://github.com/mikehearn/PayFile
> http://www.youtube.com/watch?v=r0BXnWlnIi4&feature=youtu.be
>
> 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:
> 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.
>
> ------------------------------------------------------------------------------
> 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/3bc77bbe/attachment.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/3bc77bbe/attachment.sig>;

Author Public Key

npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8

Show more details

Published at

2023-06-07 15:17:39

Kind type

1 Short Text Note

Event JSON

{ "id": "75af958e42b3f40ef3d3db43839cec04c5afd40c29c37a11311b153e90f720b1", "pubkey": "c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7", "created_at": 1686151059, "kind": 1, "tags": [ [ "e", "376923b22263ee9091876d1ae02202112b3aeaa7a25d30e967b871af6956d76a", "", "root" ], [ "e", "9ad9d874d049ba8402c72b4b7e2474256bf2d2263a3d6dc8d32ef8d4e4673c11", "", "reply" ], [ "p", "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2" ] ], "content": "📅 Original date posted:2014-04-07\n📝 Original message:Headers first loading allows the node to run SPV from the very first minutes and it can converge to full node by time.\nThis is BTW how newest versions of BOP can work.\n\nPruning however disqualifies the node as a source for bootstrapping an other full node. \nBTW, did we already agree on the service bits for an archive node?\n\n\nTamas Blummer\nhttp://bitsofproof.com\n\nOn 07.04.2014, at 20:23, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\n\u003e * Sent 456.5 gb data\n\u003e \n\u003e At my geographic service location (Singapore), this cost about $90 last month for bandwidth alone.\n\u003e \n\u003e One of the reasons I initiated the (now stalled) PayFile project was in anticipation of this problem:\n\u003e \n\u003e https://github.com/mikehearn/PayFile\n\u003e http://www.youtube.com/watch?v=r0BXnWlnIi4\u0026feature=youtu.be\n\u003e \n\u003e 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.\n\u003e \n\u003e In the meantime:\n\u003e Getting headers-first implemented and rolled out everywhere would reduce the amount of redundant downloading and hopefully reduce transmit traffic network-wide.\n\u003e Implementing chain pruning would allow people to control upload bandwidth consumption by reducing the amount of disk storage they allow.\n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment \n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees_______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/3bc77bbe/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 495 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/3bc77bbe/attachment.sig\u003e", "sig": "1ab06acf0f01eeeb129a11289867d58796b25af10a28b08bb9e2c308aa6f9b775c945d2dca9c0783f86b156253255f31e931e3a359de70f1ab5f75db8219d083" }