Since the Gnosis merge to Proof of Stake on December 7 2022, Gnosis requires two Avado packages to run:
Once installed, both packages start syncing automatically.
⏳ Be patient: Syncing takes some time. You will see high CPU usage for a while. (As a point of reference: on an Avado i7, Nethermind-gnosis took about 12 hours of high CPU usage (sync from scratch). Teku-gnosis took 24 hours to drop from ~200% to ~100% CPU usage.)
Teku-Gnosis reports its status on http://teku-gnosis.my.ava.do.
😀 What you should see:
- Status: “Syncing x %” or “In Sync” (If you see “Syncing 100%”, it means Teku is synced, but it is waiting for Nethermind-Gnosis to be in sync)
- Connected Peers: number bigger than 0
🧐 What you prefer not to see:
- “Inbound: 0”: This means you have no inbound peers, so port
9006(used for p2p communication) is closed from the outside. Manually open this port on your router if your are not using UPnP.
🙁 What you don’t want to see:
- “Waiting for the beacon chain to become ready”: It is Ok for this message to appear when you open the page. But it should the status after a few seconds. If this messages persists, Teku-Gnosis could not start. Check the logs for a clue.
Syncing Nethermind takes a lot of time (>140 GB of data), so you will need patience. You can check that it is making progress, by looking at the block numbers in http://nethermind-gnosis.my.ava.do, or the disk size or logs in http://my.ava.do/#/Packages/nethermind-gnosis.avado.dnp.dappnode.eth/detail.
Most users also run a validator on the Gnosis Chain. This requires you to run a node, deposit GNO and configure your validators.
Proceed at your own risk. YOU take all risks associated with using this software and it is possible that you could lose your funds. You are solely responsible for your stake.
Visiting the official Gnosis Beacon Chain Deposit website is the ONLY way you should make the deposit. Do not attempt to manually send funds to the deposit contract or your will lose your funds.
There are a number of ways to obtain GNO. Do your own research and proceed at your own risk. It is highly recommended that if you don’t already have GNO on the ETH mainnet that you do not purchase it on the mainnet or else you will end up by far more in gas fees than you should be to bridge it across to the Gnosis chain. If you have GNO on the mainnet already, you can bridge it to the Gnosis chain by going to https://omni.xdaichain.com/bridge.
One easy and cost effective way to obtain GNO on the Gnosis chain (formerly xDai) is to bridge Dai from the ETH mainnet to the Gnosis chain using The Gnosis Chain Bridge. When you bridge Dai to xDai, you will then already have the xDai in your wallet that is needed to pay the gas on transactions of the Gnosis chain (which only cost fractions of a cent!).
Then once you have xDai in the account you wish to use to make your validator deposit, you can use Honeyswap or CowSwap or to swap xDai for GNO. Remember that for each validator you plan to run on the Gnosis Beacon Chain, you will need exactly 1 GNO. It is highly recommended that you start with 1 validator so that you can become familiar with this process before you try to run more.
You can import the GNO token to Metamask by visiting https://blockscout.com/xdai/mainnet/token/0x9C58BAcC331c9aa871AFD802DB6379a98e80CEdb/token-transfers and then clikcing on the fox to import the token to Metamask.
Wagyu is a Desktop GUI application that makes it easy to generate validator keys. Download Waygu from https://github.com/alexpeterson91/Gnosis-Wagyu-Key-Gen/releases
Unzip the app and start the application. (If MacOs complains that the developer cannot be verified, right click and select “open”)
A wizard will guide you through the process.
If this is your first validator, have a pen and paper ready to write things down. This is important before you proceed. You will be writing down passwords and a 24 word mnemonic phrase which are your responsibility to keep safe throughout your staking journey. If you lose the 24 word mnemonic phrase, no one will be able to help you and you will not be able to withdraw your funds when withdrawals are enabled.
Note that if you wish to create more keys later on using the key generator, if you use the same keystore password for all future keys that you create and stake with on the Avado, it will make your life easier if you ever have to re-import all your keys to the validator client. Just take care to manage your passwords and mnenonic phrases carefully when creating future validator keys.
Note that if you wish to run more than 1 validator, the EASIEST way to do this is to create a new keystore, deposit data and a new mnemonic phrase for each individual validator and then make individual deposits of 1 GNO each. You can create multiple keys in a batch using the existing key generator, and that will generate multiple keys with ONE deposit data file. Only do this if you have enough funds to make the deposit for the number of keys you generate or you will have a bad time when you get to Step #5. Whatever you do, keep careful track of whatever keys you make and keep them and the other files together and consider some type of naming scheme so you don’t get confused later on.
You have been warned!
Open the settings page and enter the address where you want to receive the fees of your proposed blocks. Most users use their MetaMask address here, but of course you can also specify a hard wallet address.
🔥 Don’t skip this step. Your validators will run if you forget this step, but all block fees will be burned. 🔥
It is highly recommended that before you proceed to the next steps that you ensure that your Gnosis Beacon chain is synced. To do this, simply open the Gnosis beacon chain package and scroll down to inspect the logs. An example of what your logs will look like when the chain is in sync is shown below.
It is recommended that you import the keystore file to the validator wallet before you make the deposit to ensure that the validator will accept your keystore file before you lock your funds into the deposit contract.
Import your keys: Open the Avado Teku Gnosis package, open the Add validator box and (per key):
- Click Choose keystore file… and select your keystore file
- Enter the corresponding password
- Click Add validator
- Repeat for all your keys. If your keys all have the same password, you leave the password field as is, and immediately click Add Validator after selecting the next keystore file.
Warning! Visiting the official Gnosis Beacon Chain Deposit website is the ONLY way you should make the desposit. Do not attempt to manually send funds to the deposit contract or your will lose your funds.
Make sure your Metamask is set on the Gnosis chain (or xDai) as we discussed in Step 0.
Visit the Gnosis Beacon Chain Deposit website and verify that the URL is https://deposit.gnosischain.com/ and then connect your Metamask wallet. Make sure your wallet is set to the Gnosis/xDai network.
Now, it is time to make the deposit.
Open the validator_keys folder that was created in Step 1. Drag the deposit data file (and only the deposit_data file) into the window that is showing on the Deposit page. Wait for it to confirm the deposit data. Note that this screenshot was taken from an older version of the deposit site and it is no longer required to swap to mGNO prior to making the deposit. As long as you have at least 1 GNO in your wallet when you import the deposit data file, the wizard will do the swap for you behind the curtain.
Then you may click on Deposit.
You will be asked to check three boxes to acknowledge that you have a pulse.
Let the deposit complete.
That is it for the deposit. Give it time to process, it takes about 2-4 hours for the deposit to be recognized by the GBC.
Check the status of your validators on the Gnosis Beacon Chain Dashboard. You can do this by clicking the green bar with the 📡 logo.
At this point, your validator should start making attestations automatically when it becomes active as long as you leave the Gnosis Beacon Chain and Validator packages running 24/7.
nginx: [emerg] cannot load certificate ...
- Fix: Restart Nethermind-gnosis
Failed to create CoreCLR, HRESULT: 0x80070008
- Fix: Make sure the Dappmanager core package is up to date (i.e. at least 0.0.42)
Waiting for peers...
- Fix: Make sure the Dappmanager core package is up to date (i.e. at least 0.0.42)
Waiting for the JWT Token
- Fix: Restart Nethermind (and check the Nethermind logs for errors listed above)
Connected Peers: 0
- Fix: Make sure port
30305is open (More info)
Telegram: AVADO - Gnosis Staking