Forked Repo but also going to include runnign a local test net instuctions so will add more code than would expect to be Pulled into the main Repo

for ease the binaries are in the binaries directory

but for production use you should build and deploy from the official repo's

in binaries there are https://github.com/prysmaticlabs/prysm for prysmctl , validator https://github.com/ethereum/beacon_chain for beacon-chain https://github.com/ethereum for bootnode , geth

you can look at how to build these using this repo where all the testnest scripts and dependencies build scripts are located here

https://github.com/spring-financial-group/ethereum-pos-testnet

and that will build all the binaries in the binaries folder

to run the build-depenancies.sh script you might need to upgrade a few tools and there are git submodules under the directories

Because there were so many tools and conflicts I ran the build on a Docker container instead and then copied the files to the bianries directory I run geth and bootnode on my Mac but not the other's as they use a lot of libraires you'll have installed (especially on the Mac) for other toolign and will probably have conflicts

There is a Dockerfile setup in the repo

so I just used that and ran

docker build -t custom-bazel-image . docker run -it --rm custom-bazel-go-image bash

git clone https://github.com/prysmaticlabs/prysm cd in then run the bazel commands at the bottom of build-depenancies.sh

i.e. bazel build //cmd/prysmctl:prysmctl

the copy them onto the host into the bianries directory of the helm charts

docker cp e3ff40ed0a40://root/.cache/bazel/_bazel_root/d53767d395e223ee7ad0e8dcc2f1c5bd/execroot/main/bazel-out/k8-fastbuild/bin/cmd/prysmctl/prysmctl/prysmctl binaries/.

For the Config Files i tend to load them using Files.Get and then keep them ina Files directory as the standard Files , so it makes it cleaner and easier to test locally usign the same files

so as the same as the test net for now we'll generate a Genesis.json file and add it ot he files folder here under templates

in the pos-testnet repo use the command (the whole build of the testnet is in testnet.sh) so you can see what we are replicating here in that shell script

$PRYSM_CTL_BINARY testnet generate-genesis
--fork=deneb
--num-validators=$NUM_NODES
--chain-config-file=./config.yml
--geth-genesis-json-in=./genesis.json
--output-ssz=$NETWORK_DIR/genesis.ssz
--geth-genesis-json-out=$NETWORK_DIR/genesis.json

as part of testnet.sh we run this , so for the helm test new we'll just generate it and copy it to the template/files directory that our configmap will use so as an exmaple

../prysmctl testnet generate-genesis --fork capella --num-validators 64 --genesis-time-delay 90 --chain-config-file config.yml --geth-genesis-json-in ../execution/genesis.json --geth-genesis-json-out ../execution/genesis.json --output-ssz genesis.ssz

