Frequently asked questions

Our Code Is Not Yet Updated to Mainnet!

Our latest release of Prysm, beta.1, is not mainnet compatible. Please do not run Prysm yet until we announce it in our Discord channel, our releases page, our official mailing list or in this documentation portal.

Joining Eth2 Questions

How can I make a deposit?

The best way to make a deposit and join eth2 is to follow the direct instructions on the official eth2 launchpad.

How can I get a bunch of test ETH to spin up a lot of validators on the testnet?

Our current faucet only gives out increments of 32.5 Goerli test ETH at any given time and prevents sending out to the same address too often. If you need a larger amount of test ETH, please reach out to us on discord here.

Can I get back my ETH? How can I withdraw my validator gains?

Deposits into eth2 are one-way in the beginning. Functionality of withdrawing gains transferring ETH won’t be available until later phases of the project. You can read more about the phases of eth2 here.

Running a Node

How can I view the metrics of my node? How can I visualize them?

Your node is running the popular prometheus server for metrics collection which displays its data by default on localhost:8080/metrics. You can visualize these metrics by connecting them to a grafana instance.

Can I run a node in the background?

Absolutely! If you are running via docker, it is as easy as adding the -d flag to your docker run command itself to run it in “detached” mode. You can see your running docker instances by typing in docker ps. If you are running via our precompiled binaries, such as the script, you can use tools such as systemd (example here)

I got slashed! Why? How can I avoid getting slashed?

Slashings in the network occur when you propose two conflicting blocks (blocks with the same slot but different inner data) or when you do a conflicting vote or a surround vote (read more about surrounding here). These will never happen if your node is operating as intended. You can, however, get yourself slashed if you run multiple validator clients with the same keys. There is a chance they may create two blocks or two conflicting votes at the same time as each other, causing you to get slashed from eth2. This is more common than it seems, as typically developers want to run redundant instances of servers for reliability purposes (if one goes down, the other one is ready right away to do its job). Famously, this same event happened in the Cosmos network as seen here. There are some cool projects that aim to prevent validators from getting slashed such as this one that are community built, but we have yet to standardize this functionality into Prysm.

Where can I read more about the incentive model in eth2?

This resource from the Ethereum blog is an excellent example.

My CPU/RAM usage is huge, what’s going on?

Memory management is an ongoing process for our team - we are constantly working on improving the experience of running a node itself. For now, these are the specs we recommend (these values will go down over time):

Recommended Hardware Processor: Intel Core i7–4770 or AMD FX-8310 or better Memory: 16GB RAM Storage: 100GB available space SSD Internet: Broadband connection

Minimum Hardware: Operating System: 64-bit Linux, Mac OS X, Windows Processor: Intel Core i5–760 or AMD FX-8100 or better Memory: 8GB RAM Storage: 20GB available space SSD Internet: Broadband connection

If that still does not help, please file an issue with our team on Github here.

What’s the best cloud service to run a beacon node on?

We find Digital Ocean tends to have fairly priced instances for running beacon nodes, but as always, we recommend you running a node yourself on your machine for the full experience. You can also try the small instances on AWS ec2 to run in the cloud.

Can I run this on a raspberry pi? What are the instructions?

Yes we currently support arm 64-bit architectures such as the raspberry pi 4 and they go out as part of our pre-compiled binary releases here. Our documentation portal has instructions on how to run the entire installation process here.

Managing Validators

How can I create a new validator key and join the testnet?

The best way to join the testnet is to follow the direct instructions on We have more detailed instructions in our documentation portal depending on your operating system here.

I deposited but it’s taking a long time to become active - how can I check if my deposit was correct?

Even after you deposit, it takes several hours to join eth2 as an active validator and can take even longer if there is a queue ahead of you. You can track your validator’s status on block explorers such as and Please be patient, as there is quite a wait for new validators to become active.

I made a correct deposit and my validator status is still UNKNOWN, what’s going on?

There are a few possibilities. (1) your deposit has not yet been processed by beacon nodes. It takes a while for the beacon node to be able to process logs from the eth1 chain by design. If you have already waited a few hours and no luck, there is a chance that (2) your deposit did not verify (that is, you used some other method of creating the deposit than our recommended, standard way on the eth2 launchpad), or (3) you never actually sent a deposit to the right contract address

What is balance and what is effective balance?

Your validator balance is the actual amount of ETH you have from being a validator in eth2. It can go up or down every epoch depending on your participation. Effective balance is a bit different. It is a value that lags behind your actual balance and is used exclusively to determine rewards and penalties for your validator. It has a max value of 32ETH, but your regular balance is uncapped. You can read more about the purpose of effective balance in this excellent post by Attestant here.

When do my validators get to propose a block?

Validators receive new assignments approximately every 6.4 minutes. This period of time is known as an “epoch” and you may be assigned to propose a block several times in an epoch. Proposing a block, however, is rare, as there can only be one block proposer per slot and there are many validators in the network. Voting on blocks, that is, being assigned as an attester, is very common and you will be assigned to attest once per epoch if you are an active validator. You can see how many votes your validator has been assigned to create vs. how many blocks your validator has been assigned to propose by using a popular block explorer such as and looking up your validator index or public key.