ethereum / ethereum/staking-launchpad

Setting up validator client - pasting deposit data for step 3

Open
#164 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
304
Forks
226
PR merge metrics
No merged PRs in 30d

Description

Hi,

I've been following a process to set up the validator node on my Mac but have got stuck and am wondering if someone can help me - if this is the wrong place to post, apologies, but as a someone with moderate to poor technical skills trying to set up a validator node, others may find this helpful.

Step successfully completed:
-added goeth to my metamask
installed docker
pulled the validator and beacon images
ran and sank the beacon node (it took about 2 days to complete!)

Now, when setting up the validator client, I'm stuck. The code I have run is: docker run -it -v $HOME/.eth2:/data \gcr.io/prysmaticlabs/prysm/validator:latest \accounts create --keystore-path=/data --password= _ _ _
It's given me my deposit and public key data; however, I'm unable to copy and paste my deposit data into the page on step 3 of the medalla testnet. I can't see the json file anywhere on my computer (I can't seem to find Home/.eth2 etc anywhere even though this is the address I used from the start of this process).

I tried creating my own json file in visual studio but clearly have the wrong format for it to work.

Has anyone got any ideas of either the correct format or how to find where the deposit data key might have been stored.

Any support or ideas to simplify this process would be very welcome.

Thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no repository file, test, or entry point. Reproduce the Docker validator-client command on macOS, then inspect the reported $HOME/.eth2 location and the Medalla testnet step 3 flow; done would be clear instructions covering the generated deposit data format and where to find it.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.