---
# System prepended metadata

title: Post mortem template
tags: [youves, template, postmortem]

---

# Post mortem template

Date: 1970-01-01

Authors: name, name

Status: complete, ongoing etc

### Summary:
A quick summary of the incident and it's resolution. A few sentences, 2-3 paragraphs max.

### Detection: 
How was the problem detected?

### Root causes:
What was the technical reason this could happen?

### Trigger: 
What triggered the problem

### Impact: 
What impact did the problem have?

### Resolution:
How was it resolved?


### Action Items:
What steps were done to fix or mitigate the problem? Where are we at, currently? 


| Action Item | Type | Owner | State |
| -------- | -------- | -------- |-------- |
| Identfiy reason for failure     | mitigate     | ale     |DONE |
| Develop and test proxy contract     | mitigate     | florin     |DONE |
| Deploy proxy contract     | mitigate     | florin     |WORK IN PROGRESS |
| Rewire tez collateral engines | mitigate | multisig signers | OPEN



### Timeline:
What was the exact timeline of the relevant events/actions?

(all times UTC)

2022-11-08 20:30 ale and markus observe uusd/tez (v3) vaults not being liquidated
2022-11-09 00:33 User 'chas' reports the Unified Staking Pool missing a 'default' entry point
2022-11-09 07:30 Solution is defined, development of the proxy contract starts
2022-11-09 09:45 Deployment of the proxy contract & definition of multisig lambdas
2022-11-09 16:03 Execution of rewiring.

## Lessons Learned

### What went well

### What went wrong

### Where we got lucky

### Conclusion
A short conclusion on what we have learned and what we have done in order to prevent the same problem to happen again.