Prysm can be installed on macOS systems using the Prysm build script. This page includes instructions for performing this process.
Have questions? Stop by the #documentation channel on Discord and let us know.
These specifications must be met in order to successfully run the Prysm client.
- Operating System: 64-bit Linux, Mac OS X 10.14+ (Mojave+), Windows
- Processor: Intel Core i5–760 or AMD FX-8100 or better
- Memory: 4GB RAM
- Storage: 20GB available space SSD
- Internet: Broadband connection
According to Apple's Support site, the following Apple products are compatible with OS X 10.14.
- MacBook introduced in 2015 or later
- MacBook Air introduced in 2012 or later
- MacBook Pro introduced in 2012 or later
- Mac mini introduced in 2012 or later
- iMac introduced in 2012 or later
- iMac Pro (all models)
- Mac Pro introduced in 2013, plus mid-2010 or mid-2012 models with a recommended Metal-capable graphics card.
These hardware specifications are recommended, but not required to run the Prysm client.
Processor: Intel Core i7–4770 or AMD FX-8310 or better
Memory: 8GB RAM
Storage: 100GB available space SSD
Internet: Broadband connection
NOTICE: You must have Homebrew installed. To do so, run the command
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)".
Installing the beacon chain and validator
The easiest way to install the beacon chain and validator is by running the
prysm.sh script found in the main directory of the Prysm repository. This script will download and start up the latest release of Prysm binaries compatible with the host system.
Running the Prysm startup script
- Create a working directory and enter it:
- Fetch the
prysm.shscript from Github and make it executable:
- Run the
prysm.shscript alongside any startup parameters:
Not getting enough peers? Refer to the improve P2P connectivity section of this documentation for tips on network configuration.
prysm.sh script will now download and initialise the beacon chain with the specified parameters. The terminal will produce output like so:
At this point, the beacon chain data will begin synchronising up to the latest head block. Please note that, depending on your network capacity and CPU, this process may take several hours. Once it is complete, you will be ready to make a deposit and begin setting up a validator client.
NOTICE: The beacon node you are using should be completely synced before submitting your deposit for the validator client, otherwise the validator will not be able to validate and will inflict minor inactivity balance penalties.
Staking ETH: Running a validator client
For step-by-step assistance with performing a deposit and setting up a validator client, see the activating a validator section of this documentation.
Once your beacon node is up, the chain will be waiting for you to deposit 32 Goerli ETH into a validator deposit contract in order to activate your validator (discussed in the section below).
If you need Goerli ETH, follow the instructions found on prylabs.network to use the testnet faucet. Otherwise, you can contact a team member on Discord to be sent some.
Please note that it may take up to 12 hours for the nodes in the network to process a deposit. Once the node is active, the validator will immediately begin performing its responsibilities.
In your validator client, you will be able to frequently see your validator balance as it goes up over time. Note that, should your node ever go offline for a long period, a validator will start gradually losing its deposit until it is removed from the network entirely.
Congratulations! If you've made it this far, you are now running Ethereum 2.0 Phase 0.