<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>DeFi on Blog of Christian Felde</title><link>https://blog.cfelde.com/tags/defi/</link><description>Recent content in DeFi on Blog of Christian Felde</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 28 Jun 2026 12:41:49 +0100</lastBuildDate><atom:link href="https://blog.cfelde.com/tags/defi/index.xml" rel="self" type="application/rss+xml"/><item><title>After the Casino</title><link>https://blog.cfelde.com/2026/06/after-the-casino/</link><pubDate>Sun, 28 Jun 2026 12:41:49 +0100</pubDate><guid>https://blog.cfelde.com/2026/06/after-the-casino/</guid><description>&lt;p&gt;I&amp;rsquo;ve been involved with blockchain since around 2018, with a tilt towards TradFi and enterprise use cases. In all that time, the thing that drew me in was never the price. Back in 2021 I wrote a post with the deliberately unhelpful title &lt;a href="https://blog.cfelde.com/2021/08/dont-use-blockchain/"&gt;Don&amp;rsquo;t use blockchain&lt;/a&gt;. The argument was that blockchain is a bad database and a worse computer: slow, expensive, single-threaded by design. It has exactly one job worth paying that cost for: removing third-party risk. You stop having to trust that some operator keeps running the right software and doesn&amp;rsquo;t abuse their access. That&amp;rsquo;s it. Everything else you should minimize.&lt;/p&gt;</description></item><item><title>What the Aave crisis actually showed us</title><link>https://blog.cfelde.com/2026/04/what-the-aave-crisis-actually-showed-us/</link><pubDate>Mon, 27 Apr 2026 10:10:34 +0000</pubDate><guid>https://blog.cfelde.com/2026/04/what-the-aave-crisis-actually-showed-us/</guid><description>&lt;p&gt;If you’ve been watching the rsETH situation unfold over the last week, you’ve probably seen the headlines. A $292M bridge exploit, $13B of TVL fleeing Aave, stablecoin pools pinned at 100% utilization for days, and a slow-motion governance scramble that’s still going on as I write this.&lt;/p&gt;
&lt;p&gt;It’s tempting to file it as “another DeFi hack” and move on. I don’t think we should. This one is unusually instructive, not because the hack itself was novel (it wasn’t, bridges keep getting exploited, and as I’ve said before, I think &lt;a href="https://blog.cfelde.com/2025/07/bridging-is-an-anti-pattern/" title=""&gt;bridging is an anti-pattern&lt;/a&gt;), but because of what the response showed us about how DeFi actually works under stress. We got to see something here that’s hard to see anywhere else.&lt;/p&gt;</description></item></channel></rss>