Node operators should deploy bare metal servers to achieve optimal performance. Additionally, validator nodes must meet the recommended hardware specifications and particularly the CPU requirements, to ensure high uptime.Documentation Index
Fetch the complete documentation index at: https://injectivelabs-mintlify-jp-developers-first-half-1777019423.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Hardware Requirements
| Minimum | Recommendation |
|---|---|
| RAM Memory 128GB | RAM Memory 128GB |
| CPU 12 cores | CPU 16 cores |
| CPU base clock 3.7GHz | CPU base clock 4.2GHz |
| Storage 2TB NVMe | Storage 2TB NVMe |
| Network 1Gbps+ | Network 1Gbps+ |
Step 1: Create a Validator Account
First, run the keygen command with your desired validator key name.The output will contain a mnemonic phrase that represents your key in plain text. Make sure to save this phrase as a backup of your key, since without a key you will not be able to control your validator. The phrase is better be backed up on physical paper, storing it in cloud storage may compromise your validator later.Remember the address starting from
inj, this is going to be your Injective Validator Account address.Step 2: Obtain Mainnet INJ
To proceed with the next step, you will need to obtain some real INJ on Mainnet Ethereum (ERC-20 token address0xe28b3b32b6c345a34ff64674606124dd5aceca30).
Step 3: “Transfer” INJ to your validator account on Injective
Deposit your Mainnet INJ tokens into your validator’s account on Injective by using the staking dashboard. You will have to connect your wallet on our Hub and then deposit INJ from Ethereum Mainnet network. This will trigger an automated bridge that maps tokens from Ethereum network to Injective. After a few minutes, you should be able to verify that your deposit was successful on the UI. Alternatively, you can query your account balance using theinjectived CLI with the following command:
Step 4: Create your validator account
Obtain your node’s Tendermint validator Bech32 encoded PubKey consensus address.--moniker- Your validator’s name--amount- Your validator’s initial amount of INJ to bond--commission-max-change-rate- Your validator’s maximum commission change rate percentage (per day)--commission-max-rate- Your validator’s maximum commission rate percentage--commission-rate- Your validator’s initial commission rate percentage--min-self-delegation- Your validator’s minimum required self delegation
create-validator options to consider:
Step 5: (Optional) Delegate Additional INJ to your Validator
To gain a deeper empirical understanding of user experience that your future delegators will experience, you can try delegation through Staking Guide. These steps will allow you to experience the delegation flow using MetaMask Transactions. 🦊 Alternatively, you can always use the Injective CLI to send a delegation transaction.Step 6: (Recommended) Connecting Your Validator Identity with Keybase
By adding your Keybase pubkey to your validator identity information in Injective, you can automatically pull in your Keybase public profile information in client applications like the Injective Hub and Explorer. Here’s how to connect your validator identity with your Keybase pubkey:- Create a validator profile on Keybase at https://keybase.io/ and make sure it’s complete.
- Add your validator identity pubkey to Injective:
- Send a
MsgEditValidatorto update yourIdentityvalidator identity with your Keybase pubkey. You can also use this message to change your website, contact email, and other details.
- Send a
