<?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>Epoch Protocol</title>
        <link>https://paragraph.com/@epoch-protocol</link>
        <description>🛠️ Intent-Centric Abstraction Layer for Web3 🌐

Now in public beta 💻 - http://app.epochprotocol.xyz</description>
        <lastBuildDate>Fri, 31 Jul 2026 22:47:24 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Epoch Protocol</title>
            <url>https://storage.googleapis.com/papyrus_images/eac6dab0cffd018a0bf6446286c27759d1fcfb89f1b8214a8fa34883dcc219ec.png</url>
            <link>https://paragraph.com/@epoch-protocol</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[How Epoch Can Empower Protocols with Increased Discoverability]]></title>
            <link>https://paragraph.com/@epoch-protocol/how-epoch-can-empower-protocols-with-increased-discoverability</link>
            <guid>LGaTTv7mM6kZ1TBBAXTc</guid>
            <pubDate>Thu, 23 Oct 2025 13:43:15 GMT</pubDate>
            <description><![CDATA[How Epoch Can Empower Protocols with Increased DiscoverabilityThe Fragmentation CrisisThe Web3 ecosystem is highly fragmented, with hundreds of chains and dApps creating isolated user silos where users and liquidity are locked. Data reveals that 59.5% of EVM wallets interact on only one network, 35% interact with just two Only 4.4% operate across three chains, A mere 0.7% span four, and 0.2% five or more, creating a fundamental barrier to protocol growth and user discovery.This fragmentation ...]]></description>
            <content:encoded><![CDATA[<h1 id="h-how-epoch-can-empower-protocols-with-increased-discoverability" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">How Epoch Can Empower Protocols with Increased Discoverability</h1><h1 id="h-the-fragmentation-crisis" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Fragmentation Crisis</h1><p>The Web3 ecosystem is highly fragmented, with hundreds of chains and dApps creating isolated user silos where users and liquidity are locked.</p><p>Data reveals that 59.5% of EVM wallets interact on only one network,</p><p>35% interact with just two</p><p>Only 4.4% operate across three chains,</p><p>A mere 0.7% span four, and 0.2% five or more, creating a fundamental barrier to protocol growth and user discovery.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/89af8119dc34de1cfa700717f1a1c7bf25f8222ac56629fefd7f842e955183ed.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>This fragmentation has far-reaching consequences:</p><ul><li><p>Protocols deployed on only a few chains miss out on users whose funds live elsewhere</p></li><li><p>Cross-chain APR disparities emerge, even when protocols deploy across multiple chains, users may find better yields on chains where their assets don&apos;t reside</p></li><li><p>Complicated asset management across multiple networks fragments liquidity</p></li><li><p>Users face time-consuming processes while protocols lose potential reach</p></li></ul><p>In practical terms, millions of wallets hold significant balances on one chain but cannot directly use dApps on another without the use of cumbersome bridging or swapping.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/1e0593db299d5533d90b4f23723fd55d361278722dac8e5a1884ea6f0933bbd8.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>For example, Polygon, Arbitrum, and Base each have millions of active wallets, yet less-active chains have far fewer users. In this landscape, users lose time, and protocols lose reach.</p><h2 id="h-cross-chain-friction-and-user-drop-off" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Cross-Chain Friction and User Drop-Off</h2><p>Traditional cross-chain transactions involve numerous steps:</p><p>selecting chains, switching networks, multiple bridge and swap confirmations. An intent-driven, one-click approach collapses these into a single action.</p><p>Cross-chain interactions today are tedious. Bridging tokens often involves multiple steps, high fees, and cumbersome processes, leading to abandoned transactions.</p><p>Protocols limited to certain chains compound this issue. A user holding assets on Chain A must bridge/swap to reach a dApp on Chain B.</p><h4 id="h-current-chain-landscape-and-user-distribution" class="text-xl font-header !mt-6 !mb-3 first:!mt-0 first:!mb-0">Current Chain Landscape and User Distribution</h4><p>Active User Concentration</p><ul><li><p>Base: 38M users, $6.5M fees, 270M txs</p></li><li><p>Polygon: 18M users, $262K fees, 113M txs</p></li><li><p>Ethereum: 17M users, $41M fees, 50M txs</p></li><li><p>Arbitrum: 11M users, $1.3M fees, 94M txs</p></li><li><p>Optimism: 2M users, $332K fees, 41M txs</p></li></ul><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/3042befe944e4d8bfc94fe396f65089210f2e370e37c9e8b3ca6b2722da7667a.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>Base leads in adoption, Ethereum in fee revenue, Arbitrum in strong activity, while Polygon shows the broadest user onboarding.</p><p><strong>User Balance Tiers (&gt;$1K Accounts)</strong></p><p>$1k–$10k: 134K users (60.7%) – avg balance $3.4k</p><p>$10k–$100k: 65K users (29.5%) – avg balance $32.5k</p><p>$100k+: 22K users (9.8%) – avg balance $3.4M</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/08554e7fddf88ce23aa77fe5e01eea20c4035f9f6fff6bf646a4023caa0cc47a.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>While whales are &lt;10% of users, they hold the majority of liquidity, an outsized opportunity for protocols.</p><h3 id="h-cross-chain-user-behavior-friction-is-the-norm" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Cross-Chain User Behavior: Friction is the Norm</h3><ol><li><p>Migration Patterns</p><p>Top migration routes (past 3 months):</p><ol><li><p>Ethereum - Base: 71.7K users, $2.0B volume</p></li><li><p>Ethereum - Arbitrum: 24.1K users, $1.9B volume</p></li><li><p>Arbitrum - Ethereum: 42.1K users, $1.7B volume</p></li></ol></li><li><p>Bridge Activity Concentration</p><ol><li><p>Ethereum - Base: $12B volume (dominant route)</p></li><li><p>Ethereum -Arbitrum: next highest volume</p></li><li><p>Stablecoin bridges (USDC, USDT) dominate</p></li></ol></li></ol><p>Users clearly want to move, but bridging is costly and complex.</p><h3 id="h-blockchain-users-pain-points" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Blockchain Users&apos; Pain Points</h3><ul><li><p>Multiple approvals and confirmations</p></li><li><p>Network switching in wallets</p></li><li><p>Long bridge waiting times and fees</p></li><li><p>Route complexity and failed transactions</p></li></ul><p>This friction mirrors Web2’s 70% cart abandonment rate, but in Web3, it’s likely worse.</p><h3 id="h-the-opportunity-cross-chain-intent-infrastructure" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>The Opportunity: Cross-Chain Intent Infrastructure</strong></h3><p>Protocol Discoverability Gap</p><ul><li><p>Base’s 38M users are invisible to Arbitrum-only protocols</p></li><li><p>Polygon’s 18M users cannot easily reach Ethereum-native dApps</p></li><li><p>Whales ($100k+ users) are only 9.8% but hold most of the capital</p></li></ul><p>Yield Disparities Across Chains</p><p>Even multi-chain protocols face discoverability limits:</p><p>APRs vary by liquidity depth across chains</p><p>Users often skip better yields on other chains to avoid bridging friction, which results to inefficient capital allocation and missed growth.</p><p>Epoch replaces fragmented bridging UX with intent-driven cross-chain execution:</p><ul><li><p>Declarative Intents: users specify what (stake 1,200 USDC on the highest APR) not how</p></li><li><p>Solver Competition: solvers race to find the best execution path</p></li><li><p>Liquidity Fronting: solvers front destination tokens instantly, settle later</p></li><li><p>Account Abstraction: gasless, seamless user interactions</p></li></ul><p>This unlocks true cross-chain discoverability for protocols and eliminates UX friction for users.</p><p>Market Impact Projections</p><ol><li><p>Expanded Addressable User Base :</p><ol><li><p>3% conversion of adjacent-chain users &gt;= 1.14M new users</p></li><li><p>5% conversion &gt;= 1.9M users</p></li><li><p>10% conversion &gt;= 3.8M users (~2.5x TAM expansion)</p></li></ol></li><li><p>Whale Acquisition Potential :</p><ol><li><p>22K whale users, avg balance $3.4M</p></li><li><p>Capturing even a fraction of this cohort dramatically increases TVL</p></li><li><p>Base’s whale-heavy distribution is particularly valuable for other chains</p></li></ol></li><li><p>Network Effects :</p><ol><li><p>Protocols gain global discoverability without redeployment</p></li><li><p>Users access the best yields anywhere with no UX burden</p></li><li><p>Ecosystem benefits from efficient liquidity allocation</p></li></ol></li></ol><h3 id="h-from-fragmentation-to-growth-how-epoch-converts-the-problem-into-expansion" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">From Fragmentation to Growth: How Epoch Converts the Problem into Expansion</h3><p>The data is clear: 59.5% of wallets remain siloed, while billions in bridging volume show strong user demand but painful inefficiency.</p><p>Epoch turns these weaknesses into levers for growth.</p><p>1. Unlocks New User Acquisition</p><ul><li><p>Protocols on a single chain instantly become discoverable to adjacent chain users.</p></li><li><p>Even a 3–5% conversion from neighboring ecosystems brings 1M+ new active users.</p></li></ul><p>2. Expands Liquidity and TVL</p><ul><li><p>Whale users ($100k+ balances) represent less than 10% of wallets but hold the majority of liquidity.</p></li><li><p>Epoch removes barriers preventing whales from moving into higher-yield opportunities on other chains.</p></li><li><p>Protocols gain 25–40% more TVL through seamless cross-chain yield access.</p></li></ul><p>3. Optimizes Yields &amp; Capital Efficiency</p><ul><li><p>By abstracting away chain silos, users are routed automatically to the best APRs across chains.</p></li><li><p>These levels yield, reducing inefficiencies caused by fragmented liquidity.</p></li><li><p>Protocols benefit from stickier capital as users trust the solver network to optimize returns.</p></li></ul><p>4. Reduces User Acquisition Costs</p><ul><li><p>Traditional multi-chain expansion requires redeployment, liquidity incentives, and user education on each chain.</p></li><li><p>With Epoch, discoverability is automatic, a protocol on one chain becomes instantly visible across many.</p></li><li><p>This reduces CAC (cost of acquisition) and accelerates scaling.</p></li></ul><p>5. Creates Network Effects</p><ul><li><p>Every protocol integrated increases the value of the solver network for users.</p></li><li><p>Every new user onboarded increases discoverability for all protocols.</p></li><li><p>Over time, this creates a self-reinforcing flywheel of growth, where fragmentation drives integration instead of inefficiency.</p></li></ul><h3 id="h-epoch-as-a-growth-engine" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Epoch as a Growth Engine</h3><p>Epoch is not just reducing friction. It is:</p><ul><li><p>Expanding markets (millions of new users)</p></li><li><p>Unlocking liquidity (whales + TVL migration)</p></li><li><p>Optimizing yields (capital efficiency across chains)</p></li><li><p>Lowering acquisition costs (protocols get multi-chain discoverability for free)</p></li><li><p>Driving network effects (each integration compounds value for all participants)</p></li></ul><p>In a fragmented ecosystem, Epoch transforms isolation into integration and inefficiency into growth.</p><h3 id="h-flipside-dashboard" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Flipside dashboard</h3><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://flipsidecrypto.xyz/chat/shared/artifacts/cross-chain-user-behavior-analysis-dashboard-qpybygd1">https://flipsidecrypto.xyz/chat/shared/artifacts/cross-chain-user-behavior-analysis-dashboard-qpybygd1</a></p><h3 id="h-author" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Author:</h3><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/lindyy_lindy"><strong>Linnda</strong></a> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/lindyy_lindy">(Web3 Data Architect)</a></p>]]></content:encoded>
            <author>epoch-protocol@newsletter.paragraph.com (Epoch Protocol)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/8b5bd9697765e350063452cfaafcf839b915e5bf32e21ebf6ff901842e22ef19.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Coordinating Solvers]]></title>
            <link>https://paragraph.com/@epoch-protocol/coordinating-solvers</link>
            <guid>sWYPjUOgEeW2FtLhbCs9</guid>
            <pubDate>Mon, 02 Sep 2024 15:54:18 GMT</pubDate>
            <description><![CDATA[Intent solvers are something that&apos;s taking over the web3 space for streamlined interactions, they take the user’s desired intent, process it, find a way to make it happen, and get it executed. It sounds good when put like this, but it comes with its nuances. How do we ensure solvers/solvers can fulfill the entire intent, if not, how do we ensure solvers cover wide use cases, and ensure users get the best route and order filling? Well, the key is solver collaboration and coordination!! Co...]]></description>
            <content:encoded><![CDATA[<p>Intent solvers are something that&apos;s taking over the web3 space for streamlined interactions, they take the user’s desired intent, process it, find a way to make it happen, and get it executed.</p><p>It sounds good when put like this, but it comes with its nuances. How do we ensure solvers/solvers can fulfill the entire intent, if not, how do we ensure solvers cover wide use cases, and ensure users get the best route and order filling?</p><p>Well, the key is solver collaboration and coordination!!</p><p><strong>Collaboration</strong></p><p>Solvers can decide to work with each other to fulfill/solve different parts of the intent, they can leverage some collaboration layer to solve their bit and hand off the rest of it to the next solver.</p><p>Solvers need to understand two things here, what the ask is, and whom they should collaborate with, ideally a solver that gives a good quote or route.</p><p>Now for this, there are some bottlenecks, the biggest one is counterparty discovery, how do you discover which solver can solve the other half, or give an optimal solution for the other half?</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/4e6bcd6bae103dee9919b2ebd1f9c11764d08994b6fc695259703ed9fb24de9f.gif" 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><strong>Coordination</strong></p><p>Collaboration has its bottlenecks but it&apos;s essential to wider coverage for intents to solve for and achieve better solutions, instead of doing a blind or friendly collaboration, we can put a coordination mechanism that</p><ol><li><p>Knows who can solve what.</p></li><li><p>Query their quotes and routes.</p></li><li><p>And lastly divide parts of intent among different solvers.</p></li></ol><p>When you put in coordination along with collaboration, you reach a better solution, if a coordination mechanism knows who can solve what part of the intent, and who is giving a better quote/route, collaboration becomes easier and you are less likely to run into a situation where you don’t find a solver who can do it all.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/f2a41823e74ad47286e778ac0f426959c771d11574a49564db7e7d108642c9f6.gif" 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>Intents and intent solver space is evolving, new approaches will scale this space, and collaboration and coordination will become the defining factors for completely changing the web3 interactions.</p><p>There can be different mechanisms for solver coordination, read about Epoch Protocol’s Sub Intent Orchestration here -</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mirror.xyz/0x62BF6561db8D0105839B70c7bd4210bca3d6aCF2/uyD5t2meAwK1rXfKlLa-Y2n7yAgMxhpr1pKX5uQdg2g">https://mirror.xyz/0x62BF6561db8D0105839B70c7bd4210bca3d6aCF2/uyD5t2meAwK1rXfKlLa-Y2n7yAgMxhpr1pKX5uQdg2g</a></p>]]></content:encoded>
            <author>epoch-protocol@newsletter.paragraph.com (Epoch Protocol)</author>
        </item>
        <item>
            <title><![CDATA[Dividing and Conquering Intents]]></title>
            <link>https://paragraph.com/@epoch-protocol/dividing-and-conquering-intents</link>
            <guid>xccsVJTQjGDzJ6UT7Dla</guid>
            <pubDate>Sat, 10 Aug 2024 16:35:52 GMT</pubDate>
            <description><![CDATA[Epoch Protocol leverages Intents to abstract away protocols, chains, and execution. It translates user Intents from their initial state to their desired final state without requiring an understanding of intermediary state updates.Methods for Executing User IntentsThere are three possible approaches to solving a user’s Intent:Identify a single solver capable of solving the entire intent.Allow solvers to collaborate without orchestration on their own.Deconstruct Intents into Sub-Intents, find p...]]></description>
            <content:encoded><![CDATA[<p>Epoch Protocol leverages Intents to abstract away protocols, chains, and execution. It translates user Intents from their initial state to their desired final state without requiring an understanding of intermediary state updates.</p><h2 id="h-methods-for-executing-user-intents" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Methods for Executing User Intents</strong></h2><p>There are three possible approaches to solving a user’s Intent:</p><ol><li><p>Identify a single solver capable of solving the entire intent.</p></li><li><p>Allow solvers to collaborate without orchestration on their own.</p></li><li><p>Deconstruct Intents into Sub-Intents, find partial solutions and merge them into a complete solution (Epoch Protocol’s approach).</p></li></ol><p>The <strong>first approach</strong> requires a one-intent solver that can transition the user from the initial to the final state. For simple state updates like bridging or swapping, this is straightforward. However, as Intents require more partial state updates, fewer solvers can address them, potentially resulting in suboptimal solutions.</p><p>With the <strong>second approach,</strong> solvers would need to collaborate through peer-to-peer communication. Due to technical limitations and economic reasons might not be able to reach a more optimal solution. The solver might choose not to collaborate hindering the process of finding a solution.</p><h2 id="h-epoch-protocols-approach" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Epoch Protocol’s Approach</strong></h2><p>Epoch Protocol deconstructs Intents into smaller Sub-Intents. Each Sub-Intent is then solved by a competing market of purpose-specific Intent solvers. This approach eliminates the need for a comprehensive solver, instead relying on multiple solvers that address smaller Sub-Intents, which are then combined and committed to a settlement layer.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/797fce1bbc74620cb21204c6f84366e44f5ee51a84e59e75e58b67da540c2a37.gif" 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><h2 id="h-example-dai-on-optimism-to-eigen-layer-restaking-position" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Example: DAI on Optimism to Eigen Layer Restaking Position</strong></h2><p>Let’s consider a user who has DAI on Optimism and wants a restaking position in Eigen Layer on Ethereum Mainnet.</p><p><strong>Approach 1:</strong> Find a solver willing to exchange DAI on Optimism for an equivalent restaking position in Eigen Layer.</p><p><strong>Approach 2:</strong> Intent solvers work together to find solvers that can solve for the intermediate steps while one solver coordinates and executes the final intent.</p><p><strong>Approach 3 (Epoch Protocol):</strong> Break down the Intent into Sub-Intents:</p><ol><li><p>Swap DAI for ETH</p></li><li><p>Bridge ETH to Ethereum</p></li><li><p>Use optimal liquid staking platforms (e.g., Lido or RocketPool)</p></li><li><p>Restake obtained liquid restaking token to Eigen Layer</p></li></ol><p>Multiple solution paths are possible:</p><ol><li><p>One Intent solver provides stETH on Ethereum in exchange for DAI on Optimism, then another solver provides a way to restake stETH.</p></li><li><p>Different Intent solvers address each step: DAI to ETH, bridging ETH to Ethereum, using Lido for liquid staking, and restaking stETH.</p></li></ol><p>Epoch Protocol queries Intent solvers and their markets for possible solutions and quotes. Each route is evaluated, and the most optimal one is selected for execution</p><h2 id="h-the-importance-of-sub-intents" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>The Importance of Sub-Intents</strong></h2><p>User Intents often involve interactions with multiple protocols, combining swaps, bridges, lending, staking, and any other arbitrary protocol interaction. Finding a single solver for complex Intents becomes increasingly difficult as the number of protocol interactions increases.</p><p>The Sub-Intents model ensures that if solvers exist for all individual Sub-Intents, a solution can be found. Moreover, competing solvers for each Sub-Intent lead to more optimal solutions.</p><h2 id="h-sub-intent-orchestrator-sio" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Sub-Intent Orchestrator (SIO)</strong></h2><p>Epoch’s Sub-Intent Orchestrator (SIO) is a game-changing component that utilizes an extensive graph comprising of protocols, tokens, dApps, chains and more. Each node in the graph represents one of the elements mentioned before with their specific attributes and traits. These attributes would be able to establish connections to other such elements.</p><p>Once the SIO reaches the final desired node through these multiple potential paths, it queries multiple solvers for their proposed partial state updates. This information is used to assign costs and weights to nodes and paths.</p><p>The path with the lowest cost and maximum weight is selected, ensuring users receive the most optimized solution for their Intent.</p><h2 id="h-conclusion" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0"><strong>Conclusion</strong></h2><p>Sub-intent orchestration enables the use of smaller, purpose-specific solvers and their competing markets to reach more solutions. By selecting the most optimal solutions for all involved Sub-Intents, Epoch Protocol avoids the limitations of relying on a single comprehensive solver to address all user needs.</p>]]></content:encoded>
            <author>epoch-protocol@newsletter.paragraph.com (Epoch Protocol)</author>
        </item>
        <item>
            <title><![CDATA[Introducing: Epoch Protocol - An Intent-Centric Abstraction Layer for Web3]]></title>
            <link>https://paragraph.com/@epoch-protocol/introducing-epoch-protocol-an-intent-centric-abstraction-layer-for-web3</link>
            <guid>XxgQvmduTtcAKjuHvjkP</guid>
            <pubDate>Mon, 17 Jun 2024 17:07:17 GMT</pubDate>
            <description><![CDATA[The vision of Epoch is to use the new intent-based interaction paradigm to build an infrastructure layer that completely abstracts away the Web3 complexities for the user such as chains, protocols, gas, balance, and even execution.The Problem of Complexity and Fragmentation in Web3aka Web3’s Sophies’ ChoicesThe Exponential Growth of Protocols, dApps, and Chains Users often find it overwhelming to navigate the web3 ecosystem, identify the best protocols, and manage their assets across multiple...]]></description>
            <content:encoded><![CDATA[<p>The vision of Epoch is to use the new intent-based interaction paradigm to build an infrastructure layer that completely abstracts away the Web3 complexities for the user such as chains, protocols, gas, balance, and even execution.</p><h1 id="h-the-problem-of-complexity-and-fragmentation-in-web3" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Problem of Complexity and Fragmentation in Web3</h1><h3 id="h-aka-web3s-sophies-choices" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">aka Web3’s Sophies’ Choices</h3><ol><li><p><strong>The Exponential Growth of Protocols, dApps, and Chains</strong></p><p>Users often find it overwhelming to navigate the web3 ecosystem, identify the best protocols, and manage their assets across multiple chains.</p><p>These countless choices aren’t just a barrier for new users - they also make it tough for developers to build dApps that might need to interact with other protocols to get the user in the correct state to use their dApp.</p></li><li><p><strong>Fragmented Liquidity and Assets</strong></p><p>Users&apos; funds are often scattered across multiple networks and assets, making fund management and cross-chain dApp interaction a painful task.</p></li><li><p><strong>Mentally Taxing User Experience</strong></p><p>Performing transactions often involve multiple steps, long wait times, and interaction with newer unfamiliar dApps and protocols. Users must deal with different gas tokens, bridges, network conditions, and protocols.</p></li><li><p><strong>Lack of Non-Custodial Automation</strong></p><p>Currently, there is no way to automate transactions in a non-custodial manner, maintaining full control over one&apos;s funds. All transactions are manual, requiring users to be terminally online to execute transactions at the right moment. There’s no way to make transactions that depend on and adapt automatically to the ever-changing on-chain and off-chain conditions.</p></li><li><p><strong>Inconsistent Offerings from Protocols</strong></p><p>Different protocols offer varying rates, speeds, fees, privacy, and even MEV protection for the same actions across multiple chains. Aggregators have been great till now for verticals like bridging and swapping but as the variety of things we do on-chain increases even these aggregators would fall short of meeting the exponential growth. This would mean users must spend considerable time and effort finding the best rates for staking, swapping, lending, and other activities.</p></li><li><p><strong>Limited Intent Solvers</strong></p><p>dApps that try to give a one-stop-shop solution for users often have a fixed list of protocols and chains they interact with, which means they cannot always offer the best possible rates or routes for users&apos; transactions. Plus they cannot expand as quickly to the newest chains and protocols that might be more lucrative for users.</p></li></ol><h1 id="h-epochs-solution-using-the-intent-paradigm-along-with-declarative-intent-input-trigger-observers-smart-account-level-permissions-and-fast-finality-bridge-to-offload-the-problems-to-sophisticated-solvers" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Epoch’s Solution: Using the Intent Paradigm along with Declarative Intent Input, Trigger Observers, Smart Account Level Permissions, and Fast Finality Bridge to offload the problems to sophisticated solvers.</h1><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/55878a136ae45cfeb7bc8aa954dc132d9bb10ff3b8ea97d3ec183176c8c3e2c2.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>Epoch Protocol sits between users, other protocols, and chains and provably optimizes for best conditions for all the involved steps - it figures out the intent → finds the best routes for desired actions → and/or waits for better routes → automatically performs intermediate steps like bridge funds if deficit → makes necessary swaps → handles the gas payment and ultimately settles user’s or protocol’s intent in a non-custodial way.</p><p><strong>Intent-Centric dApp Discovery</strong> With Epoch’s Composable and Modular Intent Solver, solvers can plug modules specific to certain web3 verticals, protocols, and even other intent solver networks through adapters. They can either propose the most optimal partial solution or a complete solution.</p><p><strong>Multiple Intent Solvers and Optimized Rates</strong> Epoch Protocol provides a network of these modular intent solvers that can join the network and counterparty discovery and solver competition the network can ensure that users always get the most optimal solution.</p><p><strong>Time Abstracted Intent and Execution</strong> Epoch Protocol leverages SAFE smart wallets and account abstraction to offer fully non-custodial automation. Users maintain complete control over their funds while automating transactions based on on-chain or off-chain triggers. This ensures security and convenience without sacrificing control. This will become easier and more widely adopted through EIP-7702, ERC-7579, and ERC-7715 and various other discussions going around Smart Wallets.</p><p><strong>Building an Inter-Compatible Solver Network</strong> At Epoch we believe that the intent solver networks shouldn’t be built in silos. The composability of Epoch Protocol means that through adapters there can be a two-way connection between Epoch Intent Solvers and other intent solvers.</p><h3 id="h-components-of-epoch-protocol" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Components of Epoch Protocol</h3><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/3ac062b9b7d5f1235ef2db019238a5b09fa76d4637db3e60c8383a08a9947d5e.png" alt="Epoch Architecture" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Epoch Architecture</figcaption></figure><p><strong>Epoch Node:</strong> Divided into environments like Transaction Bundler, Context Setter, Observer, Composable Solver Environment, and Consensus to handle different stages of intent execution.</p><ul><li><p><strong>On-Chain Contracts:</strong> Includes Registry and Gatekeeper, SAFE smart wallets, Epoch Plugin(ERC-7579 compatible), Epoch Hook, Liquidity Pool, and a cross-chain Epoch Paymaster for secure and efficient transaction management.</p></li><li><p><strong>Epoch SDK:</strong> Provides dApp developers with tools to easily integrate, use intent solvers, and automate transactions, reducing development time and effort by not internalising a bunch of protocols and writing custom smart contracts.</p></li></ul><h1 id="h-what-does-it-mean-for-users-and-protocols" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What does it mean for Users and Protocols</h1><h3 id="h-for-dapps" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">For dApps</h3><ul><li><p>Simplified user onboarding by automating the acquisition of necessary tokens and positions and bridging - getting users in the correct state.</p></li><li><p>Automate transaction execution and permission management for their users.</p></li><li><p>Streamlined transactions across multiple chains, reducing the need for integrating and maintaining protocols.</p></li></ul><h3 id="h-for-users" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">For Users</h3><ul><li><p>Declarative Intent-based input would mean users can give their transaction conditions and triggers in natural language too.</p></li><li><p>Automated staking, lending, swapping, social, gaming, and much more based on optimal on-chain conditions.</p></li><li><p>Simplified management of fragmented liquidity across chains.</p></li><li><p>Better security as intent solvers can pick secure protocols and verify execution.</p></li></ul><h1 id="h-theres-more-coming" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">There’s More Coming…</h1><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/948229f06d3c9ada54d66306b47355469cec465a429810603d33e2f759bba0be.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>We’ll share more information about the Epoch Protocol in the coming days.</p><p>We’d love to connect with</p><ul><li><p><strong>developers</strong> who can make dApps and Modules for Epoch Protocol</p></li><li><p><strong>dApps</strong> who want to use intents to simplify user and development experience. Give a smoother experience to users.</p></li><li><p><strong>protocols</strong> who’d like to have their modules in the Epoch Module library.</p></li></ul><p>Follow us on Twitter - <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/0xepochprotocol">@0xEpochProtocol</a> and Join our Discord Community - <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://discord.com/invite/Pd4yZmqYjb">Here</a></p><h1 id="h-support-us-now-and-get-your-epoch-early-supporters-nft" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Support us now and get your Epoch Early Supporters NFT</h1><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://opensea.io/assets/0x7d55A44B9EbD821Ac99C0870D86792c4D65F67c2/0">https://opensea.io/assets/0x7d55A44B9EbD821Ac99C0870D86792c4D65F67c2/0</a></p><p>Give our dApp a try and you can mint the special edition NFT - app.epochprotocol.xyz</p>]]></content:encoded>
            <author>epoch-protocol@newsletter.paragraph.com (Epoch Protocol)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/a07c62083a22b97959af6a9d88f1690319bc8fca10e2a5e1bfd651d5cf10a4b0.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>