> For the complete documentation index, see [llms.txt](https://docs.sherlock.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sherlock.xyz/coverage/sherlock-v1-and-v2-deprecation-notice.md).

# Sherlock V1 & V2 Deprecation Notice

**Effective September 10, 2026**

Sherlock V1 and V2, our legacy smart contract coverage protocols launched in 2021 and early 2022, are formally deprecated and no longer supported by Sherlock.

Both protocols have been inactive from a support perspective since 2024. However, because their underlying smart contracts remain deployed onchain, users may still have funds deposited in them.

### Recommended Action

Users with funds remaining in Sherlock V1 or V2 should:

* Withdraw any remaining funds from the protocols
* Discontinue use of the V1 and V2 smart contracts
* Avoid making new deposits or interacting with the protocols going forward

Sherlock does not recommend continued use of either legacy protocol.

### Scope of This Deprecation

This notice applies specifically to the legacy **Sherlock V1 and Sherlock V2 smart contract coverage protocol deployments**.

It does **not** apply to Sherlock’s current security products or services, including Sherlock Shield and Sherlock’s current audit, bounty, and security offerings.

### Current Status

**Sherlock V1:** Deprecated\
**Sherlock V2:** Deprecated\
**Support:** Discontinued\
**Recommended action:** Withdraw remaining funds and discontinue use

### Contract Addresses

The primary deployed contract addresses for the deprecated Sherlock V1 and V2 protocols are:

**Sherlock V1**\
`0xacbBe1d537BDa855797776F969612df7bBb98215`\
[View V1 on Etherscan](https://etherscan.io/address/0xacbBe1d537BDa855797776F969612df7bBb98215?utm_source=chatgpt.com)

**Sherlock V2**\
`0x0865a889183039689034da55c1fd12af5083eabf`\
[View V2 on Etherscan](https://etherscan.io/address/0x0865a889183039689034da55c1fd12af5083eabf?utm_source=chatgpt.com)

Because the underlying contracts are deployed onchain, this deprecation notice does not remove or disable the contracts themselves. It represents Sherlock’s formal notice that these legacy protocols are no longer supported and should no longer be used.