Community Call #16: July 6 Incident Review, Community Q&A & Next Steps

This post has been edited and repurposed!

Given the exploit affecting two Lazy Summer USDC vaults on July 6, I considered cancelling this month’s call. At the same time I realized the more useful thing is to hold it and dedicate it to the incident. This is the right venue to walk through what happened, answer your questions directly, and start an open discussion about what comes next.

Strong @Recognized_Delegates and community participation is encouraged.


Call Details

Date: Wednesday, July 8th @ 14:00 CET
Location: Google Meet + cross-streamed to Twitter/X Spaces
Duration: ~60 minutes

Add it to your calendar via this link!

Agenda

  1. Incident overview & post-mortem*
    @jensei will go through what happened, current understanding of the root cause, and the Guardian Multisig actions taken across chains.*

  2. Community Q&A
    Let’s make sure there is a space to explore questions live on the call. Strong @Recognized_Delegates participation is encouraged. @BlockAnalitica and @dickson has been invited to join the call.

  3. What comes next*
    @chrisb will walk us through remediation and possible fixes, the patch back to un-pausing, the ongoing discussion around depositor impact, and gathering ideas for proposals on where the DAO goes from here.*

Call to Action

Whether you are a @Recognized_Delegates, contributor, affected depositor, or community member, this call is the place to:

  • Get a clear, first-hand account of the incident and the response
  • Ask your questions directly and get honest answers
  • Help shape the DAO’s next steps and any proposals that follow

I know this is a difficult moment, and I rather face it openly with the community than go quiet. Looking forward to seeing you there.

--jensei

1 Like

Thanks for the update, looking forward.

Appreciate the update, See you there