Deploy a Safe on Your Rollup

Safe (formerly Gnosis Safe) is the standard multisig wallet used to control admin roles, treasuries, and contract ownership on Ethereum-style chains. Instead of one key controlling funds or permissions, a Safe requires a threshold of owners (e.g. “3 of 5”) to approve any action.

Preinstalled contracts

Every OP Stack rollup launched on Conduit ships with these contracts already deployed, at the same addresses as Ethereum mainnet and other OP Stack chains:

For the full list and addresses, see the Optimism preinstalls reference.

Option 1: Deploy with the Safe SDK (recommended)

The Safe protocol-kit handles building the deployment transaction for you: you just supply your RPC URL, owners, and threshold.

npm install @safe-global/protocol-kit

import Safe, { PredictedSafeProps, SafeAccountConfig } from '@safe-global/protocol-kit'
const safeAccountConfig: SafeAccountConfig = {
  owners: ['0xOwner1...', '0xOwner2...', '0xOwner3...'],
  threshold: 2,
}
const predictedSafe: PredictedSafeProps = { safeAccountConfig }
const protocolKit = await Safe.init({
  provider: '[your_rpc_url]',
  signer: '[deployer_private_key]',
  predictedSafe,
})
const safeAddress = await protocolKit.getAddress()

const deploymentTransaction = await protocolKit.createSafeDeploymentTransaction()
const client = await protocolKit.getSafeProvider().getExternalSigner()
const txHash = await client.sendTransaction({
  to: deploymentTransaction.to,
  value: BigInt(deploymentTransaction.value),
  data: deploymentTransaction.data,
})

Once deployed, you can manage the Safe (propose/approve/execute transactions) using the Safe api-kit against your own transaction service, or manually via protocol-kit, since the hosted Safe Wallet app does not support arbitrary custom chains out of the box.

Option 2: Call the factory directly

If you’d rather not pull in the SDK, you can call the factory’s createProxyWithNonce function yourself:

function createProxyWithNonce(
    address _singleton,
    bytes memory initializer,
    uint256 saltNonce
) external returns (address proxy);

• _singleton: the SafeL2 address above (or Safe, if you don’t need events).
• initializer: the encoded call to Safe.setup(owners, threshold, to, data, fallbackHandler, paymentToken, payment, paymentReceiver) (pass your owners array and threshold, and zero/empty values for the rest unless you need those features).
• saltNonce: any value you choose; it (plus your initializer) determines the resulting Safe’s address, so you can predict it ahead of time.

This is lower-level and mainly useful if you’re scripting deployments with Foundry/cast or integrating Safe creation into your own tooling.