<?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/595b9db3c8954fe1b09c0cec27bd4252&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/595b9db3c8954fe1b09c0cec27bd4252-00001.gif</thumbnail_url><duration>609.6666666666674</duration><title>Weekly Updates on Identity Hub, Parachain, and Governance 📈</title><description> Hey everyone, it&apos;s Patrick here with this week&apos;s updates on the Identity Hub, Parachain, and Governance. We&apos;ve made some great progress on the EVM sign-in design and fixed a bug involving the wrapping of a verification message. We&apos;re also conducting research on self-signed certificates and extending assertion capabilities. We&apos;re asking the community to contribute to two motions, one on token rescue and the other on Ledge token rescue. We&apos;ve disabled Twitter linking due to a change brought by Twitter HQ, but we&apos;re working on optimizing the usage of the Twitter API. We&apos;re also working on integrating direct invocation into the Identity Hub and creating knowledge transfer resources. We&apos;ve selected Open ID Connect as our solution for sharing credentials outside the Identity Hub. We&apos;re hosting a quiz this month and a Polkadot decoded viewing party in Hanoi. We&apos;re investigating the discrepancy with CoinMarketCap to update the circulation supplies and it&apos;s unlikely that there will be a native LIT to BEP20 bridge. Thanks for joining and connect with us on Telegram, Twitter, Discord, and all the other fun places where you can find us.</description></oembed>