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

**URL:** <https://forum.summer.fi/t/community-call-16-july-6-incident-review-community-q-a-next-steps/845>\
**Category:** Governance Calls\
**Tags:** governance-call\
**Created:** [June 10, 2026, 2:33pm UTC](https://forum.summer.fi/t/community-call-16-july-6-incident-review-community-q-a-next-steps/845 "2026-06-10T14:33:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jensei](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.summer.fi/jensei/32/69_2.png) [@jensei](https://forum.summer.fi/u/jensei)\
**Post date:** [June 10, 2026, 2:33pm UTC](https://forum.summer.fi/t/community-call-16-july-6-incident-review-community-q-a-next-steps/845/1 "2026-06-10T14:33:08Z")

</div>

> 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](https://forum.summer.fi/groups/recognized_delegates) and community participation is encouraged.

* * *

### Call Details

**Date:** Wednesday, July 8th @ 14:00 CET  
**Location:** [Google Meet](https://meet.google.com/ihe-mwoj-avo) + cross-streamed to [Twitter/X Spaces](https://x.com/summerfinance_)  
**Duration:** ~60 minutes

> Add it to your calendar via [this link](https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=Mm9qODZscWhjOXI5NmpnZmY3cnY2czBkcjYgY29tbXVuaXR5QG9hem9hcHBzLmNvbQ&tmsrc=community%40oazoapps.com)!

### 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](https://forum.summer.fi/groups/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](https://forum.summer.fi/groups/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

---

<div class="post-metadata">

**Author:** ![as33](https://avatars.discourse-cdn.com/v4/letter/a/4bbf92/32.png) [@as33](https://forum.summer.fi/u/as33)\
**Post date:** [June 19, 2026, 5:22am UTC](https://forum.summer.fi/t/community-call-16-july-6-incident-review-community-q-a-next-steps/845/2 "2026-06-19T05:22:29Z")

</div>

Thanks for the update, looking forward.

Appreciate the update, See you there