Connect your wallet. Disable the "Enclave" option. Then, copy + paste the command on a text editor and set the--password-file and --output-file to output/password.txt and output/registration_001.json.
Validator enclaves using Intel SGX is not live on mainnet yet and the current version on testnet will be deprecated in favour of the upcoming V2 SGX.
Example Command:
Follow the prompts to select the number of validator keys to generate.
If successful, you should see the following files in your ~/coral/output and ~/coral/etc/keys/bls_keys folders.
Expected output:
Expected output:
*Example only. You should see a file with it's validator public key as its file name.
Transfer Puffer registration file
Open up your terminal/powershell on your Mac/Windows laptop and run:
Your <google_cloud_username> can be found in the email you used to sign up for Google Cloud. e.g., if [email protected] is the email used, then sam is your username.
Print the ssh public key.
Copy the output, click into your Google Cloud instance>>EDIT, scroll down to SSH Keys>>ADD ITEM, and paste it here. Then Save.
Open up the terminal app on your laptop and run the secure copy command to retrieve your Puffer registration file. We will upload this file onto the Puffer launchpad in the next step to register your validator.
Tip: Replace <username> & <IP_address> with the actual username & IP address of your server/node.
To find username, look to the terminal of your sever/node. Every character before the @ is your username
To find IP address of a virtual machine (VM), go to your cloud service console, click into your VM and find the "Public IP"
To find IP address of a self-hosted machine, SSH into the machine and run ip aon the terminal. The IP address will take the form of 192.168.xx.xx
Do not use any other method to transfer the registration.json file onto your laptop as the data might be corrupted during transfer. Uploading invalid registration files will result in penalties which will be deducted from your Validator Tickets.
Mint pufETH and Validator Tickets (VTs)
Purchase 2 ETH worth of pufETH and at least 28 days worth of validator tickets.
Non-enclave users must deposit 2 ETH worth of pufETH to register
A minimum of 28 Validator Tickets (VTs) are required to be deposited when registering a validator. The Guardians will exit validators if their VTs expire after 28 days without being refilled.
Validator Registration
Upload the registration.json file that you retrieved from your server/node onto your laptop here.
You will then be prompted to sign 3 transactions on your wallet.
Sign a Permit message to deposit your VTs to the PufferProtocol contract
Sign a Permit message to deposit your pufETH bond to the PufferProtocol contract
Sign the final transaction to register your validator
Await deposit by Puffer
The Guardians will provision pending validators when there is 32 ETH of liquidity in the PufferVault.
Invalid registrations will be skipped by the Guardians. Your bond will be returned but your VTs are penalized to prevent griefing.
Import validator keys
Now that your validator is registered with Puffer, you will need to import the validator key into your validator client.
ETH Docker users
Follow the steps in the page below until before the "Import validator keys" section.
Move your validator key(s) into the ~/eth-docker/.eth/validator_keys folder.
Import validator keys into your validator client
Alternatively,
If you have not configured your validator node go to the eth-docker page to complete the setup.
Monitor logs
Monitor the logs of your validator node to make sure that it is syncing (or synced) with no errors while you wait for Puffer to provision your validator deposit with 32 ETH.
