🦏
ETH Home Staking Collection
DVT Home Staking Curriculum
Replacement steps for MainnetDVT Home Staking Curriculum
DVT Home Staking Curriculum
Replacement steps for MainnetDVT Home Staking Curriculum
  • The DVT Home Staking Curriculum
  • Curriculum breakdown & timeline
  • Understanding ETH validators
    • Introduction to ETH Validators
    • Roles & Responsibilities of a node operator
    • Rewards and penalties
    • Importance of client diversity
    • Distributed Validator Technologies (DVTs)
    • Economics of using DVTs (WIP)
      • Diva Staking (WIP)
      • Obol (WIP)
      • SSV (WIP)
    • Bonded Validators
    • Economics of bonded validators (WIP)
  • Hardware & systems setup
    • Setup Overview
    • Hardware & system requirements
    • Procuring your hardware
    • Assemble your hardware
    • Practicing for free on Cloud VMs
      • Google Cloud
      • Alibaba Cloud
  • Linux OS, Networking, & Security
    • Install and prepare the OS
    • Networking & network security
    • Device level security setup
    • Verifying checksums
  • Installing & configuring your EL+CL clients
    • Set up and configure execution layer client
      • Nethermind
      • Besu
      • Geth
      • Erigon
      • Reth
    • Set up and configure consensus layer client
      • Teku BN
      • Nimbus BN
      • Lodestar BN
      • Lighthouse BN
      • Prysm BN
  • Keystore generation & MEV-Boost
    • Validator key generation
    • Set up and configure MEV-boost
  • Native Solo Staking Setup
    • Validator client setup
      • Teku VC
      • Nimbus VC
      • Lodestar VC
      • Lighthouse VC
      • Prysm VC
    • Depositing 32 ETH into your validator
    • Exiting your validator
  • Monitoring, Maintenance, and Updates
    • Set up monitoring suite
      • Installing & configuring Prometheus
      • Installing & configuring Node Exporter
      • Installing & configuring Grafana
      • Beaconcha.in App API
      • Client Uptime Check
    • Maintenance & Updates
      • Nethermind
      • Besu
      • Teku
      • Nimbus
      • Lodestar
      • Updating the monitoring suite
  • DVT Setup
    • Diva Staking
      • Diva Staking client setup
        • Default - All-in-one setup
        • Advanced - with standalone Lodestar VC
      • Registering your Diva node
      • Updating your Diva client
      • Monitoring your Diva Node
    • Obol
      • Techne Bronze Speedrun (Launchpad)
      • Techne Bronze Speedrun (CLI)
      • Obol + Bonded Validators (Techne Silver)
        • Obol + Lido CSM
    • SSV
      • SSV + Lido CSM (WIP)
      • SSV Operator
      • SSV Staker
  • Bonded Validators Setup
    • Lido CSM
      • Generating CSM keystores
      • Set Fee Recipient Address
        • Method 1: Configure on validator keys
        • Method 2: Configure on separate validator client
        • Verifying Fee Recipient Registered on MEV Relays
      • Upload/Remove/View validator keys
      • Rewards & bonds
      • Exiting CSM validators
        • "Lazy" exits (TESTNET ONLY)
        • Proper Exits
      • Role/Address management
      • Monitoring
      • Automations
        • CSM with ETHPillar
        • CSM with ETH Docker
        • CSM with Dappnode
    • Puffer
      • Non-Enclave: 2 ETH
    • Ether.fi
      • Receive distributed validator keyshares
    • Stader (WIP)
    • Rocketpool (WIP)
  • Liquid Staking Vaults
    • Stakewise V3
  • Mainnet
    • Mainnet Deployment
    • Heroglpyhs (WIP)
  • Best practices
    • Slashing prevention
    • Maximising uptime and performance
    • Optimising security
    • Managing your withdrawal wallet
  • Tips
    • Advanced networking
    • Downloading files from your node
  • Useful resources
    • General resources
    • Holesky Faucets
  • Automation/tools
    • ETHPillar
    • ETH Docker
    • Automated power on/off
      • Wake-on-LAN (WoL)
      • Network UPS Tools (NUT)
    • Validator Healthcheck Alerts
  • Solo Stakers Guild
    • Lido CSM+SSV+Obol (Testnet)
Powered by GitBook
On this page
  • GPG Key Exchange
  • Overview of steps
  • Receive EtherFi public key
  • Generate your own GPG key pair
  • Export your GPG public key
  • Export your GPG fingerprint
  • Receive EtherFi GPG fingerprint
  • Import EtherFi GPG public key & verify fingerprint
  • Decrypt encrypted keyshare files
  • Extract your keyshare files
  1. Bonded Validators Setup
  2. Ether.fi

Receive distributed validator keyshares

GPG Key Exchange

This Public key cryptography process is used to transfer the distributed validator keyshares from Ether.Fi to participating node operators securely.

Overview of steps

  1. Receive EtherFi GPG public key from the programme coordinator

  2. Generate your own GPG public-private key pair and the public key fingerprint

  3. Export your GPG public key and send it to the programme coordinator via Telegram or Discord

  4. Export your GPG fingerprint and send it to the programme coordinator via email

  5. Receive EtherFi GPG fingerprint from the programme coordinator via email

  6. Import EtherFi GPG public key into your GPG keyring and verify the fingerprint with the one you received via email

  7. Decrypt the encrypted keyshare files after you receive them from EtherFi

Receive EtherFi public key

You will receive this .asc file from EtherFi's programme coordinator via Telegram or Discord after you have been onboarded onto a testnet or mainnet cohort.

Generate your own GPG key pair 

gpg --full-generate-key

  • Choose the key type (e.g., RSA and RSA).

  • Set the key size (e.g., 4096 bits for high security).

  • Define the expiration date (or set it to never expire).

  • Provide your name and email address when prompted.

  • Set a secure passphrase to protect the private key.

Export your GPG public key

gpg --armor --export <your-email@example.com> > my-public-key.asc

  • This creates an ASCII-armored file called my-public-key.asc.

  • Copy the contents of this file and send it to the EtherFi coordinator in the Telegram or Discord chat.

Export your GPG fingerprint

gpg --fingerprint <your-email@example.com>

  • You’ll see the fingerprint printed as a series of hex digits. e.g., B365 BB56 85E2 2A50 540A 12C6 E42C FC8D 577E 83F5

  • Copy this fingerprint and email it to the EtherFi programme coordinator

Receive EtherFi GPG fingerprint

You will then receive the EtherFi GPG fingerprint as an email response.

Import EtherFi GPG public key & verify fingerprint

  • Import EtherFi GPG public key into your GPG keyring

gpg --import <etherfi-public-key.asc>

  • Verify the fingerprint using the email sent to you

gpg --fingerprint <etherfi-email@example.com>

Decrypt encrypted keyshare files

After receiving the encrypted keyshare files from EtherFi, move them into the same machine that you generated your GPG key pairs in and decrypt them.

gpg --decrypt <encrypted-file.gpg> > decrypted-file.zip

Extract your keyshare files

unzip decrypted-file.tar.gz
PreviousEther.fiNextStader (WIP)

Last updated 3 months ago