The SHERLOCK_CLAIM price identifier is intended to allow users of Sherlock to request the DVM for arbitration in the case of a disagreement about an smart contract exploit insurance claim.
## Headers
| UMIP-176 | |
| -------------- | ---------------------------------------- |
| UMIP Title | Add SHERLOCK_CLAIM as a price identifier |
| Authors | Pablo Maldonado |
| Status | Approved |
| Created | 02/05/23 |
| Discourse Link | https://discourse.umaproject.org/t/TODO |
## Summary
The SHERLOCK_CLAIM price identifier is intended to allow users of [Sherlock](https://sherlock.xyz/) to request the DVM for arbitration in the case of a disagreement about an smart contract exploit insurance claim.
## Motivation
This UMIP ammends the [UMIP-132](https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-132.md) that was not consistent with the implementation of [Sherlocks' Claim Manager](https://github.com/sherlock-protocol/sherlock-v2-core/blob/main/contracts/managers/SherlockClaimManager.sol), which is the contract that will be used to request the DVM for claims arbitration. The UMIP-176 proposes a new way of handling the SHERLOCK_CLAIM price identifier that is aligned with the current implementation of the Sherlock Claim Manager.
Sherlock is a DeFi audit marketplace and smart contract coverage protocol built on Ethereum. It provides audits by top security experts and offers optional coverage for audited contracts. In the claim lifecycle, Sherlock utilizes UMA's Optimistic Oracle and Data Verification Mechanism (DVM) for escalated claim resolution.
show original
1 Like