run prettier

Author: montyly

development-guidelines/incident_response.md

@@ -3,19 +3,20 @@
 How you respond during an incident is a direct reflection of your preparatory efforts. Shift from a reactive approach to a **proactive** one by planning with the assumption that incidents are inevitable. To fully leverage the following guidelines, consider them during the application development, and not at the final stage.
 
 ## Application design
+
 - **Identify the components that should/should not to be**
   - **Pausable**. While pausing a component can be beneficial during an incident, you must assess its potential impact on other contracts.
   - **Migrable or upgradeable**. Discovering a bug might necessitate a [migration strategy](https://blog.trailofbits.com/2018/10/29/how-contract-migration-works/) or contract upgradeable to fix the issue. However always be aware that upgradeability has its own [sets of risks](https://blog.trailofbits.com/2020/12/16/breaking-aave-upgradeability/). Making all contracts upgradeable might not be the best approach.
-  - **Decentralized**.  Using decentralized components can sometimes restrict rescue measures.
+  - **Decentralized**. Using decentralized components can sometimes restrict rescue measures.
 - **Evaluate what events are needed**. A missed event in a critical spot might result in unnoticed incidents.
-- **Evaluate what components must be on-chain and off-chain**. On-chain components are generally more at risk, but off-chain components push the risks to the off-chain owner. 
+- **Evaluate what components must be on-chain and off-chain**. On-chain components are generally more at risk, but off-chain components push the risks to the off-chain owner.
 - **Use an access control that allows fine-grained access**. Avoid setting all access controls to be available to an EOA. Opt for multisig wallets/MPC, and segregate access (e.g., the key responsible for setting fees shouldn't have access to the upgradeability feature).
 
 ## Documentation
 
 - **Document how to interpret abnormal events emission**. Only emitting events isn't sufficient; proper documentation is crucial, and users should be empowered to decode them.
 - **Document how to access the wallets**. Clearly outline how to access wallets. Both the location and access procedures for every wallet should be clear and straightforward.
-- **Document the deployment and upgrade process**. Deployment and upgrade are risky processes, and must be thoroughly documented. This should include how to test the deployment/upgrade (ex: using fork testing) and how to validate it. 
+- **Document the deployment and upgrade process**. Deployment and upgrade are risky processes, and must be thoroughly documented. This should include how to test the deployment/upgrade (ex: using fork testing) and how to validate it.
 - **Document how to contact the users and external dependencies**. Define guidelines regarding which stakeholders to contact, including the timing and mode of communication in case of incidents.
 
 ## Process
@@ -30,7 +31,7 @@ How you respond during an incident is a direct reflection of your preparatory ef
 ## Threat Intelligence
 
 - **Identify similar protocols, and stay informed of related compromises**. Being aware of vulnerabilities in similar systems can help preemptively address potential threats in your own.
-- **Identify dependencies, and monitor their behaviors to be alerted in case of compromise.**  Follow twitter, discord, newsletter, etc.
+- **Identify dependencies, and monitor their behaviors to be alerted in case of compromise.** Follow twitter, discord, newsletter, etc.
 - **Maintain open communication lines with your dependencies owners**. This will help you to stay informed if one of your dependency is compromised.
 - **Subscribe to https://newsletter.blockthreat.io/**. Block threat will help you to know about recent incidents
 
@@ -42,6 +43,6 @@ Additionally, consider conducting a threat modeling exercise. This will identify
 - [Emergency Steps – Yearn](https://github.com/yearn/yearn-devdocs/blob/master/docs/developers/v2/EMERGENCY.md)
 - [Monitoring & Incident Response - Heidi Wilder (DSS 2023)](https://www.youtube.com/watch?v=TDlkkg8N0wc)
 
-### Examples of incidents retrospective 
+### Examples of incidents retrospective
 
 - [Yield Protocol](https://medium.com/yield-protocol/post-mortem-of-incident-on-august-5th-2022-7bb70dbb9ada)