---
# System prepended metadata

title: Ejector EIP-7044 support

---

# Ejector EIP-7044 support

With the implementation of EIP-7044, the fork version is committed to the exit message.
Previously, there was a check for relevance to the current fork and past forks, now it will always be checked against `CAPELLA_FORK_VERSION`.

## Check current messages
To validate messages, you can run Ejector with the environment variable `FORCE_DENCUN_FORK_MODE=true`.

Alternatively, you can run the command:

If you are using Docker and a local env file with the configuration
```bash
docker run --platform linux/amd64 \
    -v ./:/app/ \
    lidofinance/validator-ejector@sha256:7b0c780d7d62afbf7ac7bdc6f7a35634e67a99ec733632c1fd6eed62388f4d19 \
    node /app/dist/src/scripts/validate-messages.js
```

If you are using Docker and want to pass the configuration through the console
```bash
docker run --platform linux/amd64 \
    -e CONSENSUS_NODE=http://1.2.3.4 \
    -e MESSAGES_LOCATION=messages \
    -v ./messages:/app/messages \
    lidofinance/validator-ejector@sha256:7b0c780d7d62afbf7ac7bdc6f7a35634e67a99ec733632c1fd6eed62388f4d19 \
    node /app/dist/src/scripts/validate-messages.js
```
If you are working with the project locally, run these commands:

```bash
yarn build
node dist/src/scripts/validate-messages.js
```
Next, note the console output

### Invalid output
![telegram-cloud-photo-size-2-5344060749821114528-y](https://hackmd.io/_uploads/BkIVbDMoT.jpg)

If you encounter such errors, you need to regenerate the messages indicated in the logs. To generate messages, make sure to update your software used for signing. If you're using custom code, ensure that you have specified the CAPELLA_FORK_VERSION as the network fork 
from which you want to withdraw the validator.

Additionally, you may see a notification like this when using **the app**

![image](https://hackmd.io/_uploads/BJrpFPfia.png)

This serves as a reminder for those who may not have recreated messages with the correct version of the fork. Importantly, this log may not only be caused by the wrong version of the fork, it is an additional reminder

### Valid output
![telegram-cloud-document-2-5344060749364871183](https://hackmd.io/_uploads/BymrWvMiT.jpg)
If you see this result, you don't need to re-genitize your keys, just update your Ejector:

`lidofinance/validator-ejector@sha256:7b0c780d7d62afbf7ac7bdc6f7a35634e67a99ec733632c1fd6eed62388f4d19`



