Keeta Security Incident Update: We have identified the root cause of the security incident and are currently testing a patch. Importantly, we have confirmed that the root cause was an isolated issue within the affected component and does not impact Keeta’s anchor systems or any externally connected systems. All KTA on Base remains unaffected. In parallel, we are evaluating additional precautionary safeguards that can be implemented to further protect the network and prevent a similar incident from occurring in the future. We are preparing a comprehensive technical report that will detail the exact issue, timeline of events, our response, and the measures being implemented moving forward. We will publish this report as soon as we have completed our investigation and verified all relevant information. Keeta Mainnet will remain in its current read-only state while this work is completed. We intend to return Mainnet to full operation once the patch has been thoroughly tested and the appropriate additional safeguards are in place. We are also actively evaluating the best approach to fully reimburse all impacted participants. There are technical and logistical complexities associated with each option, and we want to ensure the process is secure, accurate, and comprehensive. Our focus remains on ensuring the network is secure, returning to full operation, making all impacted participants whole, and being fully transparent about what occurred and the steps we’re taking moving forward. We appreciate the community’s continued patience and support as we work through this process.