[OP Stack Deployment] <How to set a Multi-Signature Admin account>

[zhwindy]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

In the Creating Own L2 Rollup Tutorials, we need four addresses and their private keys when setting up the chain.

• The Admin address, has the ability to upgrade contracts.
• The Batcher address
• The Proposer address
• The Sequencer address

For Admin, The current config only can set GS_ADMIN_ADDRESS and GS_ADMIN_PRIVATE_KEY for EOA account.

But I want to set the Admin to Multi-Signature account like Gnosis Safe.

How to do this? Thank you very much if there is a example.

Logs

No response

Additional Information

No response

Feedback

No response

[opfocus]

I am not very familiar with how to deploy op-stack to the production environment. My immature understanding is that we can transfer ownership, and this can be accomplished through a contract call. The link provided is to a potentially relevant contract. Please patiently wait for responses from others. CC @sbvegan https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/deployments/goerli/AddressManager.json

[zhwindy]

ok, thanks for your response

[sbvegan]

You'll notice that in the step 2 of the Generate Addresses portion of the tutorial, you're creating environment variables for the following wallet.sh script.

What this is doing is creating testing EOAs with foundry's cast. If you want to use a multi-sig wallet instead. You need to manually do so for this step and any of the following steps that require these generated EOAs.

[zhwindy]

thanks, I'm notice that the wallets.sh is only use in test deploy.
I want to use a multi-sig wallet instead but I'm not very familiar with OP Stack production deployment.
Is there any examples or documents to help familiarize with the deployment in the production? It is best to use a multi-signature admin account.

[sbvegan]

Is there any examples or documents to help familiarize with the deployment in the production?

There isn't something like that at the moment. I can work on creating new documentation in the chain operator section to address this knowledge gap.

It is best to use a multi-signature admin account.

Yes it is a better practice. At the moment, the admin account has the ability to pause and unpause L1 --> L2 transactions. So having a multi-sig setup properly would improve the security.

[zhwindy]

ok, It would be great if a document could be produced in chain operator section
thank you very much

[sbvegan]

Here's the high level guide here: https://docs.optimism.io/builders/chain-operators/management/key-management

[github-actions[bot]]

Hey @zhwindy, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.