<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[node101: Blockchain Technologies]]></title><description><![CDATA[Insights into blockchain technology, protocols, infrastructure, and emerging innovations.]]></description><link>https://blog.node101.io/s/blockchain-technologies</link><image><url>https://blog.node101.io/img/substack.png</url><title>node101: Blockchain Technologies</title><link>https://blog.node101.io/s/blockchain-technologies</link></image><generator>Substack</generator><lastBuildDate>Sun, 22 Nov 2026 13:04:24 GMT</lastBuildDate><atom:link href="https://blog.node101.io/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[node101 Teknoloji Anonim Şirketi (Inc.)]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[node101@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[node101@substack.com]]></itunes:email><itunes:name><![CDATA[node101]]></itunes:name></itunes:owner><itunes:author><![CDATA[node101]]></itunes:author><googleplay:owner><![CDATA[node101@substack.com]]></googleplay:owner><googleplay:email><![CDATA[node101@substack.com]]></googleplay:email><googleplay:author><![CDATA[node101]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The Access That Never Fails]]></title><description><![CDATA[Is it possible to design a system that will access networks constantly, but will never fail?]]></description><link>https://blog.node101.io/p/the-access-that-never-fails</link><guid isPermaLink="false">https://blog.node101.io/p/the-access-that-never-fails</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 17 Nov 2026 09:06:16 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!TGlm!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!TGlm!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!TGlm!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!TGlm!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:4499119,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/225312923?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!TGlm!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!TGlm!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb850e82c-545d-4a6e-922d-a435e5e4d673_3840x2010.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Blockchains are a part of the novel backbone that will generate the new world: whether you call it x402 or distributed computation, it is clear that the agentic future will require access to distributed networks unlike anything we have seen yet.</p><p>When the requester, the responder and the message itself are known, there is only one variable to discuss: failures. It is great to dream of a world where agents and humans are able to communicate, exchange, trade and share over a network of interoperable blockchains, but how will they handle the frictions of real life? Failures are a natural part of any distributed system, and it is impossible to ignore them.</p><p>Today, as node101, we do not just discuss the problem; we offer the solution to all our clients in our new <strong>Fault Tolerant RPC Gateway</strong> model. By combining conventional and blockchain infrastructure technologies under a single architecture, we enable an RPC model that will never silently serve the wrong information.</p><p></p><h3>Let&#8217;s first understand the problem more</h3><p>If you have never deployed a product on blockchain, you would never know: blockchains are hard to use. Even while you are trying to read simple data, like the token balance of an account, there are major problems you may face:</p><ol><li><p>the RPC you are connecting to may lag behind and fail to give you the information,</p></li><li><p>the RPC may be hacked and serve you the wrong information,</p></li><li><p>the distributed network itself may fail to produce a consistent answer.</p></li></ol><p>Although these scenarios sound very rare and hypothetical, they are not. In times of high demand, such as market downturns, people access the network with much higher throughput than in normal times. A president on the other side of the ocean makes an announcement, and capital rushes to sell or buy what they think will be affected. At such times, access to networks becomes especially complicated, and a few seconds of latency may mean a huge loss of funds. Over the past years, working with exchanges, custodians and banks, we have heard many such stories from real life.</p><p>When you are using a single RPC provider to read all of your blockchain data, this essentially means that your entire access to the blockchain is controlled by a single entity. A few seconds of latency may result in you losing funds, or a single hack of your provider may leave you open to attacks. For instance, just by manipulating your RPC endpoint to serve you an unfinalized TX as settled, a hacker can steal your funds or gain access to a service they did not pay for.</p><p></p><p>All these problems make us wonder whether it is possible to solve them and offer more secure infrastructure to our clients.</p><p></p><h3>What does the solution look like?</h3><p>The first, and correct, answer to the problem is using more than one provider. By accessing multiple, independent RPC endpoints for the same request, you basically distribute your risk. This is a strong idea when working with distributed networks.</p><p>However, for blockchains, this alone is not enough. Having multiple answers does not guarantee the correctness of the result. In cases where some portion of the network is under attack, you may still get the wrong answer depending on your choice of providers.</p><p>Luckily, blockchain has the solution within itself: as a cryptographic protocol, all blockchain data can be verified, at least partially, in a mathematical way. For instance, each downloaded state from Ethereum can be verified with a logarithmic witness to belong to the block header, or in Tendermint-based consensus models, the previous block&#8217;s signatures can be used to verify the next block&#8217;s authenticity.</p><p>Of course, no solution is perfect, but these measures solve the problem in many scenarios.</p><p></p><p>Let me explain how this works in more detail.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!wrQW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!wrQW!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 424w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 848w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 1272w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!wrQW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png" width="1456" height="542" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:542,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:58628,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/225312923?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!wrQW!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 424w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 848w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 1272w, https://substackcdn.com/image/fetch/$s_!wrQW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb5a2aafe-8cf4-45e7-b985-a7a5c2cbbd5f_1600x596.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">The Gateway distributes the request among many providers and combine with cryptography &amp; game theory to maximize the security.</figcaption></figure></div><h3>The Product: Fault Tolerant RPC Gateway</h3><p>As its name suggests, this gateway aims to achieve fault tolerance by placing a gateway in front of multiple RPC providers. The blockchain-specific part is that it uses not only response status codes but also the responses themselves to cryptographically verify and compare results.</p><p>A general request follows these steps:</p><ol><li><p>The request is sent to the Gateway IP, which looks identical to a single RPC for a client.</p></li><li><p>The request is transferred into all, or a few, of the RPC providers. The number of providers to use in each request depends on the nature of the request and the trust model.</p></li><li><p>After each provider generates the response, they send it back to the Gateway.</p></li><li><p>Gateway first verifies each response independently, both their status, but also their cryptographic integrity (does a block match its header?) and logical completeness.</p></li><li><p>Then, Gateway compares each response to each other, and requires at least a majority of the provider to agree on the result.</p></li><li><p>In the cases where security is much more important than speed, Gateway adds a final cryptographic verification through a local, light client. Light client is responsible for verifying the block header and any information that is served in the block. With this step, it becomes almost impossible for the Gateway to serve faulty information.</p></li></ol><p>Read all at once, these steps may feel like too much or seem overcomplicated, so let me explain what each one achieves behind the scenes.</p><p>The first 3 steps are basically what increase the liveness of the Gateway: if you have only a single provider, your best speed, latency and throughput are what that RPC serves you. If you have 3 providers and you need all 3 of them to be available for each request, then you cannot tolerate the failure of any of them, which is not much better either. But if you have 5 providers, and the system only requires 3 of them to respond, then until you lose more than 2 providers, the access is perfect.</p><p>Then, steps 4 and 5 make sure that all providers in the majority are getting the same result, that is, none of them were down or hacked. This majority consensus, especially when implemented with truly independent providers, is quite strong against isolated hacks and incidents.</p><p>At this point, most requests would not need the final, 6th step. In practice, it is rare to encounter a case where the 6th step is required. However, when you are transferring a critical amount or accessing sensitive information, you cannot take the risk, and there is an edge case that none of the steps above handle: in a distributed network, the network itself can be under attack or hacked, and many RPC providers can be serving the same lie unknowingly. In these scenarios, the only solution is to use cryptography. By adding this final step, the Gateway makes sure that wrong information is never served.</p><p>Of course, the light client cannot generate the information itself, so the 6th step can never correct or choose between multiple answers, but it can stop a response and let the app know if the cryptographic verification fails. This is the true power of the Gateway: unlike conventional load-balancing systems, the proxy can stop a request even when all providers agree on the wrong answer.</p><p>The most important point is that not all requests need this. The 6th step is what we call the &#8220;secure track&#8221; of the Gateway, and it is possible to send your requests through the &#8220;fast track&#8221;, which does not require cryptographic verification. By choosing your track, you essentially decide between security and speed.</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!-MS4!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!-MS4!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 424w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 848w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 1272w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!-MS4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png" width="1456" height="648" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:648,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:96801,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/225312923?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!-MS4!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 424w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 848w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 1272w, https://substackcdn.com/image/fetch/$s_!-MS4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb8ed918e-2572-4486-ba1e-05d1400b3810_1600x712.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a><figcaption class="image-caption">Steps of the Gateway&#8217;s execution.</figcaption></figure></div><h3>Current State of the Product</h3><p>After designing each component and identifying gaps, we have combined conventional and blockchain DevOps tools into the first version of our Gateway demo. In a single UI, we enable adding multiple RPC providers, customizing the consensus and verification rules behind them, and configuring a light client for each network. Currently, our demo only supports EVM-based blockchains and Bitcoin.</p><p>Right now, we are testing the product with some of our major institutional clients and making sure the product is ready to be publicly launched. By partnering with cloud providers, we also serve the product in an on-prem, local deployment mode, which further reduces the trust required and optimizes performance.</p><p>If you also want to get early tester access and see the demo with your own eyes, you can always reach us at <a href="mailto:hello@node101.io">hello@node101.io</a>.</p><p></p><p>Before finishing up this article, I want to repeat that no solution is perfect, and there is much to do on the Gateway. Nevertheless, I believe this is a perfect example of why blockchains are advantageous to institutions as well as to users. By using pure cryptography and game theory, it is possible to minimize the trust placed in the system, essentially verifying every piece of data you get before using it.</p><p>And in a world where trust is everything, everything should be verified.</p>]]></content:encoded></item><item><title><![CDATA[Fewer Validators, the Same Network]]></title><description><![CDATA[Fewer validators do not necessarily mean fewer participants.]]></description><link>https://blog.node101.io/p/fewer-validators-the-same-network</link><guid isPermaLink="false">https://blog.node101.io/p/fewer-validators-the-same-network</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 10 Nov 2026 08:06:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!kZ4M!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!kZ4M!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!kZ4M!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 424w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 848w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 1272w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!kZ4M!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png" width="1456" height="763" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:763,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:11105882,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/224269834?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!kZ4M!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 424w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 848w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 1272w, https://substackcdn.com/image/fetch/$s_!kZ4M!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff4952241-b687-4066-a8be-ea219d0570d1_3840x2012.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><br>On the cover of Hobbes&#8217;<a href="https://en.wikipedia.org/wiki/Leviathan_%28Hobbes_book%29"> </a><em><a href="https://en.wikipedia.org/wiki/Leviathan_%28Hobbes_book%29">Leviathan</a></em>, there is a giant king standing over a landscape. At first glance he looks like a single figure, but when we look closer, we see that his body is made of hundreds of small people.</p><p>Ethereum&#8217;s validators are usually seen the other way around. There are close to a million of them, and this number is often used to show how decentralized the network is. Yet, many of these validators are run by the same few companies, on the same servers and by the same teams. So, what looks like a crowd is partly a few large operators divided into small pieces.</p><p>Since<a href="https://ethereum.org/en/roadmap/pectra/"> the Pectra upgrade</a>, these pieces have started to come together again. Operators are merging their validators, and<a href="https://www.datawallet.com/crypto/ethereum-staking-statistics-and-trends"> according to recent data</a>, the number of active validators has dropped from around 975,000 in January to around 868,000 in October. Lido alone expects its operators to merge more than 265,000 validators into about 4,000.</p><p>At first, this sounds like bad news for decentralization but to understand whether it really is, we first need to ask why Ethereum had so many validators in the first place.</p><h2><strong>Why Were There So Many Validators?</strong></h2><p>Until Pectra, Ethereum only counted up to 32 ETH of a validator&#8217;s balance: a validator could hold more, but anything above 32 ETH did not earn rewards and was automatically swept out. So if you wanted to stake more, you had to spin up another validator. That meant a company staking 3.2 million ETH for its clients was not running one validator but 100,000 of them. However, these 100,000 validators were not 100,000 machines, even though this is how most people imagine them. A single validator client can run thousands of validator keys at the same time, so a company like this could be running all of them on a handful of servers, managed by the same team. Though these validators were the same to the company, for the network each of these validators was a separate participant with its own job.</p><p>This job comes back in every epoch, which lasts about 6.4 minutes: each validator signs a vote on which blocks it sees as correct, and this vote has to travel across the network to be checked by the others. Ethereum combines many of these signatures into one to save work, though every new validator still adds a little more to the load.</p><p>In<a href="https://blog.node101.io/p/introduction"> Down the Rabbit Hole</a>, I wrote that the main cost of a blockchain is coordination. Here, the network was verifying 100,000 separate signatures and keeping 100,000 separate records in its state for what was, behind the scenes, a single company running a few machines. It was as if a shareholder splitting his shares into thousands of small accounts and voting separately from each one at every meeting. The result of the vote would be the same in the end, only the meeting would take much longer for everyone, and the longer the meetings get, the harder it becomes to plan anything that needs quick decisions.</p><p>For Ethereum, one of these plans is to finalize blocks within a single slot, which means collecting every validator&#8217;s vote in about 12 seconds, and this is much easier to do with fewer validators.</p><h2><strong>What Pectra Changed</strong></h2><p>With<a href="https://eips.ethereum.org/EIPS/eip-7251"> EIP-7251</a>, Pectra, which went live in May 2025, raised the amount a single validator can hold from 32 ETH up to 2,048 ETH, while small stakers can still join with 32 ETH just as before.</p><p>With this change, large operators can merge their validators. That is, the balance of one validator is moved into another, without leaving the network and waiting in the queue to join again. Rewards also stay inside the validator and grow its balance, instead of being paid out every time it goes above 32 ETH. All of this, however, happens gradually, since only a limited number of merges can go through in each epoch so that the balance of power among validators does not change too quickly.</p><p>Merging brought one more problem with it: when a validator breaks the rules, for example by signing two different blocks for the same slot (<a href="https://www.coinbase.com/developer-platform/discover/insights/double-signing">double signing</a>), its stake gets slashed. Under the old rules, a validator holding 64 times more ETH would also lose 64 times more, and operators would be reluctant to merge. <em>And Pectra lowered this first penalty</em>. Yet, it kept the extra penalty that grows when many validators are slashed at the same time, so operators whose validators fail together are still punished more heavily.</p><h2><strong>So, Is Ethereum Less Decentralized?</strong></h2><p>With this in mind, the decreasing number of validators looks less worrying. Merging does not really move stake into fewer hands, because the stake was already in those hands; it is only easier to see now.</p><p>This is because a validator is closer to an account than to an independent participant. Thousands of validators run by the same company use the same keys, the same servers and the same team, so when something goes wrong with one of them, it goes wrong with all of them.</p><p>This also changes how we should think about risk. One might think that splitting stake into thousands of validators made it safer, but the keys of those validators were usually kept in the same place and under the same security assumptions, so if that place was compromised, all of them were at risk together. The<a href="https://thehackernews.com/2026/10/metamask-security-incident-prompts-exit.html"> MetaMask incident</a> in October showed exactly this: after a security issue in its staking infrastructure, MetaMask took thousands of validators out of the network at once as a precaution. So consolidation does not increase this risk, it only makes it visible. The one difference is in smaller mistakes, such as a misconfigured key migration, which used to hit only some of an operator&#8217;s validators and can now affect its entire stake at once. For those who really want to split the risk, the way is not more validators but<a href="https://ethereum.org/en/staking/dvt/"> Distributed Validator Technology</a> (DVT), where a single validator key is shared across several independent machines and operators.</p><h2><strong>Networks That Took the Other Path</strong></h2><p>Some networks never had this problem. On<a href="https://docs.cosmos.network/main/build/modules/staking"> Cosmos SDK</a> chains, the number of active validators is fixed, usually between one and two hundred, and if you want to stake, you don&#8217;t create a new validator but delegate your tokens to an existing one, which is why this model is often called delegated proof of stake.<a href="https://docs.monad.xyz/monad-arch/consensus/staking"> Monad</a> is an interesting example here, because even though it is an EVM L1 like Ethereum, its staking works much more like Cosmos: only the top 200 validators by stake can be in the active set, each of them needs at least 10 million MON delegated to it, and stake changes take effect at the start of the next epoch, which comes roughly every 5.5 hours. In networks like these, it is easy to see how stake is distributed, and anyone can check how much voting power the top ten validators hold.</p><p>Ethereum chose to stay open instead: anyone with 32 ETH can become a validator, and there is no limit on how many there can be. Merging only brings the number of validators closer to the number of real operators, which is what these networks have shown from the beginning.</p><h2><strong>Conclusion</strong></h2><p>In<a href="https://blog.node101.io/p/children-of-the-prophecy"> Children of the Prophecy</a> and the articles before it, I wrote that blockchain design is about managing constraints, not removing them. Merging validators is a good example of this. Ethereum makes coordination cheaper by having fewer validators, and in return, each of them carries more weight and more responsibility.</p><p>In a way, this brings us back to the cover of <em>Leviathan</em>. The king there looks like a single person until we notice the crowd that makes up his body, and Ethereum&#8217;s validators looked like a crowd until merging showed the few large operators behind them. In both cases, what we see from far away is not enough to tell how many independent parts there really are.</p><p>For years, the number of validators was presented as proof of how decentralized Ethereum is, while it was mostly a result of how the protocol counted stake. Consolidation takes this number away, and leaves us with a more honest question.</p><p>So, if the number of validators no longer tells us how decentralized Ethereum is, what should we be counting instead?</p>]]></content:encoded></item><item><title><![CDATA[The Future of Validators Lies in How Much Trust They Can Create]]></title><description><![CDATA[As margins approach zero, the key factor that will carry validators into the future is the trust they have earned. So, how is trust built?]]></description><link>https://blog.node101.io/p/the-future-of-validators-lies-in</link><guid isPermaLink="false">https://blog.node101.io/p/the-future-of-validators-lies-in</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 27 Oct 2026 12:56:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!J4Co!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!J4Co!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!J4Co!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!J4Co!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2565568,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/222315008?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!J4Co!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 424w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 848w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 1272w, https://substackcdn.com/image/fetch/$s_!J4Co!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8310a5c1-f20a-4cb0-8965-6ad05630c462_1672x941.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>In March 2026, BlackRock, the world&#8217;s largest asset manager, launched its first Ethereum ETF that passes staking rewards on to investors. The product&#8217;s materials named not only the custodian but also the validator operators staking the fund&#8217;s ether (crypto.news 2026). That same month, Visa became one of the Super Validators with the highest voting weigh&#8230;</p>
      <p>
          <a href="https://blog.node101.io/p/the-future-of-validators-lies-in">
              Read more
          </a>
      </p>
   ]]></content:encoded></item><item><title><![CDATA[The Overlooked Advantage of PoS over PoW]]></title><description><![CDATA[Why was PoS invented in the first place, and why should you care?]]></description><link>https://blog.node101.io/p/the-overlooked-advantage-of-pos-over-pow</link><guid isPermaLink="false">https://blog.node101.io/p/the-overlooked-advantage-of-pos-over-pow</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 20 Oct 2026 07:59:30 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!cnKQ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!cnKQ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!cnKQ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 424w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 848w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 1272w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!cnKQ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:8539070,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/221281222?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!cnKQ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 424w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 848w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 1272w, https://substackcdn.com/image/fetch/$s_!cnKQ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F163411aa-63dc-48ac-b295-ecedb9a1d43f_5760x3015.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>Proof of Stake (PoS) is no longer a &#8220;new&#8221; concept, yet I find that people most often confuse the reason why we had it in the first place, and what are some very important advantages of PoS, especially for global adoption of blockchain.</p><p>Thus, in this writing we will take a closer look at the PoS consensus model and its most fundamental component: validators. Starting with the core reason why we had PoS in the first place, we will discover how validators changed with the evolution of this new consensus model and the importance of this change for blockchains.</p><h3>Why did we leave Proof of Work?</h3><p>You can read a lot of arguments on why to use PoS over PoW, such as that it has huge energy consumption or that the computation power is not a very decentralized source of truth. Although these arguments have some truth in them, this is not the biggest advantage of PoS over PoW.</p><p>PoW networks are slow: Take Bitcoin for example; a few minutes per block is not very efficient already, but the real problem is the concept of finality. Before you can be sure that your Bitcoin block is finalized, you need to at least wait a few blocks, so in practice sending BTC to someone takes around an hour. This is exactly the time before Binance accepts your Bitcoin deposit, precisely because they cannot be sure that the money has arrived before this time passes.</p><p>A natural argument is to make these networks faster, for instance by making their block times shorter. For instance, if a Bitcoin block was 12 seconds long, like in Ethereum, then a BTC transfer would take around a minute. Not super fast, but much better than the previous.</p><p>The problem is that the shorter a Bitcoin block becomes, the more blocks you need to actually wait before you can make sure there will not be a fork. So if a Bitcoin block was 12 secs, then we would wait for a much higher number of blocks to avoid a fork, resulting in the same finality time in terms of hours.</p><p>This is not a design issue, but an inherent feature of PoW networks: As the source of finality is outside the network, i.e., we do not know how much computation power is available, we need to give the world some time so that it can communicate this knowledge to us.</p><h3>How does Proof of Stake solve this problem?</h3><p>In Proof of Stake, finality and leader election are done through stake, i.e., amount of coins locked in the network. This amount is always known by the network, so it is an intrinsic property. Thus, the network does not need to wait for knowledge to arrive, and we can even achieve single-block finality and subsecond block time.</p><p>Of course, PoS models have very different security assumptions, and some people argue that this faster speed comes with the cost of a less secure network than PoW. This is not a security paper, so I will not argue this here. For now, let us just focus on what PoS networks need to properly work.</p><p>First of all, we need the tokens on the network, that are controlling the consensus, to be locked. This is the reason why we can avoid forks, since locked tokens can be burned if there is a problem on the network, i.e., slashing. Interestingly, not all PoS models have slashing, but in one way or another they all require this idea of &#8220;unusable tokens&#8221; that are locked to secure the network.</p><p>This makes PoS networks require an incentivization to lock these tokens.</p><h3>Stake rewards and APY</h3><p>Finally, we have come to the financial importance of PoS models, which is the staking rewards. By defining an APY (annual percentage yield), which is what staked tokens earn periodically, the network rewards participants who stake their tokens and participate in the security of the network. Moreover, this APY is usually calculated dynamically: If there are a lot of stakers, APY decreases so that some of them are motivated to liquidate their assets, while if staking ratio is low, APY is increased to incentivize locking coins.</p><p>The emphasis here is that APY is not a security mechanism, but an incentivization over what PoS networks require to be secure. If people had other motivations to stake than financial, like a social reputation system for instance, then APY would not be a requirement, as people would still stake without gaining any tokens.</p><p>Nevertheless, rewards are the most common (or only?) way of incentivization in PoS networks today. And this mechanism has a huge effect on the nodes that are running the blockchain.</p><h3>Validators and their responsibilities</h3><p>Validators are the parties that token holders lock their tokens into, i.e. stake, to receive rewards. It is costly and very hard for regular people to run their own nodes, so they trust validators to operate a node for them, while they lock their tokens in this validator on the network. Validators are incentivized by a small portion of the earnings of the staker, named as the commission. Note that this model is not true for all PoS chains, but a wide-enough generalization.</p><p>Up until here, we have seen that PoS was a solution to the performance problems of PoW, without any financial advantages over it. This new role of validators, that are defined thanks to APY, changes this, and PoS suddenly becomes a much stronger model than PoW in terms of adoption.</p><p>With PoW, all miners need to do is to mine. They can be anonymous, or even hated by the world if they like, but as long as they mine, they are a part of the network. This is not the same with PoS. Validators are staked by people, and their look on people&#8217;s eyes, like their contributions or their performance, matters.</p><p>This is actually a delegated voting model, where each individual delegates their power to secure the network to a validator. If the validator wants this delegation to last, it must actually prove that it is doing a good job, much like governments in democracies: A government can make sure it will be reelected by only keeping the voters happy.</p><h3>Why is this an advantage of PoS over PoW?</h3><p>The observation was simple: If you give people the right to choose, then the chosen entities, that is validators, have the financial incentive to work for the best interests of people.</p><p>This is the reason why PoS can be adopted in the world much faster than PoW. PoS validators have the motivation to work for their network, contribute to the ecosystem. As a validator, we at node101 have been working for the community in many ways in the networks we delegate, such as developing products, organizing events, or educating people. The reason behind these actions was not moral, but purely financial. If we want our delegators to support us, then we need to make sure that we give the best possible service to them and the network.</p><p>On the other hand, this may also be taken as a disadvantage, totally based on your perspective. Public, regulated validators are not like free, unaudited miners. Personally, I find that the only way blockchain will be adopted is through becoming public and recognised in the law, and I find the anonymity of Bitcoin miners as a huge obstacle to Bitcoin becoming a financial payments system instead of digital gold.</p><p>Of course, just because many PoS validators are public and chosen, this does not mean PoS is ultimately better than PoW. There are still a lot of problems to be solved, and a lot of steps to take.</p><h3>Conclusion</h3><p>If you are a validator, probably you already knew about all these here, and not much to change. But if you were just a regular crypto user, then you should take a lesson here.</p><p>With all the tokens you have and you stake, you have power over the network. Of course, you do not need to use this power, and you can just continue with the default validator that your exchange is offering you. Yet, I believe it is nice to know you have an option to choose for something better.</p>]]></content:encoded></item><item><title><![CDATA[The Weight of Keeping Things Running]]></title><description><![CDATA[The Illusion of a Running Node]]></description><link>https://blog.node101.io/p/the-weight-of-keeping-things-running</link><guid isPermaLink="false">https://blog.node101.io/p/the-weight-of-keeping-things-running</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 13 Oct 2026 07:31:08 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!pPQJ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!pPQJ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!pPQJ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 424w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 848w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 1272w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!pPQJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:1920512,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/220116184?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!pPQJ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 424w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 848w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 1272w, https://substackcdn.com/image/fetch/$s_!pPQJ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3ddd4bc0-5a5a-4b8f-8d3d-12385d83cb98_1733x907.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>I still remember running my first blockchain node years ago: it was a Celestia testnet node, and I spent most of my time figuring out how to get it running. Configuring the client, keeping it synchronized, dealing with errors I had never seen before. I was quite happy once it started working, and I suppose most people running their first node would feel the same.</p><p>Things are a bit different when you operate infrastructure that other people actually depend on. An RPC endpoint might respond to every request and still serve outdated information, while a validator might have excellent uptime without revealing much about how its signing keys are managed or what happens if something goes wrong.</p><p>I find this distinction particularly interesting because we tend to judge infrastructure by what we can observe. We see whether a validator is participating in consensus or whether an endpoint is responding within its promised SLA, but much of what determines its reliability happens somewhere else.</p><p>And that&#8217;s what I want to discuss here: the work that goes into operating blockchain infrastructure beyond simply keeping the nodes running, why some familiar engineering practices become more complicated in blockchain, and why <em>I believe that the less visible parts of an operation deserve more attention</em>.</p><h2><strong>When Good Engineering Is Not Enough</strong></h2><p>Blockchain infrastructure relies on much of the same engineering knowledge as any other distributed system, there&#8217;s no reason to pretend otherwise. You still need to understand the operating system, networking, storage, monitoring, and quite a few other things before you can operate anything reliably.</p><p>Yet there are situations where following a perfectly reasonable engineering practice without considering the underlying protocol can cause more trouble than it solves.</p><p>Take redundancy, for example. Running multiple instances of a service is normally a good way to improve availability. But if two validator instances using the same consensus key sign the same block, the validator<em> <a href="https://www.coinbase.com/developer-platform/discover/insights/double-signing">may be slashed</a></em> with some serious financial consequences. The usual approach to avoid a single point of failure suddenly requires a few additional precautions, some of which are very specific to the network you&#8217;re operating.</p><p>Similar challenges exist on the RPC side as well. Keeping an endpoint responsive is one thing, but making sure that the node behind it is synchronized, following the canonical chain, and providing the data a customer needs is another. And if a node loses its peers or ends up following the wrong fork, restarting it might not help much unless you&#8217;ve understood why it got there in the first place.</p><p>None of this means conventional DevOps practices are somehow inadequate for blockchain. On the contrary, they need to be applied with an understanding of what the protocol is doing underneath. Every network has its own assumptions, and even two clients serving the same blockchain can behave quite differently when something goes wrong.</p><h2><strong>Making Reliability a Habit</strong></h2><p>An upgrade is a good example of how much work can sit behind an otherwise ordinary operation. Replacing a binary and restarting a service might take a few minutes. Figuring out whether the release is safe to deploy, whether the database remains compatible, what needs to be backed up, and how to recover if the upgrade fails can take considerably longer.</p><p>Of course, none of these concerns are unique to blockchain! Change management, access control, documentation, and recovery planning have been part of infrastructure engineering for a long time. Still, when an unsuccessful upgrade can interrupt a customer&#8217;s access to blockchain data or affect a validator&#8217;s participation in consensus, it&#8217;s worth being particularly careful about them.</p><p>At node101, quite a lot of our work goes into these less visible parts of the operation. Alongside running validators and RPC services, we&#8217;ve invested time in reviewing our security procedures, improving how changes are managed, and having our operational practices examined externally. Our engineering team has also put considerable effort into areas such as infrastructure architecture, automated deployments, and troubleshooting, which are not necessarily blockchain-specific but are indispensable to operating these services properly.</p><p>I don&#8217;t think this is the kind of work anyone gets particularly excited about from the outside. There&#8217;s not much to announce when an upgrade goes as planned, an access policy does its job, or a recovery procedure turns out to be useful. But <strong>these things matter</strong>, especially when the alternative is finding out during an incident that something was never properly considered.</p><h2><strong>Trust Needs Evidence</strong></h2><p>Something else worth considering is how little information customers or delegators actually have about the infrastructure they rely on.</p><p>If you&#8217;re delegating to a validator, you can look at its uptime, commission, and on-chain performance. If you&#8217;re using an RPC provider, you can measure its latency, throughput, and availability. These are perfectly reasonable things to examine, although I would not say they tell you enough about the operation itself.</p><p>For example, how are the validator&#8217;s signing keys protected? Who has access to production infrastructure? How are incidents handled, and are the recovery procedures ever tested? Unless you have access to the operator&#8217;s internal systems and processes, you probably have no way of answering most of these questions.</p><p>This is partly why independent evaluations are useful. They allow operational practices to be examined against a set of criteria rather than relying entirely on what an operator says about itself. Security controls, internal procedures, infrastructure design, and even the way responsibilities are distributed within a team can all be subject to external scrutiny.</p><p>We&#8217;ve put our own operations through such evaluations at node101, and I consider them useful precisely because they&#8217;re not limited to whether our nodes happen to be performing well. They examine parts of the operation that would otherwise be difficult for someone outside the company to assess.</p><p>Naturally, none of this means an operator cannot fail after passing an assessment. But there is still a meaningful difference between saying that an infrastructure is reliable and being able to show how it is operated.</p><h2><strong>The Work That Never Ends</strong></h2><p>I wouldn&#8217;t say there&#8217;s a particular point at which blockchain infrastructure can be considered completely figured out. Client implementations change, protocols introduce new requirements, and different networks occasionally present problems that don&#8217;t resemble anything you&#8217;ve dealt with before.</p><p>The more interesting question is how operators can maintain a consistent standard of service despite all of this. And there&#8217;s something slightly ironic about it: blockchain is built around the idea that participants shouldn&#8217;t have to trust one another, yet most people accessing a blockchain through an RPC provider or delegating to a validator still know relatively little about the infrastructure they&#8217;re relying on.</p><p>We spend quite a lot of time at node101 thinking about that gap, and I suspect it&#8217;ll become more important as blockchain infrastructure continues to find uses beyond its original audience.</p><p>After all, there&#8217;s a lot more to operating a node than making sure it&#8217;s running.</p>]]></content:encoded></item><item><title><![CDATA[Decentralization for Institutional Trust]]></title><description><![CDATA[How can we actually improve conventional systems with blockchain technology?]]></description><link>https://blog.node101.io/p/decentralization-for-institutional-trust</link><guid isPermaLink="false">https://blog.node101.io/p/decentralization-for-institutional-trust</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 22 Sep 2026 07:03:35 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!wFSV!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!wFSV!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!wFSV!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!wFSV!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:14545415,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/216786498?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!wFSV!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!wFSV!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1122f5f8-54ae-475a-8a77-46b978fb2e9e_3840x2010.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p>Blockchain space has this often confusion, that decentralization should always go besides anarchy and lack of rules. This is not right, and institutional trust has actually a lot to gain from true distribution.</p><p>In this article, I will discuss the importance of a decentralized design in institutional and conventional financial systems.</p><p>TL;DR Decentralization is a tool for institutions, and its adoption is already speeding up with regulations and certifications over validators.</p><h3>What does decentralization actually mean for institutions?</h3><p>In my many articles before, I have given various definitions to decentralization. Although the word has the same meaning in the essence, its capture actually differs fundamentally on use case.</p><p>For institutions, decentralization is the distribution of trust. Instead of trusting a single company, real decentralization allows institutions to distribute their trust over various entities, i.e., validators of the network.</p><p>Let us consider an example: In a normal financial exchange, the entire flow is controlled by a single company, which is bounded by the laws and regulations of a single country. Although this may seem like an advantage at first, this is actually a less superior design to a distributed network. When you take a financial blockchain, like Ethereum, you get distributed trust over validators of the network.</p><p>Validators do not represent a single entity. Each has its own regulations, company, and funding. One validator shutting down does not mean anything for the network as long as the majority of the consensus stays intact.</p><p>This has two important advantages.</p><p>First, this increases security and hardness. Conventional companies can be shut down overnight, and all of us have seen or heard of giant infrastructure companies breaking in an instance. When you are a financial system, trusting on a single hardware provider is a giant risk, and no bank or fund is actually secure enough for you to trust with your entire money. Blockchains are not bound to a single entity, and its security is not in the hands of a single DevOps team.</p><p>Second, the liveness is much higher with distributed systems. You have probably seen the tweet that Ethereum had zero downtime in the past 10 years, while all infrastructure companies, including the biggest ones like Meta or AWS, have suffered from temporary shortages. This is not an implementation problem, but a core architectural advantage that a properly decentralized network cannot be taken down by the failure of a single operator.</p><p>Thus, a true decentralized system is not banks and others trying to escape, but actually to use.</p><h3>But do institutions actually realize this?</h3><p>We can talk about an ideal world here all day long, but the important question is if others actually know about it.</p><p>Luckily yes, and this is the reason why the institutional adoption of blockchain is so rapidly increasing in the past two years despite all of its inconveniences.</p><p>It is not a secret that blockchains are not ready: There are still many technical problems, and their UX is still way worse than any &#8220;normal&#8221; system can offer. Yet, we see that with laws and regulations, all countries adopt the existing blockchains to their systems.</p><p>The real reason behind this is technological advantage. From Swift to J.P. Morgan, major financial institutions are no longer treating blockchain as an experiment. They are building their own infrastructure, launching tokenization platforms, and integrating blockchain-based settlement into conventional financial systems.</p><p>Stablecoins are another strong example. With the GENIUS Act, the United States gave dollar-backed stablecoins a much clearer institutional framework. The important point is not that the U.S. suddenly created a digital dollar, but that regulation helped legitimize a form of digital dollar infrastructure that was already global. By embracing the technology instead of rejecting it, the U.S. strengthened the dollar&#8217;s role in an increasingly digital financial system.</p><h3>And the tech is enough on its own?</h3><p>This is another common mistake. Just because blockchain technology is great on its core, it does not mean that institutions will accept it as it is.</p><p>Blockchain companies, but in particular validators and RPC providers, need to actually satisfy the asks of regulations. This has an extensive coverage, from certification like ISO/IEC 27001 to locally managed servers, validator companies have a lot of rules to satisfy if they want to be a part of this new, decentralized institutional world. </p><p>It is again very important to not confuse decentralization with lack of certification: A validator being regulated or audited does not make them less decentralized, but instead actually proves how secure and strong they are in their services.</p><p>This is also our main motivation with node101, keeping the values and power of decentralization while being a pioneer in the certification of validators. Being blockchain native, it is no excuse to postpone the hard process required to be regulation-compliant.</p><h3>The big takeaway</h3><p>Today, it is not possible to claim blockchain is just useless. It is one of the biggest technological advancements that we have had in finances and many other areas in decades, and it will be used. Not because we push it hard, but because it is better.</p><p>This being said, we should not mistake great technology with great experience. What blockchain is lacking today is not mainly speed or adoption, but order. Law, regulations and certificates are just part of the bigger picture of how blockchain will be integrated into the world of the future.</p>]]></content:encoded></item><item><title><![CDATA[The 21st Century’s Most Important National Currency Innovation]]></title><description><![CDATA[In the 21st century, sovereign currencies will run on blockchains, driving key financial innovations. But how should these foundational systems be designed?]]></description><link>https://blog.node101.io/p/the-21st-centurys-most-important</link><guid isPermaLink="false">https://blog.node101.io/p/the-21st-centurys-most-important</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 15 Sep 2026 15:58:57 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!KIYT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!KIYT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!KIYT!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!KIYT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:5124903,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/215806824?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!KIYT!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!KIYT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe87d6581-3d7d-486d-8361-24825f814e92_3840x2010.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><p><span>Having understood the fundamental threat created by this new era, which I addressed in my previous article, we can outline the hypothesis behind our answer to the question: &#8220;What should we do now?&#8221;</span></p><p><span>Our short answer is: </span><strong><span>The Turkish lira should gain a programmable and strategic monetary infrastructure, issued on a digital-asset foundation built on blockchain technology.</span></strong></p><h2><span>Why would people prefer local deposits when globally accessible, higher-yielding stable-dollar investment pools are available?<br></span></h2><p><span>At node101, we have worked for many years with global actors shaping blockchain technologies. We share the stage with founders, C-level executives, and decision-makers from this ecosystem, and have the opportunity to exchange ideas with them directly in various meetings.</span></p><p><span>For some time, we have been analysing the risks that the new digital-dollar system could create for the rest of the world and for T&#252;rkiye. To test the soundness of these analyses, we ask questions directly of U.S.-based global decision-makers whenever the opportunity arises.</span></p><p><span>At a meeting held earlier this year, I asked </span><strong><span>Tomasz Sta&#324;czak</span></strong><span>, the former director of the Ethereum Foundation, one of the most important institutions in the Ethereum ecosystem, the following question: </span><em><span>In a future where SWIFT can provide every member bank with access to stable dollars through blockchain-based payment infrastructure, and where investors holding stable dollars are offered high yield returns, what becomes of the deposit bases built on local sovereign currencies?</span></em></p><p><span>Sta&#324;czak said that he saw no serious barrier to hyper-dollarisation and believed this process could take place globally through stable dollars and Ethereum.</span></p><p><span>I posed a similar question to </span><strong><span>Jeremy Allaire</span></strong><span>, founder of Circle, the issuer of USDC, one of the most widely used stable dollars in the world today. Allaire stressed that this is not only a financial rupture but also a technological one. He said that Circle visits regional hubs such as Istanbul to explain to public- and private-sector institutions that they need to adapt to these new financial technologies, and that Circle wants to support them through this transition. Otherwise, he said, economies may inevitably be defeated by time and technology.</span></p><p><span>All of this shows us one thing: for global economies, the threat is no longer a distant possibility; it is a near, tangible, and serious reality.<br><br></span></p><p><span>It should not be forgotten that if Turkish-lira deposits weaken, the economic foundation of the Turkish lira weakens as well. If that foundation weakens, financing for roads, bridges, hospitals, restaurants, industrial facilities, and every other kind of local investment comes under greater pressure. T&#252;rkiye should therefore not be merely a follower of the new digital-dollar regime; it should become a conscious, strong, and strategic partner in this transformation.</span></p><h2><span>The Digital Turkish Lira should be part of this new system, not left outside it<br></span></h2><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!6lNs!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!6lNs!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 424w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 848w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 1272w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!6lNs!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png" width="728" height="771.5406698564593" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/aabc2224-8134-43d9-8930-29135c5386a0_836x886.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:false,&quot;imageSize&quot;:&quot;normal&quot;,&quot;height&quot;:886,&quot;width&quot;:836,&quot;resizeWidth&quot;:728,&quot;bytes&quot;:null,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:&quot;center&quot;,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!6lNs!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 424w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 848w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 1272w, https://substackcdn.com/image/fetch/$s_!6lNs!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Faabc2224-8134-43d9-8930-29135c5386a0_836x886.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>This infrastructure should add value not only to T&#252;rkiye&#8217;s economy, but also to its economic relationships with allied and friendly countries in Europe, the Middle East, Africa, and the Far East&#8212;especially its trade relationship with the United States. Within the digital financial architecture of the 21st century, the Turkish lira should be positioned not merely as a local currency to be protected, but as a strategic instrument that gives T&#252;rkiye new political power at the level of monetary policy.<br><br>A blockchain-based Digital Turkish Lira infrastructure could give the Turkish lira a true technological foundation for circulation and settlement for the first time. In this respect, it is a candidate to become one of T&#252;rkiye&#8217;s most important technical infrastructure projects of the 21st century. It should be designed as an infrastructure that meets the needs of both the public and private sectors and, through its programmable structure, enables the development of new financial products, derivative instruments, and digital assets.</span></p><p><span>This system should be accessible while also being manageable, when necessary, in a manner compatible with Ankara&#8217;s supervisory and oversight capacity. It should be designed to facilitate the flow of external resources into T&#252;rkiye and to establish a secure bridge between the Turkish lira and global digital-asset markets.</span></p><p><span>The Turkish lira should have a strong presence on a network where stable dollars, stable euros, tokenised real estate on the Arabian Peninsula, tokenised Russian gas, Chinese goods, and similar real-world assets can be settled. With an economy approaching $1.5 trillion, a population nearing 90 million, a strong military, and institutional capacity, T&#252;rkiye can become a centre that inspires </span><strong><span>confidence</span></strong><span> in this new digital financial order.</span></p><p><span>Such an infrastructure could be a powerful tool not only for economic growth, but also for combating money laundering, terrorist financing, unregistered money transfers, and illicit capital movements. The supervisory capacity of institutions such as MASAK, the CMB, and the BRSA could become more effective internationally through blockchain-based transparency and traceability. The blacklists, risk lists, and compliance mechanisms established by T&#252;rkiye could gain the capacity to produce results not only locally, but also regionally and globally.</span></p><p><span>In a world where east-west and north-south trade is increasingly conducted through digital assets, T&#252;rkiye should not be merely an observer of these flows. The Turkish lira, Turkish assets, and T&#252;rkiye&#8217;s financial institutions should become active participants in this new network economy.</span></p><h2><strong><span>A New Economic Network for the Turkish Lira</span></strong></h2><p><span>The Digital Turkish Lira is not merely a digital representation of money; it should be a strategic infrastructure choice that determines T&#252;rkiye&#8217;s place in the new global financial architecture. The aim is to move the Turkish lira beyond being a currency that remains on the defensive in the face of technology, and place it at the centre of an economic network with growing circulation, use cases, and international reach.</span></p><p><span>This transformation should be approached with a strong legal framework, security, privacy, financial stability, and the principles of public oversight in mind. If designed correctly, the Digital Turkish Lira can help T&#252;rkiye protect its financial sovereignty while building stronger connections with global capital, trade, and digital-asset markets.</span></p><p><span>In my next article, I will examine the use cases that make this infrastructure&#8217;s economic contribution concrete: the areas in which the Digital Turkish Lira can create value, from foreign trade and cross-border payments to export finance, from tokenised assets to public payments, and from SMEs&#8217; access to finance to next-generation capital markets. The real question is not whether this technology will arrive, but what role T&#252;rkiye will assume in it.</span></p>]]></content:encoded></item><item><title><![CDATA[Pruning in Blockchains: Who Keeps the Past?]]></title><description><![CDATA[A blockchain can preserve its history without every node preserving its past.]]></description><link>https://blog.node101.io/p/pruning-in-blockchains-who-keeps</link><guid isPermaLink="false">https://blog.node101.io/p/pruning-in-blockchains-who-keeps</guid><dc:creator><![CDATA[node101]]></dc:creator><pubDate>Tue, 01 Sep 2026 07:34:43 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!YUo_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!YUo_!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!YUo_!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!YUo_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png" width="1456" height="762" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:762,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:7339141,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.node101.io/i/213669215?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!YUo_!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 424w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 848w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 1272w, https://substackcdn.com/image/fetch/$s_!YUo_!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0366b59-9fcf-4c4e-ab97-47796f1ad356_3840x2010.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>In the <a href="https://substack.com/@yakupaltay"><span>series of articles</span></a><span> I&#8217;ve been writing since the beginning of the year, we have always focused on where a blockchain is headed: the block production mechanisms, consensus, peer-to-peer latency, etc. However, for this article, I want to go back to something much simpler and rather </span><strong><span>old</span></strong><span>: the first blocks of a blockchain.</span></p><p><span>Like everything else, a blockchain has a beginning: a first block, or a genesis block, so to say. Then another block gets added to it, and another. In time transactions modify balances, contracts change their states, and the network gradually builds a history of everything that has happened since its beginning. At first, keeping this history is not much of a concern because there is simply not that much to keep.</span></p><p><span>The situation becomes different after years of operation as the blockchain may have produced millions of blocks and processed billions of transactions, while every new block continues adding more information to what was already there. We usually consider this history permanent because once a block becomes part of the canonical chain, changing what happened becomes increasingly difficult.</span></p><p><span>Bitcoin is a good example of how physical this problem eventually becomes. Today, synchronizing Bitcoin Core requires downloading more than </span><strong><span>740 GB</span></strong><span> of blockchain data. Ethereum is more complicated because of its changing state: depending on </span><a href="https://ethereum.org/developers/docs/nodes-and-clients/"><span>the client</span></a><span> and the type of historical state being retained, an archive node can require </span><strong><span>multiple terabytes</span></strong><span> of storage, with some implementations requiring considerably more than others.</span></p><p><span>However, the machines storing this history do not grow together with the blockchain. Storage is limited and expensive, while the chain is expected to continue growing indefinitely. At some point, node operators therefore have to make a decision: </span><em><span>how much of the past do they actually need to keep in order to follow the present?</span></em></p><h3>Leaving the Earlier Blocks Behind</h3><p><span>A node synchronized with the tip of a blockchain does not necessarily need every previous version of its state to continue running. What matters for most of its daily operation is the current state and the information required to verify the blocks that come next. And at this point, node operators make use of something called </span><strong><span>pruning</span></strong><span>. Instead of keeping all historical information indefinitely, a node can remove data that is no longer required for its operation of adding new blocks to the blockchain. Depending on the blockchain and the way the node is configured, this can significantly reduce storage requirements without preventing it from remaining synchronized with the network.</span></p><p><span>How aggressively this can be done also depends on the architecture of the blockchain. Bitcoin Core, for example, can reduce its storage requirement from hundreds of gigabytes to only a few gigabytes in pruning mode while still validating the blockchain. In Cosmos SDK chains, operators can go even further with historical state: the software can be configured to retain only two-to-three blocks.</span></p><p><span>Nevertheless </span><strong><span>pruning does not make the current consensus less secure</span></strong><span>. A properly configured pruned node does not become a weaker participant simply because it cannot answer a query about the state from several years ago. It can still verify the information required by the protocol and follow the current chain with the same consensus rules.</span></p><p><span>All in all, from the perspective of a node operator, the decision is understandable. The blockchain grows continuously but hardware does not and keeping information that is rarely queried comes with a real and high cost. The node therefore follows the chain towards its tip and gradually leaves some of the earlier state behind.</span></p><p><span>But this creates another question: what happens when </span><em><span>we want to go back</span></em><span>?</span></p><h3><span>What Happened Five Years Ago?</span></h3><p><span>Suppose we want to understand exactly what the blockchain looked like at a particular block five years ago. This is not necessarily an unusual request. Financial records may remain legally relevant for years, an old transaction may become part of a court case, or an application may need to prove what a particular account or contract looked like at the time an agreement was executed. In such cases, knowing the current state is simply not enough. We may need to inspect an account balance, the value of a contract, or some other part of the state exactly as it existed when that block was produced.</span></p><p><span>Thousands of nodes might have received and verified that block at the time. Yet, years later, many of those same nodes may no longer be able to answer our question. They can be perfectly healthy, synchronized with the latest block and independently verifying the network while no longer keeping the historical state we are looking for.</span></p><p><span>Here, we need to distinguish between a few concepts that are usually put together when we describe blockchains as permanent: </span><strong><span>immutability</span></strong><span>,</span><strong><span> availability</span></strong><span>,</span><strong><span> </span></strong><span>and </span><strong><span>verifiability</span></strong><span>.</span></p><p><span>Blocks and states are connected through cryptographic commitments. Merkle-based structures, for example, allow enormous amounts of blockchain state to be represented by a relatively small root commitment. This means that even if we do not store the historical state ourselves, someone who preserved it can later provide us with a particular piece of information together with the necessary proof. We can then check that proof against the commitment preserved by the blockchain and verify whether the information really belonged to that historical state. In other words, we may depend on someone else to </span><strong><span>provide</span></strong><span> the old data, but we do not necessarily have to </span><strong><span>trust</span></strong><span> them about what that data contains.</span></p><p><span>However, a commitment to information and the information itself are different things. Let&#8217;s say if I give you a file together with its hash: you can verify whether the file is the one I originally committed to. If every copy of the file disappears and only its hash remains, however, the hash cannot recreate the file.</span></p><p><span>This distinction applies to blockchain history too. Cryptography can allow us to verify historical information once we obtain it, but cryptography cannot make unavailable information available.</span></p><p><span>In other words,</span><em><span> </span><strong><span>immutability does not automatically imply availability</span></strong></em><span>.</span></p><h3>Who Keeps the Past?</h3><p><span>Of course, historical blockchain data does not normally disappear simply because ordinary nodes prune it. There are archive nodes specifically maintained to preserve historical state, while indexers, explorers and RPC providers make different parts of that history accessible to applications and users.</span></p><p><span>But this changes the decentralization problem in an interesting way. There may be thousands of nodes capable of independently verifying what happens on a blockchain today, while only a much smaller number of machines can answer what an account looked like five years ago. Those archive operators cannot simply invent another historical state and convince us that it is legitimate thanks to the cryptographic commitments.</span></p><p><em><span>They can, however, choose not to provide it at all.</span></em></p><p><span>This means that </span><strong><span>historical integrity and historical availability have different security models</span></strong><span>. Consensus and cryptography protect us against someone changing the past, while access to that past still depends on someone continuing to store and serve it. In that sense, the older parts of a blockchain can gradually become more centralized in their </span><em><span>availability</span></em><span> even though they do not become more centralized in their </span><em><span>truth</span></em><span>.</span></p><p><span>This is not necessarily a problem. Requiring every node to preserve every historical state forever would mean that the hardware requirement for participating in a blockchain would continuously increase simply because the network survived another year. After decades, operating an ordinary node could require storing an enormous amount of information that has almost no relevance to current consensus. Therefore, for a blockchain expected to operate indefinitely, some form of forgetting is almost unavoidable.</span></p><h3>Conclusion</h3><p><span>We often treat permanence as if it were one property of a blockchain, but it is actually the result of several different guarantees. A blockchain can make its history extremely difficult to modify without requiring every participant to preserve every historical state forever.</span></p><p><span>If every node were required to carry everything the network had ever known, the cost of participating would increase indefinitely with the age of the blockchain. Pruning prevents this by allowing the majority of nodes to concentrate on verifying the present while a smaller part of the infrastructure preserves the past.</span></p><p><span>This creates a trade-off that is easy to overlook. As history gets larger, its integrity can remain protected by the blockchain while its availability becomes dependent on fewer participants. And those participants cannot easily lie about what happened but they may eventually become the only ones left who can show us.</span></p><p><span>Then, the question becomes not whether a blockchain can preserve its history forever, but </span><strong><span>who will still be there to provide it when we want to look back?</span></strong></p>]]></content:encoded></item></channel></rss>