ETH, BSC, Base, Arbitrum, Polygon — recreate the MultiSig there with the same deploy wallet.
Guide
Recovering EVM MultiSig funds received on the wrong network
You have an Ownbit EVM MultiSig and assets arrived on a chain you didn't plan for. The funds are not lost. An Ownbit MultiSig contract address is derived from its deploy address and that address's nonce — not from the chain — so the same deploy address reproduces the same contract address on any EVM chain. That is the key to every recovery here.
Which situation are you in?
The path depends on whether Ownbit supports MultiSig on the chain your funds landed on.
e.g. Optimism — deploy a small Sweeper contract to the same address and pull the funds out.
A. The chain IS supported by Ownbit MultiSig
Simply create the MultiSig again on that chain. Because the contract address depends only on the deploy address, redeploying there places the contract exactly where your funds are, and they become spendable through the normal MultiSig flow.
- Use the same deploy wallet. This is the one requirement — it is what makes the address match.
- Using the same participants and threshold/mode is recommended for clarity, but is not technically required.
- A MultiSig hot wallet deploys automatically using that hot wallet; a MultiSig watch-only wallet lets you pick a personal hot wallet to perform the deploy.
Once deployed, open the wallet on that chain and transfer the assets out as usual.
B. The chain is NOT supported — deploy a Sweeper
You can't recreate the MultiSig here, so instead you deploy a small Sweeper contract to the same address, then call it to move the stuck assets to your control. Import the MultiSig's deploy address as a normal single-key wallet, fund it with a little gas, and deploy the Sweeper from it — because the address derives from the deploy account, the Sweeper lands on the exact contract address holding your funds.
Keep the nonce untouched
The deploy address must have made no outgoing transaction on the target chain (its nonce must be untouched), or the created address won't match. Receiving funds is fine. Never send a stray transaction from this wallet — each one advances the nonce and can make the funds permanently unrecoverable.
Export the MultiSig's deploy private key
In Ownbit open Export Private Key for the MultiSig and select the address tagged (MS_DEPLOY_INDEX). If the MultiSig was deployed by a personal hot wallet you chose manually, export that wallet's key instead.
Import it as a temporary standard wallet
Import a wallet from that key with Private Key type = ETH (64-char hex). This temporary single-key wallet controls the deploy address.
Fund a little gas on the target network
Switch to the target network's native coin (e.g. ETH · Optimism) and hold a small amount of gas. Don't send anything out yet.
Deploy the Sweeper contract
Tap Send on the target network, set the recipient to 0x0 (in Ownbit this means "deploy a contract"), Amount = 0. On Confirm, enable Advanced options, set a sufficient Gas Limit, and paste the Sweeper bytecode into Hex data.
Verify the created address equals your MultiSig address
On the explorer the transaction shows a contract creation — the created address must equal your MultiSig address. If it doesn't, check the creation nonce the MultiSig originally used and redeploy that many times with the same wallet.
Sweep the assets to yourself
Send again to the created contract address (your MultiSig address), Amount = 0, and paste the sweep call data into Hex data. The funds arrive in your deploy wallet; if a sweep fails (e.g. low gas), just retry.
The sweep call data
Use one of these as the Hex data in the sweep step:
| Method | Hex data |
|---|---|
Sweep an ERC-20 token — sweep(address) | 0x01681a62 + 24 zeros + the token contract address (left-padded to 32 bytes) |
Sweep the native coin — sweepETH() | 0xd47f6877 (no parameters) |
This is a technical, developer-level recovery. For the full Sweeper bytecode to deploy, the reference Sweeper.sol source, and worked screenshots, see the full guide: EVM MultiSig — recovering funds received on the wrong network.
FAQ
Frequently asked questions
My EVM MultiSig received funds on a chain I didn't plan for — are they lost?
No. The MultiSig contract address derives from its deploy address (and nonce), not the chain, so the same deploy address reproduces the same contract address on any EVM chain — that's what makes recovery possible.
The chain is supported by Ownbit MultiSig — what do I do?
Just recreate the MultiSig on that chain using the same deploy wallet. The contract redeploys to the exact address holding your funds, and you can spend them through the normal MultiSig flow.
The chain is not supported — how do I recover?
Export the MultiSig's deploy private key, import it as a temporary ETH wallet, fund a little gas, deploy the Sweeper contract (recipient 0x0 + bytecode in Hex data) so it lands on your MultiSig address, then call sweep()/sweepETH() to pull the funds to your deploy address.
Why must I avoid sending transactions from the deploy wallet?
The created contract address depends on the deploy address's nonce. Any outgoing transaction advances the nonce, so the Sweeper would land on a different address and the funds could become permanently unrecoverable.
Last updated:
Download
Download Ownbit
Install the app, then set up a cold wallet or MultiSig for the workflow you need.