<?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 Jin Kwon on Medium]]></title>
        <description><![CDATA[Stories by Jin Kwon on Medium]]></description>
        <link>https://medium.com/@jinghiskwon?source=rss-ae48984c7e68------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4Qa9Aezmg7TSADIBfXnrEw.png</url>
            <title>Stories by Jin Kwon on Medium</title>
            <link>https://medium.com/@jinghiskwon?source=rss-ae48984c7e68------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:06:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jinghiskwon/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[Saga: the Multichain DeFi Home]]></title>
            <link>https://medium.com/sagaxyz/saga-the-multichain-defi-home-d9913d9d5cae?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9913d9d5cae</guid>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[multichain]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Tue, 14 Oct 2025 15:30:15 GMT</pubDate>
            <atom:updated>2025-10-14T16:08:32.853Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYzl-AZhUEAi_yKQKW28Uw.png" /></figure><h3>Introduction</h3><p>The best collateral assets in crypto often do not have the best yield opportunities. Bitcoin is the biggest and most trusted collateral asset in crypto but offers poor yield characteristics. Many other top 20 assets are similar: high FDV with limited utility. At the same time, incredible yield opportunities are rampant in other ecosystems. Foundations and teams mass distribute incentives to increase their TVL and adoption on their infrastructure.</p><p>Trillions in idle value sit locked in assets that earn nothing, while billions in yield incentives flood other ecosystems every day.</p><p>There is significant market opportunity in connecting trusted assets with the best yield opportunities. Traditionally, low yielding collateral owners lend these assets offchain to centralized financial groups. Billions of dollars are made from these opaque deals. However, this introduces counterparty risk, opaque custody, and zero transparency. Everyday users are also locked out.</p><p>Saga solves this — fully onchain. It’s the multichain home where trusted assets earn imported yield at maximum velocity.</p><h3>Importing Trusted Assets and Maximal Yield</h3><p>This spring, Saga launched the <a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">Liquidity Integration Layer</a> (LIL) to solve composability and liquidity fragmentation across the blockchain ecosystem. Through LIL, Saga acts as the connective tissue between yield-rich and liquidity-rich ecosystems, importing trusted collateral from one side and high-performing yield from the other.</p><p>Saga’s Liquidity Integration Layer is built with incredible infrastructure partners and collaborators. <a href="https://cosmos.network/">Cosmos</a> for the base appchain infrastructure and Inter Blockchain (IBC) protocol, <a href="https://www.axelar.network/">Axelar</a> for secure bridging of collateral, <a href="https://www.squidrouter.com/">Squid</a> for efficient routing and intent solutions and <a href="https://threshold.network/">Threshold and tBTC</a> for permissionless deposit and redemption of BTC in DeFi.</p><p>With these partners, the Liquidity Integration Layer unlocks <a href="https://medium.com/sagaxyz/maximizing-saga-protocol-revenue-with-defi-velocity-da1ec0723039">the highest velocity DeFi</a>, a system where capital moves faster, scales further, and compounds harder than anywhere else. Once onboarded, traditionally idle assets like BTC or ATOM plug into Saga’s Velocity DeFi layer and start earning imported yield from ecosystems overflowing with incentives. Saga is the fabric that directly connects trusted assets and maximal yield.</p><p>This is the foundation of Saga’s multichain DeFi thesis: connecting idle collateral to active opportunity. The first expression of this design is the fully onchain carry trade.</p><p>Today, we are happy to announce Saga’s first multichain DeFi product: the fully onchain carry trade, a strategy once reserved for hedge funds, now democratized for anyone with a wallet.</p><h3>Carry Trade Basics</h3><p>Carry trades are one of the most profitable strategies in global markets. They are one of the most proven ways to turn yield differentials into profit. For the first time, Saga is putting them fully onchain and opening access to everyone. The carry trade is a simple concept: borrow cheap to invest in assets that yield high interest rates.</p><p>In the FX market, trillions of dollars are deployed on the USD/JPY carry trade. Borrow Yen at low interest rates, convert the Yen to USD, then earn high USD treasury yields. The investor pockets the difference between USD interest rates and Yen interest rates as profit.</p><p>This strategy is popular and profitable in the FX world because:</p><ol><li>Different currencies have different yield potential</li><li>The exchange rates between currencies typically do not fluctuate dramatically in short time horizons</li><li>There is ample liquidity to borrow currencies</li></ol><p>In short: you borrow low, earn high, and pocket the spread.</p><h3>Carry Trade With Crypto Assets</h3><p>Crypto assets are wonderful candidates for carry trades for similar reasons as FX.</p><ol><li>Cryptocurrencies have varying yield characteristics. For example, assets like BTC and others have zero native yield while stablecoin strategies have large yield potential.</li><li>Stablecoins are designed to have very low price variance with deep liquidity between these stablecoins.</li><li>There are robust lending markets on blue chip assets.</li></ol><p>But here’s the catch: in crypto today, most carry trade strategies are closed-door. Hedge funds and whales run them offchain with counterparty risk, opaque custody, and zero transparency. Everyday users are locked out. That ends now. With Saga, every trader can run strategies once reserved for billion-dollar funds, all fully onchain, with no counterparty risk and no custody compromises.</p><p>Saga is the perfect home for carry trades. The Liquidity Integration Layer enables assets from all across the crypto ecosystems to be deposited as collateral. Saga’s Mustang and Palomino protocols let you borrow against all of these assets like BTC, ETH and other blue chip assets. Thanks to LIL, Saga can seamlessly route liquidity and yield from any ecosystem directly into these carry trade flows. Colt ensures that liquidity is always earning the highest yield available.</p><p>The result: carry trades that are fully onchain, non-custodial, and accessible to anyone.</p><h3>Designing a Fully Onchain Carry Flow</h3><p>A fully onchain carry trade requires two actions: affordable stablecoin borrowing and attractive yield on stablecoins. Let’s dive deeper into each of these flows.</p><h3>Affordable Borrowing</h3><h3>Option 1: Mustang Collateralized Debt Position (CDP) Protocol</h3><p><a href="https://medium.com/sagaxyz/introducing-mustang-decentralized-credit-unbridled-speed-a11cb4a4666d">Mustang</a> is a licensed fork of Liquity V2 and allows users to deposit digital assets like BTC, ETH, or SAGA and take out collateralized stablecoin loans. Liquity V2 is a state-of-the-art CDP protocol that allows users to set collateral ratios (or Loan-to-Value ratio) as well as borrow rates to control costs and enhance capitalization. Mustang is fully onchain and automatic. It requires no manual intervention from any centralized entity or governance to manage the CDP position.</p><h3>Option 2: Palomino Lending Protocol</h3><p><a href="https://medium.com/sagaxyz/palomino-sagas-subsidized-lending-market-for-maximum-capital-velocity-aa87c66a3c9b">Palomino</a> is a high-performance lending market built on the proven Aave v3 framework and fine-tuned for maximum yield and minimal borrowing costs. Palomino plugs into Saga’s high <a href="https://medium.com/sagaxyz/maximizing-saga-protocol-revenue-with-defi-velocity-da1ec0723039">Velocity DeFi System</a> and supercharges adoptions by subsidizing borrow rates on <a href="https://medium.com/sagaxyz/introducing-colt-the-protocol-powering-stablecoin-velocity-e72ae8920372">Colt protocol</a> assets like $D. This means rates can be incredibly low, or even negative. In other words, Palomino can pay you to borrow.</p><blockquote><em>Illustrative Example: A user with $100 worth of BTC can deposit their BTC as collateral and borrow $50 worth of stables (50% LTV) on either Mustang or Palomino with a borrow rate of 5%.</em></blockquote><h3>Maximizing Yield</h3><p>Yield generation on stables is generally heavily subsidized, and the best locations to deploy capital constantly change over time. <a href="https://medium.com/sagaxyz/introducing-colt-the-protocol-powering-stablecoin-velocity-e72ae8920372">Colt protocol</a> is a decentralized stablecoin platform that is fully backed 1:1. A user deposits $1 worth of $USDC, $USDT or $MUST into Colt’s reserve and mints $D. $D is not just a stablecoin, it is a yield-bearing unit of account that automatically redirects collateral into the highest performing opportunities.</p><p>Colt converts the underlying reserve from non-yield bearing stables to secure yield bearing tokens with the best yield. Today, this might be Noon, but next month it may be Ethena. With Colt and $D, users don’t need to constantly shift between different stables to chase after the best yield. With Colt, users never chase yield, the yield chases them. Deploy $D on Saga and always enjoy the best yield in the universe imported into Saga through Colt’s reserve.</p><blockquote><em>Illustrative Example: A user deploys $D on a stable/stable Uniswap pool on Saga (~10–20% yield), a stable/non-stable Uniswap pool on Saga (~30–60% yield), or lends out $D on Palomino (5–10% yield).</em></blockquote><h3>Automating Carry Trades</h3><p>Anyone can take advantage of Saga’s new fully onchain carry trades by combining low cost borrowing opportunities on Mustang and Palomino with the high yield opportunities on Colt assets. To maximize the carry trade potential, actively manage the entire daisy-chained flows and positions. For those who want a more automated flow, <a href="https://medium.com/sagaxyz/the-backbone-of-sagas-defi-engine-introducing-steer-f4a111ea9bce">Steer</a> is a powerful backend automation engine that will automate new carry trades on Saga. Steer automates carry trades so anyone can participate, from DeFi pros to casual users. Together with Mustang, Colt, and Palomino, it completes Saga’s fully onchain yield engine.</p><h3>Conclusion</h3><p>Saga is the new home for multichain DeFi, connecting trusted assets with maximum yield sources. Saga’s multichain DeFi fabric enables a variety of cutting edge new financial primitives. The fully onchain carry trade is the first example. It democratizes access to yield farming strategies privately employed by sophisticated investors.</p><p>Saga is the best home for the fully onchain carry trade because:</p><ul><li>Mustang unlocks CDP-style borrowing</li><li>Palomino drives subsidized lending</li><li>Colt converts liquidity into yield-bearing stables</li><li>Steer automates the flows</li><li>The Liquidity Integration Layer brings in the best assets &amp; yield opportunities across ecosystems to feed these primitives</li></ul><p>Carry trades have generated trillions in global markets. With Saga, they are now open, transparent, and onchain with no custody risk, no gatekeepers, only velocity. Saga is turning passive assets into active capital. Today it starts with the carry trade. Tomorrow, it powers the entire multichain DeFi economy.</p><p>Carry trades are Saga’s first multichain DeFi product, but the playbook is wide open for what comes next as users continue to leverage our primitives.</p><p><em>For further information, follow us on </em><a href="https://x.com/Sagaxyz__"><em>Twitter</em></a><em>, join our </em><a href="https://discord.com/invite/sagaxyz"><em>Discord</em></a><em> and </em><a href="https://t.me/sagaofficialchannel"><em>Telegram</em></a>,<em> and subscribe to our </em><a href="https://www.medium.com/sagaxyz"><em>Medium</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9913d9d5cae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/saga-the-multichain-defi-home-d9913d9d5cae">Saga: the Multichain DeFi Home</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maximizing Saga Protocol Revenue with DeFi Velocity]]></title>
            <link>https://medium.com/sagaxyz/maximizing-saga-protocol-revenue-with-defi-velocity-da1ec0723039?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/da1ec0723039</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[decentralized-finance]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[cryotocurrency]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 13:50:36 GMT</pubDate>
            <atom:updated>2025-07-10T13:50:36.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SJ4MYioJVsIqLpbwIY9UwQ.png" /></figure><p>With the recent <a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">release of Liquidity Integration Layer (LIL)</a>, the Saga ecosystem is shifting from subsidized growth to sustainable protocol revenue.</p><p>The key? DeFi velocity — a measure of how often and efficiently capital moves through protocols. High velocity means more lending, borrowing, swapping, and staking with the same dollar; more yield for users; and more revenue for the protocol.</p><p>Saga is uniquely built to maximize velocity: horizontally scalable chainlets, no gas costs, and application-layer control over incentives. All of our architecture is designed to remove friction and unleash capital flows.</p><p>Infrastructure-level costs like gas introduce friction to DeFi velocity. On the flip side, despite reduced gas costs, Solana is able to facilitate application revenue because its high velocity DeFi environment creates new and better revenue opportunities.</p><p>Saga is designed to take this to the next level. With Saga’s costless transactions and horizontally scalable architecture, DeFi on Saga can achieve unprecedented levels of velocity compared to other ecosystems. Untethered horizontal scalability leads to untethered protocol revenue opportunities.</p><p>In the last month, Saga’s Uniswap V3 deployment registered $800m on DEX volume off of merely $10–15mm USD of TVL. This means DeFi velocity on Saga is orders of magnitude higher than in other ecosystems: TVL is simply utilized more efficiently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Se6rTeckLH6l-AKxgqH29Q.png" /><figcaption>Source: <a href="https://x.com/earnium_io/status/1932813599304806799">Earnium</a></figcaption></figure><p>But we shouldn’t rest on the inherent advantages of our infrastructure.</p><p><strong><em>We can further improve the velocity of our DeFi ecosystem by utilizing the deployed capital on Saga for maximal yield opportunities.</em></strong></p><p>Let’s dive deeper.</p><h3>TVL is Underutilized in Most DeFi Ecosystems</h3><p>Uniswap V3 liquidity providers (LP) deposit USDC and ETH to earn intrinsic yield generated by swap fees. Intrinsic yield is often not sufficient to attract sustainable TVL because there is an opportunity cost associated with the underlying asset that the swap fees need to compete against.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKktKNabbjKaLWRjzq6sGQ.png" /></figure><p>For example, depositing USDC with Circle can earn treasury yield and ETH can be staked to earn staking rewards. The LP has to forgo these opportunities to lock in those tokens in Uniswap V3. Protocols attract TVL using extra incentives like airdrops, reward campaigns, or point programs to compensate for this opportunity cost. While this is a good short-term solution, it is not a sustainable method for long-term growth.</p><p>This opportunity cost creates problems in every DeFi primitive. A lending protocol that takes a deposit of USDC also needs to hurdle over the extrinsic USDC yield.</p><p><strong><em>While individual DeFi primitives could be upgraded to solve the opportunity cost issue, there is a better ecosystem-wide method to solve this problem: a fully backed stablecoin.</em></strong></p><h3>What is a Fully Backed Stablecoin?</h3><p><a href="https://medium.com/sagaxyz/supercharging-on-chain-credit-markets-the-first-subsidized-stablecoin-protocol-comes-to-saga-6f604d1cf765">DTrinity’s</a> fully backed stablecoin protocol mints a stablecoin representing an on-chain collateral reserve. The token is fully backed by an <em>exogenous </em>reserve of other stablecoins and yield bearing assets. This exogenous backing provides stronger stability, diversification, and more sustainable reserve earnings vs. endogenous and algorithmic models. Additionally, by avoiding over-collateralization requirements and ongoing borrowing costs typically associated with minting CDP-based stablecoins, it offers a more predictable cost structure and a different form of capital efficiency for users who prefer fully reserved exposure without liquidation risk.</p><p>For instance, imagine a stablecoin called SAGAUSD that requires USDC for issuance. For every SAGAUSD minted, DTrinity holds collateral that represents 1 USD at all times. Going further, this does not need to be USD-denominated. DTrinity can also issue SAGAETH that requires ETH to mint. The only condition is that for every SAGAETH, there is an asset equivalent of ETH in the reserve. This is what makes DTrinity a “fully backed” stablecoin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9DksSkl5-43b5XkbAzUniQ.png" /></figure><p>These newly minted stablecoins can be utilized as asset bases in Uniswap. Instead of an ETH/USDC pool, we can introduce a SAGAETH/SAGAUSD pool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dRTHP74LfOnR0-L13ru4sQ.png" /></figure><p>How does this help with our underutilization problem? Now that the stablecoins are deployed on Uniswap instead of the underlying asset, the reserve can rehypothecate the asset to earn extrinsic yield (a.k.a revenue).</p><h3>Using the Fully Backed Stablecoin to Internalize Extrinsic Yield</h3><p>Throughout the crypto landscape, there are plenty of yield farming opportunities for base assets such as USDC and ETH. For example, Noble’s USDN is able to earn treasury yield and LIDO staked stETH is able to earn Ethereum staking rewards. If the stablecoin protocol deems these examples safe and equivalent in value, the underlying USDC and ETH can be converted into these assets to earn extrinsic yield.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPduDsINTjhsNtO6tyCGsA.png" /></figure><p>In fact, DTrinity can eventually deploy a more diversified and complex delta-neutral strategy to maximize yield on the underlying reserves. Delta-neutral strategies are good candidates for DTrinity because they keep portfolio value unchanged when small changes occur in the value of the underlying asset. By diversifying across multiple revenue sources, DTrinity can ensure that the underlying capital is optimally utilized.</p><p><a href="https://medium.com/sagaxyz/the-backbone-of-sagas-defi-engine-introducing-steer-f4a111ea9bce">Steer</a> will integrate with DTrinity to automate these strategies and deploy the underlying reserve for optimum yield. Instead of competing against external yield opportunities, Saga as an ecosystem can instead farm these yield opportunities, earn revenue and compound intrinsic yield on top.</p><h3>Rewards Through Protocol Revenue</h3><p>Saga is <a href="https://medium.com/sagaxyz/redesigning-saga-inflation-8ed875192218">redesigning</a> its reward mechanisms from the ground up. Instead of relying on network-level inflation to incentivize participation, Saga is transitioning to application-layer emissions tied to protocol revenue.</p><p>Protocol fees from DTrinity, Liquity V2, and other primitives will be recycled back into the system to incentivize borrowing, deepen liquidity, and strengthen flywheel effects. Intrinsic native yield leads to higher velocity; higher velocity leads to more native yield.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gKiei1YuUE_kK0Jh6aFYQ.png" /></figure><p>This is the path toward reducing inflation to zero, while growing total rewards. Real yield, real sustainability.</p><h3>What About Assets That Do Not Generate Yield?</h3><p>Bitcoin is the largest asset in crypto, and one of the least utilized in DeFi. Unlike staked ETH or yield-bearing stables, BTC sits idle. No more: Saga is bringing high-velocity DeFi to BTC.</p><p>Through our exclusive license to deploy Liquity V2, we’re introducing a full-scale BTC-backed collateralized debt position (CDP) system on Saga’s high-velocity EVM chain. Liquity V2 is a decentralized borrowing protocol that lets users mint a stablecoin by collateralizing risky assets like BTC, ETH and SAGA with user-set interest rates.</p><p>BTC holders can now mint stablecoins using their BTC as collateral, and daisy chain those stables into DTrinity to earn real yield, turning non-productive assets into yield-bearing capital. Steer will be utilized to create more complex structured products that automate this “daisy chaining.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fAg5h2evHnf3R2nyVlI5qA.png" /></figure><p>This isn’t theoretical. It’s coming to Saga mainnet this summer.</p><h3>Liquity + DTrinity + Steer Combination Lays the Foundation for Onboarding Sustainable High Velocity DeFi</h3><p>This Liquity, DTrinity and Steer combination is incredibly powerful. In some market conditions, internal yield from within the Saga ecosystem may be better. In other market conditions, external yield will be more rewarding. By utilizing these three primitives, the Saga ecosystem can guarantee maximal utilization of TVL and maximize protocol revenue. <strong><em>Every asset entering Saga with a yield bearing equivalent can be deposited into DTrinity to earn the optimal yield. Assets entering Saga without a yield bearing equivalent can be converted into a yield bearing asset via Liquity.</em></strong> Steer automates the interdependencies as well as yield optimization for all the assets. Maximizing the utilization of the deployed TVL on Saga will lead to higher velocity and (as a flywheel) more protocol revenue.</p><p>This protocol revenue engine isn’t just powerful, it’s extensible. It lays the groundwork for every future DeFi primitive deployed on Saga.</p><p>As new projects, whether perpetuals, CLOB DEXs, or novel financial protocols, attract TVL into the ecosystem, that capital can be routed through Liquity, DTrinity, and Steer to generate yield at the protocol layer.</p><p>That revenue, in turn, can be used to <strong>incentivize liquidity, subsidize usage, and compound velocity</strong> across those same projects. It’s a self-funding, self-reinforcing loop — one where every new protocol deployed on Saga becomes both a beneficiary and a contributor to network-wide growth.</p><h3>Conclusion</h3><p>The next evolution of Saga isn’t about pure infrastructure. It’s about DeFi velocity, protocol revenue, and economic orchestration.</p><p>Through deep partnerships with DTrinity, Liquity, and Steer, we’re rolling out the building blocks of a fully self-sustaining DeFi economy:</p><ul><li>Stablecoins backed by real yield</li><li>Borrowing powered by volatile assets like BTC</li><li>Backend automation to deploy capital at scale</li></ul><p>This is a first-of-its-kind system, a concert of protocols deployed in tandem to engage in decentralized business like never before.</p><p>If you’re building in DeFi, or Web2 business and want to integrate DeFi rails, come see how these novel and integrated building blocks can supercharge your revenue and opportunities!</p><p>And it’s not just about building apps. This changes Saga’s economic posture from push to pull. No more paying users to come. Instead, capital comes for the yield, and the protocol profits when it flows.</p><p>Protocol revenue becomes the engine, not just for staking rewards, but for long-term growth, community funding, and network expansion.</p><p>It starts this Summer.</p><p><em>For further information, follow us on </em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f980c1ce33&amp;e=4c17c9cc64"><em>Twitter</em></a><em>, join our </em><a href="https://discord.com/invite/sagaxyz"><em>Discord</em></a><em> and</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64"><em> Telegram</em></a>,<em> and subscribe to our </em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"><em>Medium</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da1ec0723039" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/maximizing-saga-protocol-revenue-with-defi-velocity-da1ec0723039">Maximizing Saga Protocol Revenue with DeFi Velocity</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Saga Inflation]]></title>
            <link>https://medium.com/sagaxyz/redesigning-saga-inflation-8ed875192218?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ed875192218</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 17:05:45 GMT</pubDate>
            <atom:updated>2025-06-16T17:05:45.289Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KJfPqA4jg9wCzuguH_fPrA.png" /></figure><h3>Introduction</h3><p>Saga and many other Cosmos SDK-based chains currently utilize the default inflation and staking reward distribution mechanisms implemented directly on the network layer. Codifying operations such as staking reward distribution directly on the network layer has significant drawbacks. Because the network layer is responsible for securing the network, any modifications to the network layer involve a slow and methodical process to guarantee safety. This slows innovation and removes experimentation for key primitives on the chain.</p><p>For example, every Cosmos-based chain has issues stemming from vesting wallet balances receiving liquid staking rewards. The solution seems simple: lock staking rewards from the vesting wallet. However, because both the vesting wallet and staking implementation are intertwined on the network-layer, modifying this codebase is surprisingly tricky. Even though the solution is conceptually simple, it has taken years to get a potential implementation out (See Celestia’s ongoing <a href="https://github.com/celestiaorg/CIPs/pull/253">CIP</a>).</p><p>What if this implementation has unintended consequences and needs modifications? Furthermore, there are countless other ways to modify and experiment with the inflation distribution mechanism. If all these experiments were to be implemented on the network level, optimizing the flows could take years. This is too slow for Saga. We propose a more elegant solution.</p><p>Recently, Saga <a href="https://www.coindesk.com/press-release/2025/02/24/saga-launches-liquidity-integration-layer-lil-revolutionizing-cross-chain-liquidity">launched</a> the Liquidity Integration Layer (LIL), a unified DeFi layer that connects all Saga Chainlets. LIL gives Saga access to a robust EVM application layer.<strong><em> Instead of utilizing the network layer, Saga’s inflation and reward mechanism can utilize LIL to distribute rewards in the application layer.</em></strong> This blog introduces the new Saga inflation and rewards mechanism redesign aimed to improve Saga’s DeFi environment and accelerate adoption.</p><h3>Saga Inflation Redesign</h3><p>Network inflation is typically used to incentivize specific behavior in an ecosystem. In the case with Proof-of-Stake networks, the inflation is used as a carrot to convince users to stake their tokens to help secure the network. Each staked token is locked and inaccessible to a potential attacker, rendering the network more secure. The downside to network staking is that it is unipurpose: it only contributes to network security.</p><p>However, in a network with more complex applications on the application layer, network staking becomes a smaller and smaller contributor of network security. For example, every token locked in a DeFi vault long-term serves a dual purpose: contributing to DeFi economic activity and network security because those tokens are also inaccessible. Therefore directing inflation only to network staking limits the ecosystem’s growth potential.</p><p>One of the goals of this redesign is to migrate inflation to the application (or Chainlet) layer. On the Saga mainnet, the only operation that inflation can incentivize is staking. Post-LIL, a richer set of activities exists on the Chainlet layer. We want these activities to also help secure the network, similar to “proof of liquidity.” To facilitate this, the inflation and rewards mechanism needs to de-couple from the Saga mainnet and extend up to the Chainlet layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cEPhvKgkFb_8Ou5a" /></figure><p>The basic architecture is simple: instead of distributing inflation to stakers on the mainnet, we will move the distribution upstream to incentivize specific activity on our Chainlets. In fact, we already prepared this transition by onboarding <a href="https://app.merkl.xyz/?chain=5464">Merkl</a> on the SagaEVM chainlet. The next steps are to transition the inflation mechanism to fund the incentives.</p><p>We can attempt to get the perfect solution by automating this incentive distribution. However, any kind of automated solution we build today is unlikely to be nimble enough to support the experimentation we will want as more DeFi primitives come on Saga. To move efficiently, we propose the following adjustment to the chain parameter:</p><ul><li><strong>Fix the inflation rate to 3%: </strong>The current inflation is tied to the stake rate. If we are to incentivize other activities besides staking, it makes little sense for stake rate to control inflation. We preserve the ability to adjust this parameter in the future with a governance vote.</li><li><strong>Set community tax to 100%: </strong>This means 100% of the inflation will now directly pipe into the community pool, while 0% gets distributed via the Cosmos distribution module.</li><li><strong>Give authorization for a representative (the Saga Foundation for now) to distribute the community pool: </strong>This is to run incentive experiments and will eventually be automated.</li><li><strong>Remove automatic slashing: </strong>Oftentimes, we find the automatic slashing for validators and stakers too rigid. In the vast majority of cases, jailing the problematic validator is sufficient. If an attacker causes the network to halt, they can be slashed upon network restart or via a governance vote.</li></ul><p>Let’s dive deeper into how these changes affect various stakeholders in the ecosystem today.</p><h3>How This Affects Stakers</h3><p>Today, there are two reward flows for stakers: 1) on-chain Cosmos inflation and 2) recurring airdrops via <a href="https://claim.airdrop.saga.xyz/">loyalty vaults</a>. However, the reality is that the loyalty vault is also (mostly) funded by inflation as well, albeit indirectly. The Saga Foundation currently stakes a large portion of the ecosystem and Foundation allocations to help secure the network. However, this means the majority of the inflation is distributed to the Foundation. The Foundation simply redistributes this back to stakers via vaults. This flow is roundabout and unnecessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pyEBksH43t6lv-uI" /></figure><p>Having rewards split in this fashion also creates unintended consequences. For example, Saga vaults specifically exclude any vesting VC and team wallets. However, the vesting wallets are still able to collect base staking rewards directly from the network.</p><p>With this proposed change, we simplify this flow. Stakers will now collect their reward from a single source: Saga’s vaults funded by the community pool. This also means that <strong>any vesting wallets will cease to collect all staking rewards</strong>, as they will be excluded from vaults.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eH0XrU11ewSoyPXA" /></figure><p>Recently, we adjusted our vault rewards to separate out base staking activity vaults and loyalty vaults in preparation for this transition. The on-chain inflation that stakers claim via the <a href="https://wallet.keplr.app/?tab=staking">Keplr staking dashboard</a> will transition over to our staking activity vaults. The loyalty vaults will continue as before. Therefore, for most stakers who participate in our vaults, this transition should not change much. Instead of claiming staking rewards on Keplr AND vault rewards, simply claim both on the vault rewards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uzYitYwwprIOwQ0z" /></figure><p>After this initial transition, the Saga team will explore automating the claims and distribution process for our vaults. We started this transition by onboarding Merkl. With access to Saga’s robust application layer, Merkl is able to automate the claims and distribution of rewards for liquidity providers (LP). Saga plans to transition the staking vaults into a similar model to facilitate easier claiming and distribution. More will be shared in a future post.</p><h3>How This Affects Validators</h3><p>The biggest change to this flow is to the validators. Currently, validators rely upon inflation and their commission to earn their revenue. This actually causes a lot of headaches for validator economics because every component of their distribution is variable. A validator’s share of stake is variable; the inflation rate is variable and their commission is variable. Experimenting with validator reward structures is nearly impossible because all of these are codified directly on the network layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uHJxJB0JCM3-yDnt" /></figure><p>Also, validator compensation for essential chain services like operating relayers and block explorers ends up following a very indirect path. The agreements are denominated in Foundation delegations, but the actual compensation to the validator will constantly vary based on inflation and commission set by the validator. This is very awkward.</p><p>Instead, we propose bypassing this entire mechanism and paying the validators directly from the community fund. This way, the delegate representative in control of the community fund can experiment with the validator incentive mechanism more freely.</p><p>For example, the initial validator compensation model we would like to implement is as follows:</p><ul><li>From the total inflation into the community fund, a certain amount is diverted for validator compensation.</li><li>Each validator receives a fixed base amount (dollar denominated) to compensate for validator operations costs.</li><li>The Foundation will budget grants categories based on certain infrastructure needs such as “operating the most used explorer” or “top 3 relayer operators to these external networks”.</li><li>The remaining budget will be distributed based on the validator’s stake percentage.</li></ul><p>After this initial transition, the Saga Foundation will continue to experiment with validator compensation mechanisms. Once the mechanisms are settled, the goal is to eventually codify this (like our other incentives), in our application layer.</p><h3>Conclusion</h3><p>Once these initial changes are implemented, the Saga ecosystem can expect faster token economic experimentation that aligns better with a growing Saga ecosystem. While a coordinator will initially run and design these experiments, these flows, in the long run, will be implemented and automated on-chain using Saga’s innovative LIL and Chainlet technology. Saga’s inflation mechanism can utilize the vast array of EVM-compatible smart contracts and protocols, leading to better tokenomics.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ed875192218" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/redesigning-saga-inflation-8ed875192218">Redesigning Saga Inflation</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First Uniswap V3 Appchain Launch: Next Chapter in Saga’s Multichain Revolution]]></title>
            <link>https://medium.com/sagaxyz/the-first-uniswap-v3-appchain-launch-next-chapter-in-sagas-multichain-revolution-c6f81ecee011?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6f81ecee011</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[uniswap]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Fri, 20 Dec 2024 18:26:39 GMT</pubDate>
            <atom:updated>2024-12-20T18:32:24.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIekwRF30RzltBoeXg8UYQ.png" /></figure><p>The Uniswap protocol is coming to Saga. <a href="https://gov.uniswap.org/t/rfc-saga-l1-application-for-canonical-uniswap-v3-deployment/25008">Earlier this month</a>, Uniswap V3 was deployed on Saga’s natively multichain protocol. Instead of deploying on a shared L1 or L2 environment, the Uniswap protocol is deployed on a dedicated appchain (a Chainlet named “Sagaevm”) with only Uniswap-related smart contracts. It looks and feels like any other Uniswap deployment. However, this Uniswap V3 deployment is a historic first — marking the first inaugural canonical Uniswap appchain. Traditionally, deploying an application on its own appchain takes multiple months of development, coordination and significant UX challenges in bridging and routing.</p><p>On Saga, launching an appchain is table stakes. By utilizing <a href="https://docs.saga.xyz/">Saga’s platform</a>, the Sagaevm Chainlet was deployed in less than two minutes. The Sagaevm Chainlet leverages <a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">Saga’s Liquidity Integration Layer (LIL)</a> to automate bridging and routing infrastructure deployment, solving liquidity fragmentation in a natively multichain environment. For DeFi protocols, deploying on a Saga appchain comes with significant benefits.</p><p>First, Saga’s native multichain protocol offers significant DeFi scalability. The Uniswap deployment is able to consume the entire blockspace capacity of the Sagaevm Chainlet without other application transactions clogging the network. When demand is even greater, different asset pairs can be deployed on different chainlet instances, horizontally scaling across multiple parallel chainlets. Deploying a second Uniswap V3 Chainlet is instant and automatic.</p><p>Second, by leveraging Saga’s unique <a href="https://sagaxyz.cdn.prismic.io/sagaxyz/d396b945-52ed-41d5-afef-ee27c6a8a233_Saga+-+Token+Mechanism+%26+Incentives+-+Dark+Version.pdf">token economic design</a>, users of Uniswap on Saga are able to transact without gas payments. We utilize <a href="https://medium.com/sagaxyz/stack-exploder-unblocking-web3-products-with-costless-transactions-387b9f03b7c5">recycled gas tokens</a> to open a truly costless transaction experience, opening doors to broader adoption and improved usability.</p><p>Finally, improvements and customizations to the underlying chain infrastructure can be deployed much faster than on a generalized L1/L2.</p><p>Many projects have attempted appchain automation but have ultimately failed to gain significant traction. This is because simply automating the deployment of the blockchain is not enough. A successful appchain launch requires so much more: security provisioning, service on boarding, and bridging/liquidity.</p><p>On Saga, any application traditionally deployed on a shared L1 or L2 environment can be migrated and deployed as an appchain instantly. How does this work? Let’s dive deeper into the various Saga innovations that unlock this magic.</p><h3>Saga Platform Automates Launching Appchains</h3><p>Saga set out to solve a significant hurdle for decentralized appchains (dApps): network security. Typically, launching an appchain involves a lengthy, intricate process — creating a staking token, designing a tokenomics system, onboarding validators, and convincing stakeholders to support the network. Saga, however, simplifies this months-long process into a single, on-chain transaction.</p><p>Saga’s solution, a fully decentralized proof-of-stake (PoS) platform, enables developers to <a href="https://medium.com/sagaxyz/launch-your-first-saga-chainlet-99541cc35ffa">launch appchains without the need for extensive technical setup</a>. A developer can request a “chainlet” on Saga, and the platform automatically initiates a decentralized PoS chain, supported by Saga’s validators, simplifying the onboarding process while maintaining security and scalability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i40d8szogBleYL7K" /></figure><p>Saga is able to efficiently launch hundreds and thousands of appchains on-demand because Saga’s technology stack is fully vertically integrated and each chainlet launched is homogeneous. With EVM being the most popular and requested, we have partnered with Altiplantic, the <a href="https://evmos.org/">Evmos</a> Core Development Team, to build out the Evmos stack for Saga. With the latest version of Evmos, developers on Saga are able to take advantage of cutting edge technologies such as <a href="https://medium.com/evmos/evmos-introduces-native-tokens-as-erc-20-for-cosmos-1a4c7de5c3e9">Cosmos Native Tokens as ERC-20</a> and <a href="https://medium.com/evmos/evm-extensions-deep-dive-a132bee901b9">EVM Extensions</a>. These key innovations enable EVM smart contracts on Saga to directly interact with Cosmos interoperability and sovereignty innovations like the InterBlockchain Communication (IBC) protocol. Utilizing the Evmos technology results in the merging of two great technology stacks: Cosmos and Ethereum. <strong>TL;DR: With Evmos, EVM-level innovations will be coming to Saga faster.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dmwoLk5lzoFRWyS7" /></figure><p>Many projects have attempted appchain automation but have ultimately failed to gain significant traction. This is because simply automating the deployment of the blockchain is not enough. A successful appchain launch requires so much more: security provisioning, service onboarding, and bridging/liquidity. Saga’s vertically integrated stack with homogeneous appchains automates all parts of launching an appchain, including access to liquidity.</p><h3>Saga Liquidity Integration Layer (LIL) Automates Bridging and Routing</h3><p>Launching appchains with siloed economies is not particularly useful. A robust multichain ecosystem requires both easy appchain deployment as well as automatic liquidity rails. Earlier this year, <a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">we announced LIL</a>, Saga’s answer to solving fragmented liquidity. In addition to automatically provisioning the underlying blockchain, Saga automates the launching of all liquidity rails including bridging required for a successful appchain. With <a href="https://www.mintscan.io/saga/proposals/9">mainnet 0.2</a>, LIL is almost here and ready to be deployed. Once LIL is released, every chainlet will have automatic bridges set up to all other chainlets as well as other ecosystems such as Ethereum, Polygon, Solana, etc. Once the bridges are set up, efficient routing is needed to make LIL easy to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qFV076oKCybcklIj" /></figure><p>We partnered with the <a href="https://www.squidrouter.com/">Squid</a> team to automate cross-ecosystem and cross-chainlet routing across LIL. This means that any application that has integrated with Squid will be able to natively support Saga and LIL. For example, <a href="https://oku.trade/">Oku</a>, a popular front end for Uniswap V3, is able to onboard the Saga appchain version of Uniswap V3 as easily as Uniswap V3 on a shared L1/L2 because Squid is natively integrated with LIL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gFX4Mb8IZxPXIuHB" /></figure><p><a href="https://x.com/squidrouter/status/1864366575534657789">Squid also recently announced Coral</a>, their cross-chain intent solution, that makes multichain transfers significantly cheaper. By integrating Squid, Saga will have direct access to significant routing improvements and innovations from the Squid team. <strong>TL;DR: With Squid, routing innovations will be coming to Saga faster.</strong></p><h3>Saga Token Economics Enables Gasless Uniswap Experience</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bud56WNs9BzDsg3h" /></figure><p>Saga has a unique <a href="https://sagaxyz.cdn.prismic.io/sagaxyz/d396b945-52ed-41d5-afef-ee27c6a8a233_Saga+-+Token+Mechanism+%26+Incentives+-+Dark+Version.pdf">token mechanism and incentives</a> design that does not collect gas from end users. Instead 100% of gas is returned to the chainlet owner’s wallet address. Using this property, Saga is able to implement truly costless transactions using <a href="https://medium.com/sagaxyz/stack-exploder-unblocking-web3-products-with-costless-transactions-387b9f03b7c5">recycled gas tokens</a>. The Sagaevm Chainlet takes a generic valueless gas token called “Gas” that no one owns. Uniswap users on Saga will interact with Uniswap normally and sign a transaction that requires this Gas token. In the background (unbeknownst to the user), a faucet will pay the Gas token on behalf of the user. This Gas token is used for the transaction and returned back to the faucet (hence recycled). <strong>TL;DR: With Saga, token economic experiments will come to Uniswap V3 faster.</strong></p><h3>Saga Powers the Best Uniswap V3 Experience</h3><p>The first appchain instance of Uniswap V3 is on Saga due to an incredible collection of innovations. A natively multichain implementation of Uniswap enables incredible new experiences for developers and end users alike.</p><ul><li>Launch a new app chain, mint a new meme token, and instantly list on Uniswap V3 without needing to spin up any bridges</li><li>Bring in assets from other ecosystems like $ETH from Ethereum and swap on the Uniswap V3 Chainlet without paying any gas fees</li><li>Launched a game where users interact with $ETH and $USDT? Automatically tap into liquidity in the Uniswap V3 Chainlet and allow users to freely move between different assets</li></ul><p>In fact, this is not unique to the Uniswap protocol. Any smart contract deployed on a L1/L2 is able to be deployed as an appchain instantly on Saga to upgrade to appchain class product experiences.</p><h3>Conclusion</h3><p>It is inevitable that every application will be on its own appchain(s). However, previous iterations of appchains have had difficulty gaining mass adoption: the barrier to entry was too high. Saga is the only integration solution that fully automates appchains. Launching an appchain using Saga is simpler than deploying a smart contract. If you are interested in upgrading an existing smart contract to an appchain, come join the movement with Saga.</p><p>To learn more about the Saga protocol, check out our <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fwww.saga.xyz%2F&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=website&amp;index=2&amp;md5=ce25c973c1e2b7b9c051dfdaed73bae3">website</a>, <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fsagaxyz.cdn.prismic.io%2Fsagaxyz%2F08e727f2-88a2-4c95-ad17-b0b9579d2b69_saga-litepaper-march-2022.pdf&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=litepaper&amp;index=3&amp;md5=bf95fe834b6f230fd1826e59957bdb96">litepaper</a>, and <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fdocs.saga.xyz%2Fintroduction%2Fcassiopeia-overview&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=developer+documentation&amp;index=4&amp;md5=362d532a77b1b33dc0e8becca80c1068">developer documentation</a>. Be sure to join Saga’s <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fdiscord.com%2Finvite%2FUCRsTy82Ub&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=Discord&amp;index=5&amp;md5=e9e4e0fdbb9e5672a72c8e8ecc704ea7">Discord</a> and <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Ft.me%2Fsagaofficialchannel&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=Telegram&amp;index=6&amp;md5=fef085cf609cd988b5a25f4014ed8ade">Telegram</a> and follow Saga on <a href="https://cts.businesswire.com/ct/CT?id=smartlink&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Ftwitter.com%2Fsagaxyz__%3Flang%3Den&amp;esheet=53912146&amp;newsitemid=20240319541440&amp;lan=en-US&amp;anchor=Twitter&amp;index=7&amp;md5=4fc83c43a9bde444c0b1743ddaf785ea">Twitter</a> for the latest news and updates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6f81ecee011" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/the-first-uniswap-v3-appchain-launch-next-chapter-in-sagas-multichain-revolution-c6f81ecee011">The First Uniswap V3 Appchain Launch: Next Chapter in Saga’s Multichain Revolution</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Saga Liquidity Integration Layer]]></title>
            <link>https://medium.com/sagaxyz/saga-liquidity-integration-layer-40c2bab04d4b?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/40c2bab04d4b</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Mon, 09 Sep 2024 17:00:26 GMT</pubDate>
            <atom:updated>2024-11-19T00:54:29.624Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part II: A New Era in Blockchain Economics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vTo3_u7lnmh8UNPhZoCQRA.png" /></figure><h3>Introduction</h3><p>In Saga <a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">Liquidity Integration Layer Part 1</a>, we examined liquidity fragmentation plaguing the blockchain ecosystem today. Chains with different technology, stakeholders and economic incentives lead to composability erosion between applications and fragmented liquidity. Saga’s Liquidity Integration Layer (LIL) solves the liquidity fragmentation issue by introducing cross-chain composability into the Saga ecosystem. With the Liquidity Integration Layer, the Saga protocol controls both the block production and the liquidity rails. With this combination, Saga can adopt a powerful new liquidity-centric economic model never seen before in blockchain.</p><h3>What is a Liquidity-Centric Economic Model</h3><p>Most blockchain infrastructure depends on gas for protocol revenue and value accrual, forcing gas and transaction fees to be a necessary part of the user experience. However, a gas-based user experience leads to a poor user and developer experience. A gas-centric economic model stifles experimentation and innovation and curtails adoption. Saga’s liquidity-centric economic model opens the door to a new method of token accruals that solve for the problems introduced by gas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q9XL35XhGYCh_7kX" /></figure><blockquote>A liquidity-centric economic model is conceptually simple and can be summarized in a single sentence: Saga generates protocol revenue by taking a cut of all liquidity and value flowing through the LIL.</blockquote><p>Because Saga’s LIL automatically connects every chainlet and chains outside the Saga ecosystem together in a convenient product, the Saga protocol can essentially take a cut of all economic activity generated by all applications on Saga.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ACg3g4XeUfQnJxNO" /></figure><p>The potential protocol revenue and value accrual opportunity for Saga is many multiples larger using the liquidity-centric economic model vs. a gas-based toll economy. This enables the protocol to derive value exclusively from the liquidity layer instead of infrastructure costs (and gas). This is Saga’s liquidity-centric economic model. Let’s dive deeper.</p><h3>The Downsides of a Gas-Centric Economy</h3><p>Traditionally, blockchains utilize a gas-centric token economic system. To interact with applications on the blockchain, users must first acquire a native gas token and pay the validators (and their stakers) to include their transaction on the blockchain. A gas-centric token economic system leads to user experience problems that stifle growth and adoption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z-UP6dpgUjqSGL9a" /></figure><p>First, a gas-centric token economic system forces users to acquire and hold sufficient gas balances prior to interacting with the network. This creates an adoption barrier where applications must train users to hold an arbitrary token not related to their application. This inconvenience is repeated on every chain that the application is deployed on.</p><p>Second, a gas-centric token economic system leads to unpredictable and expensive transaction costs due to market-driven rates. Market-driven gas prices create artificial barriers in the exact moment an application begins to gain traction. The network should promote and encourage popular new applications. Instead, gas-based economic systems increase costs and barriers to adoption.</p><p>Third, the gas fee is a net outflow from the users to the network at all times. In a typical product adoption journey, the point where mass adoption begins and when profitability is achieved is usually two different time periods. In the real world, platform costs related to early growth are often subsidized by the platform while monetization begins after the network effects are achieved. However, when the network realizes protocol revenue indiscriminately without considering the application’s adoption goals, it creates automatic barriers to early growth periods for applications deployed on the network. Significant usability and adoption issues emerge when a transaction with zero or low value costs the same as a million dollar transaction.</p><p>Large amounts of experimentation with new applications is paramount to network effects and mass adoption. Why did the memecoin experiment explode on Solana? Solana’s cheap transactions enable new builders and applications like pump.fun to flourish. However, this is only possible as long as the infrastructure can meet or exceed the demands for its blockspace. Solana is still a gas-based economic model, after all. When demand skyrockets, it is inevitable that Solana’s gas prices will also rise, leading to the same problems as other gas-based ecosystems.</p><p>By doing away with a gas-centric economic model, we can do much better. We can design a new economic model that can giga-charge experimentation as well as maximize protocol revenue in Saga.</p><h3>Designing a Better Economic Model</h3><p>Saga’s liquidity-centric economic model is designed from the ground up to enable exponential ecosystem growth. In the technology industry, successful platforms already utilize well-established playbooks that leverage network effects to grow the total size of the pie: successful projects lead to more new projects, which leads to more successful projects over time.</p><p>It all begins with the platform maximizing its reach by subsidizing and removing initial costs to new developers. This opens the door to huge amounts of experimentation. The platform supplies these developers with the best tools to succeed and make businesses of their own on top of the platform. Once these developers begin to earn money, the platform shares in the upside of the value built on top of the platform. These platform revenues are recirculated to bring in new developers into the ecosystem.</p><p>Saga’s liquidity-centric economic model maximizes the Saga ecosystem and value for the Saga protocol by utilizing the same playbook tested in the technology industry today:</p><ul><li>Maximize experimentation by making Saga free or very cheap to get started</li><li>Maximize project success by supplying developers with the best tools to succeed, even without monetization potentials</li><li>Maximize shared upside when projects do monetize</li></ul><h3>Maximizing Experimentation with Zero-Cost Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ia99IN5Yf8tuVG0S" /></figure><p>The first phase of Saga’s new token economic model is intended to attract as much experimentation within Saga as possible. Counter to most blockchain ecosystems, Saga is designed to make infrastructure costs cheap or close to free. Saga’s token economic system is divided into the front end (user to application developer) and back end (application developer to Saga). A full description of this mechanism can be found in our <a href="https://sagaxyz.cdn.prismic.io/sagaxyz/d396b945-52ed-41d5-afef-ee27c6a8a233_Saga+-+Token+Mechanism+%26+Incentives+-+Dark+Version.pdf">token paper</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5_XtHI4YFDN91qwn" /></figure><p>On the back end, the developer directly pays the validators for spinning up and maintaining the chainlet. These chainlet fees are designed to be commoditized similar to an AWS instance.</p><p>On the front end, Saga does not charge any gas fees to the end user. Unlike other gas-centric token economic systems, all transaction fees from the users can be denominated in any token and are 100% returned back to the developer. This allows the developer to offer a completely costless blockchain experience for their users using <a href="https://medium.com/sagaxyz/stack-exploder-unblocking-web3-products-with-costless-transactions-387b9f03b7c5">recycled gas tokens</a>.</p><p>In the early stages of product development, experimentation is key. Access to blockchain infrastructure that is affordable and easily accessible is vital to early-stage projects. Saga’s protocol revenue can be used to help reduce (and potentially remove) chainlet costs for new projects. This flow creates a healthy dynamic where profitable projects are subsidizing infrastructure costs for new projects. Lowering the barriers to entry leads to more building and experimentation, which leads to more successful projects that eventually subsidize costs to future new developers.</p><p>Unlike other gas-based blockchain ecosystems that demand new applications to generate revenue immediately, Saga’s token economic design creates an environment where applications are not pressured to generate protocol revenue from the very beginning. The developer can focus on making their application the best application for their users or trying several different iterations on the way to product-market fit.</p><p>By incentivizing experimentation, Saga will become the hub for new and wild app ideas in the web3 ecosystem. If pump.fun on Solana was a thrilling ride, imagine the fast pace of innovation in a system with zero-cost infrastructure.</p><h3>Maximizing Project Success</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tV5kGhLQFMSRdrym" /></figure><p>From the pool of wild and experimental applications, a handful of projects will hit product-market fit and transform into a revenue-generating application. The next phase of Saga’s economic model is intended to convert as many of the experiments to successful projects as possible. The Saga protocol uses its protocol revenue derived from the LIL to help bootstrap new applications and ensure the projects are as successful as possible through all stages of the project lifecycle.</p><p>In the early stages, liquidity bootstrapping is vital for successful projects. The LIL can offer liquidity matching and incentive programs where the protocol itself bootstraps and matches any liquidity procured by the project and community. For example, imagine a new up and coming token on Saga called $PUMP. Theoretically, an up-and-coming application that needs liquidity bootstrapping should also see $PUMP volume increase across the LIL as users across the ecosystem move the tokens to and from DEXes. These LIL cross-chain transactions will slowly accumulate $PUMP tokens as well as $SAGA and other stablecoins from the LIL rakes. These balances can be used to seed and match liquidity in the ecosystem.</p><p>A healthy ecosystem is one with healthy liquidity. By dedicating protocol revenue to protocol-owned liquidity, the Saga protocol can participate in yield-farming opportunities and grow alongside the ecosystem.</p><p>The Saga protocol also helps in user acquisition. Saga has been executing and improving on the Power Level Over 9000 airdrop campaigns to cross-seed communities across the Saga ecosystem, ensuring the growth of the ecosystem as a whole. The more successful applications there are on Saga, the more economic activity there is in the ecosystem and ultimately more revenue for the Saga protocol.</p><p>Over the lifecycle of projects deployed on Saga, the protocol can deploy resources in other destinations such as NFT marketplaces, lending markets, stablecoins, and other DeFi primitives, depending on the needs of the projects and ecosystems. Protocol participation in the ecosystem not only builds successful applications, but also enables successful DeFi projects to emerge in the ecosystem that draw from the liquidity locked in LIL. With Saga’s liquidity-centric economic model, Saga is not only able to grow with the revenue of these DeFi platforms but also introduce new ways to lock and utilize $SAGA tokens in the ecosystem.</p><p>By lending support to applications when they need it the most, Saga will become the hub for the most successful projects in the web3 ecosystem.</p><h3>Maximizing Shared Upside</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Zr6RnqIty1FNyQ2a" /></figure><p>The final phase of Saga’s economic model is where Saga realizes protocol revenue. Accruing value by charging gas is not a value-maximizing strategy. Protocols should optimize for application and ecosystem success, then share in the upside of each application’s success. This is beneficial because shared upside in successful projects is potentially many orders of magnitude more valuable than a small fee from many unsuccessful projects.</p><p>On Saga, an application is able to get started on a chainlet for cheap. However, as soon as any tokens are bridged across the LIL, Saga takes a small cut of all activity flowing through the LIL. An experimental new project gets access to the Saga LIL essentially for free because a small cut of their experimental new token is worth nothing. The LIL continues to accrue balances of all experimental tokens flowing through the LIL, some of which are expected to become incredibly valuable.</p><p>At this point, Saga protocol can determine a plan for the (now valuable) tokens. As discussed in the previous sections, accrued protocol revenue is recirculated in the Saga ecosystem to maximize experimentation and project success. There’s a myriad of additional combinations and policies the Saga protocol can execute with the revenue balances:</p><ul><li>Retain as protocol treasury</li><li>Deploy to accrue further revenue on the held assets through DEX, lending, etc.</li><li>Sell to fund various initiatives in the Saga ecosystem</li><li>Buy and burn, reducing the total supply of Saga tokens</li><li>Distribute as airdrops to continue to grow the project and Saga ecosystem</li></ul><p>All these policies drive greater network effects on Saga. Successful projects lead to more new projects, which lead to more successful projects over time. By accruing value when the applications are successful, Saga will become the hub for the greatest value accrual in the web3 ecosystem.</p><h3>Readying the Crypto Revenue Model for Mass Adoption</h3><p>How do we know if this economic model will be successful? We know because this has already been proven in the real world. Apple’s iPhone App Store is a perfect implementation of a successful economic model that follows the same design principles. The App Store is a vibrant ecosystem with millions of applications. The App Store has developed a new class of revenue-generating mobile apps, all while raking in billions of dollars for Apple. How did Apple do this?</p><p>First, Apple lowers barriers to entry for developers to attract a massive developer base. Application developers can gain access to the full iPhone ecosystem without paying practically anything. This promotes experimentation since anyone can develop new applications, which leads to more competition, driving better applications to bubble up in the App Store. Today’s experimental apps are tomorrow’s Candycrush.</p><p>Second, Apple supplies all developers with the tools to build the best applications, even without monetization potential. Apple does not force developers to monetize their products. In fact, applications that remain free forever are encouraged in the App Store and often are the most popular applications.</p><p>Finally, once applications are ready to monetize, Apple shares in the upside of the project. Apple gets a cut of every dollar generated on the Apple platform. There is a natural network effect where experimentation builds better apps, which brings in more revenue for Apple in the long-run.</p><p>This is the same network effect Saga’s new economic model enables. Saga introduces a successful and highly profitable economic system that has been proven to work in the real world into the blockchain ecosystem.</p><h3>Conclusion</h3><p>Historically speaking, an ecosystem’s revenue follows the Pareto principle: approximately 20% of the activity generates 80% of the value. The protocol’s economic system can use gas to squeeze the less successful projects, stifling innovation and experimentation. Or the protocol can adopt a better liquidity-centric economic system that makes blockchains more accessible, maximizes experimentation and application adoption and eventually shares upside with the most successful projects. With Saga, the protocol no longer fights against project adoption. Whether it is gaming, entertainment, DeFi, social or other use cases, Saga is the best infrastructure for developers.</p><p><em>For further information, follow us on</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f980c1ce33&amp;e=4c17c9cc64"><em> Twitter</em></a><em>, join our</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=6a99f13211&amp;e=4c17c9cc64"><em> Discord</em></a><em> and</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64"><em> Telegram</em></a><em> and subscribe to our</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"><em> Medium</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40c2bab04d4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-40c2bab04d4b">Saga Liquidity Integration Layer</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Saga Liquidity Integration Layer]]></title>
            <link>https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fcf7300ff6f</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Mon, 12 Aug 2024 17:01:47 GMT</pubDate>
            <atom:updated>2024-08-13T22:01:11.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zyn07zp73yMqTndo3bUVcw.png" /></figure><h4>Part I</h4><h3>Introduction</h3><p>As the number of chains, L2s, rollups and other base infrastructure dramatically increased over the last cycle, liquidity fragmentation became an immovable problem in the blockchain ecosystem. New technologies such as chain abstraction, intents, and aggregator solutions have emerged to help address the challenges around liquidity fragmentation. However, most of these solutions require infrastructure that is manually jerry-rigged, resulting in a sub-optimal developer and user experience.</p><p>Saga is a Layer 1 protocol that allows developers to automatically spin up chainlets that provide applications with infinite horizontal scalability. Does Saga’s “infinite horizontal scalability” also therefore result in infinite liquidity fragmentation?</p><p>In this paper, we introduce Saga’s Liquidity Integration Layer (LIL) that solves the liquidity fragmentation problem.</p><h3>Why does Liquidity Naturally Fragment in the Current Meta?</h3><p>Liquidity fragmentation is fundamentally caused by the lack of composability between applications in two different chains. In a shared L1, every application is fully composable: when a new application is deployed, it automatically acquires access to every other application that has already been deployed on that L1. For this reason, liquidity fragmentation is not an issue on a single L1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P8dwlm4K6UUcwfsh" /></figure><p>In a horizontally scaled multi-chain world, things get much more complicated. At the very minimum, the developer needs to manually set up bridges to every chain they want to interact with. Even when the bridges are all set up, cross-chain interactions have usability issues. This is because three distinct stakeholders are involved for every cross-chain interaction: the source chain, bridge operators, and the destination chain. Generally speaking, each of these stakeholders is a disparate collection of projects and operate under different technical and economic models that complicate deployments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b0Q3JTyWeOnQgwf6" /></figure><p>If an application on Chain A wants to access liquidity on Chain B, the developer needs to fight against technology limitations as well as payment flows with the bridge operator (bridge fees) and Chain A validators (transaction fees) and Chain B validators (transaction fees). The developer also needs to manage 3 different UX flows related to the three stakeholders. An experience where the users transition between DEX UI, bridge UI, and application UI is not a viable solution.</p><p>However, liquidity that is pooled natively in Chain A is fully composable with all applications on Chain A. It is simply easier for Chain A to pool liquidity in Chain A instead of tapping into liquidity in Chain B. Ergo, liquidity fragments.</p><p>How do you solve the liquidity fragmentation problem? Restoring composability across multiple chains is the key to solving liquidity fragmentation. When liquidity in Chain B is just as easy to access as liquidity in Chain A, then liquidity fragmentation is no longer an issue.</p><h3>Liquidity Fragmentation in Saga</h3><p>In Saga, a developer can request a chainlet through a simple transaction. Validators monitor the Saga mainnet for this chainlet request transaction and provision a new chainlet automatically without any manual intervention. With an automated system like Saga, horizontally scaling your application is as simple as requesting a second chainlet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N5p8Z3tMKLM-fsdR" /></figure><p>Because every application is potentially on different chainlets (and potentially across multiple chainlets), liquidity is at risk of fragmenting. However, due to Saga’s unique integrated architecture, we are uniquely positioned to solve liquidity fragmentation.</p><h3>Introducing the Saga Liquidity Integration Layer</h3><p>Saga’s Liquidity Integration Layer introduces automatic composability into the Saga ecosystem. When a developer launches a fresh new chainlet, it will automatically be connected to the LIL. Through the LIL, this fresh chainlet will have immediate access to tokens, services, and applications on other chainlets as well as other ecosystems outside of Saga.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fNXsUyh93fEPCll2" /></figure><p>The LIL is a combination of four innovative products:</p><ul><li>Automatic bridges from the LIL to every chainlet</li><li>A router that determines a canonical hub for all liquidity to route through</li><li>Packet-forwarding middleware that automates routing</li><li>Hooks to enable cross-chain smart contract calls</li></ul><p>By combining these four products, the Liquidity Integration Layer enables developers to:</p><ul><li>Bring in USDC, SAGA or ETH into the developer’s chainlet</li><li>Mint a token on a chainlet and, using a simple command, bridge the token to a DEX, swap to another token, and bridge the swapped token back into the developer’s chainlet</li><li>Mint an NFT on a chainlet and, using a single API, move the NFT to an NFT marketplace and list the NFT for sale</li></ul><p>Even though developers deploy on their own chainlet, the LIL grants automatic access to applications on every other chain and ecosystem. Through the LIL, developers can finally choose both composability AND scalability.</p><p>The Liquidity Integration Layer is designed such that:</p><ul><li>All infrastructure is automatically provisioned and immediately available</li><li>Routing messages from chainlets through the Liquidity Integration Layer and back is automatically managed</li><li>The developer can interact with a unified and simple API / UX to access the Liquidity Integration Layer</li><li>Cross-chain execution enables composable applications across the Saga ecosystem</li></ul><p>Let’s dive deeper into the various innovations that enable the Saga Liquidity Integration Layer.</p><h3>Saga Liquidity Integration Layer Innovations</h3><h4>First Innovation: Automatic bridge deployment</h4><p>Easy access to liquidity depends on an automatic setup of bridging infrastructure. Prior to Saga’s Liquidity Integration Layer, developers had two choices: roll and operate their own bridge or convince a bridge partner to support their chain. Neither option is particularly appetizing as operating a bridge is highly complicated and risky while convincing bridge operators to support a new chainlet may take many months. Is there a way to automate the bridging process?</p><p>As mentioned previously, automating bridging is normally a difficult task because there are three distinct stakeholders involved: the source chain, bridge operators, and the destination chain. Generally speaking, each of these stakeholders is a disparate collection of projects and operate under different technical and economic models that complicate deployments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5pG_xg4T5EPT21QS" /></figure><p>However, in Saga, the picture is significantly simpler. The source and destination chains are operated by the same set of validators. By embedding the bridge relayer logic directly into the validator binary, the validators can also operate the bridges. Once embedded, the validators’ services can natively include operating the bridges within the Saga ecosystem. Saga is one of the first blockchains ever to have protocol-native bridge infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uQCpKsMffC2BVcPOtPBq_g.png" /></figure><p>Saga’s protocol-native bridge solution automates the provisioning of Inter-Blockchain Communication (IBC) bridges within the Saga ecosystem. The developer does not need to do anything extra besides launch their chainlet.</p><p>Another major benefit of a protocol-native bridge is that because the source and destination chains are all operated by the same validators, bridges in the Saga Liquidity Integration Layer can be all free and gasless to the developer. These benefits translate to a usable UI and UX for both the developers and end users of Saga.</p><h4>Second Innovation: Automatic liquidity routes</h4><p>While free and automatic bridges within the Saga ecosystem are amazing, canonical routes are helpful in establishing the topology of the network. Directly connecting every chainlet with every other chainlet is technically possible with Saga’s automatic bridge deployments. However, the topology can quickly become too complex due to token fungibility issues.</p><p>In addition to connections across all chainlets, developers need bridges to ecosystems outside of Saga such as Ethereum, Solana, etc. Ideally, each chainlet does not need to manually stand up bridges to various ecosystems. Saga’s Liquidity Integration Layer automates this process by creating a router (LIL Chainlet).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s6LxJkP1fgT7ld4y" /></figure><p>The LIL Chainlet is simply just another chainlet all bridges route through. Using the protocol-native bridge solution, every chainlet is automatically connected to the LIL Chainlet. By proxy, all chainlets will have automatic access to any ecosystems bridged from the LIL Chainlet. This topology is starting to feel as composable as an L1!</p><h4>Third Innovation: Automatic packet forwarding</h4><p>With the LIL Chainlet, canonical routes are set up through the Saga ecosystem. However, there’s a new issue introduced by the topology: every bridge transaction now requires at least two hops. For example, a simple Chainlet A to Chainlet B communication requires one bridge transaction from Chainlet A to LIL Chainlet and another transaction from the LIL Chainlet to Chainlet B. Traditionally, the user experience for these kinds of multi-hop bridges is not smooth. The developer or user must wait for confirmation of completion of the first hop before manually initiating a second bridge transaction. Not only is this a mechanical nuisance, it also forces the users to know the bridge infrastructure topology. We can solve this user experience problem using packet forwarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E_9tIhvpp3W6qcC0" /></figure><p>IBC packet forwarding allows multi-hop bridge transactions utilizing the memo field (similar to calldata on Ethereum) of a transaction. The Liquidity Integration Layer can automatically daisy chain as many forward requests as needed to route through the relayer topology. With the LIL Chainlet, the routes are relatively simple across the Saga ecosystem. All routes always begin with a path down to the LIL Chainlet. Generally, LIL Chainlet has no inherent functionality besides routing, so all routes eventually end with a path to another chain (whether it is a chainlet or outside ecosystem).</p><p>Saga’s Liquidity Integration Layer automates the routing within the Saga ecosystem and facilitates usable UI and UX for both the developers and end users of Saga.</p><h4>Fourth Innovation: Automatic cross-chain execution</h4><p>The final part of a fully composable system is the ability to access applications across any chain from any chainlet. Once the message passes through the LIL into the destination chain, developers want the ability to automatically execute a transaction on the destination chain. The Saga Liquidity Integration Layer accomplishes this using <a href="https://ibc.cosmos.network/architecture/adr-008-app-caller-cbs/">ADR-8 actor callbacks</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ApHm7ejPKmMGc29D" /></figure><p>Actor callbacks are conceptually similar to packet forwarding, where a specific transaction is executed on the destination chain after a set of transactions (for example a series of bridge transactions) is complete. By utilizing IBC hooks, we can embed any EVM transaction with the route transaction to be executed once the packet arrives in the destination chainlet.</p><p>If Chainlet B has a DEX smart contract (like Uniswap) deployed, any arbitrary chainlet can utilize the Saga Liquidity Integration Layer to automatically route an asset to Chainlet B, swap for another token then move the swapped token back to the originating chainlet. In fact, with cross-chain execution, the Saga Liquidity Integration Layer introduces application composability to all chainlets. Any smart contract deployed on any chainlet on Saga is automatically and instantly accessible to all developers.</p><h3>Conclusion</h3><p>By combining the four innovations, Saga’s LIL is able to automatically solve composability and liquidity fragmentation. The magic of the Liquidity Integration Layer is the automated access — the developer does not need to do anything manual or extra beyond spinning up a chainlet. A chainlet simply comes equipped with all the features of the LIL.</p><p>Saga is not the first and only decentralized blockchain protocol to champion horizontal scalability. Appchains (Cosmos, Avax Subnet, Polkadot) and rollups (Ethereum L2s, RaaS, Polygon CDK) are all horizontal designs that are available for developers. However, most of these scaling solutions introduce insurmountable complexities for the developer, chief of which is liquidity fragmentation. Horizontal scalability that introduces insurmountable difficulties and complexity for the developer is merely promising theoretical scalability. Practically, a blockchain protocol is only as scalable as how easy it is to use. A truly scalable infrastructure needs to be horizontally scalable but also be a product that people will actually use.</p><p>What differentiates Saga is the integrated approach to horizontal scalability. In our<a href="https://medium.com/sagaxyz/the-unblock-manifesto-065bf25eebc8"> Unblock Manifesto</a>, we outlined Saga’s platform-based approach to disrupting the web3 space by focusing on developer needs and ease of use. Saga’s mission is to integrate the complete product experience and offer practical scalability to developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6wsPMtypPH2wWHI4" /></figure><p>With Saga, developers can finally choose both composability AND scalability. Whether it is gaming, entertainment, DeFi, social or other use cases, Saga is the best infrastructure for developers. By combining practical and usable solutions with horizontal scalability, Saga unlocks the “infinite” in infinite horizontal scalability.</p><p><em>For further information, follow us on </em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f980c1ce33&amp;e=4c17c9cc64"><em>Twitter</em></a><em>, join our </em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=6a99f13211&amp;e=4c17c9cc64"><em>Discord</em></a><em> and</em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64"><em> Telegram</em></a><em> and subscribe to our </em><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"><em>Medium</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fcf7300ff6f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/saga-liquidity-integration-layer-8fcf7300ff6f">Saga Liquidity Integration Layer</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Exploder: How Modularism Leads to Saga]]></title>
            <link>https://medium.com/sagaxyz/stack-exploder-how-modularism-leads-to-saga-b4566805eb95?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4566805eb95</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[modular-blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Thu, 22 Feb 2024 17:51:54 GMT</pubDate>
            <atom:updated>2024-02-22T17:51:54.195Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q2KxF-Dqk2IRcqJx.png" /></figure><p>Blockchain modularity is inevitable. Right?</p><p>Over the last year, I’ve been attempting to understand blockchain scalability and how Saga fits within the evolving landscape. To ensure Saga’s success, I needed to understand how various scalability architectures worked, where these paths eventually led, and make sure we were on the optimal path. As I dissected the product differences and tradeoffs between existing appchains and rollups, I found myself chasing circular arguments and getting more confused. For anyone who also attempted to spelunk down this rabbit hole and found a giant wall of utter confusion, I completely empathize.</p><p>Everyone always asks me: how does Saga fit within the modular story? I found it pretty difficult to answer. It turns out, the reason why I couldn’t answer this simple question is that Saga doesn’t fit neatly into the <strong>current</strong> modular narrative at all. This is because the existing modular ecosystem and designs are in their infancy and still evolving.</p><p>However, by analyzing how the modular ecosystem came to be and understanding the limitations of the current modular architecture, we can predict where the modular ecosystem is headed.</p><p>As it turns out, the future of modularism looks a lot like Saga.</p><h3>Beginning with the basics: Monolithic Chains</h3><p>A blockchain is simply a very long list of states and transactions, guaranteed with a certain amount of security.</p><ul><li><strong>State</strong> represents the data of the ledger at a specific snapshot</li><li><strong>Transactions</strong> trigger state transitions</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/0*jn_swEXvgGwHurn1" /></figure><p>In a monolithic proof of stake blockchain, a committee of block producers (validators) update the ledger by agreeing on the list of transactions to be included in the next block AND the corresponding state resulting from those transactions. The block production mechanism can be functionally divided into three parts:</p><ul><li><strong>Data Availability (DA) </strong>is just a fancy word for “transaction storage.” The DA stores a list of transactions to be included in the block.</li><li><strong>Execution </strong>is just a fancy word for “calculation.” Execution computes the updated state based on those transactions.</li><li><strong>Settlement </strong>is just a fancy word for “state storage.” Settlement stores the resulting state after the execution.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*_5dHHyRS37W1HiU2" /></figure><p>Every block, a proposer validator prepares the list of transactions (DA), executes those transactions (execution) and posts the resulting state (settlement). After a consensus step of every other validator agreeing on the produced block, the state specified in the settlement stage is anointed as the latest global state.</p><p>A potential issue with the monolithic chain is that there is a theoretical limit to the amount of transactions the chain can process. While execution can be somewhat parallelized, any transaction that updates the same state needs to be processed sequentially. This is akin to the theoretical limits of CPU hyperthreading vs. multicore computation. Just like how CPUs eventually all became multicore, the monolithic chain needs to go modular to untap true scalability.</p><h3>Step 1: Modularizing Execution</h3><p>In the block production mechanism, the most computationally heavy component is the execution stage. So one scaling strategy is to offload the execution from the base chain. In this design, the mainnet simply becomes a place to store the transaction and latest state from the off-chain execution environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/0*g8Z4QrFjhEYAz32-" /></figure><p>How do you guarantee that the off-chain execution is submitting valid state to the main chain? We need to inject some amount of security into the execution environment. There are broadly two different methods.</p><p>The first method is to enforce correctness computationally. When the execution environment submits the state to the mainnet, it is also required to submit a validity proof that mathematically proves that the state is valid. This method is broadly called “zero knowledge” or ZK.</p><p>The second method is to enforce via committee. A committee (like a set of validators or node operators) attests to the accuracy of the execution. We can either implement a full proof of stake consensus on the execution environment (decentralized sequencers), or we can choose to optimistically trust a group of auditors with a challenge period.</p><p>Once the execution environment is properly secured, you can replicate this process to scale your mainnet by launching many parallel execution environments. These are the L2s, such as Optimism, Arbitrum, etc.</p><p>However, this eventually also runs into scalability issues. The mainnet’s computational load is still limited, and eventually just storing the transactions, storing the state and verifying the correctness of that state will use up the entirety of the mainnet’s computation budget.</p><h3>Step 2: Modularizing Data Availability</h3><p>For this reason, the next component we have seen the ecosystem modularize is data availability. By offloading the transaction storage task off of the mainnet, we can hyperspecialize the mainnet to just focus on state storage and verification. This way, we can spin up even larger amounts of parallel execution environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*36h5DijYsrOoRry-" /></figure><p>These off-chain DA providers are projects such as Celestia, EigenDA and Avail. However, just like the execution environment, the DA requires some form of security to guarantee that the transaction storage is trustworthy. In the case of Celestia, this is derived from their proof of stake system. With EigenDA, this is derived from restaked Ethereum.</p><p>This is the modular landscape as of today. However, this current architecture has some key issues.</p><h3>Bottlenecks with Today’s Modular Architecture</h3><p>While this current modular architecture is an improvement in scalability, it is nowhere near enough to support mainstream use cases. Supporting the global value infrastructure will require many thousands of execution environments. Standing up security for even one execution environment is operationally taxing and hugely expensive. Standing up thousands is a non-starter.</p><p>Similarly, to support the thousands of execution chains worth of traffic, a single DA and settlement layer is not enough; many parallel DA and settlement layers need to be provisioned and secured. However, launching and securing any new chain requires a huge amount of work and resources.To make a truly scalable architecture, we need to automate this process.</p><h3>Next Step: Modularizing Security</h3><p>The most difficult part of any decentralized infrastructure is provisioning the security. A truly scalable and elastic architecture is only possible if we can separate out the security from the block production modules and delegate that task to a separate dedicated chain (let’s call that the mainnet now).</p><p>How do we modularize the security?</p><p>Typically, a malicious activity in a chain will punish (slash) the validator responsible for the malicious action on its own chain chain. The interesting thing about proof of stake is that the security of the chain is self-referential. Correct block production happens due to the underlying security (value at stake). In other words, validators continue to produce correct blocks because of the risk of losing their assets. However, the underlying security is enforced by correct block production: the record of the validators’ assets are stored in the ledger itself.</p><p>We can use Cross Chain Validation (CCV) to modularize this security off the chain. CCV is a Cosmos innovation similar to Eigenlayer’s re-staking that allows chains to borrow security from another chain. With CCV, any malicious activity in the DA and execution chain is relayed back to the mainnet where the slashing is enforced. This way, the modules automatically inherit the full security of the mainnet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/0*Ddi9WZtcfrYJyJ4r" /></figure><p>In this model, the mainnet’s only responsibility is to acquire security and share security to the various off-mainnet block production modules. In addition to scalability, unifying the security for the entire block production cycle in this fashion is a safer architecture. In the current modular world, the amount of security for a given transaction is probabilistic, depending on where in the cycle of block production it is in. Probabilistic security leads to many issues in bridging and user experience.</p><h3>The Inevitability of Integration</h3><p>The concept of modularity was not invented in Web3. In fact, the cycle of specialization and integration have driven many innovation cycles in the past. In the early PC days, the CPU was a generalized solution for all compute. Eventually, new use cases necessitated additional specialized modules external to the CPU. For example, graphical use cases were pushed into the GPU, audio into sound cards and network workloads into the network cards. Each of these specialized modules eventually went through many improvement iterations where the module standardized and commoditized.</p><p>Once these modularized solutions are sufficiently optimized and standardized, it is often more efficient to integrate it back into a single package. Most processors and SoCs found today are integrated products that handle some combination of general, graphical, audio and network compute.</p><p>Similarly, many parts of the modular blockchain architecture will be integrated for increased efficiency.</p><h3>Next Step: Integrating Block Production and Automating Scalability</h3><p>There’s a funny thing that happens once you move all the block production components off of the mainnet. Just like how modern processors have integrated the various computing modules back into a single SoC for improved efficiency, future blockchain architectures will integrate the block production modules into a single module. The only reason all these block production modules were split to begin with was to offboard the execution from the mainnet. With an integrated security architecture, it makes little sense to keep them separate. We expect the off-mainnet DA, execution and settlement logic to integrate back into a single component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*VRBFhwt_CShxybmg" /></figure><p>In fact, instead of having the mainnet just maintain and share security, we can introduce a new function onto the mainnet to automate the launching of the off-mainnet components. By modularizing the entire block production modules off the mainnet and introducing the ability to automatically launch these off-mainnet modules, we can build an infinitely scalable architecture.</p><p>In fact, this is exactly Saga’s architecture. We call our mainnet the Saga Platform Chain and our off-mainnet block production component a Chainlet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*wgSgv0JZ1-8C2H9J" /></figure><h3>Conclusion</h3><p>Is blockchain modularity inevitable? Most certainly so. In this article, we have investigated the motivations and paths in the blockchain ecosystem that have led us to this modular architecture. We then outlined the current limitations of the modular architecture as it stands today. Finally, we explored what’s next with modularism. With modularized security and reintegration of the block production cycle, we can visibly observe the bleeding edge converge to the Saga design.</p><p>Witness the inevitable state of modularism happening today at Saga.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4566805eb95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/stack-exploder-how-modularism-leads-to-saga-b4566805eb95">Stack Exploder: How Modularism Leads to Saga</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Exploder: Unblocking Web3 Products With Costless Transactions]]></title>
            <link>https://medium.com/sagaxyz/stack-exploder-unblocking-web3-products-with-costless-transactions-387b9f03b7c5?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/387b9f03b7c5</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[unblock]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Wed, 17 Jan 2024 06:40:53 GMT</pubDate>
            <atom:updated>2024-01-17T06:40:53.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pWb-_lYg1WnjC9B0.png" /></figure><p>Blockchains traditionally use gas tokens: 1) to pay for infrastructure providers like validators and miners and 2) as a mechanism for spam prevention and transaction ordering. The need for gas tokens often creates awkward user experience issues where end users need to acquire arbitrary tokens from exchanges or other methods prior to interacting with a Web3 product. While a nuisance for DeFi use cases, this awkward user experience is existential for gaming and entertainment where user experience is king. Imagine a non-Web3 gamer valiantly defeating the Sith Lord, only to be interrupted with a message requesting to connect their Metamask and pay gas to mint an NFT achievement. Fortunately, there are some workarounds.</p><p>Account abstraction (ERC-4337) is a popular solution to allow “gasless” transactions on behalf of the end user. In this blog post, we will discuss how Account Abstraction works, explain why it is not a comprehensive solution for the developer and propose a new Saga-native solution — the recycled gas token.</p><h3>Account Abstraction</h3><p>With a traditional transaction mechanism, a user submits a transaction to a validator with the necessary gas fees. The validator takes the gas as payment and includes the transaction in the blockchain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/0*qJgzQ-ti5euvZw7K" /></figure><p>Account Abstraction (ERC-4337) separates the verification mechanism from the transaction inclusion mechanism on Ethereum, enabling a separate paymaster to be used for the necessary gas fees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9h8vxxW8awixi369" /></figure><p>For the end user, Account Abstraction looks and feels like gasless transactions. However, it is incorrect to call this “gasless” as it is more akin to “sponsored gas,” where someone pays the gas on behalf of the users. While Account Abstraction is a fantastic tool for developers, using it for a “gasless experience” creates other potential user experience problems.</p><h3>Issues with Sponsored Gas</h3><p>Sponsored gas only punts the gas issue for another party to resolve on behalf of the user. Generally speaking, the developer of the application ends up footing the gas bill. This poses two general issues in user experience for the developer.</p><p>First, the gas payment required by the validator to include transactions into the blockchain becomes an economic sink for the developer. Unfortunately, most developers do not have infinite resources to continuously pay gas fees on behalf of all their users. In one form or another, sponsored gas transactions need to be economically profitable for the developer. This means that developers need to be very selective about whose transactions they will and won’t sponsor. Any users that the selection criteria deems not economical will need to pay for their own gas and have a degraded product experience. A miscalculation will quickly deplete the paymaster wallet and cause errors for the users.</p><p>Second, even if the developer correctly filters the correct balance of user transactions, the transaction cost for including a transaction in the blockchain is completely out of the developer’s control. The cost per transaction is variable based on the demand of the blockchain, and (again) miscalculation will quickly deplete the paymaster wallet and cause errors for their users. Ethereum gas costs can vary by more than 10x quite frequently depending on meme coin and other DeFi activity. A developer who normally sponsors $1,000 in monthly gas may suddenly require $10,000 worth of $ETH.</p><p>The crux of the user experience issue is that transaction fees are an economic drain from users to the validators.</p><h3>Saga Revolutionizes Token Flows</h3><p>In Saga’s <a href="https://sagaxyz.cdn.prismic.io/sagaxyz/d396b945-52ed-41d5-afef-ee27c6a8a233_Saga+-+Token+Mechanism+%26+Incentives+-+Dark+Version.pdf">Token Mechanism and Incentives Paper</a>, we outlined how we re-architected economic flows in the Saga protocol. With Saga Chainlets, validators are compensated directly by developers for providing infrastructure. Therefore, validators do not collect transaction fees from Chainlets. Instead, all transaction fees are returned back to the developer’s account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/0*AU4xpW33vbN0tJKc" /></figure><p>The developer can choose to keep all transaction fees as revenue. Alternatively, we can use this clever economic flow to create a truly sustainable costless blockchain experience.</p><h3>Introducing Recycled Gas Tokens</h3><p>When the user interacts with the application, the developer can faucet an appropriate amount of tokens into the user’s wallet. For example, this can be done when a user opens an account to start playing a game or just-in-time (JIT) as they sign transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*pB-ysfzZZgP5PWy2" /></figure><p>For the JIT example, the gas tokens’ faucet transactions and the user’s transaction can be atomically batched into the blockchain at the same time. Using Saga’s token flow, the entire balance of the gas tokens are then returned back to the developer’s wallet to be fauceted to future users and transactions. No economic value is funneled out through gas fees.</p><p>Using the recycled gas token mechanism, the developer can use their gas token similar to web API tokens, granting access to any subset of users dynamically. For example, a developer can create a faucet that gives 3 free transactions to any users. Then, for a subscription fee, give access to 100 transactions a day. With recycled gas tokens, possibilities are endless and it is always always zero-cost to the developer.</p><p>The benefits also extend to the developers’ backend services. In other blockchain systems, a developer is no different from users. When the developer needs to update their own application state, the developer needs to pay the blockchain validators gas fees to update those states. In traditional web applications, database migrations are quite common and necessary to improve the product. However, in Web3, changes in state cost so much that developers will simply avoid making substantive changes to the blockchain state once deployed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/0*Acf-lQYoNxHGk30W" /></figure><p>With Saga, because the gas token is always recycled back to the developer, the developer’s server-to-chain infrastructure costs nothing to the developer. The developer’s backend can access and modify the chain all day without costs or restrictions.</p><h3>Conclusion</h3><p><a href="https://medium.com/sagaxyz/the-unblock-manifesto-065bf25eebc8">Unblocking</a> economics flows for developers is required for mass adoption of blockchain. Recycled gas tokens is only one method Saga uses to unblock developers. By supporting truly costless transactions, we can lift economic barriers from builders and unlock Saga scale applications. For more details around how you can Unblock your application, follow us on<a href="https://twitter.com/Sagaxyz__"> X</a>, join our<a href="https://discord.gg/UCRsTy82Ub"> Discord</a> and<a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64"> Telegram</a> and subscribe to our<a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"> Medium</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=387b9f03b7c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/stack-exploder-unblocking-web3-products-with-costless-transactions-387b9f03b7c5">Stack Exploder: Unblocking Web3 Products With Costless Transactions</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Saga Community Genesis Airdrop]]></title>
            <link>https://medium.com/sagaxyz/saga-community-genesis-airdrop-e0f94c1f2220?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0f94c1f2220</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[airdrop]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Thu, 04 Jan 2024 09:47:36 GMT</pubDate>
            <atom:updated>2024-03-08T03:02:44.686Z</atom:updated>
            <content:encoded><![CDATA[<h4>Eligibility Criteria and Methodology</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c1J2fvb3tNU8RF6_.png" /></figure><p>Hello Saganauts!</p><p>Happy New Year! Your long wait is now over. We are thrilled to reveal our airdrop eligibility criteria for the broader Saga community.</p><p>Late Q3 2023, Saga kickstarted the 2024 crypto airdrop season with an announcement of the <a href="https://medium.com/sagaxyz/saga-launch-airdrop-criteria-innovators-b524db039478">airdrop criteria for Saga Innovators</a>, builders and their gamers/users. In December, Saga launched Saga Advent, season 1 of our groundbreaking <a href="https://decrypt.co/210472/saga-blockchain-launches-play-airdrop-game-tournaments-heres-how-earn">Play-to-Airdrop</a> campaign with daily tournaments and quests across the 25 days of Christmas. We hosted 13 events with 10 different games, with an opportunity to play every day. The total number of players across all the tournaments during this period was 3,000+.</p><p>As we open 2024 and get ever closer to Saga Mainnet, we are unveiling the eligibility criteria for Saga’s general community airdrop, the last major component of our genesis airdrop. All snapshots have been taken, and today we are happy to announce full details for how our community can participate.</p><p>Snapshots aren’t everything, though. Read to the end for Play-to-Airdrop Season 2: <em>The Three Kingdoms</em> and our Saga Developer Tournament series!</p><h3>Valuing Loyalty</h3><p>In addition to the underlying utility of staking to secure the Saga Mainnet and paying for Chainlets, the $SAGA token represents membership into a community with a shared set of values. An airdrop is a good opportunity to define those values and welcome initial community members by rewarding those who have demonstrated value alignment.</p><p>One key value we want to reward and encourage is loyalty. In the world of crypto, loyalty is defined by active engagement in a community and taking a long-term view on an ecosystem. Therefore, for Saga’s token generation event (TGE) distribution, we are targeting loyal stakers and users of our closest tech partners, as demonstrated by their activity through the toughest crypto bear environment.</p><p>In early 2023, we announced three marquee partnerships with foundations and communities that strongly believe in the appchain future: <a href="https://medium.com/sagaxyz/saga-announces-collaboration-with-celestia-to-implement-sequencers-as-a-service-to-scale-rollups-fda01311919f">Celestia</a>, <a href="https://medium.com/sagaxyz/saga-and-polygon-announce-partnership-to-automate-supernets-polygons-appchain-solution-db82d654c43f">Polygon</a> and <a href="https://medium.com/sagaxyz/saga-and-ava-labs-announce-partnership-to-further-automate-subnets-avalanches-customizable-4986b75af451">Avalanche</a>. Saga is a platform solution that automates the launching of dedicated blockspace, such as Cosmos appchains, Celestia Rollups, Polygon CDK chains and Avalanche Subnets. As a sign of appreciation to those projects who believed in the Saga technology and mission, certain members of the Celestia, Polygon and Avalanche communities will be receiving an airdrop of genesis $SAGA tokens.</p><p>In addition, the Saga security chain and platform chain are built using the Cosmos SDK. In recognition of our roots, certain members of the ATOM community will also be receiving an airdrop of genesis $SAGA tokens.</p><p>Read further to learn more about our specific methodology and eligibility requirements.</p><h3>Methodology</h3><p>Every eligible participant in each community will be categorized into small, medium and large airdrops depending on certain criteria. Each tier receives 5x the airdrop of the last tier (i.e. medium receives 5x the amount of small; large receives 5x the amount of medium; and (therefore) large receives 25x the amount of airdrop vs. small).</p><p>There will be a bonus multiplier (4x) on top of the base airdrop for those who exhibited incredibly strong loyalty within those communities.</p><h3>Eligibility Criteria</h3><h4>ATOM Community</h4><p>In the ATOM community, the 101,000+ wallets that 1) increased stake from 04/20/2023 to 10/20/2023 and 2) had more than 25 $ATOM staked on 10/20/2023 are eligible for the $SAGA airdrop. There is a loyalty bonus for those who increased their stake by more than 30% during that time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XLntSfJSLvA1LCui" /></figure><h4>Celestia Community</h4><p>In the Celestia community, 27,000+ wallets that staked more than 23 $TIA on 12/01/2023 are eligible for the $SAGA airdrop. There is a loyalty bonus for those who increased stake from 11/07/2023 to 12/01/2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gTJ1fLFsXkBelDPDcetDYA.png" /></figure><h4>Polygon Community</h4><p>In the Polygon community, 26,000+ wallets that staked more than 300 $MATIC on 10/20/2023 or wallets that bridged more than 0.4 $ETH using the ZKEVM bridge are eligible for the $SAGA airdrop. There is a loyalty bonus for those who increased stake from 04/20/2023 to 10/20/2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3taEVOEXlt7j5Mbs" /></figure><h4>Avalanche Community</h4><p>In the Avalanche community, 26,000+ wallets that staked $AVAX on 04/20/2023 or 10/20/2023 are eligible for the $SAGA airdrop. There is a loyalty bonus for those whose staking duration is greater than 150 days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XKwdn9uTQVqoX-1V" /></figure><h3>Saga Play-to-Airdrop Season 2: The Three Kingdoms</h3><p>Season 2 of our Play-to-Airdrop campaign will be known as <em>The Three Kingdoms</em> in honor of our partners. From January-February, we will be running tournaments for games building cross-chain between Saga and each of our key partner ecosystems: Avalanche, Polygon and Solana!</p><p>We will run tournaments for about 5 games with each of our partners, with the leaderboards eligible for $SAGA airdrops. The tournaments will be announced on a rolling basis, so it is crucial that you follow our <a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f980c1ce33&amp;e=4c17c9cc64">X</a>, join our<a href="https://discord.gg/UCRsTy82Ub"> Discord</a> and <a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64">Telegram</a> and subscribe to our<a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"> Medium</a> to get the latest news.</p><p>To be 100% clear, these tournaments will be on top of the schedule we already have planned in partnership with Game3.gg, Indigg, Bitmetis and a few guilds yet to be announced!</p><p>Some games will need to be downloaded in advance, so make sure to give yourself ample time to prepare and get to know your fellow players a bit before the competition begins!</p><h3>Saga Developer Tournaments</h3><p>And of course, we couldn’t do a launch campaign without welcoming our individual developers who are still exploring projects and are therefore not yet Innovators.</p><p>We will be running 2–3 tournaments during January-February where we will open Pegasus Testnet to our developer community for stress-testing. We will release details for these tournaments soon — remember, follow our socials (<a href="https://twitter.com/Sagaxyz__">X</a>,<a href="https://discord.gg/UCRsTy82Ub"> Discord, </a><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64">Telegram, </a><a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64">Medium) </a>for the latest! Hint: verification across our socials may be part of the tournament criteria. We can’t have those bots overloading our validators. 🙂</p><h3>Conclusion</h3><p>With the airdrop eligibility criteria we’ve designed, every $SAGA holder can be confident that they are amongst the strongest diamond hands who believe in the future of appchains. Our snapshot dates through the deepest period of the bear ensure that only those who are true believers are included.</p><p>In the wake of a long bear, airdrop season is finally brewing. With Saga, we opted for the epic opening across FIVE incredible communities simultaneously. Best of luck to our Saganauts far and wide!</p><p>Every eligible airdrop recipient will need to manually claim in our claims page, which will go live soon. Our claims process will not begin until the claims page goes live, so even if you know you’re eligible based on the criteria above, sit tight until you hear further from us. For the latest airdrop details and claiming process, follow us on <a href="https://twitter.com/Sagaxyz__">X</a>, join our<a href="https://discord.gg/UCRsTy82Ub"> Discord</a> and <a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=f450024c8d&amp;e=4c17c9cc64">Telegram</a> and subscribe to our<a href="https://xyz.us10.list-manage.com/track/click?u=ca44fab3b7b6185f64afb274a&amp;id=853c5406bb&amp;e=4c17c9cc64"> Medium</a>.</p><p><strong>THE AIRDROP IS NOT AND WILL NOT BE AVAILABLE TO U.S. PERSONS (OR PERSONS ACTING ON BEHALF OF U.S. PERSONS). IN ORDER TO PARTICIPATE IN THE AIRDROP, A PERSON OR ENTITY MUST NOT BE A U.S. PERSON AS DEFINED IN RULE 902 UNDER THE UNITED STATES SECURITIES ACT OF 1933 OR A U.S. PERSON WITHIN THE MEANING SECTION 7701(A)(30) OF THE UNITED STATES INTERNAL REVENUE CODE. A FULL TERMS AND CONDITIONS FOR PARTICIPATION IN THE AIRDROP WILL BE MADE AVAILABLE AS PART OF THE CLAIMS PROCESS.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0f94c1f2220" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/saga-community-genesis-airdrop-e0f94c1f2220">Saga Community Genesis Airdrop</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stack Exploder: Scaling Node Infrastructure in a 1000+ Appchain Multiverse with Saga Edge Nodes]]></title>
            <link>https://medium.com/sagaxyz/stack-exploder-scaling-node-infrastructure-in-a-1000-appchain-multiverse-with-saga-edge-nodes-98d171e9e973?source=rss-ae48984c7e68------2</link>
            <guid isPermaLink="false">https://medium.com/p/98d171e9e973</guid>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Jin Kwon]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 01:41:37 GMT</pubDate>
            <atom:updated>2023-12-12T01:41:37.396Z</atom:updated>
            <content:encoded><![CDATA[<p>Saga is leading <a href="https://x.com/Sagaxyz__/status/1729183414958592458?s=20">The Unblock movement</a>, ushering in a new world where developers can build their web3 applications in as simple a way as possible. In the <a href="https://medium.com/sagaxyz/the-unblock-manifesto-065bf25eebc8">Unblock Manifesto</a>, we highlighted how application developers have difficulty acquiring sufficient blockspace due to the need to manually stand up various parts of the infrastructure. Saga automates and trivializes the infrastructure for the developer by offering an Integrated Stack that automates launching on-demand blockspace.</p><p>An effective Integrated Stack requires the platform to automatically handle an immense amount of read, write and syncing requests. While existing infrastructure is sufficient for the status quo, it is not well equipped to handle demand of 1000+ appchains. The Saga Platform has many innovations that drive a breakthrough, but the most important component is a scalable back-end node infrastructure.</p><p>Today, we’re very excited to share our Saga Edge Node with the community.</p><h3>Current Node Infrastructure Architecture</h3><p>In a proof-of-stake blockchain, validators need to peer with each other to share consensus and other block production messages. At the same time, users need access to the validators to facilitate transactions to be included in blocks and read the latest state of the blockchain. If validators allow arbitrary connections from any of these sources, they open themselves to being intentionally or accidentally DDoSed. As a network, this is not acceptable because DDoSed validators do not participate in consensus and may halt the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/0*1RKDoLAgcTwT5HSn" /><figcaption>Directly exposing validator nodes may DDoS the validator</figcaption></figure><p>To solve this problem, networks employ a sentry (or proxy) node architecture. The validator node hides behind one or more sentry nodes. The validators only peer with their own sentry nodes, and all external stakeholders communicate to the validator through their corresponding sentry node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/0*CsFP5KJu-PxGduF9" /><figcaption>Example of a typical sentry node architecture to protect the validator</figcaption></figure><p>With any sudden increase in traffic, a sentry architecture is very effective in protecting the validator by offering 3 options to handle the requests:</p><ul><li>First, the sentry node can throttle access from users</li><li>Second, the validator can choose to cut peering from the validator to (public) Sentry and allow block production to continue through their (private) Sentry connection to other validators</li><li>Finally, the validator may stand up multiple public sentries to service the requests from users</li></ul><p>In practice, validator operators generally employ option 3 by placing sentries in an autoscale group in the cloud that spins up new instances when the current instances are busy. While this type of architecture was sufficient for a small cluster of appchains, it quickly runs into scaling issues in a system where there are 1000s of blockchains.</p><h3>Issues with the Sentry Node Architecture: Cost</h3><p>There are three issues that compound with one another that make the existing sentry node architecture not suitable for Saga-scale.</p><p>First, a sentry node is usually a full node that does not sign blocks. This means that every sentry node is executing every transaction and block and verifying state transitions as if they were a validating node. The computation load of a sentry node is excessively high for what it needs to do. Assume each validator node costs 100 dollars per month to operate. Because a sentry node is the same cost as a validator node, if a validator chooses to operate 1 validator node and 2 sentry nodes, the cost per validator would be $300 (3x$100) per month.</p><p>Second, every validator needs to operate a sentry node to protect its external IP address. Using the $300 per month figure, a network with 100 validators requires $30,000 (100x$300) per month in node operating costs to be secure.</p><p>Finally, the sentry node is unique per chain. Because each sentry node is a full node of a particular network, the $30,000 cost per month needs to be multiplied by the number of chains. In a 1000 chain system, this would amount to $30,000,000 per month in aggregate node operating costs.</p><p>Obviously, the true aggregate cost is likely less than this figure since some validators will run zero or one sentry node. However, it is very evident why this kind of architecture is not viable for a system like Saga where there may be thousands of chains operated by the validators. From an architecture design perspective, prioritizing redundancy at the validator site-level instead of the network-level leads to over-provisioned and unused hardware.</p><h3>Issues with the Sentry Node Architecture: Uncertainty and Inflexibility</h3><p>Each sentry or full node is a generalized infrastructure component: it provisions hardware resources to handle all types of requests regardless of the needs of the network. In addition, different requests have bottlenecks from completely separate components of the infrastructure. For example, read requests may be bottlenecked by the number and quality of full nodes. Write requests may be bottlenecked by the mempool size and block generation speed. IBC requests may be bottlenecked by the relayer implementation, as well as block generation in the destination chain.</p><p>Finally, because of the generalized nature of sentry nodes, it takes a bit of time to spin up — each new sentry node needs to state sync and join the latest round of consensus before they are able to help scale the network. An effective node infrastructure should be able to dynamically spin up specific resources from the live traffic pattern of the network.</p><h3>Introducing Saga Edge Node</h3><p>Saga Edge Node makes node architecture more scalable by reducing infrastructure complexity and costs. The Saga Edge Node has the following qualities:</p><ol><li>A Saga Edge Node is incredibly cheap to run and does not break system consistency to have more than one running in parallel (and is therefore truly horizontally scalable)</li><li>A Saga Edge Node can service as many Chainlets as needed</li><li>A Saga Edge Node is able to act as a virtual node and actively manage requests in the validator infrastructure</li></ol><p>Let’s explore how it works.</p><h3>Making Saga Edge Nodes cheap to operate</h3><p>A traditional sentry node is a full node, which means every sentry node is re-executing every transaction and updating their internal state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/0*Q9j6gplKHO5-nFeD" /><figcaption>Traditional sentry nodes recompute the internal state to follow consensus</figcaption></figure><p>This amount of computation redundancy quickly accumulates costs to the node infrastructure. Instead, we can design the Edge Node to hold the IP address of the validator node and simply relay the requests across. With this, we push the redundancy from validator site-level to the network-level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*K1HdeFenRrh_uRyb" /><figcaption>Saga Edge Nodes do not recompute the internal state</figcaption></figure><p>The Saga Edge Node therefore becomes incredibly cheap to operate because it is a simple lookup table and a passive relayer of connection requests from the requester to the validator node in question.</p><h3>Multiplex Edge Node across multiple chains</h3><p>We can improve the Saga Edge Node implementation by multiplexing requests for multiple chains into the same Edge Node. With this improvement, requests for all Chainlet activities can aggregate into the same Edge Node. The peering connections will automatically be relayed to the corresponding internal node.</p><p>How does this mechanically work? One issue is that because we have stripped out the part of the sentry node that syncs with the validator node, the Saga Edge Node is no longer aware of what individual requests are doing. We can model a solution similarly to how HTTP leaks Server Name Indication (SNI) in the TLS abstraction layer. When a requester sends any data to the Saga Edge Node, they can leak the chain_id field to route to the correct internal node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/0*2_HWpOJMng82AOIf" /><figcaption>Edge nodes multiplex requests across all Chainlets into a single instance</figcaption></figure><p>With this implementation, validators and other node infrastructure providers can manage aggregate traffic across all Saga Chainlets, instead of worrying about standing up different sentry nodes for each individual chain.</p><h3>Virtualize full nodes for active request management</h3><p>While significantly improved from the existing sentry node architecture, the implementation has some issues. First, the requester must break the abstraction layer to leak chain_id information to the Saga Edge Node. Second, Edge Node is a passive participant in this system. Because the Edge Node has no knowledge about what requests are doing, all connection requests are automatically routed to the validator node. The peering connections are still one-to-one, meaning that if there are two requesters requesting the same thing, the validator node needs to make two separate peering connections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/0*QIrdvrotVbmvQxVe" /><figcaption>Two different requests for the same information leads to multiple peering requests on validator node</figcaption></figure><p>We can make the Saga Edge Node a more active participant in the network by forwarding certain metadata (such as head, round, step, etc) from the validator node to the Edge Node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/0*vIx9lszGuue3WY_M" /><figcaption>Forwarding appropriate metadata allows Edge Nodes to act like virtual full nodes</figcaption></figure><p>Using this metadata, the Saga Edge Node can appear like a virtual full node and peer directly with requesters. By peering directly, the validator nodes only need to peer with the Edge Node cluster, making operations much more efficient. This also removes the need for the requesters to leak the chain_id on requests.</p><p>Another benefit of this now active Edge Node is that the Edge Nodes can now begin redirecting certain requests such as state sync and PRC requests away from the validator nodes. This way, the validator node infrastructure can be stripped down to simply execute transactions and pass consensus messages between validators.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*c3PkxK4BzdIm6Pk3" /><figcaption>Saga Edge Nodes can actively redirect requests to appropriate internal resources and services</figcaption></figure><p>In fact, we can enable our Edge Node architecture to peer into various components within the Saga infrastructure to effectively provide back propagation to the end users. For example, when there are too many transactions in the mempool, the Edge Node could simply decline any further write requests. Alternatively, the Edge Node can peer into the IBC relayer queue and decline any further IBC messages based on the queue size. Edge Node back propagation is a powerful way to limit the resource demand to run a chainlet validator node. This is one way the Saga Platform can guarantee and deliver clearly defined SLA metrics to application developers and Chainlet customers, such as mempool size and IBC transaction limits.</p><h3>Conclusion</h3><p>A scalable node infrastructure is usually not a big focus for other blockchain ecosystems because the negative effects of an unoptimized node infrastructure are not immediately felt by the stakeholders. The accumulated cost of running redundant hardware indirectly contributes to expensive validator compensation. The uncertainty and inflexibility of the infrastructure indirectly contributes to inconsistent uptime and performance metrics.</p><p>The Saga Edge Node allows the infrastructure to horizontally scale purpose-driven components while keeping costs minimal. It is the latest innovation in the Saga Platform that allows application developers to unblock themselves through lower costs and predictable SLA and performance of their blockspace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98d171e9e973" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sagaxyz/stack-exploder-scaling-node-infrastructure-in-a-1000-appchain-multiverse-with-saga-edge-nodes-98d171e9e973">Stack Exploder: Scaling Node Infrastructure in a 1000+ Appchain Multiverse with Saga Edge Nodes</a> was originally published in <a href="https://medium.com/sagaxyz">Saga AI Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>