<?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/b6ded31028e04371b3f1b32f1283d8e3&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/b6ded31028e04371b3f1b32f1283d8e3-64d8ca2d537c2856.gif</thumbnail_url><duration>490.426</duration><title>Wordex Architecture for Real Time Treasury Risk</title><description>This Loom presents the Wordex system architecture to fix how jito treasury block engine fees are currently not deployed. It explains that treasury reads pull live data via Solana minutes, using the JITO SPL governance account and getProgramAccounts to fetch the native treasury PDA balance, and token balances come from the Covalence Balance API rather than on-chain account reads. It uses DefiLlama for TVL and 90-day historical arrays to compute a daily slope, runs three risk scenarios at minus 40 percent, minus 60 percent, and minus 80 percent, and triggers high concentration alerts when a single token exceeds 70 percent of the treasury. It also pulls live external rate data from Camino and Magifine APIs, JupiterLend supplies, and DRIPS, then uses a Cloud API to generate a formatted governance proposal and an execution layer currently on DevNet until phase 2.</description></oembed>