[Core Protocol] Hardware signer support?

[upnodedev]

Issue Description

The official doc has said that

You should not use the wallets.sh tool for production deployments. If you are deploying an OP Stack based chain into production, you should likely be using a combination of hardware security modules and hardware wallets.

But I don't find a way to use a combination of hardware security modules and hardware wallets like the doc said.

Can someone guide us on this, we want to launch an OP stack chain on mainnet shortly.

Additional Information

https://stack.optimism.io/docs/build/getting-started/#generate-accounts

[sbvegan]

Hey @upnodedev, on a high level you would craft the transaction with a tool like viem and then sign the transactions with a hardware wallet. I'll see if I can find someone to provide more detailed information.

If you haven't gotten in touch with OP Labs yet on your mainnet launch, I'd suggest filling out this form

[sbvegan]

I'm very sorry about that, I'll flag this to the team internally

[binjix23]

Hi, can you please try again?

https://airtable.com/appQ2S9IatldkoNQw/pagiw2NJAcOXn5Wd9/form

[upnodedev]

Still same error

[sbvegan]

Weird, I gave this a try and was able submit a test. Can you try a different browser?

[upnodedev]

Hi @sbvegan @binjix23 I have found the actual error message

{
  "type": "INVALID_PERMISSIONS",
  "message": "You are not permitted to perform this operation"
}

[sbvegan]

Okay so I learned that there is an option in the forge script, with --ledger or --trezor you can use a hardware wallet. It uses the same backend as something like metamask with libusb. So you can replace the account generation with generating your addresses with a hardware wallet. Then sign the transactions with the hardware wallet key.

Here's the foundry docs: https://book.getfoundry.sh/tutorials/best-practices?highlight=script#private-key-management

[sbvegan]

cc @upnodedev this should resolve your question, let me know if you have any more questions on this topic or feel free to open up a new discussion.

[upnodedev]

This is for the L1 contract deployment but don't sure about proposer and batcher

[upnodedev]

Can we rotate batcher and proposer with admin key in case emergency situation has happened

[sbvegan]

Can we rotate batcher and proposer with admin key in case emergency situation has happened

Yes, you can make updates to the SystemConfig smart contract.

This is for the L1 contract deployment but don't sure about proposer and batcher

The batcher and proposer have the ability to use a remote signer through the standard json RPC API (eth_signTransaction). We use this in combination with a HSM.

[sbvegan]

Hey @upnodedev, I'm going to go ahead and close this discussion. The following is a summary of the questions and answers:

Deploying contracts with a hardware wallet

Utilize the following options in the forge script, with --ledger or --trezor you can use a hardware wallet. It uses the same backend as something like metamask with libusb. So you can replace the account generation with generating your addresses with a hardware wallet. Then sign the transactions with the hardware wallet key.

Here's the foundry docs: https://book.getfoundry.sh/tutorials/best-practices?highlight=script#private-key-management

Can we rotate batcher and proposer with admin key in case emergency situation has happened

Yes, you can make updates to the SystemConfig smart contract.

How to handle the batcher and proposer

The batcher and proposer have the ability to use a remote signer through the standard json RPC API (eth_signTransaction). We use this in combination with a HSM.

[github-actions[bot]]

Hey @upnodedev, 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.