# Geth / Lighthouse / MEV

This page shows the commands to update Geth / Lighthouse / MEV for the upcoming fork on April 12, 2023 (Shanghai). 

It's based on a "standard" install using Somer Esat's guide for [Geth/Lighthouse](https://someresat.medium.com/guide-to-staking-on-ethereum-ubuntu-lighthouse-773f5d982e03)

## Update Geth

{% hint style="info" %}
You can verify the most recent Geth release [here](https://github.com/ethereum/go-ethereum/releases)\
This install uses v1.11.5, current as of April 8, 2023
{% endhint %}

2\) **Stop Geth:**

```
sudo systemctl stop geth
```

2\)  **Change to Home directory:**

```
cd ~
```

3\)  **Use curl to download latest version:**

```
curl -LO https://gethstore.blob.core.windows.net/builds/geth-linux-amd64-1.11.5-a38f4108.tar.gz
```

4\) **Extract, Copy, and Clean up:**

```
tar xvf geth-linux-amd64-1.11.5-a38f4108.tar.gz
cd geth-linux-amd64-1.11.5-a38f4108
sudo cp geth /usr/local/bin
cd ~
rm geth-linux-amd64-1.11.5-a38f4108.tar.gz
rm -r geth-linux-amd64-1.11.5-a38f4108

```

5\) **Start Geth:**

```
sudo systemctl start geth
```

**6) Use `geth --version` to confirm v1.11.5 is installed:**

```
geth --version
```

You should see v1.11.5 in the response:

<figure><img src="/files/OBZtx0Y35vii4pIOGBR4" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Geth is updated and ready for the fork on April 12, 2023
{% endhint %}

## Update Lighthouse

{% hint style="info" %}
You can verify the most recent Lighthouse release [here](https://github.com/sigp/lighthouse/releases).&#x20;

This guide uses v4.0.2, as of April 13, 2023
{% endhint %}

1\) **Change directory to the Home folder:**

```
cd ~
```

2\) **Download Lighthouse software:**

```
curl -LO https://github.com/sigp/lighthouse/releases/download/v4.0.2-rc.0/lighthouse-v4.0.2-rc.0-x86_64-unknown-linux-gnu.tar.gz
```

3\) **Stop Lighthouse services**:

```
sudo systemctl stop lighthousevalidator && sudo systemctl stop lighthousebeacon
```

4\) **Extract, Copy, and Clean up**:

```
tar xvf lighthouse-v4.0.2-rc.0-x86_64-unknown-linux-gnu.tar.gz
sudo cp lighthouse /usr/local/bin
rm lighthouse-v4.0.2-rc.0-x86_64-unknown-linux-gnu.tar.gz
rm lighthouse

```

5\) **Start Lighthouse services:**

```
sudo systemctl start lighthousebeacon && sudo systemctl start lighthousevalidator
```

**6) Use lighthouse --version to confirm v4.0.1 is installed:**

```
lighthouse --version
```

You should see v4.0.2 in the response:

<figure><img src="/files/i9XWuWM1wfRlNnRQ3PEM" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Lighthouse is updated and ready for the fork on April 12, 2023
{% endhint %}

## Update MEV

{% hint style="info" %}
If you don't have MEV installed, you can skip this section.

Based on [CoinCashew - MEV guide](https://www.coincashew.com/coins/overview-eth/mev-boost)
{% endhint %}

**1) Compile binary and stop service**

```
CGO_CFLAGS="-O -D__BLST_PORTABLE__" go install github.com/flashbots/mev-boost@latest
sudo systemctl stop mevboost
```

**2) Copy binary and start `mevboost`**

```
sudo cp ~/go/bin/mev-boost /usr/local/bin
sudo chown mevboost:mevboost /usr/local/bin/mev-boost
sudo systemctl start mevboost
```

{% hint style="success" %}
MEVboost is now updated and ready for the fork
{% endhint %}

Now that Geth, Lighthouse, and MEV are now updated, you are ready for the Shanghai fork on April 12, 2023

Be sure to check that your validators are attesting after the fork occurs.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://agstakingco.gitbook.io/eth-updates-april-12-2023/geth-lighthouse-mev.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.