{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/595b9db3c8954fe1b09c0cec27bd4252\" frameborder=\"0\" width=\"1664\" height=\"1248\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1248,"width":1664,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1248,"thumbnail_width":1664,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/595b9db3c8954fe1b09c0cec27bd4252-00001.gif","duration":609.6666666666674,"title":"Weekly Updates on Identity Hub, Parachain, and Governance 📈","description":" Hey everyone, it's Patrick here with this week's updates on the Identity Hub, Parachain, and Governance. We've made some great progress on the EVM sign-in design and fixed a bug involving the wrapping of a verification message. We're also conducting research on self-signed certificates and extending assertion capabilities. We're asking the community to contribute to two motions, one on token rescue and the other on Ledge token rescue. We've disabled Twitter linking due to a change brought by Twitter HQ, but we're working on optimizing the usage of the Twitter API. We're also working on integrating direct invocation into the Identity Hub and creating knowledge transfer resources. We've selected Open ID Connect as our solution for sharing credentials outside the Identity Hub. We're hosting a quiz this month and a Polkadot decoded viewing party in Hanoi. We're investigating the discrepancy with CoinMarketCap to update the circulation supplies and it'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."}