<?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 Dove Protocol on Medium]]></title>
        <description><![CDATA[Stories by Dove Protocol on Medium]]></description>
        <link>https://medium.com/@doveprotocol?source=rss-11f15f2bab60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iHkny-Qb1Y7C89VNwdui1Q.png</url>
            <title>Stories by Dove Protocol on Medium</title>
            <link>https://medium.com/@doveprotocol?source=rss-11f15f2bab60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:42:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@doveprotocol/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[What’s next?]]></title>
            <link>https://medium.com/@doveprotocol/whats-next-abd400e057d2?source=rss-11f15f2bab60------2</link>
            <guid isPermaLink="false">https://medium.com/p/abd400e057d2</guid>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Dove Protocol]]></dc:creator>
            <pubDate>Tue, 16 May 2023 19:25:43 GMT</pubDate>
            <atom:updated>2023-05-16T19:25:43.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*55OEuIV22GbAkW-Q.png" /></figure><p>We recently <a href="https://twitter.com/doveprotocol/status/1651706298566692867">announced</a> the open-sourcing the protocol of our v0, the first functional iteration of Dove, currently deployed on testnets.</p><p>Beyond being a dAMM, we want Dove to be a fully permissionless, self-governing and self-running protocol. In order to reach that goal, we have defined the 3 next iterations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1wmAIydreUhnHQfxIEw2jw.png" /></figure><p>We are eager to transition Dove from the testing stage into a fully operational platform. This requires meticulous diligence in reducing potential bugs and vulnerabilities (through rigorous audits) to provide maximum safety for our liquidity providers and traders.</p><p>As a platform of public utility, Dove needs a mechanism for collective decision-making. The responsibility and authority for this governance will be bestowed upon those who contribute and participate in our platform, through a fair distribution mechanism. This arrangement will ensure that the incentives of all stakeholders are perfectly aligned, and the governance mechanism will be deeply interwoven with the platform’s operational fabric.</p><p>Following the establishment of this governance mechanism, we plan to progressively decentralize Dove, ultimately transferring control to our community.</p><p>The commitment and engagement of early contributors and platform users will be duly recognized and rewarded as we grow and evolve.</p><h3>All roads lead to Dove</h3><p>By fixing the liquidity fragmentation issue and the need of bridging liquidity, a wide range of possibilities open up. Protocols won’t need to focus on liquidity of the L2 they want to build on, rather they will be able to select an L2 based on its technical merits.</p><p>We also foresee that Dove will unlock liquidity to execute leveraged LSD strategies on any L2.</p><p><a href="https://twitter.com/DoveProtocol"><strong>Twitter</strong></a><strong> | </strong><a href="https://discord.gg/dYE4qqbjhh"><strong>Discord</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsq6Vy_X_x4bI--aTFjh9g.png" /></figure><p><strong>Unified liquidity, accessible anywhere.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abd400e057d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Dove]]></title>
            <link>https://medium.com/@doveprotocol/introducing-dove-dfd449d4bf21?source=rss-11f15f2bab60------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfd449d4bf21</guid>
            <category><![CDATA[l2]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[amm]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Dove Protocol]]></dc:creator>
            <pubDate>Fri, 27 Jan 2023 22:41:08 GMT</pubDate>
            <atom:updated>2023-01-28T10:55:25.115Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNtcXas2-60wCxWqghSqlg.png" /></figure><p>Dove is a cross-chain AMM. It is our take on the “<a href="https://medium.com/starkware/damm-decentralized-amm-59b329fb4cc3">dAMM</a>” that was conceptualized by both Louis Guthmann and Brett Davos.</p><p>It is based on existing designs of constant function market makers (CFMMs) such as Uniswap v2, Solidly, and others. The main advantage is that it uses cross-chain messaging to allow for trading to take place on multiple chains (Polygon, Optimism, Arbitrum, etc.). This way liquidity stays unified and secure on Ethereum.</p><p>In short ; <strong><em>provide liquidity on L1, trade on L2.</em></strong></p><h3>In the eye of the Dove</h3><p>One of the highest risks in all of DeFi is the risk that liquidity providers incur when bridging their LP tokens outside Ethereum mainnet. Furthermore, the current state of DeFi operates on disjointed AMMs across different chains, which causes liquidity fragmentation across the L2 ecosystem. This leads to a decrease in the amount of available liquidity for trades, resulting in less favorable prices overall.</p><p>Dove aims to address this issue by introducing a protocol that not only offers the same benefits as CFMMs such as lazy LP token management and user-friendly interface, but also enables liquidity to be accessible to swap demand across multiple layers, rather than being limited to just one.</p><p>Contrary to a typical AMM where liquidity and pricing are coupled together, we separate these two. As a result, Dove can operate multiple AMMs for a specific trading pair across different L2 layers, all utilizing the same liquidity sourced from L1.</p><p>This increased capital efficiency benefits both LPs [exposed to more fees] and traders [better prices].</p><h3>What’s to come</h3><p>The asynchronous and cross-chain nature of the protocol introduces new challenges that, in the context of a traditional AMM, are considered trivial. We are still in the process of carefully crafting tests as robust as possible to ensure it is safe to use.</p><p>For its first iteration, we decided to have a limited support of tokens that restricts it to like-assets [stablecoins, ETH, stETH, …].</p><p>It is part of our plans to get the codebase audited, including by a FV team and through public auditing platforms.</p><p><a href="https://twitter.com/DoveProtocol"><strong>Twitter</strong></a><strong> | </strong><a href="https://discord.gg/dYE4qqbjhh"><strong>Discord</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsq6Vy_X_x4bI--aTFjh9g.png" /></figure><p><em>Unified liquidity, accessible anywhere.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfd449d4bf21" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>