Skip to content

Commit

Permalink
Update sync.mdx
Browse files Browse the repository at this point in the history
  • Loading branch information
evanorti committed Nov 15, 2023
1 parent 00dc070 commit c34c218
Showing 1 changed file with 30 additions and 4 deletions.
34 changes: 30 additions & 4 deletions docs/full-node/run-a-full-terra-node/sync.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -225,7 +225,7 @@ From here, you can [monitor the sync](#monitor-the-sync). Make sure to check on

### Phoenix mainnet

If you would like to sync your node using the Phoenix mainnet, you will need to use version `v2.0.0` of terrad up until the block height of `890000`. To sync your node from block `890000` to block `2979805`, you will need to use version `v2.1.1` of terrad. From block `2979805` until block `4711800`, use version `v2.2.0` of terrad until block `4711800`. From block `4711800` until block `5994365`, use version `v2.3.0`. From block `5994365` until block `7316000`, use version `v2.4.0`. From block `7316000` onward, use version `v2.5.2`to complete the sync.
If you would like to sync your node using the Phoenix mainnet, you will need to use version `v2.0.0` of terrad up until the block height of `890000`. To sync your node from block `890000` to block `2979805`, you will need to use version `v2.1.1` of terrad. From block `2979805` until block `4711800`, use version `v2.2.0` of terrad until block `4711800`. From block `4711800` until block `5994365`, use version `v2.3.0`. From block `5994365` until block `7316000`, use version `v2.4.0`. From block `7316000` until block `7722000`, use version `v2.5.2`. From block `7722000` onward, use version `v2.6.1` to complete the sync.

1. To switch to version `v2.0.0` of terrad, [change into your `core` directory](./build-terra-core.mdx#get-the-terra-core-source-code) and execute the following commands in your terminal:

Expand Down Expand Up @@ -337,7 +337,7 @@ terrad start

Syncing will halt at block `5994365`, at which point you will need to change the version of terrad and then resume the syncing process.

11. To sync your Phoenix mainnet node from block `5994365` to the most recent block, you will need to navigate to the `core` directory and change your terrad version to `v2.4.0`.
11. To sync your Phoenix mainnet node from block `5994365` until block block `7316000`, you will need to navigate to the `core` directory and change your terrad version to `v2.4.0`.

```sh Terminal
git checkout v2.4.0
Expand All @@ -360,7 +360,7 @@ terrad start

Syncing will halt at block `7316000`, at which point you will need to change the version of terrad and then resume the syncing process.

13. To sync your Phoenix mainnet node from block `7316000` to the most recent block, you will need to navigate to the `core` directory and change your terrad version to `v2.5.2`.
13. To sync your Phoenix mainnet node from block `7316000` until block block `7722000`, you will need to navigate to the `core` directory and change your terrad version to `v2.5.2`.

```sh Terminal
git checkout v2.5.2
Expand All @@ -375,8 +375,34 @@ terrad version

The result of this command should be `v2.5.2`.

14. Now, you can resume the syncing process:

14. Now, you can resume and finalize the syncing process:
```sh Terminal
terrad start
```

Syncing will halt at block `7316000`, at which point you will need to change the version of terrad and then resume the syncing process.




15. To sync your Phoenix mainnet node from block `7722000` to the most recent block, you will need to navigate to the `core` directory and change your terrad version to `v2.6.1`.

```sh Terminal
git checkout v2.6.1
make install
```

Again, make sure that you have switched to the correct version of terrad by running the following command:

```sh Terminal
terrad version
```

The result of this command should be `v2.6.1`.


16. Now, you can resume and finalize the syncing process:

```sh Terminal
terrad start
Expand Down

0 comments on commit c34c218

Please sign in to comment.