Eth staking docs

ToDos

• Update this readme
• Change python server to upload server, and upload ssz file instead of copying it to node storage
• Write script to automatically copy over custom genesis parameters to teku and geth

---

Bootstrapping the secrets

This part of the documentation only needs to be run once, and it's only needed if you want to generate fresh secrets and not if you already have them.

---

Generating a node key for eth clients

You can use the bootnode utility for this to create a nodekey immediately after geth init. You can download it with "Geth & Tools" from https://geth.ethereum.org/downloads/

bootnode -genkey nodekey

You then copy the contents of the generated nodekey file to the node-key-secret.yaml file.

Generating a jwt secret for eth clients

openssl rand -hex 32 | tr -d "\n"

You then copy the this secret to the jwt-secret.yaml file.

Configure ethereum nodes to connect to the Ephemery testnet config

Download the testnet-all.tar.gz file for the latest release of the Ephemery testnet and then unzip inside this folder.

mkdir testnet-all
cd testnet-all
tar -xzf testnet-all.tar.gz

---

Geth

Then from these files you use the following values to configure geth in geth-kotal.yaml:

For {bootnodes} look in ~/testnet-all/boot_enode.txt. Entries must be separated,by,commas and "enclosed in quotes", like:

bootnodes:
  - enode://0f2c301a9a3f9fa2ccfa362b79552c052905d8c2982f707f46cd29ece5a9e1c14ecd06f4ac951b228f059a43c6284a1a14fce709e8976cac93b50345218bf2e9@135.181.140.168:30343

For {networkID} look for chainId in ~/testnet-all/genesis.json and place it like this in geth-kotal.yaml:

genesis:
  networkId: 39438064

---

Teku

For teku-kotal.yaml you can use the following values:

checkpointSyncUrl: "https://github.com/pk910/test-testnet-repo/releases/download/ephemery-64/genesis.ssz"

Bootnodes For {bootnodes} look in ~/testnet-all/boot_enr.txt. Entries must be separated,by,commas and "enclosed in quotes". In your teku-kotal.yaml you can add this like:

  bootnodes:
    - enr:-Iq4QGdecZrX_n9aWd0T0r3w9aVTnjbrO9nyDSMunKwxh6M3fkTuDamFtcu4Ulgq82WA7V10XJJJgDFUqrYEGAonNGiGAYSHF-YRgmlkgnY0gmlwhIjzHgyJc2VjcDI1NmsxoQJDyix-IHa_mVwLBEN9NeG8I-RUjNQK_MGxk9OqRQUAtIN1ZHCCIyg
    - enr:-Ly4QPV3Xkpt1mHGyxiflkPcTF_6ySM5J0CnzJn1XsmZ-R6lDCbtGGNmcdBv0F9OPNFE17c0ASWyTYj-MzBh50rQtwgBh2F0dG5ldHOIAAAAAAAAAACEZXRoMpBaQ55pQAAQGwUAAAAAAAAAgmlkgnY0gmlwhIe1jKiJc2VjcDI1NmsxoQNm8zjpsaWBrGjgxmYltemjKegOnSpzQ0QaZ5cjo15svIhzeW5jbmV0cwCDdGNwgiNQg3VkcIIjUA
    - enr:-Jq4QCP4f0z6BRbs3f2Pbkw8n842B5m6ram9bNr0EkZ5a9c3Y0LzHDUGXZQ5kKSxlYUJT-7J97SWAufLPr9ikQKqPZkBhGV0aDKQWkOeaUAAEBsFAAAAAAAAAIJpZIJ2NIJpcISI8x4MiXNlY3AyNTZrMaECZ3D1cbwdyk2ylwZhhcDv3ku4eVs-F3Kpt8VuJCGh_myDdWRwgiMp

Network config The network config can be found in the file testnet-all/config.yaml and you have to provide the contents of this file, into a separate configmap you'll find at eth-nodes/teku-beacon-configmap.yaml. The contents of this configmap are mounted into a volume inside the teku beacon pod. Kotal takes care of this for you. Only thing you have to do further is specify to Teku in teku-kotal.yaml what network config file it needs to pick up.

network: "/opt/teku/kotal-config/network-config.yaml"

Running the eth clients

kubectl apply -f eth-nodes/.

You will see output like this:

namespace/eth-nodes created
node.ethereum.kotal.io/geth-node created
secret/jwt-secret configured
secret/geth-nodekey configured

Interacting with the ethereum clients and their APIs

Teku Beacon API http://localhost/beacon-rest/eth/v1/beacon/genesis