<?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:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Catalysis on Medium]]></title>
        <description><![CDATA[Stories by Catalysis on Medium]]></description>
        <link>https://medium.com/@catalysis?source=rss-cc12847abb92------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kOieWo0UwjxpIMDABxj_Zw.png</url>
            <title>Stories by Catalysis on Medium</title>
            <link>https://medium.com/@catalysis?source=rss-cc12847abb92------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 07 Apr 2026 14:43:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@catalysis/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Catalysis and Kernel: Building the Foundation for 1000 DVNs]]></title>
            <link>https://catalysis.medium.com/catalysis-and-kernel-building-the-foundation-for-1000-dvns-116bd514161a?source=rss-cc12847abb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/116bd514161a</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[restaking]]></category>
            <category><![CDATA[binance-smart-chain]]></category>
            <category><![CDATA[bnb]]></category>
            <category><![CDATA[bsc]]></category>
            <dc:creator><![CDATA[Catalysis]]></dc:creator>
            <pubDate>Thu, 27 Feb 2025 13:04:33 GMT</pubDate>
            <atom:updated>2025-02-27T13:04:33.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mUH-3qXhSPaw_l1lhCwJqw.jpeg" /></figure><p>Blockchain security has always been defined by economic weight — the more assets securing a network, the harder it is to attack. Restaking expands this concept, allowing staked assets to secure multiple decentralized services simultaneously. This shift fundamentally transforms how we think about blockchain security while creating a market for trust.</p><p>No longer must each protocol bootstrap its own validator set from scratch. No longer must billions in staked assets sit idle, securing just one network.</p><p>Restaking has unlocked over <a href="https://dune.com/blocklytics/ethereum-restaking">$19B</a> in capital for onchain security — <strong><em>but accessing and deploying this capital remains a multifaceted challenge, involving engineering complexities, market fragmentation, and economic design.</em></strong></p><p>This is where Catalysis and Kernel step in. By combining Kernel’s robust DVN (dynamic validation network) infrastructure with Catalysis’s unified security layer, we’re creating something novel: <strong><em>a world where teams can build universal decentralized networks that can source security from the BNB chain, operate across multiple restaking ecosystems, and scale without friction.</em></strong></p><p>Think of it as the <strong><em>‘Shopify moment’</em></strong> for decentralized services — where what once required months of specialized infrastructure can now be deployed in days.</p><p><em>To understand how we’re making this possible, let’s look at the unique capabilities each protocol brings to the table.</em></p><h3>Introducing Catalysis Network and Kernel</h3><h3>Catalysis Network</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_jz0aNhHVfkf8u2x" /></figure><p><a href="https://catalysis.network/">Catalysis</a> is the first true abstraction layer for shared security. It enables decentralized networks (DVNs, AVSs, BVSs) to dynamically source and rebalance security across <a href="https://kerneldao.com/">Kernel</a>, <a href="https://www.eigenlayer.xyz/">Eigenlayer</a>, <a href="https://symbiotic.fi/">Symbiotic</a>, <a href="https://satlayer.xyz/">SatLayer</a>, and more — without requiring teams to integrate separately with each protocol.</p><h3>KernelDAO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XTKpkAnDs5jukIlS" /></figure><p><a href="https://kerneldao.com/">KernelDAO</a> is a top restaking protocol, with over $2 billion total value locked and live on 10+ chains including Ethereum, BNB Chain, Arbitrum, Optimism, and expanding further. Kernel powers off-chain validation and execution networks through its pioneering Dynamic Validation Network (DVN) architecture. Instead of DVNs needing to manage their own validator coordination and slashing mechanisms, Kernel provides an on-demand, trust-minimized network of operators who handle execution tasks reliably.</p><p>Together, we’re tackling both sides of the restaking equation:</p><ul><li><strong><em>Catalysis aggregates and abstracts access to crypto-economic security, while</em></strong></li><li><strong><em>Kernel provides the infra for efficient sourcing of security from the BNB Smart Chain.</em></strong></li></ul><p><em>This combination creates a powerful foundation for the next generation of decentralized services. But to truly understand its impact, we need to examine the problems teams face today.</em></p><h3>The Challenges of Building with Shared Security</h3><p>Restaking is moving us towards a future where security becomes fluid — where the same stake that secures Ethereum can also secure a zero-knowledge proving network, a decentralized sequencer, or a cross-chain bridge — essentially anything in general that requires decentralization.</p><p><strong><em>Effectively, what Flashbots did to MEV, restaking protocols are doing to decentralize security — opening Pandora’s box of possibilities.</em></strong></p><p>However, today, there are a bunch of hurdles stopping the restaking space from being adopted at scale by DVN builders and developers:</p><ol><li><strong>Fragmented Security Markets</strong></li></ol><p>Despite billions available in restaked capital, teams can’t efficiently access this security. Each restaking protocol operates as an isolated pool, forcing decentralized networks (DVNs, AVSs etc) to integrate with multiple platforms or accept limited security from a single source.</p><p>2. <strong>Infrastructure Overhead</strong></p><p>Building a DVN requires managing complex validator networks, designing their own incentive models, slashing logic, implementing custom consensus mechanisms, and coordinating off-chain execution. Teams spend months on infrastructure instead of their core service.</p><p>3. <strong>Fractured Developer Experience</strong></p><p>Today, the developer experience w.r.t. building decentralized networks is complex and tedious because of the absence of standard tooling for building such services.</p><p>4. <strong>Operational Complexity</strong></p><p>Node operators must maintain separate setups for each restaking platform, leading to inefficient operations and higher costs that ultimately get passed on to DVNs.</p><p>5. <strong>Security Rebalancing</strong></p><p>Without dynamic rebalancing capabilities, DVNs can’t optimize their security costs or protect against concentration risks across different restaking protocols.</p><p><em>These challenges have created a bottleneck in the ecosystem. Solving them requires rethinking how DVNs are built and deployed.</em></p><h3>Kernel and Catalysis Partnership: What Does This Mean to DVN Development</h3><p>Kernel and Catalysis are teaming up to turn DVN building into a modular and scalable process. Instead of spending months architecting validator logic, economic security, and slashing mechanisms, teams can focus purely on innovation — whether they’re building zk-coprocessors, decentralized AI protocols, data availability layers, or anything that needs decentralization in general .</p><p>The impact? <strong>More DVNs, launched faster and at lower cost.</strong></p><p>More DVNs mean:</p><ul><li><strong>Greater utility and capital efficiency for restaking capital</strong> → Stronger incentives for node operators &amp; restakers.</li><li><strong>Higher decentralization</strong> → A diverse range of services, reducing reliance on monolithic networks.</li><li><strong>A thriving marketplace for on-chain trust</strong> → A self-reinforcing cycle where <strong>DVNs drive demand for restaking, and restaking fuels more DVNs</strong>.</li></ul><p><em>The partnership between Kernel and Catalysis is a paradigm shift in how decentralized services are built and secured.</em></p><h3>Developer Experience of Building DVNs Drastically Improves With This Partnership</h3><p>By abstracting economic security allocation (Catalysis) and simplifying off-chain execution infrastructure (Kernel), this approach fundamentally redefines the DVN development lifecycle.</p><p>Here’s a quick overview of the development process:</p><ul><li><strong>Design core logic</strong> → Teams focus on their unique service logic, whether it’s ZK-proving, AI inference, data availability, or anything that needs decentralization in general.</li><li><strong>Deploy with Catalyst-SDK</strong> → Like Cosmos SDK for blockchains, Catalyst-SDK provides production-grade modules for building robust DVNs like modules for staking, consensus and networking.</li><li><strong>Integrate with Kernel</strong> → Leverage Kernel’s DVN infrastructure for operator management and task execution.</li><li><strong>Source security</strong> → Through Catalysis, decentralized services can dynamically access security from the BSC Smart chain. Not only this, through Catalysis, projects can rebalance security from other chains like Ethereum (via Eigenlayer, Symbiotic), Bitcoin (via Babylon, Satlayer), Solana (via Jito) etc.</li></ul><p><em>This modular approach means teams can launch production-ready DVNs in days rather than months, with the flexibility to scale beyond a single pool of economic security.</em></p><h3>Use Cases that Catalysis and Kernel Enable</h3><p>The combination of Kernel’s DVNs and Catalysis’ shared security abstraction opens the door for a new wave of decentralized applications.</p><ol><li><strong>Decentralized AI (dAI) Services</strong></li></ol><p>Distributed networks for AI model verification, inference, and federated learning. These services enable trustless AI computation while ensuring model integrity and fair reward distribution across participants validating AI tasks.</p><p>2. <strong>Decentralized Physical Infrastructure (DePIN) Networks</strong></p><p>Networks coordinating real-world infrastructure like storage, bandwidth, and compute. Kernel and Catalysis enable efficient operator management and dynamic security allocation for these geographically distributed services.</p><p>3. <strong>Zero-Knowledge Coprocessors</strong></p><p>Specialized networks that generate and verify zero-knowledge proofs at scale. By leveraging shared security, these services can provide cost-effective ZK computation while maintaining decentralization and economic security.</p><p>4. <strong>Decentralized Markets</strong></p><p>Prediction markets, DEXs, and other financial services requiring trust-minimized price feeds and order matching. These decentralized services benefit from dynamic security rebalancing to maintain economic security proportional to value secured.</p><p>5. <strong>DVN Slashing Insurance</strong></p><p>Protection against financial losses from validator slashing events. Kernel verifies slashing conditions accurately while Catalysis dynamically adjusts security across protocols to minimize systemic risks.</p><p>6. <strong>Arbitrage Bots</strong></p><p>Trust-minimized execution of trading strategies across exchanges and chains. Catalysis provides economic security against manipulation, while Kernel validates execution fairness to prevent front-running.</p><p>7. <strong>Decentralized Points System</strong></p><p>Secure attribution of reputation and rewards across on-chain and off-chain actions. Catalysis prevents Sybil attacks through economic security, while Kernel’s networks validate real-world interactions.</p><p><em>Each of these services benefits from both Kernel’s robust operator network and Catalysis’s unified security layer, enabling faster deployment and more efficient operation than previously possible.</em></p><h3>The Path Forward: Building a Future with Thousands of DVNs</h3><p>With billions in capital ready to secure the next generation of decentralized services, the missing piece has been infrastructure that makes building and scaling decentralized networks accessible to all teams.</p><p>From AI networks to ZK-coprocessors, these services will demonstrate the power of unified security and standardized infrastructure. And we at Catalysis and Kernel are enabling the next generation of builders to create and scale decentralized services.</p><p>Join us in building this future.</p><h3>Important links</h3><p><strong>Catalysis Network</strong></p><ul><li><a href="https://catalysis.network/">Website</a></li><li><a href="https://docs.catalysis.network/">Documentation</a></li><li><a href="https://catalysis.medium.com/">Blogs</a></li><li><a href="https://x.com/0xcatalysis">Twitter</a></li></ul><p><strong>Kernel</strong></p><ul><li><a href="https://kerneldao.com/">Website</a></li><li><a href="https://kerneldao.gitbook.io/kernel">Technical docs</a></li><li><a href="https://blogs.kerneldao.com/">Blogs</a></li><li><a href="https://forum.kerneldao.com/t/welcome-to-kernel-dao-governance-forum/5">Forum</a></li><li><a href="https://x.com/kernel_dao">Twitter</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=116bd514161a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Catalysis: Enabling a Future with Thousands of AVSs]]></title>
            <link>https://catalysis.medium.com/why-catalysis-enabling-a-future-with-thousands-of-avss-9197bedcf283?source=rss-cc12847abb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/9197bedcf283</guid>
            <category><![CDATA[restaking]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[eigenlayer]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Catalysis]]></dc:creator>
            <pubDate>Mon, 21 Oct 2024 07:45:46 GMT</pubDate>
            <atom:updated>2024-11-30T12:34:25.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cpk1ozb4x30JzTQZLZ_PMg.jpeg" /><figcaption>Catalysis: A future of a thousand AVSs</figcaption></figure><p>In the rapidly evolving world of decentralization, <strong>shared security (or restaking)</strong> has emerged as a powerful mechanism to bootstrap decentralized protocols and services. With <a href="https://defillama.com/protocols/Restaking">billions of dollars restaked</a> across Shared Security Protocols demanding a return on their deposits, the critical question becomes: where does the yield come from? <strong>AVSs are the answer</strong>.</p><p>As shared security protocols grow in importance, the restaking ecosystem now faces a critical challenge: the need for more <strong>AVSs (Actively Validated Services)</strong> to sustain its growth and ensure long-term viability. How many AVSs are needed to satisfy the yield requirements on this huge pool of capital? <strong>Potentially thousands.</strong></p><p>However, deploying and operating an AVS in the <strong>currently fragmented shared security ecosystem</strong> is technically challenging and there is no mechanism that aggregates supply and demand to enable price discovery for economic security.</p><p>Given these obstacles, how do we get to a future with thousands of AVSs? <strong>Catalysis</strong>.</p><p>At <a href="https://x.com/0xcatalysis">Catalysis</a>, we believe we’re at a critical juncture in the restaking ecosystem, requiring innovation around <strong>AVS economics</strong> and <strong>developer experience</strong> to ensure a sustainable future for the entire shared security space.</p><p><em>Note: For the purpose of this blog, AVS refers to any decentralized off-chain compute system secured by shared security</em>¹<em>.</em></p><h3>1. The Current State of the Restaking Ecosystem</h3><p>The concept of restaking is becoming a cornerstone of <strong>decentralized security</strong>. As networks outsource security to shared protocols, it unlocks enormous value for both the security providers and the services utilizing that security. However, the current landscape is limited by the number of AVSs available, creating a bottleneck for the <strong>growth and sustainability</strong> of restaking protocols.</p><p>Right now, there are only a handful of AVSs that anchor this ecosystem. At the time of writing this blog, there are <a href="https://app.eigenlayer.xyz/avs">19 AVSs</a> on the Eigenlayer dashboard. Symbiotic has also announced its first cohort of <a href="https://blog.symbiotic.fi/introducing-cohort-1/">14 AVSs</a>.</p><p>This is a start, but when we consider the scale required to secure an expansive shared security ecosystem and meet <strong>restakers’ demand for yield</strong>, it becomes clear that we will need hundreds — if not thousands — of AVSs in the near future. This growth is essential to maintain the <strong>sustainability of restaking yields</strong> that both operators and restakers depend on. Without enough AVSs, the ecosystem risks stagnation.</p><p>The good thing is, we think leveraging shared security protocols represents a compelling opportunity for most decentralized networks and could attract <strong>Web2 providers</strong> looking to offer <strong>enhanced trust assumptions</strong> on parts of the technical stack.</p><p>At Catalysis, our mission is to facilitate this growth by <strong>aggregating supply across restaking protocols</strong>, offering <strong>efficient price discovery</strong> and<strong> competition</strong> in an otherwise <strong>fragmented marketplace</strong>, and providing an <strong>unparalleled developer experience</strong> for AVSs and node operators alike.</p><h3>2. The Urgent Need to Facilitate AVS Deployment</h3><p>Consider the early days of Shopify: initially, only a small number of merchants (<strong>&lt;50,000</strong>) were using the platform. However, as Shopify simplified the process of building and scaling an online store, the ecosystem grew exponentially. Today, millions of merchants use Shopify because it <strong>eliminated the friction</strong> that once made e-commerce difficult to access.</p><p>As <a href="https://www.shopify.com/">Shopify</a>’s founder, Tobi Lütke, <a href="https://www.startuparchive.org/p/tobi-lutke-explains-what-the-vcs-who-passed-on-shopify-got-wrong">puts it</a>:</p><p>“<em>The reason there were only 40,000 online stores was because it was hard, expensive, and everyone who tried ran into all these brick walls of complexity, which Shopify, one after another, smoothed over and made simple to do.</em><strong><em> What a lot of free-market thinkers don’t understand is that between the demand and eventual supply lies friction</em></strong><em>.</em>”</p><p>Similarly, the restaking ecosystem is on the verge of its own “<strong>Shopify moment</strong>.” To meet the growing demand, we need a much larger number of AVSs to provide the scale necessary to support the economics (yield) on the billions of dollars in restaked assets.</p><p>Just as Shopify aggregated supply and demand for e-commerce, transforming the complex, time-consuming process of starting an online business into something accessible and straightforward, Catalysis aims to aggregate both sides of the shared security marketplace. By doing so, we will empower developers to deliver the next generation of decentralized services — thousands of them.</p><h3>3. What is so special about AVSs?</h3><p>AVS, or Actively Validated Service, is a term used to describe systems that require their own distributed validation mechanisms for verification. As explained by <a href="https://docs.eigenlayer.xyz/eigenlayer/overview/key-terms">Eigenlayer</a>, an AVS could be:</p><p>“<em>Any system that requires its own distributed validation semantics for verification, such as sidechains, data availability layers, new virtual machines, keeper networks, oracle networks, bridges, threshold cryptography schemes, and trusted execution environments.</em>”</p><p>What makes AVSs unique is their <strong>flexibility</strong>. They allow developers to write custom off-chain computation code that is secured by a decentralized network of node operators. This gives developers the freedom to experiment — not only with different execution environments, but also with custom consensus mechanisms tailored to their specific needs.</p><p>The flexibility of AVSs also extends beyond blockchain-specific use cases. It enables <strong>Web2 software products</strong> to decentralize certain product elements of their larger stack, adding enhanced trust assumptions that cannot be achieved in a centralized setting. The potential scope and market size of this application are enormous, and we believe this opportunity is currently not well understood by the market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gNlkz7VcbYqB7hBt" /></figure><p>By leveraging shared security, AVS developers don’t need to bootstrap their own security infrastructure. Instead, they can tap into the security provided by larger existing decentralized networks. This unlocks the ability to build <strong>truly decentralized, permissionless systems</strong> with ease, making innovation faster and more accessible.</p><h3>4. What Happens If There Aren’t Enough AVSs?</h3><p>The risk is real. If the growth of AVSs stalls, the entire restaking ecosystem could face serious consequences. Without enough AVSs, restaking yields could plummet, making it less attractive for node operators and stakers. If stakers begin withdrawing their deposits, the supply of economic security shrinks, triggering a downward spiral where AVSs lack sufficient economic backing.</p><p>This could lead to a collapse in the shared security space, where the incentives no longer align, and the <strong>ecosystem becomes unsustainable</strong>.</p><p>The entire space needs to scale. A handful of AVSs simply can’t support the long-term viability of multiple restaking protocols.</p><p>The good news? Hundreds of AVSs are in development and expected to launch in the coming months. Restaking protocols within the Babylon ecosystem, like <a href="https://satlayer.xyz/">Satlayer</a> &amp; <a href="https://pell.network/">Pell Network</a>, are also seeing strong interest. Experiments are underway at all levels to remove friction, and Catalysis is leading the charge.</p><h3>5. Catalysis’ Vision: A Future of Thousands of AVSs</h3><p>At Catalysis, we envision a future where thousands of AVSs are seamlessly operating across multiple shared security protocols. These AVSs will power critical infrastructure across <strong>decentralized AI (dAI)</strong>, <strong>decentralized physical infrastructure networks (dePIN)</strong>, <strong>zero-knowledge (ZK) applications</strong>, <a href="https://x.com/dabit3/status/1829153823673233735">verifiable web2 SaaS</a> and countless new use cases that crypto will unlock in the near future.</p><p>Our mission is to unlock this future by providing aggregation, abstraction and a unified developer experience to make the creation, operation, and scaling of AVSs frictionless. This is where we see the ecosystem heading, and we believe the growth of AVSs is critical to the broader adoption of decentralized technologies.</p><h3>6. How Catalysis Enables This Future</h3><p>Catalysis’ abstraction layer is the catalyst and driving force for this future. By simplifying the complexities of building and managing AVSs, we make it effortless for new AVSs to launch and scale across multiple restaking protocols. With the Catalysis SDK, developers can plug into any shared security platform without dealing with the nuances of each protocol’s underlying architecture.</p><p>Our goal is to guide AVS teams through the entire journey — from determining the economic security required and structuring rewards, to building AVS software ready for mainnet deployment.</p><p>This frictionless experience is what will enable the “<strong>Cambrian explosion</strong>” of AVSs, fueling the next wave of growth in decentralized services. The abstraction layer makes it possible for AVS teams to focus on building and innovating, rather than on the complexities of restaking. We empower AVS teams to focus on innovation, not infrastructure.</p><h3>7. Why Should AVSs Choose Catalysis?</h3><p>For AVS teams, Catalysis’ aggregation network offers unparalleled<strong> flexibility</strong> and <strong>efficiency</strong>. We allow for the creation of “<em>partial AVSs”</em> that can operate across multiple restaking platforms, enabling, for the first time, market-wide <strong>price discovery</strong> for economic security.</p><p>This approach — what we call a “<em>multi-planetary</em>” model of shared security — ensures that AVSs aren’t tied to a single protocol. Instead, they can leverage the best features of each platform, optimizing both their security and resiliency.</p><p>Catalysis also offers a <strong>flexible framework</strong> for developers, giving them the tools they need to experiment with different security configurations and find what works best for their needs. <strong>We provide the infrastructure; while AVS teams bring the innovation.</strong></p><p>Benefits for AVSs:</p><ol><li><strong>Dynamic Rebalancing</strong>: AVSs can dynamically rebalance economic security in real-time across multiple restaking platforms, ensuring optimal performance and cost-effectiveness.</li><li><strong>Native Rewards</strong>: AVSs can natively distribute rewards to restakers on any platform where economic security is sourced — eliminating the need for cross-chain transfers or bridging.</li><li><strong>Enhanced Buying Power</strong>: By aggregating demand across AVSs, Catalysis enhances buying power, fostering competition among restaking protocols. This leads to better pricing for AVSs.</li><li><strong>Unified Interface</strong>: AVS teams can access multiple pools of economic security through a single, unified interface, simplifying the complexity of managing multi-platform operations.</li><li><strong>Robust Security</strong>: AVSs built with Catalysis are more resilient against cascading slashings and the migration of restaked assets, offering stronger protection.</li><li><strong>Enhanced Developer Experience (DevEx)</strong>: Our Catalyst-SDK streamlines the process of building <strong>universal, robust AVSs</strong>, saving time and reducing duplication of efforts.</li></ol><h3>8. Benefits for Node Operators</h3><p>Catalysis offers substantial advantages for node operators by simplifying the management of AVS infrastructure across multiple restaking platforms. With the <strong>Catalyst-CLI</strong> tool, operators can seamlessly manage their AVS setups from a single interface, streamlining operations and reducing complexity. This <strong>unified solution</strong> eliminates the need to run separate infrastructure for each platform, instead offering a single node setup that saves both time and effort.</p><p>A key benefit of Catalysis is the <strong>significant reduction in DevOps engineering expenses</strong>. By providing a robust toolkit, Catalysis helps operators avoid building internal tooling for each new restaking platform. This not only minimizes development overhead but also ensures that node operators can scale their AVS management to handle thousands of services with minimal effort.</p><p>AVSs built using the <strong>Catalyst-SDK are highly reliable</strong>, eliminating common issues such as debugging obscure errors or handling key management problems. This robustness means operators can focus on maintaining secure and efficient infrastructure without the distraction of technical glitches.</p><p>Moreover, Catalysis empowers node operators of all sizes to participate in running AVS infrastructure, not just the larger ones. This inclusion contributes to the <strong>decentralization of the node operator set,</strong> addressing a <a href="https://restake.watch/">growing problem</a> in the restaking ecosystem.</p><p>Ultimately, Catalysis enables node operators to run a <strong>robust and scalable infrastructure</strong>, allowing them to focus on performance rather than operational burdens, making it a must-have for efficient AVS infrastructure management.</p><h3>9. Benefits for Shared Security Protocols</h3><p>Catalysis brings significant advantages to<strong> shared security protocols (SSPs)</strong> by aggregating demand and acting as a distribution channel, creating a more competitive and fair environment for these platforms. One of the key features Catalysis unlocks is <strong>leveling the playing field</strong> for restaking protocols, allowing them to compete on the strength and efficiency — in terms of both cost and performance — of their offerings. This also opens us opportunities for newer protocols to gain traction.</p><p>By simplifying the onboarding process for AVSs, Catalysis encourages more projects to deploy as AVSs, driving overall ecosystem growth. As more AVSs are attracted to these platforms, it creates a <strong>win-win situation</strong> where both AVS teams and SSPs benefit from increased participation.</p><p>In addition to driving adoption, Catalysis helps SSPs offer <strong>better features and more reliable economic security</strong>, making their platforms more appealing to AVSs seeking robust solutions. The influx of high-quality AVSs further enhances the robustness and value of these protocols, fostering a vibrant, <strong>competitive ecosystem</strong> for the future.</p><h3>10. Why Now Is the Right Time</h3><p>The timing couldn’t be better. With more than ten <strong>shared security protocols</strong>² now live and maturing, as well as <a href="https://u--1.com/lrts">liquid restaking protocols</a> accumulating billions in deposits, the ecosystem is primed for rapid growth. These protocols are attracting ever-growing deposits from restakers, creating a dynamic that demands a corresponding increase in AVS deployments to support yield requirements.</p><p>For the first time, AVS teams are faced with an <strong>overwhelming array of choices</strong> and feature sets available across these restaking platforms, making it challenging to decide where to build.</p><p>However, the growth of the shared security ecosystem can only be sustained if we have enough AVSs to fuel it. Catalysis is here to meet that demand by providing the infrastructure necessary to drive the <strong>exponential growth of AVSs</strong> over the coming years.</p><h3>11. Conclusion</h3><p>The restaking ecosystem is at a pivotal moment. Without a significant increase in the number of AVSs, the long-term sustainability of shared security could be at risk. Catalysis exists to solve this challenge, providing the <strong>aggregation</strong> and<strong> abstraction layer</strong> that will enable thousands of AVSs to flourish.</p><p>By making it frictionless to build, operate, and scale AVSs, Catalysis is enabling a future where shared security becomes the backbone of a vast range of decentralized services. Now is the time to build, and Catalysis is the key to unlocking that future.</p><p>We’ll be launching our <strong><em>devnet</em></strong> in a few weeks — stay tuned!</p><h3>12. References</h3><ol><li>Alternative Nomenclature:<em> Actively Validated Service (AVS — Eigenlayer), Network (Symbiotic), Distributed Secure Service (DSS — Karak), Node Consensus Network (NCN — Jito), Bitcoin Validated Service (BVS — Satlayer), Decentralized Validated Service (DVS — Pell).</em></li><li>SSPs<em>: </em><a href="https://www.eigenlayer.xyz/"><em>Eigenlayer</em></a><em>, </em><a href="https://symbiotic.fi/"><em>Symbiotic</em></a><em>, </em><a href="https://karak.network/"><em>Karak</em></a><em>, </em><a href="https://nektar.network/"><em>Nektar</em></a><em>, </em><a href="https://satlayer.xyz/"><em>Satlayer</em></a><em>, </em><a href="https://pell.network/"><em>Pell</em></a><em>, </em><a href="https://www.jito.network/blog/announcing-jito-restaking/"><em>Jito</em></a><em>, </em><a href="https://www.picasso.network/"><em>Picasso</em></a><em>, </em><a href="https://solayer.org/"><em>Solayer</em></a><em>, </em><a href="https://docs.availproject.org/docs/introduction-to-avail/avail-fusion"><em>Avail Fusion</em></a></li><li>LRTs<em>: </em><a href="https://www.ether.fi/"><em>Etherfi</em></a><em>, </em><a href="https://www.puffer.fi/"><em>Puffer</em></a><em>, </em><a href="https://www.renzoprotocol.com/"><em>Renzo</em></a><em>, </em><a href="https://kelpdao.xyz/"><em>Kelp</em></a><em>, </em><a href="https://www.swellnetwork.io/"><em>Swell</em></a><em>, </em><a href="https://www.bedrock.technology/"><em>Bedrock</em></a><em>, </em><a href="https://www.level.money/"><em>Level</em></a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9197bedcf283" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shared Security Abstraction]]></title>
            <link>https://catalysis.medium.com/shared-security-abstraction-5910fbd5b79c?source=rss-cc12847abb92------2</link>
            <guid isPermaLink="false">https://medium.com/p/5910fbd5b79c</guid>
            <category><![CDATA[eigenlayer]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[restaking]]></category>
            <category><![CDATA[liquid-restaking]]></category>
            <category><![CDATA[shared-security]]></category>
            <dc:creator><![CDATA[Catalysis]]></dc:creator>
            <pubDate>Mon, 29 Jul 2024 05:45:01 GMT</pubDate>
            <atom:updated>2024-07-30T09:38:24.267Z</atom:updated>
            <content:encoded><![CDATA[<p>Enabling teams to seamlessly build shared security networks.</p><p>Thanks to <a href="https://x.com/0xkrane">krane</a>, <a href="https://x.com/gmEthereum">austin</a>, siddharth (<a href="https://x.com/MarlinProtocol">marlin</a>), <a href="https://x.com/crypto_malone">richard</a>, <a href="https://x.com/stateroot">nicholas</a>, <a href="https://x.com/0xb3d3">bede</a>, <a href="https://x.com/JJAlicea0x">storm</a>, <a href="https://x.com/joel_john95">joel</a>, <a href="https://x.com/shutterbugsid">sid</a> for their thoughtful discussions and feedback.</p><h3>Introduction</h3><p>In the rapidly evolving landscape of blockchains, restaking or shared security has emerged as a pivotal concept. It involves borrowing economic security from larger, more secure protocols to bootstrap a new network.</p><p>The shared security space is gaining momentum with more protocols wanting to decentralize their projects by leveraging the economic security offered by shared security protocols. On the supply side, restaking protocols have a <a href="https://defillama.com/protocols/Restaking">combined TVL</a> of almost <strong>$19B</strong>. However, this space remains demand constrained due to the lack of a sufficient number of AVS networks.</p><p>Through our recent customer research, we’ve identified that the most significant hurdle for AVS network teams is the onboarding process.</p><p>Over the past few weeks, we spoke with teams building or having already built AVS networks to understand their use cases, reasons for using shared security and pain points in development. Additionally, we talked to LRT protocols and node operators to gather their insights on managing AVS networks.</p><p>The journey from deciding to build an AVS to deploying it in production is time-consuming and resource-intensive. This complexity often discourages teams, both small and large, from pursuing shared security solutions. This eventually slows down the growth and adoption of the restaking ecosystem.</p><h3>Motivation</h3><p>For restaking protocols to grow and thrive, the onboarding of AVS networks needs to be seamless and much easier.</p><p>However, building an AVS network is hard. Network teams spend hundreds of developer hours writing a ton of both offchain and onchain logic to build their networks. This process should be frictionless and should ideally require much less time &amp; effort.</p><p><strong>What does a network really want?</strong></p><ol><li>A target amount of economic security (say <em>$500M</em> or <em>10k ETH</em>).</li><li>To pay a little in yield in exchange for renting shared security. Let’s say they want to pay up to <em>X%</em> of the token supply (say <em>5%</em>) in exchange for renting shared security.</li><li>Flexibility to choose the best shared security protocol in terms of price &amp; reliability. The best choice for a given AVS network may be a blend of multiple shared security protocols.</li><li>An onboarding process that takes no more than a week. Today, the entire process from building to deployment takes around a couple of months, especially if the team doesn’t have prior experience in restaking.</li></ol><p><strong>What does a network NOT want?</strong></p><ol><li>To spend weeks understanding the low-level design of available shared security protocols.</li><li>To experience analysis paralysis when deciding which shared security protocol to build on.</li><li>To facilitate offline agreements with LRTs/Operators for asset delegation.</li></ol><figure><img alt="Why choose when you can build on both?" src="https://cdn-images-1.medium.com/max/500/1*DIoLgPbzt_bh0EQErn2xEQ.jpeg" /></figure><h3>Shared Security Abstraction</h3><p>We are introducing <strong>“Shared Security Abstraction” (SSA) </strong>— a concept designed to abstract the complexities of underlying restaking protocols for AVS networks, making shared security more accessible and efficient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNp5LPOqlGnKWKM5ilFpUA.png" /><figcaption>Image 1: Visual explainer for Shared Security Abstraction</figcaption></figure><p>A better analogy would be <strong>Chain Abstraction</strong>. Just as chain abstraction allows end users to spend their crypto assets irrespective of the chain, <strong>Shared Security Abstraction</strong> allows networks to rent economic security irrespective of the underlying shared security protocol.</p><p>This is important because there are now a variety of restaking protocols to build on, which has fragmented the developer experience for AVS network builders. They now have to spend considerable time and effort evaluating different restaking platforms, understanding their architectures, and developing on one of them.</p><p>Network builders should be able to focus on decentralizing their networks without being overwhelmed by these choices. Instead, they should concentrate on their core business logic, and <strong>Shared Security Abstraction</strong> allows them to do just that.</p><p><strong>Shared Security Abstraction</strong> unlocks a variety of use-cases:</p><ol><li><strong>Diversified Security</strong>: It allows a network to derive security from multiple restaking protocols, not just one. Thus increasing the capital pool available to the network, potentially reducing security bootstrapping costs.<br>– For example, a network can obtain <em>40%</em> of its economic security from <a href="https://www.eigenlayer.xyz/">Eigenlayer</a>, <em>30%</em> from <a href="https://symbiotic.fi/">Symbiotic</a>, and <em>20%</em> from <a href="https://karak.network/">Karak</a> and <em>10%</em> from <a href="https://babylonchain.io/">Babylon</a> (see <em>Image 2</em> below)<br>– This approach also has the positive effect of load distribution, preventing the <a href="https://vitalik.eth.limo/general/2023/05/21/dont_overload.html">overloading</a> of any single blockchain network.</li><li><strong>Simplified Complexity</strong>: It abstracts away the complexities of the underlying shared security protocols.</li><li><strong>Enhanced Liquidity Participation</strong>: It allows large restaking participants like LRTs to participate in auctions to potentially secure AVS networks across restaking protocols, bringing the off-chain deal making process onchain.</li><li><strong>Reduced Over-Reliance</strong>: It shields AVS networks from over-reliance on a single restaking protocol, promoting greater resilience and flexibility.</li><li><strong>Reputation Markets</strong>: It enables reputation markets to be built based on the cumulative performance of AVS networks, operators &amp; LRTs.</li><li><strong>Risk Management</strong>: Data from shared security abstraction protocols can be leveraged by risk engines to create more accurate risk-reward portfolios.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MmmQ31QIe7nlMIqtu8H6Zw.png" /><figcaption>Image 2: Diversified Security</figcaption></figure><p>However, to fulfill the vision of <strong>Shared Security Abstraction</strong>, we first need to tackle the problem of onboarding AVS networks to the shared security ecosystem. The upcoming article discusses in detail the challenges and potential solutions to this problem.</p><h3>Conclusion</h3><p>At <a href="https://x.com/0xcatalysts">Catalysis</a>, our goal is to simplify and streamline the entire lifecycle of an AVS network, from development to production, enabling teams to concentrate on their core business logic.</p><p>We believe that building AVS networks should be seamless and as frictionless as possible. This would drive the demand side of restaking, ultimately forming the basis of a robust shared security market.</p><p>This is the vision of Shared Security Abstraction. And, we’re just getting started. Stay tuned for what’s next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5910fbd5b79c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>