• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
Shutter DAO 0x36Shutter DAO 0x36by0x39EE88e8c70f289a28892D062aB0D4EB06432Fa0jlhvc.eth

Hire a development house to take the necessary steps to bring SHU to Base and deploy a Safe on Base

Voting ended about 1 year agoSucceeded

Rationale

SHU is the governance token of Shutter DAO 0x36. It is native to Ethereum Mainnet and it can be bridged to OP Mainnet and Gnosis Chain.

Base is an Ethereum L2 and part of the Optimism Superchain. It is currently the second-largest Ethereum L2 by total value locked (TVL) and the fastest-growing Ethereum L2 in 2024. It also has a large DEX trading volume, including many altcoins. See [Base on L2 Beat] (https://l2beat.com/scaling/projects/base) for details.

Bringing SHU to Base will allow more people to purchase SHU at a lower cost and participate in Shutter DAO 0x36 governance. Should the keyper operator need to acquire SHU in the future for staking purposes this will also lower their cost of transaction and make it easier for more to participate in the network security.

After bringing SHU to Base, Shutter DAO 0x36 will likely want to hold tokens on Base. A Safe on Base controlled by Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap is the most secure way for Shutter DAO 0x36 to manage these tokens directly. Hence, that needs to be set up.

Implementation

  1. Create a SHU token contract on Base

  2. List SHU on the Base bridge

  3. Deploy a Safe on Base controlled by Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap, via these steps:

a. Create a Safe multisig account for Shutter DAO 0x36 on Base (ChainID: 8453(0x2105))

b. Allow Shutter DAO 0x36 on Ethereum Mainnet to control the Safe via UMA oSnap

c. Complete a test transfer from the Safe on Base (triggered by Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap)

d. Remove signers (other than Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap)

a. Create a Safe multisig account for Shutter DAO 0x36 on Base (ChainID: 8453(0x2105))

b. Allow Shutter DAO 0x36 on Ethereum Mainnet to control the Safe via UMA oSnap

c. Complete a test transfer from the Safe on Base (triggered by Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap)

d. Remove signers (other than Shutter DAO 0x36 on Ethereum Mainnet via UMA oSnap)

Of course, if the dev house or anyone has a better implementation idea, please feel free to share.

Selecting A Dev House

If Blockful is available, this task should be given to Blockful - because they are the Shutter DAO 0x36 dev house on retainer and they brought SHU to OP Mainnet - provided they give a reasonable time estimation and cost quotation.

If Blockful is not available, this task should be opened to a competitive RFP.

Blockful has provided a quotation on the Shutter DAO 0x36 Forum

Platform

Snapshot (If passed, this proposal will not trigger an on-chain transaction.)

Off-Chain Vote

For and select Blockful
25.46M SHU82.8%
For but select other dev houses
696.13 SHU0%
Against
1.39M SHU4.5%
Abstain
3.88M SHU12.6%
Quorum:102%
Download mobile app to vote

Discussion

Shutter DAO 0x36Hire a development house to take the necessary steps to bring SHU to Base and deploy a Safe on Base

Timeline

Jan 23, 2025Proposal created
Jan 23, 2025Proposal vote started
Jan 26, 2025Proposal vote ended
May 01, 2025Proposal updated