12.1.2023 Update:

Out of respect to ongoing regulatory engagement, we have removed the Oct. 24 post, and as previously communicated, are performing a full review on our response to the Oct. 2 incident. We will share more information at the appropriate time.