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

Small Updates to Guide/Teku #291

Closed
wants to merge 6 commits into from
Closed
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
16 changes: 14 additions & 2 deletions docs/node/guide/beacon/teku.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Teku is a consensus client built to meet institutional needs and security requir

:::info Download Teku

Visit Teku's page on how to download Lodestar.
Visit Teku's page on how to download Teku.

https://docs.teku.consensys.net/en/latest/

Expand All @@ -51,9 +51,11 @@ We recommend the use of Checkpoint sync to sync your Beacon Node quickly, and av
Gnosis provides a checkpoint sync server at https://checkpoint.gnosischain.com/.

```shell

# Usage
$ teku
--initial-state https://checkpoint.gnosischain.com/
--initial-state=https://checkpoint.gnosischain.com/eth/v2/debug/beacon/states/finalized

```

:::info More about Checkpoint Sync
Expand Down Expand Up @@ -149,21 +151,31 @@ networks:
name: gnosis_net
```

:::note

Teku by default uses a user ID of 1000, which may not be compatible with the permissions on you host machine. This is why we recommend to set your `$PUID` variable and use it with the Teku container at the line `user: "${PUID:-1000}"`. If Teku won’t start and you receive error messages like `ERROR - Failed to write in /data/validator/slashprotection` this is one solution to resolve those issues.

:::

### 3. Environment Variables

Add an `.env` file with your user id (`id --user`) in `/home/$USER/gnosis/.env`.

``` title="/home/$USER/gnosis/.env

PUID=1000

```

### 4. Start Containers

Start the consensus layer client listed in the compose file:

```shell

cd /home/$USER/gnosis
docker-compose up -d

```


Expand Down
6 changes: 1 addition & 5 deletions docs/node/guide/execution/nethermind.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,11 +107,7 @@ networks:

The JWT secret is a token that allows the EL client to communicate with the CL client, and is required for Nethermind to operate post-merge. We use `rand` to create a random string, and store the `jwt.hex` file in `/home/$USER/gnosis/jwtsecret/`.

Create a new JWT secret file:

```shell title="/home/$USER/gnosis/jwtsecret/jwt.hex"
openssl rand -hex 32 | tr -d "\n" > /home/$USER/gnosis/jwtsecret/jwt.hex
```
Check [create JWT](../configure-server.md#create-jwt) section in `Step 1: Configure Server`.


### 4. Start Container
Expand Down