<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Blobscan</title>
        <link>https://paragraph.com/@blobscan</link>
        <description>A newsletter exploring blob transactions, Ethereum data availability, and the latest updates from the Blobscan project.</description>
        <lastBuildDate>Thu, 19 Nov 2026 04:25:58 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Blobscan</title>
            <url>https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/efa9f480e703856baa6372845109ce0143ba7d1dde85c749d18039a16ec34ea8.jpg</url>
            <link>https://paragraph.com/@blobscan</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Announcing Blobscan’s transition to decentralized blob storage]]></title>
            <link>https://paragraph.com/@blobscan/announcing-transition-to-decentralized-blob-storage</link>
            <guid>zE1Hwhildicorus9Ewkh</guid>
            <pubDate>Fri, 03 Jul 2026 15:45:37 GMT</pubDate>
            <description><![CDATA[Blobscan is evolving toward a fully IPFS-backed blob archive. This update introduces changes to our archival policy across testnets, reduces our reliance on centralized storage, and lays the foundation for a more sustainable, community-driven preservation network. Learn what’s changing, why we’re making these decisions, and how you can help support Ethereum blob preservation.]]></description>
            <content:encoded><![CDATA[<p>Ethereum’s transition to blob-carrying transactions with <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.eip4844.com/">EIP-4844</a> introduced a new class of ephemeral data availability. Since day one, one of Blobscan’s goals has been to preserve this data <strong>beyond Ethereum’s native retention window, ensuring blobs remain accessible long after they disappear from the consensus layer.</strong></p><p>Over the past years, we’ve operated archival infrastructure for Ethereum mainnet, Gnosis and multiple testnets, storing and serving blobs for public access.</p><p>As Ethereum blobs adoption and Blobscan have grown, so have the operational costs of long-term blob retention. At the same time, <strong>we've come to believe that preserving Ethereum's blob history shouldn't depend on a single centralized storage provider.</strong></p><p>Today, we’re announcing the next step in Blobscan’s evolution: <strong>a migration toward a fully IPFS-backed blob archive.</strong></p><p>This migration also comes with some<strong> changes to our storage policy</strong> that will help keep the project sustainable while allowing us to focus our resources where they matter most.</p><h1 id="h-why-were-making-these-changes" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="chart_increasing" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4c8.png" draggable="false" loading="lazy" align="absmiddle"></span> Why we’re making these changes</h1><p>This decision is driven by two factors.</p><p>First, operating long-term blob archives on our current centralized storage provider (Google Cloud) has become increasingly expensive. While storage itself represents a cost,<strong> egress has become one of the largest recurring expenses</strong> of serving public blob data. </p><p><em>We previously wrote about the economics and operational challenges of maintaining Ethereum blob archives in </em><a target="_new" rel="noopener" class="dont-break-out decorated-link" href="https://paragraph.com/@blobscan/blobscan-the-cost-of-archiving-ethereums-blob-data"><em>Blobscan: The Cost of Archiving Ethereum’s Blob Data</em></a></p><p>Second, actual usage patterns are heavily concentrated on Ethereum mainnet. Compared to mainnet, Sepolia and Hoodi receive very little traffic on both the explorer and the API. <strong>By far, the overwhelming majority of Blobscan usage today comes from Ethereum mainnet.</strong></p><p>By reducing infrastructure commitments for low-usage networks, we can continue investing in the infrastructure that provides the most value while ensuring Blobscan remains sustainable for the long term.</p><h1 id="h-changes-to-blob-availability-on-testnets-sepolia-and-hoodi" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="test_tube" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f9ea.png" draggable="false" loading="lazy" align="absmiddle"></span> Changes to blob availability on testnets (Sepolia and Hoodi)</h1><p>Starting <strong>July 3, 2026</strong>, Blobscan will no longer provide <strong>guaranteed archival storage</strong> for the Sepolia and Hoodi networks.</p><p>After this date:</p><ul><li><p><strong>Blobscan will no longer guarantee long-term availability</strong> of Sepolia and Hoodi blobs.</p></li><li><p>Blobs will continue to be stored in our IPFS infrastructure on a <strong>best-effort</strong> basis, but they will <strong>not be pinned</strong> by Blobscan (at least for now).</p></li><li><p>Blob downloads will continue to be available through our IPFS Gateway whenever the data is still present in the cluster.</p></li><li><p><strong>Google Cloud download URLs for all networks are not guaranteed after July 3, 2026.</strong> Blob downloads will progressively transition to our IPFS Gateway, which becomes the canonical way to retrieve blob data.</p></li></ul><p>This <strong>does not</strong> mean we’re dropping support for these networks.</p><p>We will continue running the indexers and maintaining the explorer, analytics, charts, and API for both Sepolia and Hoodi exactly as before. Only the <strong>long-term preservation guarantees</strong> are changing.</p><h1 id="h-roadmap-to-a-fully-ipfs-backed-archive" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="globe_with_meridians" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f310.png" draggable="false" loading="lazy" align="absmiddle"></span> Roadmap to a fully IPFS-backed archive</h1><p>Blobscan is transitioning away from centralized object storage and toward <strong>IPFS as the canonical storage and distribution layer</strong> for Ethereum blob data.</p><h2 id="h-phase-1-ipfs-becomes-the-primary-archive" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Phase 1 — IPFS becomes the primary archive</h2><p>Effective immediately:</p><ul><li><p>Every archived blob is imported into the Blobscan IPFS cluster.</p></li><li><p>Blob pages and the API expose each blob’s <strong>IPFS CID</strong>.</p></li><li><p><strong>Ethereum mainnet blobs are pinned</strong>, ensuring long-term preservation.</p></li><li><p><strong>Sepolia and Hoodi blobs are stored without pinning</strong> and are therefore available on a best-effort basis.</p></li></ul><h2 id="h-phase-2-retiring-google-cloud-downloads" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Phase 2 — Retiring Google Cloud downloads</h2><p>Starting <strong>July 31, 2026</strong>, Blobscan will stop serving blob downloads from Google Cloud.</p><p>From that point onward:</p><ul><li><p>Blob downloads will be served through the <strong>Blobscan IPFS Gateway</strong>.</p></li><li><p>The <strong>IPFS CID becomes the canonical way</strong> to retrieve blob data.</p></li></ul><p>This migration significantly reduces both storage costs and, more importantly, <strong>bandwidth and egress costs</strong>, while removing our dependency on centralized storage providers.</p><h1 id="h-ethereum-mainnet-and-gnosis-remain-fully-supported" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="shield" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f6e1-fe0f.png" draggable="false" loading="lazy" align="absmiddle"></span> Ethereum Mainnet and Gnosis remain fully supported</h1><p>Our commitment to <strong>Ethereum mainnet and Gnosis</strong> is unchanged.</p><p>Every Ethereum mainnet and Gnosis blob archived by Blobscan is:</p><ul><li><p><span data-name="pushpin" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4cc.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Pinned</strong> in the Blobscan IPFS cluster.</p></li><li><p><span data-name="floppy_disk" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4be.png" draggable="false" loading="lazy" align="absmiddle"></span> Replicated across our archival infrastructure.</p></li><li><p><span data-name="link" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f517.png" draggable="false" loading="lazy" align="absmiddle"></span> Accessible through its IPFS CID.</p></li><li><p><span data-name="check_mark_button" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/2705.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Guaranteed</strong> to remain available for long-term retrieval.</p></li></ul><h1 id="h-building-a-community-archive" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="handshake" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f91d.png" draggable="false" loading="lazy" align="absmiddle"></span> Building a community archive</h1><p>Our long-term vision is for blob preservation to become <strong>a decentralized public-good infrastructure</strong> rather than a service operated by a single organization.</p><p>Over the coming months, we’ll continue expanding our IPFS cluster with community-operated nodes, allowing independent operators to contribute storage and replication capacity for Ethereum blob history.</p><p>We’ll publish documentation explaining how anyone can join the network.</p><h1 id="h-looking-ahead" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="crystal_ball" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f52e.png" draggable="false" loading="lazy" align="absmiddle"></span> Looking ahead</h1><p>This migration marks an important milestone for Blobscan.</p><p>Instead of investing in increasingly larger centralized storage systems, we’re investing in <strong>a decentralized preservation network built on IPFS</strong>.</p><p>Our priorities for the coming months are:</p><ul><li><p><span data-name="rocket" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f680.png" draggable="false" loading="lazy" align="absmiddle"></span> Complete the migration to a <strong>fully IPFS-backed archive</strong>.</p></li><li><p><span data-name="earth_africa" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f30d.png" draggable="false" loading="lazy" align="absmiddle"></span> Expand the Blobscan IPFS cluster with community operators.</p></li><li><p><span data-name="bulb" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4a1.png" draggable="false" loading="lazy" align="absmiddle"></span> Explore new<strong> long-term funding models beyond grants.</strong></p></li></ul><h1 id="h-support-blobscan" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><span data-name="heart" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/2764-fe0f.png" draggable="false" loading="lazy" align="absmiddle"></span> Support Blobscan</h1><p>Blobscan has always been built as <strong>open infrastructure for the Ethereum ecosystem</strong>.</p><p>Like many public-good projects, grants alone are <strong>not enough</strong> to ensure long-term sustainability. As those funding opportunities become increasingly limited, community support becomes more important than ever.</p><p>If Blobscan has been useful to you or your organization, you can help us continue preserving Ethereum blob history by supporting the project.</p><p>You can support Blobscan by:</p><ul><li><p><span data-name="purple_heart" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f49c.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Making a donation</strong> on our new <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://qf.giveth.io/project/blobscan">Giveth</a> page.</p></li><li><p><span data-name="earth_africa" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f30d.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Running an IPFS node</strong> once we open participation in the Blobscan IPFS cluster.</p></li><li><p><span data-name="mega" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4e3.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Sharing Blobscan</strong> with developers, researchers, and the broader Ethereum community.</p></li></ul><p><span data-name="folded_hands" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f64f.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Thank you for helping us build a more decentralized and resilient future for Ethereum blob data.</strong></p>]]></content:encoded>
            <author>blobscan@newsletter.paragraph.com (Blobscan developers)</author>
            <category>ethereum</category>
            <category>eip-4844</category>
            <category>ipfs</category>
            <category>data availability</category>
            <category>public goods</category>
        </item>
        <item>
            <title><![CDATA[Blobscan: The Cost of Archiving Ethereum’s Blob Data]]></title>
            <link>https://paragraph.com/@blobscan/blobscan-the-cost-of-archiving-ethereums-blob-data</link>
            <guid>c3JINsf0j8yGzKYeoTjN</guid>
            <pubDate>Sat, 21 Mar 2026 11:07:20 GMT</pubDate>
            <description><![CDATA[A deep dive into the real infrastructure, costs, and sustainability challenges behind preserving blob data long-term.]]></description>
            <content:encoded><![CDATA[<h2 id="h-navigating-sustainability-in-the-current-crypto-landscape" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Navigating Sustainability in the Current Crypto Landscape</strong></h2><p>The current economic environment in the Ethereum ecosystem and the broader crypto landscape has pushed many projects to rethink how they sustain themselves.</p><p>With grants and external funding becoming scarcer—a trajectory <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/VitalikButerin/status/2017145595819933745">also</a> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://vitalik.eth.limo/general/2025/03/29/pubos.html">advocated</a> by Vitalik Buterin—public goods projects like Blobscan must now explore sustainable business models beyond traditional grant funding.</p><p>As Ethereum continues to scale its data availability layer, the infrastructure required to archive and serve blob data is also growing.</p><h2 id="h-increasing-storage-demands-after-ethereum-upgrades" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Increasing Storage Demands After Ethereum Upgrades</h2><p>One of Blobscan's missions is to archive blobs and provide access to the data indefinitely.</p><p><strong>Blobscan preserves blob data beyond the typical retention window used by Ethereum nodes, enabling long-term research, verification, and historical analysis of Ethereum’s data availability layer.</strong></p><p>However, recent Ethereum network upgrades now allow more blobs per block, which naturally increases storage costs for us. Until last year, we were using Google Cloud for both storage and compute. While it served us well, it came with unpredictable costs due to spikes in usage. </p><p>Below is a simplified overview of blob target and maximum values across upgrades that expanded blob capacity:</p><table><colgroup><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1" colwidth="180"><p><strong>Network Upgrade</strong></p></th><th colspan="1" rowspan="1"><p><strong>Blob Target - Blob Max</strong></p></th><th colspan="1" rowspan="1"><p><strong>Mainnet activation date</strong></p></th></tr><tr><td colspan="1" rowspan="1" colwidth="180"><p>Dencun<br>(<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-4844">EIP-4844</a>)</p></td><td colspan="1" rowspan="1"><p>3 - 6</p></td><td colspan="1" rowspan="1"><p>March 13, 2024</p></td></tr><tr><td colspan="1" rowspan="1" colwidth="180"><p>Pectra<br>(<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-7691">EIP-7691</a>)</p></td><td colspan="1" rowspan="1"><p>6 - 9</p></td><td colspan="1" rowspan="1"><p>May 7, 2025</p></td></tr><tr><td colspan="1" rowspan="1" colwidth="180"><p>Fusaka<br>(<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-7594">PeerDAS</a>)</p></td><td colspan="1" rowspan="1"><p>6 - 9</p></td><td colspan="1" rowspan="1"><p>December 3, 2025</p></td></tr><tr><td colspan="1" rowspan="1" colwidth="180"><p>Fusaka (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-8134">BPO1</a>)</p></td><td colspan="1" rowspan="1"><p>10 - 15</p></td><td colspan="1" rowspan="1"><p>December 9, 2025</p></td></tr><tr><td colspan="1" rowspan="1" colwidth="180"><p>Fusaka (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-8135">BPO2</a>)</p></td><td colspan="1" rowspan="1"><p>14 - 21</p></td><td colspan="1" rowspan="1"><p>January 7, 2026</p></td></tr></tbody></table><p>At the current configuration on Ethereum mainnet, we are seeing approximately <strong>30,000–35,000 blobs per day</strong>, which corresponds to roughly 3.8–4.5 GB of data per day—<strong>over 100 GB of new data every month that Blobscan archives for long-term availability.</strong></p><p>This represents a significant and continuously growing dataset that remains accessible over time.</p><p>With Fusaka’s BPO2 parameters, daily blob throughput could increase significantly. Under sustained target conditions, this would translate to approximately:</p><ul><li><p><strong>~12.9 GB per day at target</strong></p></li><li><p><strong>~19.4 GB per day at max capacity</strong></p></li></ul><p>For an archival service like Blobscan, this represents a multiple increase in long-term storage requirements. Every protocol-level increase in blob capacity compounds our infrastructure costs over time.</p><h2 id="h-from-unpredictable-cloud-costs-to-infrastructure-stability" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">From Unpredictable Cloud Costs to Infrastructure Stability</h2><p>For this reason, last year we migrated our infrastructure from Google Cloud virtual machines to a DigitalOcean Kubernetes cluster.</p><p>Since then, our costs have decreased and become much more stable and predictable. This migration significantly reduced infrastructure volatility.</p><p>We also made important API improvements:</p><ul><li><p>Added rate limits</p></li><li><p>Disabled direct blob downloads</p></li></ul><p>Previously, direct downloads caused double egress charges due to a design oversight. This effectively doubled some of our bandwidth costs. Fixing this had a meaningful financial impact.</p><h2 id="h-transparent-breakdown-of-our-monthly-costs" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Transparent Breakdown of Our Monthly Costs</h2><p>To give a clear picture of our monthly expenses:</p><table><colgroup><col><col></colgroup><tbody><tr><td colspan="1" rowspan="1"><p><strong>Service</strong></p></td><td colspan="1" rowspan="1"><p><strong>Approximate USD per month</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>DigitalOcean Kubernetes<br>(5 Blobscan instances)</p></td><td colspan="1" rowspan="1"><p>$400</p></td></tr><tr><td colspan="1" rowspan="1"><p>Google Cloud Storage<br>(data storage and egress)</p></td><td colspan="1" rowspan="1"><p>$250–$400</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sentry</p></td><td colspan="1" rowspan="1"><p>$30</p></td></tr><tr><td colspan="1" rowspan="1"><p>Grafana Cloud</p></td><td colspan="1" rowspan="1"><p>$100</p></td></tr><tr><td colspan="1" rowspan="1"><p>Quicknode</p></td><td colspan="1" rowspan="1"><p>$49</p></td></tr></tbody></table><p>This brings our total monthly operational costs to approximately <strong>$1000</strong>, depending on usage patterns.</p><p>It is important to note that this amount <strong>only covers infrastructure costs</strong>. It does not include any development, maintenance, or operational work on the project itself. At the moment, the funds we have remaining are reserved exclusively for keeping the servers running.</p><p>At our current burn rate, we have roughly <strong>seven months of runway</strong> to continue operating under the existing structure.</p><h1 id="h-decentralizing-storage-of-blobs" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Decentralizing Storage of Blobs</h1><h2 id="h-our-experience-with-decentralized-storage-swarm" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Our Experience with Decentralized Storage: Swarm</h2><p>We experimented with decentralized storage using <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ethswarm.org/">Swarm</a>. Our collaboration worked for some time, but our upload rate requirements were higher than what a single Swarm bee node could sustainably handle.</p><p><em>We want to emphasize that we maintain a positive relationship with the Swarm team and do not place any blame. In fact, we are aware that the Swarm team is actively working on a new solution to handle higher upload rates, which is promising for future collaborations.</em></p><h2 id="h-exploring-ipfs-and-community-powered-storage" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Exploring IPFS and Community-Powered Storage</h2><p>To ensure long-term sustainability, we are exploring hosting blob data on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ipfs.tech/">IPFS</a> using our own dedicated hardware.</p><p><strong>Instead of Blobscan bearing the full archival burden alone, IPFS could allow the Ethereum community to participate in preserving blob data.</strong></p><p>This approach would allow the community to:</p><ul><li><p>Run IPFS nodes</p></li><li><p>Pin our <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ipld.io/">IPLD</a> blob data</p></li><li><p>Distribute storage responsibility</p></li><li><p>Increase resilience and decentralization</p></li></ul><p><strong>By distributing storage responsibilities, even a small number of community-run nodes can help ensure Blobscan’s resilience and long-term sustainability.</strong></p><p>We believe this could transform Blobscan from a centrally hosted service into a truly distributed public infrastructure.</p><h1 id="h-what-comes-next" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What Comes Next</h1><h2 id="h-reducing-scope-to-extend-runway" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Reducing Scope to Extend Runway</h2><p>To further reduce operational costs, we are considering <strong>sunsetting support for the Hoodi and Sepolia testnets.</strong></p><p>Currently, we operate <strong>five Blobscan instances</strong>: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://staging.blobscan.com/">staging</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blobscan.com/">Ethereum mainnet</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://sepolia.blobscan.com/">Sepolia</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://hoodi.blobscan.com/">Hoodi</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://gnosis.blobscan.com/">Gnosis</a>. However, only the Ethereum mainnet instance has meaningful, sustained usage. The remaining instances generate infrastructure and maintenance costs without comparable community activity.</p><p>Focusing our resources on the Ethereum mainnet instance would allow us to reduce operational overhead while preserving the part of Blobscan that provides the most value today.</p><p>These are pragmatic decisions aimed at focusing resources where they have the greatest impact for users while extending the project’s sustainability.</p><p>If there is strong community interest—or if someone offers infrastructure support such as an IPFS cluster—we would gladly explore maintaining these additional networks in a more sustainable way.</p><h2 id="h-new-revenue-experiments" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">New Revenue Experiments</h2><p>In the coming months, we plan to introduce:</p><ul><li><p><strong>API subscription plans</strong></p></li><li><p><strong>Ads and sponsorship opportunities</strong></p></li></ul><p>These initiatives are part of our effort to build a sustainable model while keeping Blobscan accessible to the broader Ethereum community.</p><p>We will experiment carefully, aiming to strike a balance between sustainability and preserving Blobscan’s public good ethos.</p><h1 id="h-a-call-to-the-community" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">A Call to the Community</h1><p>Blobscan was built as public infrastructure for Ethereum.</p><p>Today, the ecosystem is evolving. Grants are fewer. Costs are growing. Sustainability is no longer optional—it is necessary.</p><p>We are committed to adapting responsibly and transparently. But we cannot do it alone.</p><p><strong>Even a small number of community-run nodes pinning blob data could significantly reduce the long-term infrastructure burden on Blobscan.</strong></p><p>If you are:</p><ul><li><p>Interested in running an IPFS node</p></li><li><p>Able to provide storage infrastructure</p></li><li><p>Interested in sponsoring or partnering</p></li><li><p>A builder who depends on Blobscan</p></li></ul><p>We invite you to reach out:</p><p><span data-name="envelope_with_arrow" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4e9.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Email:</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="mailto:contact@blobscan.com">contact@blobscan.com</a><br><span data-name="speech_balloon" class="emoji" data-type="emoji"><img src="https://cdn.jsdelivr.net/npm/emoji-datasource-apple/img/apple/64/1f4ac.png" draggable="false" loading="lazy" align="absmiddle"></span> <strong>Discord:</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blobscan.com/discord">https://blobscan.com/discord</a></p><p>Together, we can ensure that Blobscan remains resilient, decentralized, and sustainable for the long term.</p>]]></content:encoded>
            <author>blobscan@newsletter.paragraph.com (Blobscan developers)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/c117ee6bc59e3a697f6ccca46b4fc742e3b1900e25ddcab77870c2ae56392e3d.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>