Claim ID | Cover ID | Project | Claim Amount | Purchase Date | Claim Submitted | Verdict | Notes | Year |
---|---|---|---|---|---|---|---|---|
V2 #24 | 1369 | Goldfinch | 2024-10-09 11:11 | 2025-02-02 14:37 | Denied | The claimant provided onchain proof of loss, which claim assessors reviewed and discussed along with the submitted incident details in the claim submission. Assessors discussed this claim request on the governance forum, where they concluded that no loss of funds due to any of the covered terms occurred. The loss in question was due to a loan default on an uncollateralized loan issued from Goldfinch’s senior pool. Assessor’s noted that Protocol Cover does not cover credit risk, and Goldfinch’s documentation noted that Protocol Cover did not provide protections for credit risk. Assessors concluded in their discussion on the forum that this claim was not valid and no votes were cast to approve this claim request, which resulted in a deny outcome. | 2025 | |
V2 #25 | 1369 | Goldfinch | 2024-10-09 11:11 | 2025-02-08 22:42 | Denied | The claimant who submitted Claim V2 #24 re-submitted their claim with the same details included in their previous claim submission. Assessors discussed this on the forum where they concluded that no new information was provided and this claim was not valid. No votes were cast to approve this claim request, which resulted in a deny outcome. | 2025 | |
V2 #26 | 2704 | Arcadia | 2025-07-11 22:23 | 2025-07-29 19:46 | Approved | OpenCover filed this claim on behalf of the claimant, who originally purchased their cover through OpenCover. Onchain proof of loss was provided along with the incident details for this claim. Claim assessors calculated the loss amount for this claim and verified this amount with the OpenCover team, as well. The claimant did purchase cover before the exploit occured; their cover was acfive at the time of loss; and the loss event did meet the criteria outlined in the Single Protocol Cover wording. After careful review and discussion on the governance forum, claim assessors voted to approve this claim after validating the loss onchain. | 2025 | |
V2 #27 | 2705 | Arcadia | 2025-07-11 22:30 | 2025-07-29 20:08 | Approved | OpenCover filed this claim on behalf of the claimant, who originally purchased their cover through OpenCover. Onchain proof of loss was provided along with the incident details for this claim. Claim assessors calculated the loss amount for this claim and verified this amount with the OpenCover team, as well. The claimant did purchase cover before the exploit occured; their cover was acfive at the time of loss; and the loss event did meet the criteria outlined in the Single Protocol Cover wording. After careful review and discussion on the governance forum, claim assessors voted to approve this claim after validating the loss onchain. | 2025 | |
V2 #28 | 2620 | Arcadia | 2025-06-26 09:44 | 2025-07-29 20:39 | Approved | OpenCover filed this claim on behalf of the claimant, who originally purchased their cover through OpenCover. Onchain proof of loss was provided along with the incident details for this claim. Claim assessors calculated the loss amount for this claim and verified this amount with the OpenCover team, as well. The claimant did purchase cover before the exploit occured; their cover was acfive at the time of loss; and the loss event did meet the criteria outlined in the Single Protocol Cover wording. After careful review and discussion on the governance forum, claim assessors voted to approve this claim after validating the loss onchain. | 2025 |