(Remember if you built the binaries using the Docker image they won't run on your mac they are the binaries used for the helm chart release )

you can download the binaries directly to use them locally for the test chain from the above repos for the Mac i've done that in downloadedBianreisMac in the above repo so you can always run the testnet.sh locally

:

Ethereum Helm Charts

A set of Helm charts to run multiple components of the Ethereum blockchain on Kubernetes.

Deployment examples that use these helm charts can be found under ethpandaops/ethereum-k8s-testnets.

Usage

Helm must be installed to use the charts. Please refer to Helm's documentation to get started.

Once Helm has been set up correctly, add the repo as follows:

helm repo add ethereum-helm-charts https://ethpandaops.github.io/ethereum-helm-charts

If you had already added this repo earlier, run helm repo update to retrieve the latest versions of the packages. You can then run the following command to see the charts.

helm search repo ethereum-helm-charts

To install the ethstats chart:

helm install ethstats ethereum-helm-charts/ethstats

To uninstall the chart:

helm delete ethstats

List of charts

Execution layer clients

• besu
• erigon
• ethereumjs
• geth
• nethermind
• reth

Consensus layer clients

• grandine
• lighthouse
• lodestar
• nimbus
• prysm
• teku

Generic

• ethereum-node - Umbrella chart that uses the execution and consensus layer client charts.

Tooling

• beacon-metrics-gazer - A prometheus exporter for Ethereum validator clients.
• beaconchain-explorer - Beacon chain block explorer.
• blob-me-baby - Send arbitary blob data in well-formatted blobs
• blobscan-indexer - Blobscan-Indexer indexes blobs in MongoDB for use with Blobscan.
• blobscan - Blobscan is the first blockchain explorer that helps to navigate and visualize those EIP-4844 blobs.
• blockscout - Execution layer block explorer.
• blutgang - The wd40 of ethereum load balancers.
• checkpointz - A beacon chain Checkpoint Sync provider.
• consensus-monitor - Web UI to check your ethereum consensus layer nodes via their beacon APIs.
• dora - Lightweight Beaconchain explorer.
• dugtrio - Fault tolerant load balancer for beacon chain RPC apis.
• dshackle - Fault tolerant load balancer for blockchain apis, including Ethereum RPC.
• eleel - A multiplexer for Ethereum execution clients.
• erpc - EVM RPC proxy.
• eth-faucet - Ether faucet server built with Go and Svelte.
• eth2-fork-mon - Fork monitor for a configurable set of beacon nodes.
• ethereum-address-metrics-exporter - A prometheus exporter for Ethereum externally owned account and contract addresses.
• ethereum-metrics-exporter - A prometheus exporter for Ethereum execution and consensus clients.
• ethereum-validator-metrics-exporter - A prometheus exporter for Ethereum validators.
• ethstats - Web UI to track execution layer node status.
• fauceth - EIP1559 compatible web faucet using Hcaptcha.
• forkmon - Fork monitor for execution layer nodes.
• ganache - Simulator for development and testing purposes of the execution layer.
• genesis-generator - A tool to generate and expose genesis files for the execution and consensus layer clients.
• ipfs-cluster - IPFS Cluster
• powfaucet - Modularized faucet for EVM chains with different protection methods (Captcha, PoW Mining, IP Limits, Wallet Balances and more)
• rpc-proxy - A proxy for web3 JSONRPC. Rate limiting and method filtering.
• rpc-snooper - A tool to snoop on RPC calls and log them to stdout.
• smart-contract-verifier-http - Smart contract verification service.
• stubbies - Ethereum execution client stub for consensus layer clients.
• testnet-faucet - Web faucet that can be used to distribute testnet ETH to users.
• testnet-homepage - Simple website that can be used to display useful information about your testnet.
• tracoor-single - An Ethereum beacon data and execution trace explorer in single mode.
• tracoor-server - An Ethereum beacon data and execution trace explorer in server mode.
• tracoor-agent - An Ethereum beacon data and execution trace explorer in agent mode.
• web3signer - An open-source remote signing service.
• xatu-discovery - Ethereum p2p monitoring tool that discovers node records.
• xatu-mimicry - Ethereum p2p monitoring tool that collects data from the execution layer.
• xatu-sentry - Ethereum p2p monitoring tool that runs along side a Ethereum consensus client and collects data via the consensus client's Beacon API.
• xatu-cannon - Ethereum data collection tool that runs along side a Ethereum consensus client and collects data via the consensus client's Beacon API.
• xatu-server - Ethereum p2p monitoring tool that collects events from and controls various Xatu clients.

Development

Prerequisites

• pre-commit - Used to setup pre-commit git hooks
• docker - Used by many Makefile targets

Pre-commit hooks

This repository used pre-commit to manage and run certain git hooks. Hook definitions can be found within the .pre-commit-config.yaml file.

Run the following to add the hooks to your local repository:

make init

Useful commands

The README for every chart is auto generated using helm-docs. This is defined as a pre-commit hook. If you want to run it manually, you can run:

make docs

The CT (Chart Testing) tool is used to lint and validate charts. You can run this via:

make lint

License

MIT License