<?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 Kolten on Medium]]></title>
        <description><![CDATA[Stories by Kolten on Medium]]></description>
        <link>https://medium.com/@kolten?source=rss-2ea40c62c05------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2xx7pjdCn7oFdnz9bLHw-Q.jpeg</url>
            <title>Stories by Kolten on Medium</title>
            <link>https://medium.com/@kolten?source=rss-2ea40c62c05------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:29:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kolten/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[Introducing the “Bad Debt” Dashboard]]></title>
            <link>https://medium.com/risk-dao/introducing-the-bad-debt-dashboard-c855cc1f2163?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/c855cc1f2163</guid>
            <category><![CDATA[stable-coin]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Wed, 08 Jun 2022 15:06:28 GMT</pubDate>
            <atom:updated>2022-06-08T15:06:28.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oRBdQlt1a789vl5C" /></figure><p>As part of our efforts to increase transparency around DeFi borrowing and lending protocols, we’ve just launched a new dashboard that tracks bad debt (i.e. insolvent accounts) across Compound compatible protocols. You can find the dashboard <a href="https://bad-debt.riskdao.org/">here</a>.</p><h3>How it Works</h3><p>The bad debt dashboard periodically scans all user debt and collateral, and whenever user debt &gt; user collateral, it is added to the total bad debt of the platform. To make the system more lightweight, we scan the full user list once a week, and scan the active list of users every hour.</p><p>The USD value of the collateral and debt is not taken from the lending platform price feed (and during the development stage we found a buggy price feed in one of the platforms). Instead we use Krystal’s new price feed API which quotes real time market prices and the Zapper API that gives prices for more complex assets.</p><p>The bad debt dashboard is fully open source, and currently covers 8 lending platforms on different chains. We welcome PRs to support more protocols. The backend repository is available <a href="https://github.com/Risk-DAO/bad-debt-leaderboard">here</a> and the front end repository is <a href="https://github.com/Risk-DAO/bad-debt-frontend">here</a>.</p><h3>What’s an Insolvent Account?</h3><p>In Compound, and other similar protocols, an insolvent account is one whose borrowed balance exceeds its total collateral amount (in dollar terms).</p><p>Usually when an account exceeds the collateral amount it is liquidated by a third party (e.g. a bot) for an incentive and the user forfeits their collateral to make the debt whole. However, when an account is not liquidated on time, the liquidated collateral might not be enough to cover the position’s debt, and it adds to the amount of <em>bad deb</em>t within the protocol — which can pose a risk to users.</p><h3>Risks to Users</h3><p>There is no way to force users with bad debt to return their loan. The reason that a large amount of bad debt poses a risk to users is straightforward: as bad debt builds up, more users will be unable to withdraw their funds. And due to the design of Compound and similar protocols, the last to withdraw from the protocol will realize the loss.</p><p>For example, if a protocol has $70m in bad debt, it means that $70m of the deposited funds are un-withdrawable, and the last user(s) to withdraw will be forced to take on the $70m loss.</p><p>We hope that this dashboard helps better visualize the risks associated with various protocols across the DeFi ecosystem!</p><h3>About Risk DAO</h3><p>Risk DAO is a service DAO focused on providing a new, open source risk assessment framework and associated audits to DeFi lending and borrowing protocols as well as L1 networks.</p><p>You can follow us on Twitter <a href="https://twitter.com/Risk_DAO">here</a>. You can join our Discord <a href="https://discord.com/invite/NYyeDQDDvM">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c855cc1f2163" width="1" height="1" alt=""><hr><p><a href="https://medium.com/risk-dao/introducing-the-bad-debt-dashboard-c855cc1f2163">Introducing the “Bad Debt” Dashboard</a> was originally published in <a href="https://medium.com/risk-dao">Risk DAO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vesta Finance: System Parameterization Risk Analysis]]></title>
            <link>https://medium.com/risk-dao/vesta-finance-system-parameterization-risk-analysis-b52aaf7b56e5?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/b52aaf7b56e5</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[vesta-finance]]></category>
            <category><![CDATA[stable-coin]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Tue, 31 May 2022 15:19:05 GMT</pubDate>
            <atom:updated>2022-05-31T15:29:21.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zVHTx8JCt7j9m__o" /></figure><p>During the month of May 2022, Risk DAO was engaged to perform a risk analysis for Vesta Finance’s system parameters. The full report is publicly available <a href="https://github.com/Risk-DAO/Reports/blob/main/Vesta%20Finance:%20System%20Parameterization%20Analysis.pdf">here</a>. In this blog post, we summarise the results of our analysis and compare them to the current state of Vesta Finance.</p><h3>Background</h3><p>Vesta Finance is a zero interest rate lending protocol. It allows users to borrow VST, a USD-pegged stable coin, against a list of collateral assets. Similar to <a href="https://docs.liquity.org/">Liquity protocol</a>, it allows users to stake their VST into <strong>stability pools</strong>, which are used as the first liquidity source in times of liquidations.As another layer of protection, if the stability pool is empty, liquidations are executed by distributing the liquidated user’s collateral and debt among all other borrowers in the system.</p><p>Finally, to make sure VST is traded with a value of at least $1, it allows redemption of VST in return for an underlying collateral. Stability pool losses, liquidation distribution, and redemptions have severe consequences on the user experience, however the ultimate risk of any lending platform is insolvency. Hence, in this analysis, we focus on system insolvency.</p><p>While the current implementation of Vesta Finance is inspired by Liquity’s design, the team expressed their desire to pivot into a more standard parameterized model and so throughout this report we use Compound compatible definitions and notations.</p><p>In this summary we only discuss the collateral value (a.k.a LTV) and debt ceiling values, and we refer the reader to the <a href="https://github.com/Risk-DAO/Reports/blob/main/Vesta%20Finance:%20System%20Parameterization%20Analysis.pdf">full report</a> for an analysis of more parameters. The collateral value is the amount of VST a user could borrow for each $1 of deposited collateral. The debt ceiling is the maximum amount of VST that can be borrowed by all users against a certain collateral. Both values are configurable and can be set with a different value for each collateral type.</p><h3>Quantitative simulation</h3><p>At Risk DAO we’ve developed a novel <a href="https://github.com/Risk-DAO/Reports/blob/main/Risk%20Analysis%20Framework.pdf">simulation model</a>. We take real world liquidation data of popular assets from centralised exchanges, along with the price trajectory of the assets. We then extrapolate the liquidation sizes and price trajectory to the asset we wish to analyse, and simulate the outcome based on the asset’s available DeFi liquidity. Our approach eliminates most assumptions over user behaviour during market crashes, and makes it more feasible to analyse the risk of a platform prior to its launch, and for multichain lending platforms, where the data for user behaviour is even more sparse.</p><p>The simulation model is used to reason about the safety of collateral factor and debt ceiling values (and in the full report we also use it to reason about additional risk parameters).</p><p>With the model we run hundreds of thousands of simulations to estimate the expected system insolvency under each scenario. The figure below shows a single simulation run, with price trajectory (in green), market liquidity (red), liquidation volume (yellow) and stability pool size (orange) change over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*08YpRAfvKBQGmkQ4OzcH1A.png" /></figure><h3>Qualitative assessment and best practices</h3><p>Vesta Finance, and the entire Arbitrum L2 ecosystem, are both at an early stage in their life cycle. As such, there is a lot of uncertainty and potential issues that mathematical models cannot quantify. Some potential issues, such as smart contract bugs or rug pulls, are better mitigated by placing a debt ceiling to cap the worst case scenarios. Other issues, such as a lagged oracle price can be mitigated by reducing the collateral factor.</p><p>For the Vesta Finance analysis we took the following considerations into account:</p><ul><li>Price oracle quality: e.g., Chainlink price feed vs TWAP price oracle.</li><li>The quality of the on-chain liquidity: e.g., is the liquidity organic or incentivised? Is it owned by the protocol? Etc.</li><li>The collateral underlying asset smart contract complexity and other systemic risks.</li></ul><h3>Quantitative analysis results</h3><p>Our quantitative simulation runs different monthly liquidation volumes, which range between x0.5 to x6 of the collateral debt ceiling. For example, if the asset debt ceiling is $10M, then we run simulations for monthly liquidation volumes that range between $5M to $60M.</p><p>Then for every liquidation volume and debt ceiling we run multiple simulations and summarise the result with a number that ranges between 0 to 1. A result of 0.7, for example, suggests that the maximal loss during the worst case liquidation that was simulated was 30%. Thus, under ideal settings, a collateral factor that would have been set to that result would bring the maximum loss to 0. In practice however, the liquidation incentive should also be taken into account, and should be subtracted from the result.</p><p>The results of the simulations also depend on some market conditions, such as the DEX liquidity and the stability pool size. We ran the simulation for tens of thousands of different market parameters, and it is possible to browse all these results <a href="https://medium.com/risk-dao/using-the-riskdao-simulation-gui-2aaffd6c5792">here</a>.</p><p>Below we present the results that best represent the current market conditions. These results can be used to reason about the safety of the current Vesta Finance configuration.</p><h3>ETH</h3><p>Currently Vesta does not have a debt ceiling for the ETH collateral, however the current VST debt that is backed by ETH amounts to $2.7M. The stability pool of ETH consists of 25% of the total debt.</p><p>The simulation results for these parameters are depicted in the figure below. As Vesta is still an early stage protocol, we recommend that an average of the results for factors 0.5–2 should be used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/0*OKFzAH_wYenvoJUh" /></figure><p>Result: As mentioned previously, ETH does not have a debt ceiling in Vesta, and we advise the team to set a ceiling. If there were a debt ceiling of $10M, the current risk parameters in Vesta would successfully pass our simulation stress tests.</p><h3>gOHM</h3><p>Currently Vesta has a debt ceiling of $2M of gOHM. The simulation results for these parameters are depicted in the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/0*Hsd5bA4RyLqSpONf" /></figure><p>Result: The current risk parameters in Vesta successfully pass our simulation stress tests.</p><h3>renBTC</h3><p>Currently Vesta does not have a debt ceiling for the renBTC collateral, however the current VST debt that is backed by renBTC amounts to $0.6M. The stability pool of renBTC consists of 10% of the total debt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/0*PDcqxIUWbg3bbAzz" /></figure><p>Result: Currently renBTC does not have any debt ceiling, and we advise the team to set one. For the current renBTC debt, the current risk parameters in Vesta successfully pass our simulation stress tests.</p><h3>GMX</h3><p>Currently Vesta defines a $1M debt ceiling for GMX collateral. The simulation results for these parameters are depicted in the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/0*FqsbsQqT5G6rt6j6" /></figure><p>Result: the current risk parameters in Vesta successfully pass our simulation stress tests.</p><h3>DPX</h3><p>Currently Vesta defines a $3M debt ceiling for DPX collateral. The simulation results for these parameters are depicted in the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/0*LWW0uK8VeG8DcntB" /></figure><p>Result: the current risk parameters in Vesta successfully pass our simulation stress tests.</p><h3>Qualitative analysis results</h3><p>The table below shows the result of our qualitative analysis and in the <a href="https://github.com/Risk-DAO/Reports/blob/main/Vesta%20Finance:%20System%20Parameterization%20Analysis.pdf">full report</a> we also give a score for each of the assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*UDnbPlVqrwSbP3TJ" /></figure><h3>Price oracles</h3><p>Vesta Finance uses a Chainlink price feed for ETH, however they currently do not use any sanity check for the return result. Furthermore, for renBTC the price of BTC is taken, without a sanity check for a possible deviation of renBTC to BTC price. The GMX oracle is a Uniswap v3 TWAP oracle, with a TWAP window of 30 minutes, and thus will lag. The DPX price oracle is operated by the DPX team.</p><h3>Liquidity</h3><p>renBTC on Arbitrum heavily depends on a single DEX, namely, the renBTC/WBTC pair on CurveFi, with only 200 liquidity contriubtors. gOHM and DPX liquidity are incentivized by liquidity mining and heavily fluctuate on Arbitrum.</p><h3>Additional Risks</h3><p>renBTC suffers from custodian risk. gOHM, GMX, and DPX can all be minted and/or upgraded upon a governance decision. More details about their governance are given in the full report.</p><h3>Debt ceiling</h3><p>In the full report we advise the team to apply a debt ceiling policy that stems both from the quantitative and the qualitative analysis. At the time of writing, the policy is yet to be implemented, and in particular, some of the assets still have an infinite debt ceiling.</p><p>For more details please see the <a href="https://github.com/Risk-DAO/Reports/blob/main/Vesta%20Finance:%20System%20Parameterization%20Analysis.pdf">full report</a>.</p><h3>About Risk DAO</h3><p>Risk DAO is a service DAO focused on providing a new, open source risk assessment framework and associated audits to DeFi lending and borrowing protocols as well as L1 networks.</p><p>You can follow us on Twitter <a href="https://twitter.com/Risk_DAO">here</a>. You can join our Discord <a href="https://discord.com/invite/NYyeDQDDvM">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b52aaf7b56e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/risk-dao/vesta-finance-system-parameterization-risk-analysis-b52aaf7b56e5">Vesta Finance: System Parameterization Risk Analysis</a> was originally published in <a href="https://medium.com/risk-dao">Risk DAO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Risk DAO]]></title>
            <link>https://medium.com/risk-dao/introducing-risk-dao-75a241115c95?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/75a241115c95</guid>
            <category><![CDATA[stable-coin]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[risk-assessment]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Wed, 25 May 2022 14:20:09 GMT</pubDate>
            <atom:updated>2022-05-25T14:20:09.927Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lMlJ0HAfRw0knitm" /></figure><p>We’re excited to announce the launch of <a href="https://twitter.com/Risk_DAO">Risk DAO</a> — a service DAO spearheaded by <a href="https://www.bprotocol.org/">B.Protocol</a> and <a href="https://twitter.com/1kxnetwork">1kx</a> that will focus on providing a new, open source risk assessment framework and associated audits to DeFi lending and borrowing protocols as well as L1 networks.</p><h3>Why Risk DAO?</h3><p>Lending, borrowing, and CDP protocols account for over 30% of DeFi’s $110B total value locked. As a dominant sector in a rapidly growing industry, it’s important that we build open source tools and resources to make protocols safer and the risks more clear for users. Risk DAO will aim to do just that.</p><p>Tens to hundreds of millions of dollars have been wiped out or put at risk due to economic exploits and/or mismanagement of borrowing protocols, further highlighting the need for objective third party risk assessments and frequent monitoring.</p><p>Our new methodology takes in to account real world liquidation data of popular assets from centralized exchanges, along with the price trajectory of the assets in question. We extrapolate the liquidation sizes and price trajectory to the asset we wish to analyze, and simulate the outcome based on the asset’s available DeFi liquidity. This approach eliminates most of the assumptions that are usually made in risk assessments in the DeFi ecosystem regarding user behavior during market crashes, and makes it more feasible to analyze the risk of a platform, including for multichain lending platforms, where the data for user behavior is even more sparse.</p><h3>Our Services</h3><p>Here’s a summary of the services we’ll offer to DeFi protocols and L1s, all of which are rendered as one time audits, with the potential for ongoing collaboration:</p><ul><li>Stress tests (e.g. bad debt likelihood, liquidation performance)</li><li>Parameter optimization (e.g. collateral factor (MCR), liquidation penalty)</li><li>Survey of collateral risks (e.g. price oracle strength, liquidity)</li><li>Chain specific analysis (e.g. liquidity propagation time, block time and gas costs)</li></ul><p>These various aspects of a borrowing system are analyzed through an in-house risk assessment model built by B. Protocol that’s outlined in depth <a href="https://medium.com/b-protocol/data-extrapolation-framework-for-risk-assessment-of-defi-lending-platforms-290945d11cb7">here</a>.</p><h3>Work With Us</h3><p>Building a new project? Looking to make your protocol more robust? Reach out on <a href="https://twitter.com/Risk_DAO">Twitter</a>, <a href="https://t.me/koltenb">Telegram</a>, or <a href="https://discord.gg/NYyeDQDDvM">Discord</a> and we’ll handle the rest!</p><p>If you’re still unsure, explore what we’ve built further by reading <a href="https://medium.com/b-protocol/data-extrapolation-framework-for-risk-assessment-of-defi-lending-platforms-290945d11cb7"><em>Data Extrapolation Framework for Risk Assessment of DeFi Lending Platforms</em></a><em> </em>or the full report outlining our risk analysis framework <a href="https://github.com/backstop-protocol/whitepaper/blob/master/Risk%20Analysis%20Framework.pdf">here</a>.</p><h3>Join Us</h3><p>Last, but not least, like any new DAO <strong>we’re looking for talented individuals</strong>. If you’re interested in math, risk analysis, data analytics, or becoming a researcher,<strong> </strong><a href="https://discord.gg/NYyeDQDDvM"><strong>join the Discord and fill out a membership request</strong></a>. Specifically, we’re looking for those with skills in:</p><p>• Technical Writing (academic experience is a plus)</p><p>• Designing and implementing mathematical models</p><p>• DeFi Security</p><p>• DeFi Research and Writing</p><p>• Data Analytics</p><p>After you fill out the membership request form, we’ll follow up ASAP. Note: We’ll be scaling slowly at first as we work out the kinks associated with running a new DAO, but as things get rolling we’ll continue to onboard interested applicants.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75a241115c95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/risk-dao/introducing-risk-dao-75a241115c95">Introducing Risk DAO</a> was originally published in <a href="https://medium.com/risk-dao">Risk DAO</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Liquity Sponsors #HackMoney2021]]></title>
            <link>https://medium.com/liquity/liquity-sponsors-hackmoney2021-59f019aa624e?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f019aa624e</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[ethglobal]]></category>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[moneyhack]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Wed, 16 Jun 2021 15:29:48 GMT</pubDate>
            <atom:updated>2022-06-17T16:14:21.391Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UfUNwgAVEupa6AsT1DmpKQ.png" /></figure><p>We’re excited to announce that we’re sponsoring ETHGlobal’s Hack Money 2021 event taking place June 18th—July 9th!</p><p><em>The application deadline has been extended to June 17th, </em><a href="https://defi.ethglobal.co/"><strong><em>apply here</em></strong></a><em>.</em></p><h3>Interest-free Borrowing</h3><p>Liquity is a decentralized borrowing protocol that allows you to draw 0% interest loans against ETH used as collateral. Loans are paid out in LUSD — a USD pegged stablecoin, and need to maintain a minimum collateral ratio as low as 110%.</p><p>In addition to the collateral, the loans are secured by a <a href="https://docs.liquity.org/faq/stability-pool-and-liquidations">Stability Pool</a> containing LUSD and by fellow borrowers collectively acting as guarantors of last resort. Learn more about these mechanisms <a href="https://docs.liquity.org/faq/stability-pool-and-liquidations#what-are-liquidations">here</a>.</p><p><strong>Liquity as a protocol is non-custodial, immutable, and governance-free</strong>.</p><p>Since our launch on April 5, 2021, Liquity has grown to become the <a href="https://defipulse.com/liquity">9th largest</a> Ethereum-based DeFi protocol with over 5,000 members on Discord and a community of 20+ <a href="https://www.liquity.org/frontend">Frontend Operators</a> contributing to the decentralization of the protocol.</p><h3>Need Inspiration?</h3><p>We hope to keep this hackathon as open-ended as possible, but definitely understand if you need help with ideas. Our community has shared a few areas of interest over the past few weeks including:</p><ul><li>Trove management tools (avoiding liquidations, redemptions, etc.)</li><li>Migration tools (Maker to Liquity, Compound to Liquity, etc.)</li><li>Auto-leveraging / deleveraging tools</li><li>One-click multi-tasking using DS Proxy (e.g. claim LQTY rewards + stake)</li><li>Products that increase LUSD demand by utilizing Curve, Yearn, Pickle Finance, or other integrations.</li></ul><p>Feel free to search <a href="https://discord.com/invite/2up5U32">our Discord</a> for more ideas or ask us in the #sponsor-liquity channel of the ETHGlobal Discord.</p><p>We also hosted a hackathon before our April launch, you can see the winning projects <a href="https://medium.com/liquity/liquity-gr9-hackathon-winners-f5566a30958f">here</a>.</p><h3>Prizes</h3><ul><li>🥇 First place: $2,500 in LQTY</li><li>🥈 Second place: $1,500 in LQTY</li><li>🥉 Third place: $1,500 in LQTY</li><li>🌊 Pool (split between all valid submissions): $1,500 in LQTY</li></ul><p><em>Note: LQTY is Liquity’s secondary token. It can be earned by Liquity users and staked to earn revenue generated by the protocol.</em></p><h3>Resources</h3><p>If you’re new to Liquity, these are the best resources to get started:</p><ul><li><a href="https://www.liquity.org/">https://www.liquity.org/</a></li><li><a href="https://docs.liquity.org/">https://docs.liquity.org/</a></li><li><a href="https://github.com/liquity/dev">https://github.com/liquity/dev</a></li><li><a href="https://medium.com/liquity">https://medium.com/liquity</a></li></ul><h3>Join Our Community</h3><p>Don’t hesitate to join our <a href="https://discord.com/invite/2up5U32">community Discord</a>, get active, and ask questions! We can’t wait to see the awesome products and tools you’ll build throughout the event.</p><p><strong>Resources</strong>: <a href="https://www.liquity.org/">Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> | <a href="https://t.me/liquityprotocol">Telegram</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f019aa624e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/liquity-sponsors-hackmoney2021-59f019aa624e">Liquity Sponsors #HackMoney2021</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beginner’s Guide to Trove Management]]></title>
            <link>https://medium.com/liquity/a-beginners-guide-to-trove-management-5d876891e1cd?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d876891e1cd</guid>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[borrowing]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[stable-coin]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Thu, 10 Jun 2021 15:59:25 GMT</pubDate>
            <atom:updated>2022-06-17T16:03:46.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*mI6X7NfEtCEdNW00AKhEBg.png" /></figure><p>Opening a Trove and borrowing LUSD can be stressful, but it doesn’t have to be! In this guide, I’ll be going over the basics of Trove management including what to keep an eye on, the risks, and how to protect yourself from those risks.</p><h3>Opening a Trove</h3><p>Our community moderator, Derrick, has already written a step-by-step guide on opening a Liquity Trove (<a href="https://medium.com/@DerrickN_/how-to-borrow-lusd-using-liquity-d5df73c13421">found here</a>), so I’ll skip straight to the important stuff.</p><p>When you navigate to a <a href="https://www.liquity.org/frontend#use-liquity">frontend</a> to open a Trove, you’ll eventually be presented with information like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*e3m2yrqwF654M0m9q2VliA.png" /></figure><p>The Liquidation Reserve and the Borrowing Fee are easy enough. The Liquidation Reserve is a flat 200 LUSD that is “set aside” from your debt and awarded to liquidators in the event your Trove is liquidated. It’s not a “real” fee, and you get it back whenever you pay back your debt.</p><p>The Borrowing Fee is a one-time fee ranging from 0.5% to 5% that is added to your debt. Remember: Liquity doesn’t charge interest on loans and there’s no time limit on your debt — pay once and keep your LUSD as long as you like. To get your ETH collateral back, you simply pay back all of your LUSD, which doesn’t incur an extra fee.</p><p>Next, you should check your collateral ratio and (depending on the frontend) your liquidation price:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*AziDLWVQznt18wEeb6oWCw.png" /></figure><p><em>Note: If your frontend doesn’t show a liquidation price, you can calculate it yourself using the following formula: </em><em>(110 * ETH price) / Collateral Ratio .</em></p><p>Your Trove’s collateral ratio is the ratio between the Dollar value of your ETH collateral (according to Chainlink ETH:USD price feed) in your Trove and its debt in LUSD. You can influence the ratio by adjusting your Trove’s collateral and/or debt up or down:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/269/1*PE8wMTjuTvoLstcAbJpVHA.gif" /></figure><p><em>Note: As the price of ETH fluctuates, so does your collateral ratio. If ETH price goes up, your collateral ratio goes up and vice versa. LUSD’s price is not relevant for calculating your collateral ratio.</em></p><p>Under normal operation, a 110% collateral ratio is the <em>minimum</em> required by Liquity. This means that if your collateral ratio drops below 110%, your Trove <em>will</em> <em>be liquidated</em> — i.e. your ETH collateral will be forfeited and distributed to Stability Pool depositors. In the event you’re liquidated, you’ll still keep your borrowed LUSD, but your Trove will be closed.</p><p>Under <a href="https://docs.liquity.org/faq/recovery-mode">Recovery Mode</a> the rules are different. Recovery Mode is “activated” when the Total Collateral Ratio (i.e. the Dollar value of the entire system collateral at the current ETH:USD price, to the entire system debt) of the system goes below 150%. When the system is in Recovery Mode, the liquidation rules change, and Troves with a collateral ratio of <strong>150% or lower</strong> are eligible for liquidation.</p><p><em>Note: Troves can be liquidated out of order, meaning high-value Troves may be liquidated before riskier, lower-value Troves.</em></p><p>With both of those collateral ratio requirements in mind, let’s go over some ways to try to avoid liquidation.</p><h3>Avoiding Liquidations</h3><p>As a Trove owner, avoiding liquidation is likely going to be your number one priority. After all, no one wants to lose 10% of their position, and getting liquidated can be stressful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*WSaOzZAc1qCskCPo8wPiKw.png" /></figure><p>To avoid liquidations, be sure to pick a collateral ratio /liquidation price that you are <em>comfortable</em> with. For example, advanced DeFi users may be comfortable with a 165% collateral ratio, but less risky users should give themselves more room to work with. The price of ETH is volatile, which means your collateral ratio can rise and fall quickly. If you won’t be around to save your Trove during a big dip, make sure you have a large enough safety net.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*SDQcpeBbgs1nysSGDmYlkQ.png" /><figcaption>ETH price in May. Source: TradingView</figcaption></figure><p>In May ’21 alone ETH had multiple 20+% price drops — when opening a Trove, you should keep that in mind as you’re deciding on a collateral ratio / liquidation price that works for you. For example: if you’re a passive DeFi user, opening a Trove with a 130% collateral ratio is a <strong>risky</strong> move. If ETH drops 21% and you’re not around, you’re getting liquidated.</p><p>For risk averse users, or users who don’t plan on managing their Trove every day or so, it’s generally recommended to maintain a collateral ratio (CR) that is comfortably above both the 110% minimum CR and the 150% Recovery Mode CR. This protects you in <em>both </em>scenarios. An example ratio for risk averse users might be 200%-250% or higher. You may lose some capital efficiency, but you can keep your peace of mind — which of those is more important is up to you.</p><p><em>Note: Advanced DeFi users will always be able to get the most out of borrowing with Liquity, but please avoid taking on risk that you’re not comfortable with just because others are doing so.</em></p><h3>Avoiding Redemptions</h3><p>The next type of “risk” you should keep in mind is redemption risk and how it may affect your Trove. Sometimes people confuse being redeemed against with liquidations or partial liquidations, but they are quite different.</p><p>I’ve written a separate blog post explaining redemptions in detail (<a href="https://medium.com/liquity/understanding-liquitys-redemption-mechanism-b9f2fc78cddb">found here</a>), so I’ll skip to the important stuff as I did earlier.</p><p>How redemptions work is straightforward:</p><ul><li>Someone comes along to redeem LUSD</li><li>All Troves are sorted from lowest collateral ratio to the highest collateral ratio (i.e. most risky to least risky)</li><li>The redeemed LUSD is used to pay off the debt of the riskiest Trove(s) in return for their collateral</li></ul><p>This means that it’s possible for someone to pay off your debt in return for your collateral if you’re among the riskiest Troves — <strong><em>regardless of your collateral ratio</em></strong><em>. </em>While getting redeemed has its cons, there are two things to keep in mind:</p><ul><li>You aren’t “losing” money, the effect a redemption has on your Trove is net neutral. While you lose some ETH collateral, you also “lose” debt — i.e. you have less debt to pay back post-redemption.</li><li>Since the impact on your position is net neutral, they’re not the same as a liquidation. In the event you’re liquidated, you <strong>lose </strong>10% of your Trove’s value. That’s not the case with redemptions.</li></ul><p>The biggest con of being affected by redemption is that you lose some of your ETH exposure and will have to buy it back. But fear not, there is a simple strategy to avoid redemptions: avoid being among the riskiest Troves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7bMEePBw21jY2lwDM_yuw.png" /></figure><p>Almost every Liquity frontend provides a list of <a href="https://liquity.app/#/risky-troves">risky Troves</a> as shown above. To get an idea of your redemption risk, you can see where you rank among the risky Troves and how much LUSD debt is front of your Trove.</p><p>For example, if you’re on the first page of the list, there’s a good chance you’ll be redeemed against. If you’re on the fifth page of the the list, and a few million LUSD debt is ahead of you, you’re likely safe from redemptions for the time being.</p><p>If redemptions are something that concerns you, ensuring that you have a big enough buffer between your Trove and the riskiest Troves is the safest strategy to avoid them. You can also find a list of redeemed Troves <a href="https://duneanalytics.com/dani/Liquity">here</a> and use that to get an idea of what collateral ratios are frequently redeemed against.</p><h3>Gas Prices</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AC2m54MumAYhsedKDoKQmw.png" /><figcaption>Source: Coin Metrics</figcaption></figure><p>The last thing I want to touch on is Ethereum’s gas prices, which are <em>volatile — </em>especially in times of market stress. This has nothing to do with Liquity itself and everything to do with demand for Ethereum block space. When the price of ETH is dropping quickly, every other user on Ethereum is trying to adjust their DeFi positions at the same time as you, making fees more expensive than normal.</p><p>Please keep this in mind throughout your Trove management process. If ETH drops quickly, will you have to panic to pay off your debt or add more collateral? If so, are you prepared to pay high gas prices? If that sounds stressful, then be sure to consider such scenarios when interfacing with Liquity or any other DeFi protocol. Giving yourself enough room to breathe in times of market stress is never a bad strategy when managing your Trove.</p><h3>What now?</h3><p>With all of the tips out of the way, you should be ready to start experimenting with Liquity. You can do so by navigating to the Liquity frontend registry <a href="https://www.liquity.org/frontend#use-liquity">here</a>. We also expect more advanced Trove management tools like Instadapp and DeFi Saver to go live soon — making the above processes easier.</p><p>If you’re still confused by anything, please refer to Derrick’s tutorial, <a href="https://medium.com/@DerrickN_/how-to-borrow-lusd-using-liquity-d5df73c13421"><em>How to Borrow LUSD using Liquity</em></a>, and our <a href="https://docs.liquity.org/">FAQ</a>.</p><p>If you’d like to join the community, you can find us on <a href="https://discord.com/invite/2up5U32">Discord</a>!</p><p><strong>Resources</strong>: <a href="https://www.liquity.org/">Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> | <a href="https://t.me/liquityprotocol">Telegram</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d876891e1cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/a-beginners-guide-to-trove-management-5d876891e1cd">A Beginner’s Guide to Trove Management</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Liquity Handled its First Big Stress Test]]></title>
            <link>https://medium.com/liquity/how-liquity-handled-its-first-big-stress-test-160f20d5b18f?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/160f20d5b18f</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[stable-coin]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[liquity]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Wed, 19 May 2021 17:16:34 GMT</pubDate>
            <atom:updated>2022-06-17T16:01:53.833Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*RZKFch4d9zxquDtfcK73cA.png" /></figure><p>On 5/19/2021, Liquity faced its first big stress test as the ETH price dropped (rather quickly) from ~$3,400 to ~$1,800 on some exchanges. In this post, I’ll provide a brief recap of what happened.</p><h3>Market Turmoil</h3><p>First things first, Liquity handled today’s extreme market conditions as designed. As ETH’s price plummeted, we saw over 300 Troves liquidated, some under regular liquidation conditions and some under the liquidation conditions permitted by Recovery Mode, which Liquity briefly entered twice during the chaos.</p><p>Big shoutout to Chainlink’s ETH:USD price feed for holding its ground and providing up-to-date price information — keeping Liquity on track!</p><p>For those unfamiliar: Under normal conditions, Troves with a collateral ratio lower than 110% can be liquidated. In Recovery Mode, which activates when the <em>Total Collateral Ratio</em> (TCR) of the system drops below 150%, Troves with a collateral ratio lower than 150% can be liquidated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*ciLdlqq5No3mf-fVTLbU1Q.png" /></figure><p>In the chart above, you can see how quickly the system was able to handle liquidations in times of severe stress — starting the day with 1,054 Troves and ending with ~677 Troves by the time the ETH drop slowed according to <a href="https://duneanalytics.com/dani/Liquity">Dune Analytics</a>.</p><p>In total, 121 Troves were liquidated under normal conditions while 189 Troves were liquidated under Recovery Mode conditions (<a href="https://duneanalytics.com/queries/49426">query here</a>). However, it’s worth noting we don’t have precise data on how many Troves were actually liquidated <em>above</em> 110% in Recovery Mode at this time.</p><p>Either way, facilitating liquidations in this manner kept Liquity healthy and allowed the system to bounce quickly out of Recovery Mode each time it entered. In fact, the bounces happened too quickly for Dune to pick up on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*sEFC5Q88jdnrWvFe2qZg9A.png" /></figure><p>Despite the large amount of liquidated positions, the Stability Pool was able to effectively absorb all of the defaulted debt. ~93.5M LUSD debt was offset against the Stability Pool and ~48,668 of liquidated ETH was distributed to Stability Pool depositors. With the ETH price now recovering, this means Stability depositors should be in the green and were able to “buy the dip”.</p><p>Note: If you’re unfamiliar with the Stability Pool, I recommend reading <a href="https://medium.com/liquity/understanding-liquitys-stability-pool-212cec402db5"><em>Understanding Liquity’s Stability Pool</em></a>.</p><h3>Aftermath</h3><p>Now that the storm has calmed, the system remains in a healthy state with all defaulted debt made whole, Stability Depositors in the green, and a Total Collateral Ratio of 281% at time of writing. Here are some quick stats summarizing what’s left:</p><p>~880M LUSD remains in circulation after ~460M LUSD was burned by users paying back debts, redeeming LUSD, or through liquidations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/929/1*ulU5EHcw5uvSLaowWB_nqg.png" /></figure><p>~909k ETH ($2.47B) still remains in the system, spread across 677 Troves:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*UQhgA6bHD_5L0aB7ZMmpBw.png" /></figure><p>All in all, we’re proud of how Liquity behaved during its biggest test to date. That said, we understand that getting liquidated is <em>not fun</em>, especially when gas fees are a prohibitive factor. You can find a resource on maintaining a “safe” collateral ratio <a href="https://docs.liquity.org/faq/borrowing#what-is-the-minimum-collateral-ratio-mcr-and-the-recommended-collateral-ratio">here</a>. If you need support or have questions about Liquity and how it works, feel free to <a href="https://discord.com/invite/2up5U32">join our Discord</a>.</p><p><strong>Note</strong>: Stay tuned for a sequel where we cover LUSD’s price behavior, as we believe Coingecko’s price data may not be telling the full story. We’re still gathering the data and will put something out ASAP.</p><p><strong>Resources</strong>: <a href="https://www.liquity.org/">Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a> | <a href="https://t.me/liquityprotocol">Liquity Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=160f20d5b18f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/how-liquity-handled-its-first-big-stress-test-160f20d5b18f">How Liquity Handled its First Big Stress Test</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Liquity’s Stability Pool]]></title>
            <link>https://medium.com/liquity/understanding-liquitys-stability-pool-212cec402db5?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/212cec402db5</guid>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[stable-coin]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Tue, 20 Apr 2021 15:37:17 GMT</pubDate>
            <atom:updated>2022-06-16T19:02:39.613Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*1uT-fWeDgqjQW2hbysVOkA.png" /></figure><p>Since launch, LUSD deposited to Liquity’s Stability Pool has continued to grow — recently crossing 1.1B deposited. As a result, we want new users and our community to fully understand the mechanisms at play.</p><p>In this post, I’ll be going over the basics of the Stability Pool, how it works, and some things to keep in mind when depositing.</p><h3>What is the Stability Pool?</h3><p>Liquity’s Stability Pool is the first line of defense in maintaining system solvency. In other words, the Stability Pool absorbs and cancels debt from defaulted (i.e. liquidated) Troves — a responsibility usually managed by collateral auctions in systems like MakerDAO.</p><p>How the Stability Pool replaces such auctions is straightforward: it allows LUSD holders to commit capital <em>upfront</em> in order to “buy” liquidated ETH and offset the bad debt. This is an appealing swap due to the over-collateralization of Troves. In general, Stability Providers will receive more ETH (in $ terms) than LUSD burned — enjoying a nice discount on ETH.</p><p>All a user must do is deposit LUSD to the Stability Pool and wait. Then, when a Trove gets liquidated, its ETH collateral is distributed proportionally to all Stability Pool depositors (Stability Providers) and a proportional amount of LUSD is burned across all Stability Providers to pay off the defaulted debt.</p><p>Here’s a visual:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*wi0xyz06B0y8EtXstOmjyQ.png" /><figcaption>1) Trove gets liquidated, ETH collateral is distributed to Stability Providers.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*_ZVg9BKTtzE6vNUNoseH4Q.png" /><figcaption>2) LUSD is burned from Stability Pool to “pay off” the Trove’s bad debt.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*qjXCfGVuTwxnW_5W8wLlyg.png" /><figcaption>3) Stability Providers receive more ETH (in $ terms) than LUSD burned due to over-collateralization.</figcaption></figure><p>The Stability Pool democratizes access to otherwise complex and lengthy collateral auctions while also yielding another benefit: quick liquidations. Due to the quick liquidations facilitated by the Stability Pool, Liquity is able to allow for a low minimum collateral ratio of 110% —improving capital efficiency for borrowers.</p><p>Since we’ve already covered this dynamic in a previous post, I won’t cover it here. I recommend reading <a href="https://medium.com/liquity/how-faster-liquidations-improve-capital-efficiency-5589174f75c0"><em>How Faster Liquidations Improve Capital Efficiency</em></a> for more details. Moving on…</p><h3>Why Deposit to the Stability Pool?</h3><p>The primary reason someone might deposit to the Stability Pool is to simply acquire ETH at a discount whenever Troves get liquidated — we’re all ETH bulls here, aren’t we? But there’s another reason that sweetens the deal: LQTY rewards.</p><p>Since the Stability Pool is a fundamental piece of Liquity’s infrastructure, it’s important to ensure that Stability Providers are properly incentivized by the protocol. To do this, Liquity distributes LQTY rewards pro-rata to Stability Providers for the duration of their deposit. Put differently: The more LUSD a user has in the pool and the longer they keep it deposited, the more LQTY rewards they receive. Those LQTY rewards can then be claimed and <a href="https://docs.liquity.org/faq/staking">staked</a> to earn fees generated by the protocol.</p><p>All-in-all, Stability Providers are volunteering to give up their LUSD exposure in order to ensure system solvency, acquire liquidated ETH, and earn LQTY rewards over time.</p><h3>Things to Keep in Mind</h3><p>While depositing to the Stability Pool might seem like a dream come true, there are still some things to keep in mind.</p><p>First thing to keep in mind is that Liquity frontends give users a “kickback rate” on Stability Pool deposits. The kickback rate specifies how Stability Pool rewards are split between a frontend and its users. For example, A 99% kickback rate means that users receive 99% of their LQTY rewards while the frontend receives 1%. <a href="https://docs.liquity.org/faq/frontend-operators#what-is-the-kickback-rate">More details here</a>.</p><p>The second thing to keep in mind is that you will be losing LUSD over time — most accidentally overlook this. The rate at which your deposit decreases depends the frequency and size of liquidations occurring over the duration of your deposit. This means that there’s no predictable decay rate for users’ LUSD.</p><p>The last thing to keep in mind is that depositing to the Stability Pool isn’t “risk-free”. By committing to “buy” liquidated ETH upfront, users are also committing to buying ETH during price drops. This means that it’s possible for the ETH that users receive to be worth less shortly after receiving it due to a quick price drop — though over time this should be balanced out by less severe circumstances.</p><p>Now you’ve covered the basics of Liquity’s Stability Pool! If you’re looking to explore the Stability Pool in more detail, I recommend reading <a href="https://medium.com/liquity/how-faster-liquidations-improve-capital-efficiency-5589174f75c0"><em>How Faster Liquidations Improve Capital Efficiency</em></a><em>, </em><a href="https://docsend.com/view/bwiczmy">our whitepaper</a>,<em> </em>and our <a href="https://docs.liquity.org/faq/lusd-redemptions">FAQ</a>.</p><p><strong>Resources</strong>:<a href="https://www.liquity.org/"> Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=212cec402db5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/understanding-liquitys-stability-pool-212cec402db5">Understanding Liquity’s Stability Pool</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Liquity’s Redemption Mechanism]]></title>
            <link>https://medium.com/liquity/understanding-liquitys-redemption-mechanism-b9f2fc78cddb?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9f2fc78cddb</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[stable-coin]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Tue, 13 Apr 2021 16:12:49 GMT</pubDate>
            <atom:updated>2022-06-16T18:59:12.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*ngDKediDfognl10Jvq4umA.png" /></figure><p>After launch, one common source of confusion we’ve seen is around Liquity’s redemption mechanism. Since LUSD redemptions were deactivated for 14 days post-launch, it seems like a good time to fill everyone in as we near the end of the grace period.</p><p>Before we get started, I’ll answer the most common question right away. No, redemptions are <em>not</em> the same as paying back your Trove’s debt. You can do that free of charge and debt repayment has been available since launch.</p><h3>What are LUSD redemptions?</h3><p>LUSD redemptions are one of Liquity’s most unique features. Simply put: The redemption mechanism gives LUSD holders the ability to redeem LUSD at face value for the underlying ETH collateral at any time. Redemptions are always honored such that 1 LUSD equals $1 worth of ETH <em>(minus the current redemption fee).</em></p><p><em>As mentioned above, the redemption mechanism is separate from paying back your Trove’s debt. Paying back one’s debt is free of charge, while redemptions will incur a fee.</em></p><p>How redemptions work is simpler than one might think, let’s walk through it:</p><ul><li>Someone comes along to redeem their LUSD</li><li>All Troves (i.e. positions in Liquity) are sorted from lowest collateral ratio to the highest collateral ratio (most risky to least risky)</li><li>The redeemed LUSD is used to pay off the debt of the riskiest Trove(s) in return for their collateral</li><li>The Trove owner’s remaining collateral is left for them to claim (borrowers who are redeemed against do not incur a net loss)</li></ul><p>Yes, you read that correctly. Redemptions pay off the debt of Liquity’s riskiest users in return for their collateral.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*Axh-uxYZ_bFjIDU5.gif" /></figure><p><em>Note: By default, redemptions incur a fee of at least 0.5%, making them unattractive outside of below peg arbitrage opportunities.</em></p><h3>Why allow LUSD redemptions?</h3><p>While the ability to pay off someone else’s debt in return for their collateral seems strange at first, redemptions play a key role in Liquity.</p><p>One important feature of redemptions is that they help protect LUSD’s price floor of $1 through direct arbitrage. When LUSD is floating below peg, an arbitrageur can simply redeem their LUSD against the system as if it was worth $1. As a result, this shrinks the outstanding supply of LUSD, which will likely have a positive effect on LUSD’s price. On the other hand, when LUSD is at or above peg, redemptions end up being a bad deal for the redeemer.</p><p>A second important feature of redemptions is that they directly affect the borrowing fee charged on newly issued debt. When redemptions occur, the system’s baseRate increases, in turn causing Liquity’s one-time borrowing fee to increase — discouraging people from borrowing and dampening the amount of new LUSD entering the market. When redemptions aren’t occurring, the baseRate gradually decays over time, making it cheaper to borrow and encouraging new LUSD to enter the market.</p><p><em>Note: The </em><em>baseRate also applies to redemptions. Not only does borrowing become more costly as redemptions occur, redemptions become costlier too.</em></p><h3>How can I be affected by LUSD redemptions?</h3><p>As a Trove owner, losing your ETH collateral to a redemption isn’t desirable, but it’s not the end of the world either. If your Trove is redeemed against, you <em>will not</em> incur a net loss — you’ll only lose some of your ETH exposure while receiving a lesser debt burden.</p><p>However, it is possible that your Trove can be “fully redeemed” against. This means that a redemption fully paid off your Trove’s debt in return for a corresponding amount of collateral. If this happens, your Trove will be closed and your surplus ETH collateral will be sent to the CollSurplusPool where you can claim it from your frontend of choice. Even in the event of a full redemption, you don’t incur a net loss. That said, it is possible to keep your Trove out of the “line of fire” and avoid being redeemed against altogether.</p><p>It’s important to remember that the <em>riskiest </em>Troves are redeemed against first — i.e. the Troves with the lowest collateral ratios. To avoid being affected by redemptions, one can simply monitor their position among Troves and adjust accordingly. This strategy becomes even more viable if you notice LUSD starting to float below $1. As long as LUSD is trading above $1, people have no incentive to redeem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lA4xdzDdiu-JkChT2BVxvQ.png" /></figure><p>To help in this process, most Liquity Frontend Operators provide a Risky Troves tab that will allow you to easily monitor your place in line. The less risky your Trove, the less likely you are to be affected by redemptions — so it’s quite easy to steer clear of them. Staying at or above a 150% collateral ratio is generally recommended, however, a Trove can still be redeemed against at <em>any</em> collateral ratio as long as it’s among the most risky. <a href="https://docs.liquity.org/faq/borrowing#what-is-the-minimum-collateral-ratio-mcr-and-the-recommended-collateral-ratio">More on that here</a>.</p><p>Now you’ve covered the basics around redemptions! If you’re looking to explore Liquity’s redemption mechanism in more detail, I recommend reading <a href="https://medium.com/liquity/on-price-stability-of-liquity-64ce8420f753"><em>On Price Stability of Liquity</em></a><em>, </em><a href="https://docsend.com/view/bwiczmy">our whitepaper</a>,<em> </em>and our <a href="https://docs.liquity.org/faq/lusd-redemptions">FAQ</a>.</p><p><strong>Resources</strong>:<a href="https://www.liquity.org/"> Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9f2fc78cddb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/understanding-liquitys-redemption-mechanism-b9f2fc78cddb">Understanding Liquity’s Redemption Mechanism</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Liquity Integrates Leading Oracle Network Chainlink on Mainnet to Secure Lending Operations]]></title>
            <link>https://medium.com/liquity/liquity-integrates-leading-oracle-network-chainlink-on-mainnet-to-secure-lending-operations-d9c4eb9a3eed?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9c4eb9a3eed</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[chain-link]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Mon, 05 Apr 2021 14:59:48 GMT</pubDate>
            <atom:updated>2022-06-16T18:55:16.484Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lOJ2lUkd5rF66g0b" /></figure><p>We are excited to announce that <a href="https://www.liquity.org/">Liquity</a> is now consuming the <a href="https://chain.link/">Chainlink</a> ETH/USD Price Oracle on mainnet. This integration enables Liquity to fetch the most current ETH/USD price data as needed for core protocol functions such as opening Troves, triggering liquidations, or redeeming LUSD. Integrating the <a href="https://data.chain.link/eth-usd">Chainlink ETH/USD decentralized data feed</a> will ensure the safety and accuracy of prices referenced within Liquity, protecting users against downtime and various data manipulation attacks, such as those <a href="https://blog.chain.link/flash-loans-and-the-importance-of-tamper-proof-oracles/">recently experienced in DeFi by flash loans</a>.</p><h3>How Liquity Provides Interest-Free Loans with Greater Capital Efficiency</h3><p>Liquity is a decentralized borrowing protocol that allows users to draw interest-free loans against their ETH collateral, known as Troves. It improves upon similar protocols by implementing an algorithmic monetary policy and a novel, highly efficient liquidation mechanism — allowing for a 110% minimum collateralization ratio as opposed to much higher ratios in other lending protocols. This provides better capital efficiency for borrowers.</p><p>Such a low collateralization ratio (i.e., liquidation threshold) is not achievable in other protocols because the time it takes to liquidate positions could put their system at risk. If the value of the liquidated collateral drops too quickly, the debt may never get settled — under-collateralizing the entire system and putting user funds at risk.</p><p>Liquity solves this problem by handling liquidations as follows:</p><ol><li>Offset under-collateralized Troves using the Stability Pool funded by LUSD tokens</li><li>Redistribute under-collateralized Troves to other borrowers if the Stability Pool is empty</li></ol><p>Liquity first uses the LUSD tokens in its Stability Pool to absorb any under-collateralized debt. Any user may deposit LUSD tokens to the Stability Pool, allowing them to earn the collateral from liquidated Troves. When a liquidation occurs, the liquidated debt is canceled by burning an equal amount of LUSD from the Stability Pool, with the liquidated ETH then distributed to Stability Providers.</p><p>Suppose the liquidated debt is <em>higher</em> than the amount of LUSD in the Stability Pool. In that case, the system tries to cancel as much debt as possible with the tokens in the Stability Pool, then redistributes the remaining liquidated collateral and debt across all active Troves. The combination of these two mechanisms removes the need for inefficient and lengthy collateral auctions. Instead, Liquity can liquidate Troves when a collateralization ratio drops below 110% instantaneously.</p><p>While we’ve explored how Liquity improves the <em>speed</em> of liquidations, there’s one more necessary component to address: the importance of a fast and secure oracle network</p><h3>Leveraging Chainlink for Reliable Price Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GOKUOECT0UEB0top" /></figure><p>The Chainlink <a href="https://data.chain.link/eth-usd">ETH/USD Price Oracle</a></p><p>To make these liquidations possible, Liquity also needs an oracle mechanism for accessing reliable, real-time ETH/USD price data. Since the Liquity protocol itself is governance-free and immutable, we cannot rely on a single source of truth or single oracle for data delivery to obtain the ETH/USD price. If that single source or centralized oracle gets compromised, becomes unresponsive, or otherwise provides faulty information, it would put the entire protocol at great risk.</p><p>We selected Chainlink because it is the most time-tested decentralized oracle solution on mainnet, backed by high-quality data, secure node operators, and a robust reputation framework for proving the security and performance of its systems. In addition to that, Chainlink can be accessed using an immutable proxy interface, which is crucial for Liquity being an immutable protocol. These features are why Chainlink is the most widely used solution in the DeFi industry, already securing 10+ billion dollars in on-chain value for leading projects like Synthetix, Aave, and Nexus Mutual.</p><p>By leveraging Chainlink, Liquity’s ETH/USD reference price is secured by a decentralized network of independent, Sybil-resistant oracle nodes run by leading blockchain DevOps, ensuring high availability and tamperproofness in the delivery of data on-chain. These Chainlink nodes source data from numerous independent high-quality data aggregators like BraveNewCoin and Amberdata, meaning there are multiple data sources that each represent a volume-weighted price aggregated from all relevant centralized and decentralized exchanges. This sourcing method is key because it prevents outlier price data on single exchanges from corrupting the aggregated price referenced by Liquity during the creation of Troves, the redemption of LUSD, and execution of liquidations. Thus, Liquity will consistently issue loans and redeem LUSD at fair market value, as well as keep the protocol fully collateralized and solvent.</p><p>Liquity also benefits from Chainlink’s frequent price updates, which happen every time there is a 0.5% deviation in the ETH/USD price. In other words, borrowers can rest assured that the price is closely following real market rates, and won’t be in for surprises due to a lag in oracle updates.</p><p>All-in-all, Chainlink provides secure external data necessary to protect Liquity and its users in a trust-minimized and reliable way.</p><blockquote>“Using Chainlink oracles to secure collateral, redemptions, and liquidations was a clear step in further securing the Liquity protocol and improving its capital efficiency,” said our Founder Robert Lauko.</blockquote><blockquote>“We’re able to rely on Chainlink to protect user funds against common price feed exploits like flash loan attacks, without spending valuable engineering resources maintaining complex oracle infrastructure. This allows us to focus on building production systems at a much faster pace.”</blockquote><h3>Learn More</h3><p>You can keep up with Liquity on <a href="https://www.liquity.org/">our website</a> or <a href="https://twitter.com/LiquityProtocol">Twitter</a>, and join our <a href="http://discord.gg/2up5U32">Discord</a> to hang out with our community.</p><p>You can also check out our documentation at<a href="https://docs.liquity.org/"> https://docs.liquity.org/</a>.</p><p><strong>About Chainlink</strong></p><p>Chainlink is the most widely used and secure way to power universally connected smart contracts. With Chainlink, developers can connect any blockchain with high-quality data sources from other blockchains as well as real-world data. Managed by a global, decentralized community of hundreds of thousands of people, Chainlink is introducing a fairer model for contracts. Its network currently secures billions of dollars in value for smart contracts across the decentralized finance (DeFi), insurance and gaming ecosystems, among others.</p><p>Chainlink is trusted by hundreds of organizations to deliver definitive truth via secure, reliable data feeds. To learn more, visit <a href="https://chain.link/">chain.link</a>, subscribe to the <a href="https://chn.lk/newsletter">Chainlink newsletter</a>, and follow <a href="http://www.twitter.com/chainlink">@chainlink</a> on Twitter.</p><p><a href="https://docs.chain.link/docs/getting-started">Docs</a> |<a href="https://www.reddit.com/r/Chainlink/"> </a><a href="https://discordapp.com/invite/aSK4zew">Discord</a> | <a href="https://www.reddit.com/r/Chainlink/">Reddit</a> | <a href="https://www.youtube.com/channel/UCnjkrlqaWEBSnKZQ71gdyFA">YouTube</a> | <a href="https://t.me/chainlinkofficial">Telegram</a> | <a href="https://blog.chain.link/tag/events/">Events</a> | <a href="https://github.com/smartcontractkit/chainlink">GitHub</a> | <a href="https://feeds.chain.link/">Price Feeds</a> | <a href="https://www.chain.link/solutions/defi">DeFi</a> | <a href="https://chain.link/solutions/chainlink-vrf">VRF</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9c4eb9a3eed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/liquity-integrates-leading-oracle-network-chainlink-on-mainnet-to-secure-lending-operations-d9c4eb9a3eed">Liquity Integrates Leading Oracle Network Chainlink on Mainnet to Secure Lending Operations</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Liquity GR9 Hackathon Winners]]></title>
            <link>https://medium.com/liquity/liquity-gr9-hackathon-winners-f5566a30958f?source=rss-2ea40c62c05------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5566a30958f</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[liquity]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[gitcoin]]></category>
            <dc:creator><![CDATA[Kolten]]></dc:creator>
            <pubDate>Sat, 03 Apr 2021 16:14:29 GMT</pubDate>
            <atom:updated>2022-06-16T18:48:59.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*P8f142DGtn5t0yew" /></figure><p>Last month we sponsored the Gitcoin Grants Round 9 hackathon where we made three bounties available with 4.8 ETH in prizes:</p><ul><li><a href="https://gitcoin.co/issue/liquity/beta/2/100025005">Redemption Arbitrage Bot</a></li><li><a href="https://gitcoin.co/issue/liquity/beta/3/100025006">Maker to Liquity Migration Tool</a></li><li><a href="https://gitcoin.co/issue/liquity/beta/4/100025007">Open-ended: Best Liquity Tool / Integration</a></li></ul><p>Today, we’re excited to announce the winners of each bounty!</p><h3>Redemption Arbitrage Bot</h3><p>The winner of the Redemption Arbitrage Bot bounty is <a href="https://github.com/chris124567">chris124567</a>. You can find their submission <a href="https://github.com/chris124567/bot">here</a>.</p><p>It works by checking prices from the Uniswap pair and the Chainlink oracle every block. If LUSD is sufficiently cheaper on Uniswap, then the bot will calculate how much it would get by swapping ETH for LUSD on Uniswap after slippage.</p><p>It will then pass the result of that calculation to redeemLUSD and generate the relevant transaction data for the arbitrage smart contract. This smart contract will transfer the specified amount of WETH to Uniswap, execute the swap for LUSD, then redeem the LUSD through the TroveManager contract.</p><h3>Maker to Liquity Migration Tool</h3><p>The winner of the Maker to Liquity Migration Tool bounty is <a href="https://github.com/theonlyfoxy">theonlyfoxy</a>. You can find their submission <a href="https://github.com/HardCod3rs/liquity-migration">here</a>.</p><p>This tool works by using Uniswap to take out a DAI flash loan, fully repays and closes the user’s Maker vault, opens a Trove on Liquity using the ETH released from the Maker vault, exchanges the borrowed LUSD for DAI , and uses the DAI to repay the flash loan.</p><h3>Open-ended: Best Liquity Tool / Integration</h3><p>The winner of our open-ended bounty is <a href="https://github.com/masaun">masaun</a>. You can find their submission <a href="https://github.com/masaun/shared-trove-on-liquity">here</a>.</p><p>Masuan’s submission for this bounty is a shared Trove on Liquity. The tool allows users to pool together their ETH collateral in order to open a Trove — reducing the minimum debt per user, since by default minimum debt is 2,000 LUSD / Trove. The more user’s per shared Trove, the less the minimum debt becomes a burden for users.</p><p><strong>Congratulations to all three winners!</strong> 🎉</p><p>We’re extremely grateful that you all took the time to experiment with Liquity throughout this event and hope you enjoyed the hackathon. We’re looking forward to taking part in many more hackathons in the future and getting Liquity into the hands of more builders.</p><p><strong>Resources</strong>:<a href="https://www.liquity.org/"> Website</a> |<a href="https://twitter.com/LiquityProtocol"> Twitter</a> |<a href="https://discord.com/invite/2up5U32"> Discord</a> |<a href="https://github.com/liquity"> Github</a> |<a href="https://www.reddit.com/r/Liquity/"> Reddit</a> |<a href="https://t.me/joinchat/FHUpr7TiwC2IfI_n"> Liquity 中文社區</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5566a30958f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/liquity/liquity-gr9-hackathon-winners-f5566a30958f">Liquity GR9 Hackathon Winners</a> was originally published in <a href="https://medium.com/liquity">Liquity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>