CoinCashew
English
English
  • Home
  • About Us
  • Donations
  • Contributing
    • Contributor Covenant Code of Conduct
    • Style Guide
  • Disclaimer
  • Wallets
    • Guide: Crypto Wallet Tips 101 - Do's and Don'ts
      • Review: Metal Bitcoin Seed Storage by jlopp
  • Coins
    • Ethereum: ETH
      • 🛡️EthPillar: one-liner setup tool and node management TUI
      • 🥩Guide | How to setup a validator for Ethereum staking on mainnet
        • Overview - Manual Installation
        • PART I - INSTALLATION
          • Step 1: Prerequisites
          • Step 2: Configuring Node
          • Step 3: Installing execution client
            • Nethermind
            • Besu
            • Geth
            • Erigon
            • Reth
          • Step 4: Installing consensus client
            • Lighthouse
            • Lodestar
            • Teku
            • Nimbus
            • Prysm
          • Step 5: Installing Validator
            • Setting up Validator Keys
            • Installing Validator
              • Lighthouse
              • Lodestar
              • Teku
              • Nimbus
              • Prysm
            • Next Steps
          • Monitoring your validator with Grafana and Prometheus
          • Mobile App Node Monitoring by beaconcha.in
          • Monitoring with Uptime Check by Google Cloud
        • PART II - MAINTENANCE
          • Updating Execution Client
          • Updating Consensus Client
          • Backups Checklist: Critical Staking Node Data
          • Uninstalling Staking Node
          • Finding the longest attestation slot gap
          • Checking my eth validator's sync committee duties
          • Checklist | Confirming a healthy functional ETH staking node
        • PART III - TIPS
          • Voluntary Exiting a Validator
          • Verifying Your Mnemonic Phrase
          • Adding a New Validator to an Existing Setup with Existing Seed Words
          • Switching / Migrating Consensus Client
          • 🛡️Switching / Migrating Execution Client
          • ⚡Using Node as RPC URL endpoint
          • Using All Available LVM Disk Space
          • Reducing Network Bandwidth Usage
          • How to re-sync using checkpoint sync
          • Important Directory Locations
          • Improving Validator Attestation Effectiveness
          • EIP2333 Key Generator by iancoleman.io
          • 😁Geth - Enabling path-based state storage
          • Disk Usage by Execution / Consensus Client
          • Dealing with Storage Issues on the Execution Client
        • Join the Community
        • Credits
        • See Also
        • Changelog
      • 🌠Guide | How to setup a validator for Ethereum staking on testnet HOODI
        • Overview - Manual Installation
        • Step 1: Prerequisites
        • Step 2: Configuring Node
        • Step 3: Installing execution client
          • Nethermind
          • Besu
          • Geth
          • Erigon
          • Reth
        • Step 4: Installing consensus client
          • Lighthouse
          • Lodestar
          • Teku
          • Nimbus
          • Prysm
        • Step 5: Installing Validator
          • Setting up Validator Keys
          • Installing Validator
            • Lighthouse
            • Lodestar
            • Teku
            • Nimbus
            • Prysm
          • Next Steps
        • Maintenance
          • Updating Execution Client
          • Updating Consensus Client
          • Backups Checklist: Critical Staking Node Data
          • Uninstalling Staking Node
      • ⛓️Guide | How to setup a validator for Ethereum staking on testnet HOLESKY
        • Overview - Manual Installation
        • Step 1: Prerequisites
        • Step 2: Configuring Node
        • Step 3: Installing execution client
          • Nethermind
          • Besu
          • Geth
          • Erigon
          • Reth
        • Step 4: Installing consensus client
          • Lighthouse
          • Lodestar
          • Teku
          • Nimbus
          • Prysm
        • Step 5: Installing Validator
          • Setting up Validator Keys
          • Installing Validator
            • Lighthouse
            • Lodestar
            • Teku
            • Nimbus
            • Prysm
          • Next Steps
        • Maintenance
          • Updating Execution Client
          • Updating Consensus Client
          • Backups Checklist: Critical Staking Node Data
          • Uninstalling Staking Node
      • 💰Guide | MEV-boost for Ethereum Staking
        • MEV Relay List
      • 🔎Guide | Recover Ethereum Validator Mnemonic Seed
      • 🦉Update Withdrawal Keys for Ethereum Validator (BLS to Execution Change or 0x00 to 0x01) with ETHDO
      • 📜Archived Guides
        • Guide Version 1 | How to setup a validator for Ethereum staking on MAINNET
          • PART I - INSTALLATION
            • Step 1: Prerequisites
            • Step 2: Configuring Node
            • Step 3: Setting up Validator Keys
            • Step 4: Installing execution client
            • Step 5: Installing consensus client
            • Monitoring your validator with Grafana and Prometheus
            • Mobile App Node Monitoring by beaconcha.in
            • Security Best Practices for your ETH staking validator node
            • Synchronizing time with Chrony
            • Monitoring with Uptime Check by Google Cloud
          • PART II - MAINTENANCE
            • Updating your consensus client
            • Updating your execution client
            • Uninstalling V1 Staking Node
            • Finding the longest attestation slot gap
            • Checking my eth validator's sync committee duties
            • Pruning the execution client to free up disk space
            • Checklist | Confirming a healthy functional ETH staking node
          • PART III - TIPS
            • 🛡️Switching / Migrating Execution Client
            • Voluntary Exiting a Validator
            • Verifying Your Mnemonic Phrase
            • Adding a New Validator to an Existing Setup with Existing Seed Words
            • Switching / Migrating Consensus Client
            • Using All Available LVM Disk Space
            • Reducing Network Bandwidth Usage
            • How to re-sync using checkpoint sync
            • Important Directory Locations
            • Hosting Execution client on a Different Machine
            • Adding or Changing Graffiti flag
            • Improving Validator Attestation Effectiveness
            • EIP2333 Key Generator by iancoleman.io
            • Disk Usage by Execution / Consensus Client
            • Dealing with Storage Issues on the Execution Client
          • Join the Community
          • Credits
          • See Also
          • Changelog
        • Guide Version 1 | How to setup a validator for Ethereum staking on testnet GOERLI
          • Step 1: Prerequisites
          • Step 2: Configuring Node
          • Step 3: Setting up Validator Keys
          • Step 4: Installing execution client
          • Step 5: Installing consensus client
        • Guide Version 2 | How to setup a validator for Ethereum staking on testnet GOERLI
          • Step 1: Prerequisites
          • Step 2: Configuring Node
          • Step 3: Installing execution client
            • Nethermind
            • Besu
            • Geth
            • Erigon
          • Step 4: Installing consensus client
            • Lighthouse
            • Lodestar
            • Teku
            • Nimbus
            • Prysm
          • Step 5: Installing Validator
            • Setting up Validator Keys
            • Installing Validator
              • Lighthouse
              • Lodestar
              • Teku
              • Nimbus
              • Prysm
            • Next Steps
          • Maintenance
            • Updating Execution Client
            • Updating Consensus Client
            • Backups Checklist: Critical Staking Node Data
            • Uninstalling Staking Node
        • Guide | Ethereum Staking on Zhejiang Testnet
        • Guide | Besu + Lodestar | Most Viable Diverse Client | Staking Ethereum on Kiln testnet
        • Guide | How to setup a validator for Ethereum staking on Pithos testnet in 10 minutes or less
        • Ethereum Merge Upgrade Checklist for Home Stakers and Validators
        • Guide | Operation Client Diversity: Migrate Prysm to Teku
      • Guide: How to buy ETH
    • Cardano: ADA
      • Guide: How to Set Up a Cardano Stake Pool
        • Benefits of Operating a Cardano Stake Pool
        • PART I - INSTALLATION
          • Prerequisites
          • Hardening an Ubuntu Server
          • Setting Up chrony
          • Installing the Glasgow Haskell Compiler and Cabal
          • Compiling Cardano Node
        • PART II - CONFIGURATION
          • Downloading Configuration Files
          • Configuring Topology
          • Configuring an Air-gapped, Offline Computer
          • Creating Startup Scripts and Services
        • PART III - OPERATION
          • Starting the Nodes
          • Accessing Built-in Help
          • Generating Keys for the Block-producing Node
          • Setting Up Payment and Stake Keys
          • Registering Your Stake Address
          • Registering Your Stake Pool
          • Verifying Stake Pool Operation
          • Setting Up Dashboards
          • Configuring Slot Leader Calculations
          • Securing Your Stake Pool Using a Hardware Wallet
          • Setting up a Mithril Signer
        • PART IV - ADMINISTRATION & MAINTENANCE
          • Checking Stake Pool Rewards
          • Claiming Stake Pool Rewards
          • Delegating to a Stake Pool
          • Delegating to a Representative
          • Issuing a New Operational Certificate
          • Updating Stake Pool Information
          • Upgrading a Node
          • Retiring Your Stake Pool
          • Auditing Your nodes configuration
          • KES Key Rotation / Operational Certificate Companion Script
        • PART V - TIPS
          • Submitting a Simple Transaction
          • Transferring Files Using SSH
          • Updating Configuration Files
          • Implementing Peer Sharing
          • Uploading Pool Metadata to GitHub Pages
          • Obtaining a PoolTool API Key
          • Configuring Glasgow Haskell Compiler Runtime System Options
          • Reducing Missed Slot Leader Checks and Improving Cardano Node Performance
          • Increasing Swap File Size
          • Setting Up an External Passive Relay Node
          • Setting Up WireGuard
          • Monitoring Node Security Using OSSEC Server and Slack
          • Resetting an Installation
          • Fixing a Corrupt Blockchain
          • Verifying an ITN Stake Pool
          • Fixing the Mnemonic Staking Balance Bug
        • Appendix A - Best Practices Checklist
        • Appendix B - Cardano Resource Index
        • Discord Chat Channel
        • See Also
        • Credits
      • Guide: How to buy ADA
      • Guide: How to stake ADA
    • Monero: XMR
      • Guide | How to run your own Monero node
      • Guide: How to mine Monero
      • Create a XMR paper wallet
      • External Reading Material
        • Movie: Monero Means Money
        • Guide: Zero to Monero
        • Book: Mastering Monero
