XRPL 3.4.1 is now the new minimum software version with the recent amendments activated and the vulnerability report has been published. Through the bug bounty program, an issue was reported on September 22 that could have led to the creation of additional XRP via an integer overflow bug in code dating back to 2015, which we then fixed on September 25. No one triggered the bug, no XRP was created through it, no funds were lost, and network integrity preserved. Our top priority was and has always been network security. Us at the XRP Ledger Foundation, RippleX, core devs and validators came together to fix quickly this issue by using the process we had in place to deal with this kind of scenario and mapped out the path forward. Personally i'm very grateful for all the people who made this possible especially the validators. Because of the severity, the social consensus among validators and core developers was to release the patch as binaries first (withholding source temporarily) to prevent bad actors from exploiting the vulnerability during the upgrade window. A path seen on other networks in similar situations. This is especially relevant given the existence of AI and the resulting need to react more quickly. The security efforts are expanded significantly with Formal Verification and AI at the core, you'll hear a lot more about this. While AI is the biggest threat these days, AI also helps us to harden and secure the protocol.