<?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"><channel><title><![CDATA[Investor Reporting in Crypto Still Lags Behind]]></title><description><![CDATA[<p dir="auto"><img src="/forum/assets/uploads/files/1776333741725-d379cd3b-87cc-4cce-89f1-8156f1cdfa4f-image.png" alt="d379cd3b-87cc-4cce-89f1-8156f1cdfa4f-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Beyond market-making opacity, the report from Novora points to a broader investor relations problem in crypto. While over 90% of protocols generate measurable revenue, only a small fraction provide regular updates or formal reports to token holders.</p>
<p dir="auto">Just 18% of projects publish quarterly updates, and only 8% issue detailed token holder reports. This suggests that while data exists, it is rarely structured into clear, investor-friendly communication.</p>
<p dir="auto">Interestingly, third-party analytics platforms already track much of this information, meaning the issue isn’t data availability—it’s the lack of transparency and accountability from projects themselves.</p>
]]></description><link>https://undeads.com/forum/topic/18545/investor-reporting-in-crypto-still-lags-behind</link><generator>RSS for Node</generator><lastBuildDate>Tue, 05 May 2026 06:17:52 GMT</lastBuildDate><atom:link href="https://undeads.com/forum/topic/18545.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Apr 2026 10:02:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Investor Reporting in Crypto Still Lags Behind on Thu, 16 Apr 2026 13:22:48 GMT]]></title><description><![CDATA[<p dir="auto">investors: “can we get updates?” projects: “best we can do is vibes.”</p>
]]></description><link>https://undeads.com/forum/post/50443</link><guid isPermaLink="true">https://undeads.com/forum/post/50443</guid><dc:creator><![CDATA[ed]]></dc:creator><pubDate>Thu, 16 Apr 2026 13:22:48 GMT</pubDate></item></channel></rss>