<oembed><type>rich</type><version>1.0</version><author_name>npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_name><author_url>https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-07-23&#xA;📝 Original message:On Thu, Jul 23, 2015 at 9:52 PM, Jameson Lopp via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; Running a node certainly has real-world costs that shouldn&#39;t be ignored.&#xA;&gt; There are plenty of advocates who argue that Bitcoin should strive to keep&#xA;&gt; it feasible for the average user to run their own node (as opposed to&#xA;&gt; Satoshi&#39;s vision of beefy servers in data centers.) My impression is that&#xA;&gt; even most of these advocates agree that it will be acceptable to eventually&#xA;&gt; increase block sizes as resources become faster and cheaper because it won&#39;t&#xA;&gt; be &#39;pricing out&#39; the average user from running their own node. If this is&#xA;&gt; the case, it seems to me that we have a problem given that there is no&#xA;&gt; established baseline for the acceptable performance / hardware cost&#xA;&gt; requirements to run a node. I&#39;d really like to see further clarification&#xA;&gt; from these advocates around the acceptable cost of running a node and how we&#xA;&gt; can measure the global reduction in hardware and bandwidth costs in order to&#xA;&gt; establish a baseline that we can use to justify additional resource usage by&#xA;&gt; nodes.&#xA;&#xA;Although I don&#39;t have a concrete proposals myself, I agree that&#xA;without having any common notion of what the &#34;minimal target hardware&#34;&#xA;looks like, it is very difficult to discuss other things that depend&#xA;on that.&#xA;If there&#39;s data that shows that a 100 usd raspberry pi with a 1 MB&#xA;connection in say, India (I actually have no idea about internet&#xA;speeds there) size X is a viable full node, then I don&#39;t think anybody&#xA;can reasonably oppose to rising the block size to X, and such a&#xA;hardfork can perfectly be uncontroversial.&#xA;I&#39;m exaggerating ultra-low specifications, but it&#39;s just an example to&#xA;illustrate your point.&#xA;There was a thread about formalizing such &#34;minimum hardware&#xA;requirements&#34;, but I think the discussion simply finished there:&#xA;- Let&#39;s do this&#xA;- Yeah, let&#39;s do it&#xA;- +1, let&#39;s have concrete values, I generally agree.</html></oembed>