{"type":"rich","version":"1.0","author_name":"npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u","author_url":"https://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-09\n📝 Original message:I've advocated for this in the past, and reasonable counter-arguments I\nwas presented with are: (1) bittorrent is horribly insecure - it would\nbe easy to DoS the initial block download if that were the goal, and (2)\nthere's a reasonable pathway to doing this all in-protocol, so there's\nno reason to introduce external dependencies.\n\nOn 04/09/2014 01:31 PM, slush wrote:\n\u003e Another idea: Integrate torrent download of bootstrap.dat into bitcoind.\n\u003e Normal user (especially a beginner) won't learn how to download\n\u003e bootstrap separately and import it into bitcoind; he simply give up the\n\u003e synchronization once he realize it takes too much time. From my\n\u003e experience downloading the bootstrap significantly improves catching the\n\u003e blockchain, which may attract some more users to run bitcoind.\n\u003e \n\u003e Not sure about C++, but simple torrent client in python is like 30 lines\n\u003e of code (using libtorrent).\n\u003e \n\u003e Marek\n\u003e \n\u003e \n\u003e On Wed, Apr 9, 2014 at 10:12 PM, slush \u003cslush at centrum.cz\n\u003e \u003cmailto:slush at centrum.cz\u003e\u003e wrote:\n\u003e \n\u003e     I believe there're plenty bitcoind instances running, but they don't\n\u003e     have configured port forwarding properly.There's uPNP support in\n\u003e     bitcoind, but it works only on simple setups.\n\u003e \n\u003e     Maybe there're some not yet considered way how to expose these\n\u003e     *existing* instances to Internet, to strenghten the network. Maybe\n\u003e     just self-test indicating the node is not reachable from outside\n\u003e     (together with short howto like in some torrent clients).\n\u003e \n\u003e     These days IPv6 is slowly deploying to server environments, but\n\u003e     maybe there's some simple way how to bundle ipv6 tunnelling into\n\u003e     bitcoind so any instance will become ipv6-reachable automatically?\n\u003e \n\u003e     Maybe there're other ideas how to improve current situation without\n\u003e     needs of reworking the architecture.\n\u003e \n\u003e     Marek\n\u003e \n\u003e \n\u003e     On Wed, Apr 9, 2014 at 9:33 PM, Gregory Maxwell \u003cgmaxwell at gmail.com\n\u003e     \u003cmailto:gmaxwell at gmail.com\u003e\u003e wrote:\n\u003e \n\u003e         On Wed, Apr 9, 2014 at 11:58 AM, Justus Ranvier\n\u003e         \u003cjustusranvier at gmail.com \u003cmailto:justusranvier at gmail.com\u003e\u003e wrote:\n\u003e         \u003e Anyone reading the archives of the list will see about triple the\n\u003e         \u003e number of people independently confirming the resource usage\n\u003e         problem\n\u003e         \u003e than they will see denying it, so I'm not particularly worried.\n\u003e \n\u003e         The list has open membership, there is no particular\n\u003e         qualification or\n\u003e         background required to post here. Optimal use of an information\n\u003e         source\n\u003e         requires critical reading and understanding the limitations of the\n\u003e         medium. Counting comments is usually not a great way to assess\n\u003e         technical considerations on an open public forum.  Doubly so because\n\u003e         those comments were not actually talking about the same thing I am\n\u003e         talking about.\n\u003e \n\u003e         Existing implementations are inefficient in many known ways (and, no\n\u003e         doubt, some unknown ones). This list is about developing\n\u003e         protocol and\n\u003e         implementations including improving their efficiency.  When talking\n\u003e         about incentives the costs you need to consider are the costs of the\n\u003e         best realistic option.  As far as I know there is no doubt from\n\u003e         anyone\n\u003e         technically experienced that under the current network rules full\n\u003e         nodes can be operated with vastly less resources than current\n\u003e         implementations use, it's just a question of the relatively modest\n\u003e         implementation improvements.\n\u003e \n\u003e         When you argue that Bitcoin doesn't have the right incentives (and\n\u003e         thus something??) I retort that the actual resource\n\u003e         _requirements_ are\n\u003e         for the protocol very low. I gave specific example numbers to enable\n\u003e         correction or clarification if I've said something wrong or\n\u003e         controversial. Pointing out that existing implementations are\n\u003e         not that\n\u003e         currently as efficient as the underlying requirements and that some\n\u003e         large number of users do not like the efficiency of existing\n\u003e         implementations doesn't tell me anything I disagree with or didn't\n\u003e         already know. Whats being discussed around here contributes to\n\u003e         prioritizing improvements over the existing implementations.\n\u003e \n\u003e         I hope this clarifies something.\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         _______________________________________________\n\u003e         Bitcoin-development mailing list\n\u003e         Bitcoin-development at lists.sourceforge.net\n\u003e         \u003cmailto:Bitcoin-development at lists.sourceforge.net\u003e\n\u003e         https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e \n\u003e \n\u003e \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 \n\u003e \n\u003e \n\u003e _______________________________________________\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\u003e"}