{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/4588dcadfa2e4ce1a662f57863eaf7cb\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/4588dcadfa2e4ce1a662f57863eaf7cb-4f42d765e852f000.gif","duration":300.075,"title":"Analyzing Crarity Smart Contracts for Security Issues","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's security."}