NG
Althea

Althea

Setup Guide

1. Download Althea Chain and the Gravity Tools

2. Generate Keys

Be sure to back up the phrase you get!

NB: ‘nodesguru’ is just the name of your moniker (2nd command) and name of your key (3rd command), you can select any you like. Also, they can be different.

Important: write generated mnemonic phrase in a safe place.

3. Genesis

Copy the genesis file use the following commands:

Edit using vi or nano your configuration file ~/.althea/config/config.toml to contain the following:

Execute:

Find persistent_peers, replace with the next value:

4. Start Althea Node

Press Ctrl+A then D to detach screen.

Check for Althea synchronization using:

Once “catching_up” becomes “false” you can proceed with the next steps (synchronization can take up to 24 hours). Additionally, you can check Current Height here.

5. Request Some Tokens

Check your address:

Copy your address from the ‘address’ field.

Sometimes faucet is not working correctly. In this case, please ask tokens in #althea-validators channel in Althea discord.

Check balance:

Send your validator setup transaction. Set moniker=<yournodename> and from=<keyname> (take it from step 2):

Enter your passphrase and select ‘y’.

Confirm that you are validating. Put your validator keyname:

6. Setup Gravity Bridge

You are now validating on the Althea blockchain. But as a validator, you also need to run the Gravity bridge components or you will be slashed and removed from the validator set after about 16 hours.

Edit your Validator node config to enable the RPC. Set ‘enable’ for api to true in the app.toml.

After you do this you need to restart your

validator.

hit ctrl-c and then run

Press Ctrl+A then D to detach screen.

7. Register Your Delegate Keys

Once you save the phrase generated by this command you will have two phrases to keep track of. Save THIS PHRASE you will need it later. The one generated here is your ‘delegate address’ and the one you generated before is your ‘validator address’.

8. Fund Your Delegate Keys

Both your Ethereum delegate key and your Cosmos delegate key will need some tokens to pay gas. On the Althea chain side you were sent some ‘footoken’ along with your ALTG. We’re essentially using footoken as a gas token for this testnet.

You should have received 100 Althea Governance Token in uALTG and the same amount of footoken. We’re going to send half to the delegate address.

To get the address for your validator key you can run the below, where ‘myvalidatorkeyname’ is whatever you named your key in the ‘generate your key’ step.

9. Download and Setup Geth on the Goerli Testnet

We will be using Geth Ethereum light clients for this task. For production Gravity, we suggest that you point your Orchestrator at a Geth light client and then configure your light client to peer with full nodes that you control. This provides higher reliability as light clients are very quick to start/stop and resync. Allowing you to for example rebuild an Ethereum full node without having days of Orchestrator downtime.

Please note that only Geth full nodes can serve Geth light clients, no other node type will do. Also, you must configure a Geth full node to serve light client requests as they do not do so by default.

For the purposes of this testnet just follow the instructions below, even on the slowest node you should be synced inside of a few minutes.

Press Ctrl+A then D to detach screen.

10. Start Your Orchestrator

Now that the setup is complete you can start your Orchestrator. Use the Cosmos mnemonic generated in the ‘register delegate keys’ step and the Ethereum private key also generated in that step. You should setup your Orchestrator in systemd or elsewhere to keep it running and restart it when it crashes.

If your Orchestrator goes down for more than 16 hours during the testnet you will be slashed and booted from the active validator set.

Since you’ll be running this a lot I suggest putting the command into a script, like so:

Press Ctrl+A then D to detach screen.

Stuck? Ask!

By continuing to use our website, you consent to our use of cookies in accordance with our cookie policy