Created
November 17, 2024 23:53
-
-
Save nfl0/1f792b2ea99b9ccde81b04cb0bd6bf8d to your computer and use it in GitHub Desktop.
Becoming a Penumbra validator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Penumbra Validator Setup Guide | |
## Prerequisites | |
1. Ensure system meets the following requirements: | |
- 8GB RAM, 2-4 vCPUs, 200GB SSD storage. | |
- Public IP for peer-to-peer connections. | |
2. Install dependencies: `git`, `rustup`, and `cargo`. | |
--- | |
## Step 1: Install Penumbra (`pd`) | |
1. Clone the Penumbra repository: | |
git clone https://github.com/penumbra-zone/penumbra.git | |
cd penumbra | |
2. Build and install the `pd` binary: | |
cargo install --path . | |
--- | |
## Step 2: Join a Network | |
1. Fetch the network configuration: | |
pd network join <network-name> | |
Replace `<network-name>` with the desired network (e.g., `mainnet` or `testnet`). | |
--- | |
## Step 3: Set Up Validator Keys | |
1. Generate validator key pair: | |
pd validator keygen | |
2. Backup the generated keys securely. | |
--- | |
## Step 4: Run the Node | |
1. Start the full node: | |
pd start | |
2. Review and adjust `config.toml` if necessary, located at: | |
~/.penumbra/network_data/node0/cometbft/config/config.toml | |
--- | |
## Step 5: Stake Tokens to Become a Validator | |
1. Delegate stake using `pcli`: | |
pcli tx delegate <amount> --to <validator-address> | |
Replace `<amount>` with the token amount and `<validator-address>` with your validator address. | |
2. Monitor logs to confirm validation participation. | |
--- | |
## Notes | |
- Ensure the following ports are properly configured: | |
- `26656/TCP` for P2P communication (public). | |
- Refer to the network guide for additional ports. | |
- Regularly update `pd` by pulling the latest repository changes and rebuilding. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use cargo build to build the binary instead of cargo install :
cargo build --release