Powered by GitBook
On this page
  • 1. Obtain ETH
  • 2. Generate validator keys
  • Result: There are two types of files generated.
  • 3. Transfer validator keys to node
  • 4. Deposit transactions at the Launchpad
  • 4. Review backups
Edit on GitHub
  1. Coins
  2. Ethereum: ETH
  3. Guide | How to setup a validator for Ethereum staking on mainnet
  4. PART I - INSTALLATION
  5. Step 5: Installing Validator

Setting up Validator Keys

PreviousStep 5: Installing ValidatorNextInstalling Validator

Last updated 1 month ago

1. Obtain ETH

To make the deposit transaction(s), you will want your 32 ETH, or multiples, in a single hardware wallet address.

Every 32 ETH you own allows you to make 1 validator. You can run thousands of validators with your node.

2. Generate validator keys

Before continuing please have the following:

Before continuing please understand the following:

If this is not possible, at least physically disconnect from the network by unplugging ethernet cable or disconnecting from Wifi.

Ways to create your validator keys:

Option 1 for Ubuntu - ethstaker_deposit-cli

1. Download ethstaker_deposit-cli from Github.

#Install dependencies
sudo apt install jq curl -y

#Setup variables
RELEASE_URL="https://api.github.com/repos/eth-educators/ethstaker-deposit-cli/releases/latest"
BINARIES_URL="$(curl -s $RELEASE_URL | jq -r ".assets[] | select(.name) | .browser_download_url" | grep linux-amd64.tar.gz$)"
BINARY_FILE="ethstaker_deposit-cli.tar.gz"

