<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Monero Double Count Bug with Morphtoken EPI #4</title>
        <link>https://watch.monerotalk.live/videos/watch/33e41158-27c8-476f-b8a9-425548fd54a0</link>
        <description>XMR Donation Address: 49GdSCVTTE4TaDknDFn95QGc3mn3g7JZiPKX6QM7ZpuE5cscRFuGNhnjATKnjDHY7tNUQMM63n24uPYbj1AXFBk5KUPnDrL Apparently there was a bug that caused some issues in Monero land. It has all been fixed but we want to talk about what the bug was and more importantly how the community handled it. Maybe there are things we can do next go-around to improve how warnings are issued...or maybe this is just how open source is. Social Media: TWITTER: https://twitter.com/monerotalk FACEBOOK: https://www.facebook.com/MoneroTalk/ HOST: https://twitter.com/douglastuman PODCAST: https://www.monerotalk.live CONTACT: monerotalklive@gmail.com If you enjoyed the show &amp; would like to support us, a donation of any size would be greatly appreciated and would mean so much! #monero #xmr #decentralized #privacy #privacycoin #technology #blockchain #moneronews #xmrnews #crypto #bitcoin #cryptocurrency #cryptoregulation #bug #morphtoken #doublecount</description>
        <lastBuildDate>Thu, 02 Jul 2026 15:21:46 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://watch.monerotalk.live</generator>
        <image>
            <title>Monero Double Count Bug with Morphtoken EPI #4</title>
            <url>https://watch.monerotalk.live/client/assets/images/icons/icon-1500x1500.png</url>
            <link>https://watch.monerotalk.live/videos/watch/33e41158-27c8-476f-b8a9-425548fd54a0</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://watch.monerotalk.live/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://watch.monerotalk.live/feeds/video-comments.xml?videoId=33e41158-27c8-476f-b8a9-425548fd54a0" rel="self" type="application/rss+xml"/>
    </channel>
</rss>