<?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/9c03cabdd29f4ad096224b6d911f8051&quot; frameborder=&quot;0&quot; width=&quot;1440&quot; height=&quot;1080&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1080</height><width>1440</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1080</thumbnail_height><thumbnail_width>1440</thumbnail_width><thumbnail_url>https://cdn.loom.com/assets/img/og/slack-protected-video.gif</thumbnail_url><duration>265.767</duration><title>Understanding Re-Entrancy Attacks in System Workflow</title><description>In this video, I explain the basic workflow of the system to simulate re-entrancy attacks, detect exploits, and send alerts via emails. The system design involves deploying the contract bank v1, event listeners for withdraw and deposit events, and monitoring user actions. I demonstrate deploying the contract, sending emails, depositing money, detecting attacks, and verifying email notifications. No specific action is requested from viewers.</description></oembed>