Hire A Dev House to Bring SHU to Base and Deploy a Safe on Base

Shutter DAO DAO Proposals
1

Proposal

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

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 is also home to a large DEX trading volume, including many altcoins. See [Base on L2 Beat] (Base - L2BEAT) for details.

Bringing SHU to Base will allow more people to purchase SHU at a lower cost and participate in Shutter DAO 0x36 governance .

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 directly manage these tokens. 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)

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.

Platform

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

Voting Options

Vote “FOR” to if you support hiring a dev house to bring SHU to Base

OR

Vote “AGAINST” if you do not support this proposal

OR

Vote “ABSTAIN” if you do not have an opinion

2

Sounds like a reasonable thing to do given the popularity of Base

1 Like
3

Blockful is available and ready to execute. We’ve done the same process before for Optimism. It should be straight forward to execute, but the study hours of the previous case and scoping with a new engineer are counted on the estimates, although already done.

As we encountered some unpredictability last time, we are being extra cautious with our estimate, but will only charge the hours used, as per usual.

Team

1 SC Engineer (picollo.eth)

1 Project Manager (zeugh.eth)

Estimate

Task Hours
Study, Scoping and Estimate 4
Deploy token on Base 5
Deploy safe on Base 1
Add UMA oSnap plugin to Snapshot 2
List token on the Base bridge 2
Bridge from L1 to L2 6
Bridge from L2 to L1 6
oSnap setup 4
Snapshot tx test 4
(PM) Organization, Context and Management 6

Total: 40h

Cost

Blockful standard rate for Shutter DAO is of $85/h as per our previously approved proposal

$85 x 40h = $3,400

Timeline

The project will be executed inside a period of 2 weeks, from Jan 13th to Jan 27th. We are confident on the possibility of finishing earlier, but this period would allow to accomodate any unexpected changes as seen in the previous work.

Payment

Regarding the payment, Blockful is working on a new proposal to change our process of charging the DAO.

We’ve been discussing with other DAO members that we’ve been finding it hard to balance management work vs execution work due to the standard of small proposals that run separetely, need previous scoping and estimation, proposal writing, reporting and charging every time, spread across time with no regular flow of demands.

We’re big fans of shutter and want to continue our work with 0x36, and for that are working on a proposal to streamline our contributions with a bigger proportion of hours focused at shipping things that benefit the DAO and it’s members.

The new proposal should be on the forum in the next few days. If approved, we’d like to include this payment already through the new process. If the new process is not approved, this proposal should be charged by an end of the month report as previously agreed.

2 Likes
4

Thank you for showing interest for this task! Personally I think most of estimation looks reasonable

Would you mind to clarify this item? I assumed you guys are not building a bridge so would be good to clarify what does bridge from l1 to l2 work means there. i.e. what work/code does it entails etc since your guys also list: List token on the Base bridge

Good idea to reduce the proposal overhead as well by combining this with other works as well

5

Hey Han, sorry for the late response.

Last time we did the bridging with OP we encountered some issues. This time is very likely to not be used, but we are saving the trouble of having to make a second proposal to include the costs of extra hours by working with bridge related issues.

This task is looking into guaranteeing the bridging is working properly, and should very likely be a 5 minute job in the final reporting to charge for it.

1 Like