<?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>zksurvivors</title>
        <link>https://paragraph.com/@zksurvivors</link>
        <description>Introducing zkSurvivors – where rarity meets resilience in the world of NFTs</description>
        <lastBuildDate>Tue, 04 Aug 2026 09:07:40 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>zksurvivors</title>
            <url>https://storage.googleapis.com/papyrus_images/c3fc713f4cec6968b2d17e19bdb618cf4939946080b2666968df17af64443d53.png</url>
            <link>https://paragraph.com/@zksurvivors</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Lets Study]]></title>
            <link>https://paragraph.com/@zksurvivors/lets-study</link>
            <guid>SoFR6t5AcVvwTWpd2vRb</guid>
            <pubDate>Tue, 28 May 2024 13:15:58 GMT</pubDate>
            <description><![CDATA[1/ The L2 landscape has changed a ton over the past few years. I definitely didn&apos;t use to have to scroll down on #l2beat . I also know it is not easy to understand the differences between these systems. While I have a coffee, here is a TL;DR on what we&apos;re building #zksync . 2/ This space is complex, and even for developers working inside the Ethereum ecosystem I *know* it isn&apos;t easy to understand the differences between rollup projects. You then mix in hype/marketing and it can...]]></description>
            <content:encoded><![CDATA[<p>1/ The L2 landscape has changed a ton over the past few years. I definitely didn&apos;t use to have to scroll down on #l2beat .</p><p>I also know it is not easy to understand the differences between these systems. While I have a coffee, here is a TL;DR on what we&apos;re building #zksync .</p><p>2/ This space is complex, and even for developers working inside the Ethereum ecosystem I *know* it isn&apos;t easy to understand the differences between rollup projects. You then mix in hype/marketing and it can be difficult to see the signal from the noise.</p><p>3/ Optimistic vs ZK is still not well understood, let alone the more exotic creatures in the blockchain zoo (optimiums, volitions, validiums). I&apos;ll try and keep this as simple as I can, because this system is genuinely really exciting and I want people to understand better.</p><p>4/ The vision is a system that is the infra under an application layer that adds value to the lives of billions of people. Applications that make people&apos;s lives better, much like the internet today, but supercharged because of what blockchains can add for value and ownership.</p><p>5/ To realize this vision, it is obvious to me that this system needs to scale like the internet. Engineers call this &quot;horizontally&quot; - essentially we can just add hardware and expand the network. We need to do this with no compromises.</p><p>6/ This is why ZK is a superpower. You can prove the correctness of a huge system that performed a ton of computational work with a tiny proof that can be verified on any smartphone. This is why ZK systems can scale horizontally (sensibly), and optimistic systems can&apos;t.</p><p>7/ To offer a bit more context, this horizontal scalability really just means: deploy more rollups into this protocol layer. They can be app specific, or general, but all of this can be abstracted away from the end users. Here is a really scientific image that hopefully helps:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/b3bad0af98c35a728be0b7d7a540a0952eaf86afccb26e9c8a30c304b4980eea.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>8/ At the protocol layer, these systems all need to trustlessly interact. If they don&apos;t, the entire user experience is fragmented (just as today it feels fragmented when interacting with different L2s, or L1s for that matter).</p><p>9/ Optimistic systems can&apos;t implement this interaction properly.</p><p>The options are basically:</p><ul><li><p>wait 7 days for the interaction (the challenge period)</p></li><li><p>every L2 to run a full node for every L2 any of its users want to interact with</p></li><li><p>use a middleman, who charges users.</p></li></ul><p>All bad.</p><p>10/ Using ZK lets these systems interact trustlessly, any rollup to any rollup. They can just interact and _know_ that the state of the other system is correct. The math proves it.</p><p>11/ Users won&apos;t even need to know where the game they are playing is hosted, or which rollup their friend is using when they want to send them $20 for lunch. They shouldn&apos;t need to know.</p><p>12/ Optimistic rollups also need to post all of their transaction inputs to the L1, because ... this is how they work! The data is needed to resolve a potential challenge to the state transition. At the scale we&apos;re talking, this is a huge amount of data.</p><p>13/ ZK systems also don&apos;t have this problem. You can prove the correctness of the system without posting all the state to L1 (you can post somewhere else, or build a private system). This is a validium. You know it is correct, but you don&apos;t have the state on Ethereum.</p><p>14/ Did I mention that proofs can be combined across the whole zksync ecosystem, and you could verify the _entire_ network in a single proof? This means the onchain costs trend to zero as the system scales. Oh and you can verify it on any smartphone.</p><p>15/ The system we&apos;re building zksync is highly scalable, highly performant, highly secure, and completely different to some of these other systems that are unfortunately all lumped together as &quot;L2s&quot;. These things are not the same. Many will be gone one year from now.</p><p>16/ The ecosystem will be made up of many ZK chains, often configured differently to match specific use-cases, but with the same strong security guarantees and fast, trustless interop.</p><p>17/ Anyone will be able to permissionlessly deploy a new ZK chain into the ecosystem, and interact across the network instantly.</p><p>18/ There is a huge amount more to say, but I&apos;ve finished that coffee and this is the key intuition I wanted to share today. This is why I&apos;m excited about #zksync , why ZK systems really will change the world, and why ZK is the endgame.</p><p>19/ Please send questions if things aren&apos;t clear. I plan to add more context soon about the v24 upgrade (which is related to this &quot;shared bridge&quot; in my beautiful picture above).</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/edb75417608842fa1c960dbdb9df079dc0ef25380b2cc39cda0f165f954065a0.webp" alt="ZK IS THE END GAME" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">ZK IS THE END GAME</figcaption></figure>]]></content:encoded>
            <author>zksurvivors@newsletter.paragraph.com (zksurvivors)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/069c277169152ed82901c7cd2a7c5a1a818296fbfa4e2bcba30e760fbfb69bce.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>