# Reimbursement Proposal for Affected Partners from Liquidation Incident **URL:** \ **Category:** Proposals\ **Created:** [December 12, 2024, 3:35pm UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724 "2024-12-12T15:35:07Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![BenAffleck](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ssv.network/benaffleck/32/19_2.png) [@BenAffleck](https://forum.ssv.network/u/BenAffleck)\ **Post date:** [December 12, 2024, 3:35pm UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/1 "2024-12-12T15:35:07Z")
## **Proposal Summary** This proposal seeks DAO approval to reimburse affected partners who incurred losses during the recent liquidation event caused by network fee updates. The incident, which occurred on November 19th, 2024, highlights the need for improved communication, transparency, and operational measures. A reimbursement of the full liquidation amount per eligible cluster is proposed to offset losses and restore partner confidence. ## **Motivation** The recent liquidation incident exposed deficiencies in the network fee update process, resulting in unforeseen losses for certain partners. While the protocol parameters were followed as intended, insufficient communication and notification of the fee deviation led to liquidations. Addressing these losses through reimbursement reflects the DAO’s commitment to fairness, trust, and collaboration. By implementing this proposal, the DAO can: - Restore the confidence of affected partners. - Demonstrate accountability and commitment to improvement. - Strengthen relationships within the SSV community and ecosystem. ## **Proposal Particulars** ### **Objective** To reimburse affected partners for their losses during the liquidation incident and implement safeguards to prevent similar issues in the future. ### **Scope** Reimburse partners who were liquidated due to the fee deviation on November 19th, 2024, according to this list of transactions as [filtered on Etherscan](https://etherscan.io/advanced-filter?eladd=0xdd9bc35ae942ef0cfa76930954a156b3ff30a4e1&eltpc=0x1fce24c373e07f89214e9187598635036111dbb363e99f4ce498488cdc66e688&age=2024-11-19~2024-11-19&ps=100). ### **Reimbursement Mechanism** **Identification of Affected Clusters** On-chain data was captured for the 19th of November after block [21220583,](https://etherscan.io/block/21220583) when the network fee was updated, to identify the clusters directly and immediately impacted by the increased network fee. Those entities were filtered using Etherscan and compiled into the list below. As of the posting of this proposal to the ssv.network forum, the ssv.network users can submit their claim if they believe they have been affected. This claim has to contain on-chain blockchain explorer proof that they were affected. If the claim is valid, such user’s addresses will be added to the list of eligible clusters for the final version of the proposal that will move to snapshot. Only the affected clusters reactivated within 7 days of liquidation are considered. Only clusters that meet the established criteria for reimbursement will be approved. **Distribution of SSV Tokens** The Master of Coin will propose a batched transaction to the DAO multi-sig to release the approved reimbursement amount in SSV tokens directly to the cluster owner’s address, ensuring a direct and efficient transfer process. The cluster owner’s address is taken directly from the liquidate() call of the corresponding TX, as recorded in the eligibility list provided. **Eligible Clusters** | | tx | Owner Account | Liquidated Collateral | | --- | --- | --- | --- | | 1 | [Ethereum Transaction Hash: 0xae4849d244... | Etherscan](https://etherscan.io/tx/0xae4849d244b2367eaa55604755463484ee859bb4a5544985fe6f5f455243b75f) | 0xfd519cf55f8845BD311eE0E8d257FeBAfF3f6Bac | 38.2745299 | | 2 | [Ethereum Transaction Hash: 0x77bc433eb8... | Etherscan](https://etherscan.io/tx/0x77bc433eb8672f62d1c9677b51dcca66ad4d616389755b38157a75bf475f80f2) | 0xda1942E8E5881DfC850BDEca0C4777d92c322184 | 34.28506148 | | 3 | [Ethereum Transaction Hash: 0x759c6291cb... | Etherscan](https://etherscan.io/tx/0x759c6291cbf876169a516f74f2bf238c6bb2c6f84d384d9d1d22eeb0b9abdf81) | 0xc86B8B29926488FaBe686755a1c8e1C8a077aBdb | 48.6675059 | | 4 | [Ethereum Transaction Hash: 0xc68c923628... | Etherscan](https://etherscan.io/tx/0xc68c9236288dfa43369112aee0677be90d2f74db3f637b111f2ca7cad9c5e3d0) | 0xc86B8B29926488FaBe686755a1c8e1C8a077aBdb | 48.9918469 | | 5 | [Ethereum Transaction Hash: 0xb5d79d89d9... | Etherscan](https://etherscan.io/tx/0xb5d79d89d9a001aebb1bfdc9147aef0493a7643fcbe36df2f59ce60ec31e15f7) | 0xc86B8B29926488FaBe686755a1c8e1C8a077aBdb | 48.2141409 | | 6 | [Ethereum Transaction Hash: 0xee056b358d... | Etherscan](https://etherscan.io/tx/0xee056b358dbbffea09b89af968ca0543e89ef01f6740f87d6cbbd6e74c6cbb24) | 0xc86B8B29926488FaBe686755a1c8e1C8a077aBdb | 48.20458772 | | 7 | [Ethereum Transaction Hash: 0x3c6475bdd1... | Etherscan](https://etherscan.io/tx/0x3c6475bdd1f407621be23e650d6d063590ced1b4782b6d42d49c13dfa458ad3d) | 0x85Ca05D933d5b5fdFe928Db77c45367965aAD308 | 35.9369862 | | 8 | [Ethereum Transaction Hash: 0x3d7a8c72d9... | Etherscan](https://etherscan.io/tx/0x3d7a8c72d957187a45db8d036b688142e0af86147266c201646a42b9ae2cabef) | 0x840541529e28564c1795DFeFe5fEC26fa557f778 | 50.45342008 | | 9 | [Ethereum Transaction Hash: 0x9e4645f489... | Etherscan](https://etherscan.io/tx/0x9e4645f489a1ecbb2833dee991c3529e5d0f911dde4de86648ca8bc4fdd57d16) | 0x765f6eeac5C5b555191c15e01Cc0b3cf88073Ca3 | 21.28381764 | | 10 | [Ethereum Transaction Hash: 0x1bb6248f88... | Etherscan](https://etherscan.io/tx/0x1bb6248f88aeffcb833360a79c12488bfcc18701f3de8242aa311e226d1f11c7) | 0x7465169A70212f7069623E7eA4e86605a8096D54 | 35.652393 | | 11 | [Ethereum Transaction Hash: 0xe6d889ab70... | Etherscan](https://etherscan.io/tx/0xe6d889ab7044ae670c90297b86073730300ef6f2c866f71b833b61b043bcbd29) | 0x7465169A70212f7069623E7eA4e86605a8096D54 | 35.54570726 | | 12 | [Ethereum Transaction Hash: 0x932b71c12e... | Etherscan](https://etherscan.io/tx/0x932b71c12e3a4ff487ec14aa439d7c21eeebe17d4b8cd7cdf9c4ba7114b55ef2) | 0x6B7468504757a4918a96078F352572d172115263 | 15.78466178 | | 13 | [Ethereum Transaction Hash: 0x026a2019bc... | Etherscan](https://etherscan.io/tx/0x026a2019bc251e4003ff902c50fa8d12c31875a7e721f722a25e5a95c7bb989d) | 0x12c1eF3208de4805Ba4Ac3fEa6A4F132f8D31243 | 3.042187321 | | 14 | [Ethereum Transaction Hash: 0x0064e727d8... | Etherscan](https://etherscan.io/tx/0x0064e727d8bab7962bef4deea0e43ba4ae3d53ecd38ea3e5b65fd2213bab5f6b) | 0x5f241267040426B30308D0A72e10FA182Ad7caC6 | 31.89266169 | | 15 | [Ethereum Transaction Hash: 0x357b5607e3... | Etherscan](https://etherscan.io/tx/0x357b5607e35d57028d86391414286de1514f802fadb2b8b7a256f84b5ff25689) | 0xda1942E8E5881DfC850BDEca0C4777d92c322184 | 43.8859931 | | 16 | [Ethereum Transaction Hash: 0x42e297eef8... | Etherscan](https://etherscan.io/tx/0x42e297eef8c303b6b6fd5e318c7da925f4b1552c83d1ba94d00edf1d8f700ece) | 0x5f241267040426B30308D0A72e10FA182Ad7caC6 | 24.01863204 | | 17 | [Ethereum Transaction Hash: 0x0188e04842... | Etherscan](https://etherscan.io/tx/0x0188e048427a1f031a14c0279069b6f19fd500b1a390a54816fde757eaf19381) | 0x30e3056A42D84f9998F3CfC57dB63373fC882b26 | 42.17667388 | | 18 | [Ethereum Transaction Hash: 0xb63303322d... | Etherscan](https://etherscan.io/tx/0xb63303322d5b1fcce1564c8f2794f031a6dec0d20a191e8f547a5afff384f494) | 0xa5F2Bb69633825C51aAaB6337C7B5C61818feaD2 | 48.17320854 | | 19 | [Ethereum Transaction Hash: 0x4ab82f7d2e... | Etherscan](https://etherscan.io/tx/0x4ab82f7d2e556e7716745da87795591932a4c82bfbd5c4129f51f6be0463ea6b) | 0x7465169A70212f7069623E7eA4e86605a8096D54 | 35.66902487 | | 20 | [Ethereum Transaction Hash: 0x2076babf1a... | Etherscan](https://etherscan.io/tx/0x2076babf1a991abf540406d6052db1706f65f12686f09b824b5cbfa886221fc1) | 0x499b628441903598F68AC97f62bB817882938246 | 16.84742928 | | 21 | [Ethereum Transaction Hash: 0x20fd6e3c1e... | Etherscan](https://etherscan.io/tx/0x20fd6e3c1e81d7e8de09e94e1c03024e39fdb380dfac4e9af84f54971ddc2c79) | 0x126beae9F195016015560517b388212d42668e4F | 41.81425841 | | 22 | [Ethereum Transaction Hash: 0x9cb57bfd71... | Etherscan](https://etherscan.io/tx/0x9cb57bfd71252faa844e51cafc51500d14d399f6507bae5980c0674c47f8edc7) | 0x089E4537BC114Ee3D5f518F072C3B9045095526D | 30.86916019 | | 23 | [Ethereum Transaction Hash: 0x3f4a1ebc74... | Etherscan](https://etherscan.io/tx/0x3f4a1ebc746059eeb778b59f6568e69cfe8c3f7f44cbb1444d05a1c9eee4b0ca) | 0x170F48123eF348A874B237BC442963754f0a45e6 | 55.09356422 | ## **Key Metrics and Success Indicators** - All partners are reimbursed the full liquidation collateral for each of their clusters ## **Budget and Funding** - **Reimbursement Total** : 834.7774523 SSV - **Source of Funds** : DAO Treasury ## **Risks and Mitigation** ### Risks: - Misallocation of funds to ineligible clusters. ### Mitigation: - Rigorous verification process to confirm eligibility. - Transparency in reimbursement execution through DAO channels. ## **Next Steps** 1. Verify affected clusters and finalize reimbursement calculations. 2. Approve this proposal through a DAO vote. 3. Execute reimbursements via multi-sig wallet. 4. Implement enhanced notification and documentation measures to prevent similar incidents. ## **Supporting Materials** - **Network Fee Documentation** : [DAO Controlled Network Parameters Feed [Evergreen]](https://forum.ssv.network/t/dao-controlled-network-parameters-feed-evergreen/1308) ## **Conclusion** The reimbursement proposal is a critical step in addressing the recent liquidation incident and reinforcing trust within the SSV community. By approving this proposal, the DAO demonstrates its commitment to accountability, transparency, and operational excellence. ---
**Author:** ![sili](https://avatars.discourse-cdn.com/v4/letter/s/dbc845/32.png) [@sili](https://forum.ssv.network/u/sili)\ **Post date:** [December 13, 2024, 6:06pm UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/2 "2024-12-13T18:06:08Z")
Please help check the following cluster: Owner address: 0x170F48123eF348A874B237BC442963754f0a45e6 cluster: [SSVScan - SSV Network explorer](https://ssvscan.io/cluster/0d34148933d61e6dfc8561f4aa5a761a529772ccc430b358841b7c9d38eefd63) Transaction proof: [Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0x3f4a1ebc746059eeb778b59f6568e69cfe8c3f7f44cbb1444d05a1c9eee4b0ca) Thank you! ---
**Author:** ![arjun](https://avatars.discourse-cdn.com/v4/letter/a/8e7dd6/32.png) [@arjun](https://forum.ssv.network/u/arjun)\ **Post date:** [December 14, 2024, 3:18pm UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/3 "2024-12-14T15:18:39Z")
One of our clusters isn’t included owner address: 0x089E4537BC114Ee3D5f518F072C3B9045095526D which cluster: 60c7b50e6e4432a21a4b7804a593d73899a0066132fa27040df3240517a50d2c transaction proof: [Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0x9cb57bfd71252faa844e51cafc51500d14d399f6507bae5980c0674c47f8edc7) Event Log: [Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0x9cb57bfd71252faa844e51cafc51500d14d399f6507bae5980c0674c47f8edc7#eventlog) ---
**Author:** ![BenAffleck](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ssv.network/benaffleck/32/19_2.png) [@BenAffleck](https://forum.ssv.network/u/BenAffleck)\ **Post date:** [December 17, 2024, 6:56am UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/4 "2024-12-17T06:56:24Z")
Hello @sili, Hello @arjun, Thank you very much for bringing this to our attention. Your clusters have indeed not been listed since the TX that led to liquidations was a bit more convoluted in a bundle and did not show up in simple filtering. We have updated the filter and included your transactions at the end. Please verify. Thank you! ---
**Author:** ![BenAffleck](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ssv.network/benaffleck/32/19_2.png) [@BenAffleck](https://forum.ssv.network/u/BenAffleck)\ **Post date:** [December 19, 2024, 5:23pm UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/5 "2024-12-19T17:23:51Z")
🚦Voting is now live. [https://snapshot.box/#/s:mainnet.ssvnetwork.eth/proposal/0x29c61e0d96c501db219046cd97a5d4cbd54f5b992ec89a800db11ed92386dc6c](https://snapshot.box/#/s:mainnet.ssvnetwork.eth/proposal/0x29c61e0d96c501db219046cd97a5d4cbd54f5b992ec89a800db11ed92386dc6c) ---
**Author:** ![Yuting](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ssv.network/yuting/32/1096_2.png) [@Yuting](https://forum.ssv.network/u/Yuting)\ **Post date:** [December 20, 2024, 8:03am UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/6 "2024-12-20T08:03:13Z")
I think this event taught us a lesson, and I believe there will be many follow-ups to improve ---
**Author:** ![AXBLOX](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ssv.network/axblox/32/834_2.png) [@AXBLOX](https://forum.ssv.network/u/AXBLOX)\ **Post date:** [December 21, 2024, 2:00am UTC](https://forum.ssv.network/t/reimbursement-proposal-for-affected-partners-from-liquidation-incident/1724/7 "2024-12-21T02:00:32Z")
> [@BenAffleck](#): > > This proposal seeks DAO approval to reimburse affected partners who incurred losses during the recent liquidation event caused by network fee updates. The incident, which occurred on November 19th, 2024, highlights the need for improved communication, transparency, and operational measures. A reimbursement of the full liquidation amount per eligible cluster is proposed to offset losses and restore partner confidence. Fair, transparent and focused on rebuilding trust. Love the accountability!