Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: wrong command name #494

Merged
merged 1 commit into from
Jun 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/advanced/cli-guides/recovery-safe-deployment.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -41,5 +41,5 @@ The Safe should have been successfully recreated with the same address on the ta

Our services cannot index if you've recreated a Safe from an L1 network (like mainnet) on an L2 network. That's because for L1, we use trace-based indexing, and for L2 events indexing, L1 Safe singleton does not emit events.

To address this, you'll need to update it to the L2 singleton with the command `update_to_l2` or consider transferring the funds to a new Safe on L2 that you control with the `drain` command.
For detailed instructions on running these commands, please refer to the [common commands](../cli-reference/common-commands.mdx) section for more information.
To address this, you'll need to update it to the L2 singleton with the command `update_version_to_l2` or consider transferring the funds to a new Safe on L2 that you control with the `drain` command.
For detailed instructions on running these commands, please refer to the [common commands](../cli-reference/common-commands.mdx) section for more information.
11 changes: 6 additions & 5 deletions pages/advanced/cli-reference/common-commands.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Updates the Safe to the latest version (if you are on a known network like Mainn

```bash
update
```
```

## Transactions

Expand Down Expand Up @@ -80,7 +80,7 @@ Adds a new owner `address` to the Safe.

```bash
add_owner <address>
```
```

### Load owners

Expand Down Expand Up @@ -185,7 +185,7 @@ Changes the `threshold` of the Safe.

```bash
change_threshold <integer>
```
```

## Modules

Expand Down Expand Up @@ -239,7 +239,7 @@ Updates the master copy to be `address`. It's used to update the Safe.

```bash
change_master_copy <address>
```
```

## Update to L2

Expand All @@ -253,5 +253,6 @@ It can be found [here](https://github.com/safe-global/safe-contracts/blob/main/c
The nonce for the Safe must be 0, and supported versions are `v1.1.1`, `v1.3.0`, and `v1.4.1`.

```bash
update_to_l2 <address>
update_version_to_l2 <address>
```
where `address` is the address of the update contract.
Loading