CIP-77: Disabling oSnap Module due to UMA Deprecation

CIP-Number: 77
title: Disabling oSnap Module due to UMA Deprecation
author: @middleway.eth
status: Active
created: 2025-11-20

Simple Summary

This proposal disables the UMA oSnap module currently attached to the CoW DAO main Safe. This action is required because UMA is deprecating the oSnap service, and it will cease to function on December 15, 2025.

Motivation

In July 2023, CIP-30 implemented oSnap to allow for optimistic on-chain execution of Snapshot votes, reducing reliance on the multi-signature wallet signers.

Recently, UMA announced the deprecation of the oSnap tool to focus on their prediction market resolution services. The official notice from UMA states:

“UMA will be deprecating support for oSnap (Snapshot proposal execution tool) on December 15th, 2025… oSnap will not be able to execute transactions from your DAO’s Safe treasury after this date.”

To maintain the security and hygiene of the CoW DAO governance contracts, it is necessary to remove deprecated modules. Failing to remove the module could leave a non-functional entry point on the DAO’s treasury.

Specification

The proposal seeks to call the disableModule function on the CoW DAO Safe to remove the specific oSnap module deployed in CIP-30.

Target Safe: 0xcA771eda0c70aA7d053aB1B25004559B918FE662 (CoW DAO Treasury) Module to Disable: 0x85f520D59deBD4c2902BB7f79ACbc3Dd4b5AB699 (Existing oSnap Module)

By executing this transaction, the Safe will revert to its previous state regarding transaction execution (requiring Safe Signers to execute transactions based on Snapshot outcomes), unless a replacement solution is proposed and implemented separately.

Rationale

The service powering the module is being shut down by UMA, so keeping the module enabled serves no utility after the deprecation date. Additionally, it is standard security practice to remove any code or smart contract permissions that are no longer supported or monitored by their developers.

Execution

Two transactions are required:

1. The first transaction payload will interact with the CoW DAO Safe to disable the module. Tenderly simulation is available in the following link. The transaction could be easily recreated from the safe UI.
2. The second transaction should update the “snapshot” text record on the cow.eth ens: cow.eth on ENS to the new settings json file uploaded to ipfs here: https://ipfs.io/ipfs/QmRMwpUayBXkiv27oHWtBNYBawLyPhMyHav2SgadgYMo8r . Tenderly simulation for this transaction in the following link