🛠️
Technical Documentation
  • Introduction
    • About Empeiria
  • Empe Blockchain
    • Overview
    • Chain Architecture
      • Auth
      • Authz
      • Bank
      • Distribution
      • Governance
      • Staking
      • IBC
      • DidDoc
      • Vesting
      • Minter
  • EVDI
    • EVDI Architecture
    • Self-Sovereign Identity
      • Technical Foundations
      • Roles in the SSI framework
      • Protocols and Standards
  • User Guide
    • Empe DID Wallet
      • Intro
      • Download and first launch
      • Create or import did
      • Main screen overview
      • How to claim credential from issuer
      • How to use credential with verifier
      • Settings and other options
    • Keplr Wallet and Blockchain Operations
      • How to Connect Keplr Wallet
    • Ping Pub operation
    • Staking Tokens Guide
    • Voting on Governance Proposals Guide
    • Sending Tokens Guide
  • Developer Guide
    • Tutorial: Credential Issuance & Verification
      • Overview
      • Understanding Key Concepts
      • Project Setup
      • Deploying the Issuer
      • Uploading the Credential Schema
      • Issuing Credentials
      • Frontend for Credential Issuance
      • Testing Credential Issuance
      • Deploying the Verifier
      • Setting Up the Verification Flow
      • Creating a Verification Endpoint
      • Creating a Protected Dashboard
      • Testing the Verification Flow
      • Summary & Next Steps
    • One-click deployment
      • Introduction
      • Registration
      • Login
      • Creating an Issuer
      • Issuer Data Description
      • Creating a Verifier
      • Verifier Data Description
    • Verifier
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • Query Language
      • Frontend Integration
      • Client Configuration
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • FAQ
    • Issuer
      • Terminology and Concepts
      • Architecture Overview
      • Core Responsibilities
      • DID Document Management
      • Schemas Management
      • Issuing Credentials
      • Interacting with Wallets
      • Security Considerations
      • Error Handling and Troubleshooting
      • Future Enhancements
      • References and Standards
      • FAQ
    • Wallet SDK (Coming soon)
    • Introduction to cosmwasm
  • Validator Guide
    • Important links
    • Validators Guide
      • New validator
      • Hardware requirements
      • Required software installation
      • Go installation
      • Install prebuild binary
      • Install binary from source code (option B)
      • Configure a node
      • Cosmovisor setup
      • Sync with state-sync
      • Full state sync from archive snapshot
      • Latest snapshot
      • Run a Validator
      • Migration to v0.2.2
      • Migration to v0.3.0
    • FAQ
  • Appendix
    • Glossary
Powered by GitBook
On this page
  • Becoming a validator
  • Requirements
  • 1. Add wallet key
  • What is a Validator?
  • Create Your Validator
  • Confirm Your Validator is Running
  1. Validator Guide
  2. Validators Guide

Run a Validator

PreviousLatest snapshotNextMigration to v0.2.2

Last updated 9 months ago

Becoming a validator

Once you properly set up a full node, you can become a validator node and start earning by validating the chain transactions.

Requirements

If you want to become an Empe validator you need to:

  1. Be a full node and cosmovisor up. If you are not, please follow the full and

  2. The node must be synchronized

emped status | jq .SyncInfo.catching_up

The command above should return

false
  1. Own enough tokens. To become a validator you need at least 2 empe tokens to create the validator, and for transaction fee. You can obtain your tokens from faucet:

1. Add wallet key

Inside the testnet you can use the Ledger, but you can also use the wallet software with the emped. However, if you wish to use Ledger, please add the --ledger flat to any command.

Please remember to copy the 12-word seed phrase in a secure place. They are your mnemonic. If you lose them you lose all your tokens and access to your validator.

Create the first wallet with the following command:

emped keys add <KEY_NAME>
# Enter a password that you can remember

The output of the command will provide the 24 words that are the mnemonic.

Create two wallets one for the validator and the second for the vesting account: example

If you are using the Ledger device you must first connect it to your computer, start the Cosmos application (on the device), and run the command

emped keys add <KEY_NAME> --ledger
# Enter a password that you can remember

In this case, the 12 words are not provided because they have already been configured in the Ledger initialization

emped keys add validator
Enter keyring passphrase:
Re-enter keyring passphrase:

- name: validator
  type: local
  address: empe1atqq8lmeptgn2jlx2q8r42p572yhh6lzle7vng
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A8D47crCW+YkFGduj6brpuzectp3D61xRIx/qbEGGTif"}'
  mnemonic: ""
  
emped keys add vesting
Enter keyring passphrase:

What is a Validator?

Create Your Validator

Your empevalconspub consensus public key from tendermint can be used to create a new validator by staking tokens. You can find your validator pubkey by running:

emped tendermint show-validator

To create your validator use the following command:

emped tx staking create-validator \
  --amount=1000000uempe \
  --pubkey=$(emped tendermint show-validator) \
  --moniker=<YOUR_MONIKER> \
  --chain-id=empe-testnet-2\
  --commission-rate="0.10" \
  --commission-max-rate="0.20" \
  --commission-max-change-rate="0.01" \
  --gas="auto" \
  --min-self-delegation="1000000" \
  --fees=20uempe \
  --from=<KEY_NAME>

When specifying commission parameters, the commission-max-change-rate is used to measure % point change over the commission-rate. E.g. 1% to 2% is a 100% rate increase, but only 1 percentage point.

You can confirm that you are in the validator set by using an explorer.

Confirm Your Validator is Running

Your validator is active if the following command returns anything:

emped query tendermint-validator-set | grep "$(emped tendermint show-validator | jq .key  | tr -d \")"

You should now see your validator in one of the block explorers. You are looking for the bech32 encoded address in the ~/.emped-chain/config/priv_validator_key.json file.

To be in the validator set, you need to have more total voting power than the 50th validator.

If you don't have tokens get some from faucet () or ask on a validators group.

are responsible for committing new blocks to the blockchain through voting. A validator's stake is slashed if they become unavailable or sign blocks at the same height. Please read about to protect your node from DDOS attacks and to ensure high availability.

node configuration guide
Cosmovisor setup
https://faucet-testnet.empe.io
https://testnet.ping.pub/empe/faucet
Validators
Sentry Node Architecture