echo "Downloading URL: $BINARIES_URL"

cd $HOME
#Download binary
wget -O $BINARY_FILE $BINARIES_URL
#Extract archive
tar -xzvf $BINARY_FILE -C $HOME
#Rename
mv ethstaker_deposit*amd64 ethstaker_deposit-cli
cd ethstaker_deposit-cli

2. Make a new mnemonic

Replace <HARDWARE_WALLET_ADDRESS> with withdrawal address.

./deposit new-mnemonic --chain mainnet --execution_address <HARDWARE_WALLET_ADDRESS>
  • Choose your language

  • Repeat your withdrawal/execution address for confirmation

  • Choose the language of the mnemonic word list

  • Choose how many new validators you wish to run

  • Create a keystore password that secures your validator keystore files

  • Repeat your keystore password for confirmation

  • Answer yes if you want to generate compounding 0x02 validator

  • Write down your 24 word mnemonic seed

  • Type your mnemonic, first 4 letters is enough

You will see the following messages after successfully generated the keystore(s) and the deposit(s):


                  #####     #####
                ##     #####     ##
    ###         ##   #######     #########################
    ##  ##      #####               ##                   ##
    ##     #####                 ##                       ##
    ##     ##                     ##                      ###
   ########                        ##                     ####
   ##        ##   ###         #####                       #####
   #                          ##                         # #####
   #                            #                        #  #####
   ##                             ##                    ##
   ##                              ##                   ##
   ##             ###              ##                   ##
   ###############                 ##                   ##
   ###               ##                                 ##
      #############################                    ##
                     ##                             ###
                     #######     #################     ###
                     ##   ## ##        ##   ##    ###
                     ##############          #############

