<?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>Identity on Blog of Christian Felde</title><link>https://blog.cfelde.com/tags/identity/</link><description>Recent content in Identity 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/identity/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></channel></rss>