• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
Nexus Mutual DAONexus Mutual DAOby0xFa760444A229e78A50Ca9b3779f4ce4CcE10E1700xFa76…E170

Should We Reimburse Risk Assessors for Undue Loss From Claim 113?

Voting ended over 3 years agoSucceeded

Robert M.C. Forster of Ease (formerly, ArmorFi) posted a proposal on the forum to seek reimbursement for Risk Assessors who had NXM burned to facilitate Claim 113: a 5,000,000 DAI claim payout. The member who filed Claim 113 provided proof of loss that demonstrated a $1.4m loss, but due to the technical limitations present in Nexus V1, partial payments cannot be made, so the full covered amount was paid out to the member who filed Claim 113.

Robert’s proposal seeks reimbursement for 43,940 wNXM to compensate Risk Assessors affected by this claim payout. There has been discussion on how the Protocol Cover wording (https://nexusmutual.io/pages/ProtocolCoverv1.0.pdf) can be interpreted and if there was the expectation that a partial claim could be made.

After discussion on the forum, the following options were proposed and will be subject to a Snapshot vote:

  • Option A: Reimburse affected Risk Assessors 43,490 wNXM
  • Option B: Reimburse affected Risk Assessors 22,000 wNXM
  • Option C: Do not reimburse Risk Assessors

This proposal has been discussed at length on the forum, and members can refer to the two forum posts for more information when deciding their vote:

  1. Proposal: Reimburse Risk Assessors for Undue Loss from Claim 113 (https://forum.nexusmutual.io/t/proposal-reimburse-risk-assessors-for-undue-loss-from-claim-113/854)
  2. Update: Reimburse Risk Assessors for Undue Loss from Claim 113 (https://forum.nexusmutual.io/t/update-reimburse-risk-assessors-for-undue-loss-from-claim-113/874)

Off-Chain Vote

Reimburse 43,490 NXM
0 NXM0%
Reimburse 22,000 NXM
213.51K NXM24.5%
Do not reimburse
657.68K NXM75.5%
Download mobile app to vote

Discussion

Nexus Mutual DAOShould We Reimburse Risk Assessors for Undue Loss From Claim 113?

Timeline

Jul 25, 2022Proposal created
Jul 25, 2022Proposal vote started
Jul 30, 2022Proposal vote ended
Oct 26, 2023Proposal updated