Creating your keys:               [####################################]  <N>/<N>
Creating your keystores:          [####################################]  <N>/<N>
Verifying your keystores:         [####################################]  <N>/<N>
Verifying your deposits:          [####################################]  <N>/<N>

Success!
Your keys can be found at: /home/username/ethstaker_deposit-cli/validator_keys
Option 2 for Windows/Linux/Mac - Wagyu GUI

Wagyu is an application aimed at lowering the technical bar to staking on Ethereum.

As a 'one-click installer', it provides a clean UI automating the setup and management of all the infrastructure necessary to stake without the user needing to have any technical knowledge.

  1. Click create new secret recovery phrase

  2. Select your network

  3. Click create

  4. Write down your 24 word secret recovery phrase

  5. Check your phrase to confirm you copied it correctly

  6. Specify number of new keys to generate

  7. Specify your keystore password

  8. Specify your Withdrawal address

  9. Click next

  10. Re-type your keystore password

  11. Browse to where you want to save your keys

  12. Review information and close

Option 3 - Offline Tails with ethstaker_deposit-cli

The Tails OS is an amnesic operating system, meaning it will save nothing and leave no tracks behind each time you boot it.

1. Prerequisites

You need:

  • 2 storage mediums (can be USB stick, SD cards or external hard drives)

  • One of them must be > 8GB

  • Windows or Mac computer

  • 30 minutes or longer depending on your download speed

2. Download Tails OS

Make sure you follow the guide on the Tails website to verify your download of Tails.

3. Download and install the software to transfer your Tails image on your USB stick

For Windows, use one of

4. Making your bootable USB stick

Run the above software. This is an example how it looks like on Mac OS with etcher, but other software should be similar.

Select the Tails OS image that you downloaded as the image. Then select the USB stick (the larger one).

Then flash the image to the larger USB stick.

5. Download and verify the ethstaker_deposit-cli

Download the latest ethstaker_deposit-cli binary by referring to Option 1's steps.

Copy the file to the other USB stick.

6. Reboot your computer and into Tails OS

After you have done all the above, you can reboot. If you are connected by a LAN cable to the internet, you can disconnect it manually.

Plug in the USB stick that has your Tails OS.

On Mac, press and hold the Option key immediately upon hearing the startup chime. Release the key after Startup Manager appears.

On Windows, it depends on your computer manufacturer. Usually it is by pressing F1 or F12. If it doesn't work, try googling "Enter boot options menu on [Insert your PC brand]"

Choose the USB stick that you loaded up with Tails OS to boot into Tails.

7. Welcome to Tails OS

You can boot with all the default settings.

8. Run ethstaker_deposit-cli

Plug in your other USB key with the ethstaker_deposit-cli file.

Locate the USB key, mount the drive and add execute permissions.

# Locate the usb key
sudo fdisk -l
# Create a mount point
sudo mkdir -p /media/usb-drive
# Mount the usb key. Change device name
sudo mount /dev/sda1 /media/usb-drive
# Change directories
cd /media/usb-drive/ethstaker_deposit-cli
# Add execute permissions
sudo chmod +x ./deposit

9. Make a new mnemonic

Replace <HARDWARE_WALLET_ADDRESS> with withdrawal address.

./deposit new-mnemonic --chain mainnet --execution_address <HARDWARE_WALLET_ADDRESS>
  • Choose your language

  • Repeat your withdrawal/execution address for confirmation

  • Choose the language of the mnemonic word list

  • Choose how many new validators you wish to run

  • Create a keystore password that secures your validator keystore files

  • Repeat your keystore password for confirmation

  • Answer yes if you want to generate compounding 0x02 validator

  • Write down your 24 word mnemonic seed

  • Type your mnemonic, first 4 letters is enough

You will see the following messages after successfully generated the keystore(s) and the deposit(s):


                  #####     #####
                ##     #####     ##
    ###         ##   #######     #########################
    ##  ##      #####               ##                   ##
    ##     #####                 ##                       ##
    ##     ##                     ##                      ###
   ########                        ##                     ####
   ##        ##   ###         #####                       #####
   #                          ##                         # #####
   #                            #                        #  #####
   ##                             ##                    ##
   ##                              ##                   ##
   ##             ###              ##                   ##
   ###############                 ##                   ##
   ###               ##                                 ##
      #############################                    ##
                     ##                             ###
                     #######     #################     ###
                     ##   ## ##        ##   ##    ###
                     ##############          #############

Creating your keys:               [####################################]  <N>/<N>
Creating your keystores:          [####################################]  <N>/<N>
Verifying your keystores:         [####################################]  <N>/<N>
Verifying your deposits:          [####################################]  <N>/<N>

Success!
Your keys can be found at: /home/username/ethstaker_deposit-cli/validator_keys

Result: a folder called validator_keys containing keystore-m files and deposit_data.json

If you ran this command directly from your non-Tails USB stick, the validator keys should stay on it.

If it hasn't, copy the directory over to your non-Tails USB stick.

Confirm your validator_keys are on the USB stick before leaving.

ls /media/usb-drive/ethstaker_deposit-cli/validator_keys

Result: There are two types of files generated.

File type
Purpose

Keystore file(s)

[i.e.. keystore-16945983.json]

  • Controls the validator's ability to sign transactions

  • Imported and loaded into your validator

  • Keep private. Do not share with anyone

  • Can be recreated from your mnemonic seed/secret recovery phrase

Deposit data file(s)

[i.e. deposit_data-16945983.json]

  • Public information about your validator

  • Required to execute your deposit through the Ethereum Launchpad

  • Can be recreated from your mnemonic seed/secret recovery phrase

Local node: Skip this step if you generated your keys on your node with ethstaker_deposit-cli. No need to transfer as they're already there.

After creating the validator keys offline, you'll want to copy these validator keys to your node.

To align with this guide's steps, make the default validator_keys path on your node.

mkdir -p $HOME/ethstaker_deposit-cli/validator_keys

To transfer validator key files to your node from your local computer, consider using:

Option 1 - File Transfer
  • File transfer

Transfer the keystore-m_xxxxxxxx.json files to the following location on your node.

$HOME/ethstaker_deposit-cli/validator_keys
Option 2 - USB Key

Step 1: From OFFLINE machine, copy validator keys to a USB key.

Plug the USB key into offline machine, then locate the device name.

# Locate the usb key
sudo fdisk -l

Upon executing the above command you will get an output similar to the one below:

Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *     8192 15555555 25555555 7.4G  b W95 FAT32

Mount the key. Change the device name accordingly.

# Create a mount point
sudo mkdir -p /media/usb-drive
# Mount the usb key
sudo mount /dev/sdc1 /media/usb-drive

Copy the keys. Adjust the path names if needed.

# Create a directory on the usb drive to copy the keys into
sudo mkdir -p /media/usb-drive/ethstaker_deposit-cli/validator_keys
# Copy the keys to the usb drive
sudo cp $HOME/ethstaker_deposit-cli/validator_keys/*.json /media/usb-drive/ethstaker_deposit-cli/validator_keys
# Cleanup
sudo umount /media/usb-drive

Step 2: From a USB key, copy validator keys to the NODE.

Plug the USB key into node, then locate the device name.

# Locate the usb key
sudo fdisk -l

Upon executing the above command you will get an output similar to the one below:

Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *     8192 15555555 25555555 7.4G  b W95 FAT32

Mount the key. Change the device name accordingly.

# Create a mount point
sudo mkdir -p /media/usb-drive
# Mount the usb key
sudo mount /dev/sdc1 /media/usb-drive

Copy the keys. Adjust the path names if needed.

# Create a directory copy the keys into
sudo mkdir -p $HOME/ethstaker_deposit-cli/validator_keys
# Copy the keys to the default path
sudo cp /media/usb-drive/ethstaker_deposit-cli/validator_keys/*.json $HOME/ethstaker_deposit-cli/validator_keys
# Cleanup
sudo umount /media/usb-drive

After transferring the files, verify that the keystore-m files are in the proper location on your node.

ls -l $HOME/ethstaker_deposit-cli/validator_keys

Expected sample output:

-r--r----- 1 ethereum ethereum 706 Oct  1 02:33 deposit_data-1696645983.json
-r--r----- 1 ethereum ethereum 710 Oct  1 02:33 keystore-m_12381_3600_0_0_0-161664283.json

Only deposit the 32 ETH per validator if you are confident your node will be fully synced, which takes on average a day - check your logs, and ready to perform validator duties. You can return later to launchpad with your deposit-data to finish the next steps.

  1. Upload yourdeposit_data-#########.json found in the validator_keys directory.

  2. Connect the launchpad with your wallet, review and accept terms. Ensure you're connected to Mainnet network.

  1. Confirm the transaction(s). There's one deposit transaction of 32 ETH for each validator.

  • Deposit Example: If you want to run 3 validators you will need to have (32 x 3) = 96 ETH plus some extra to cover the gas fees.

  • Ledger Nano Hardware wallet users: If you encounter difficulty making the deposit transaction, enable blind signing and contract data.

4. Review backups

  • Stay Offline: Write down your mnemonic seed offline. Not email. Not cloud.

  • Verify your hardware wallet's backup: Most important of all data, this is where your withdrawal address belongs and ultimately controls the 32 ETH

  • In case of recovery: Stored on a USB key, keep copies of

    • validator_keys directory - contains all the keystore .json files

    • keystore password - used to encrypt keystore files

DO NOT USE AN EXCHANGE ADDRESS AS WITHDRAWAL ADDRESS.

Offline Key Generation Best Practices: The mnemonic seed (24 words) to your validator should be protected by keeping them offline. Use Tails OS (see option 3) or a (Option 1) or Wagyu to generate keys.

Download Wagyu:

You will learn how to boot up a windows PC into an airgapped .

Download the official image from the . Might take a while, go grab a coffee.

For Mac, download

Make sure you have saved your validator keys directory in your other USB stick (non Tails OS) before you shutdown Tails. Tails will delete everything saved on it after you shutdown.

Congrats on learning how to use Tails OS to make an air gapped system.

3. Transfer validator keys to node

Windows OS - use or

Mac or Linux - use or or

4. Deposit transactions at the Launchpad

Follow the walk-through at the Launchpad:

Batch Depositing Tip: If you have many deposits to make for many validators, consider using This greatly improves the deposit experience as multiple deposits can be batched into one transaction, thereby saving gas fees and saving your fingers by minimizing Metamask clicking.

Source:

Verify Deposit Contract: Your transaction is depositing ETH to the Check, double-check, triple-check that the official Ethereum Deposit Contract address is correct.

Critical Crypto Reminder: Keep your mnemonics, keep your ETH.

More than 1 backup of mnemonic: Multiple copies with multiple locations is better. Best stored in a

Validator key setup and deposits are complete!

🥩
🛑
🛑
🔥
🎉
⬆️
👩‍💻
🔥
🎉
Linux Live USB
https://wagyu.gg
Tails operating system
Tails website
Etcher
Win32 Disk Imager
Rufus
Etcher
WinSCP
FileZilla
FileZilla
SFTP
rsync
https://launchpad.ethereum.org
🐳
Abyss.finance's eth2depositor tool.
https://twitter.com/AbyssFinance/status/1379732382044069888
official deposit contract address.
0x00000000219ab540356cBB839Cbe05303d7705Fa
metal seed.
🌱
🔑
Safe multisig wallet
Withdrawal Address
https://etherscan.io
Example of Vitalik's address in checksum format