<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/4588dcadfa2e4ce1a662f57863eaf7cb&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4588dcadfa2e4ce1a662f57863eaf7cb-4f42d765e852f000.gif</thumbnail_url><duration>300.075</duration><title>Analyzing Crarity Smart Contracts for Security Issues</title><description>In this video, I analyze a Clarity Smart Contract to identify potential issues, focusing on a single contract analysis. I found a total of 20 findings, including six critical issues, one medium, and two low severity problems. One critical issue I highlighted is a re-entrancy vulnerability at line 310, where an external call is made before updating the state, which could allow an attacker to exploit the contract. I recommend moving the state update before the external call to mitigate this risk. I encourage you to review these findings and consider implementing the suggested changes to enhance the contract&apos;s security.</description></oembed>