SIP-201: Allowing governance on L1 in case OVM becomes inaccessible

Simple Summary

Moving CouncilDilution.sol to OVM creates a risk of being unable to vote on SIP and SCCP proposals (by normal means) if OVM becomes unavailable for some reason. Allowing (re-)deployment of CouncilDilution.sol to L1 in such cases ensures continued governance with little to no interruption.

Abstract

SIP-201 amends SIP-191 to allow (re-)deployment of CouncilDilution.sol on L1, in case OVM is unavailable or otherwise not usable by normal means to propose or vote on SIP and SCCP proposals.

Motivation

With SIP-191 the formerly on L1 deployed CouncilDilution.sol has been moved to OVM to reduce gas costs and speed up the governance process. However this opens governance up to being unusable (by normal means) in case of OVM becoming unavailable or otherwise unreasonably difficult to interact with, for example if the OVM sequencer fails.

By allowing (re-)deployment of CouncilDilution.sol to L1, the Spartan Council's ability to conduct proper governance gets preserved. If OVM truly becomes unavailable for a prolonged time, the likelihood for contentious governance votes is very high, so a proper governance platform has to be available on short notice, to ensure proper continuation of the governance process.

Specification

Overview

SIP-201 amends SIP-191 to allow (re-)deployment of CouncilDilution.sol on L1, in case OVM is unavailable or otherwise not usable by normal means to propose or vote on SIP and SCCP proposals.

Rationale

SIP-191 was posted to Snapshot governance before the draft could be modified. By amending SIP-191 after it passed governance approval, this important backstop can be easily added retroactively without delaying the migration of CouncilDilution.sol to OVM.

Technical Specification

If SIP-201 is approved, it will be considered a mandatory addition (amendment) to SIP-191.

Configurable Values (Via SCCP)

N/A

Copyright

Copyright and related rights waived via CC0.