Services
  • 𝐥𝐞𝐬𝐧𝐢𝐤 | 𝐔𝐓𝐒𝐀
  • 🌐Cosmos WIKI
    • 🔧Creating / Editing a Validator
    • 📨Cosmos / governance
    • 🛠️Useful commands
    • 🔨Changing ports in the Cosmos ecosystem
    • 🌁IBC (HERMES)
    • ⚒️Node-exporter + Grafana + Prometheus + Alertmanager
    • ⚒️TenderDuty v2 - monitoring and alerting
  • Mainnet
    • Arkeo
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Atomone
      • 💻Installation
      • ⌚State sync
      • ⌚Snapshots
      • 📬Updates
    • Aura
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Dora Factory
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Dymension
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Genesis L1
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Gitopia
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Jackal
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Konstellation
      • 💻Installation
      • ⌚Snapshot
      • 📬Updates
    • Nibiru
      • 💻Installation
      • ⌚State sync
      • 📬Updates
      • 📬Price feeder (✔️Oracle)
    • Provenance
      • 💻Installation
      • 📬Updates
    • Teritori
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Quicksilver
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Uptick
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Source protocol
      • 💻Installation
      • 📬Updates
    • Zenrock
      • 💻Installation
      • 💻Sidecar (✔️Oracle)
      • 💻Create a validator
      • ⌚State sync
      • ⌚Snapshot
      • 📬Updates
  • TESTNET
    • Atomone
      • 💻Installation
      • 📬Updates
    • Airchains
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Aura
      • 💻Installation
      • 📬Updates
    • Arkeo
      • 💻Installation
      • ⌚State sync
      • 📬Updates
      • 📬Providers
    • AXON PROTOCOL
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Dora Factory
      • 💻Installation
      • 📬Updates
    • Dymension
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Empeiria
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Galactica
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Jackal
      • 💻Installation
      • 📬Updates
    • Kira
      • 💻Installation
    • PRYSM
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Source protocol
      • 💻Installation
      • 📬Updates
    • Story Protocol
      • 💻Installation
      • 💻Create a validator
      • ⌚State sync
      • ⌚Snapshot
      • 📬Updates
    • Tellor
      • 💻Installation
      • ⌚State sync
      • 📬Updates
      • 📬Data Reporter (✔️Oracle)
    • Quicksilver
      • 💻Installation
      • 📬Updates
    • Warden Protocol
      • 💻Installation
      • ⌚State sync
      • 📬Updates
      • 📬Oracle
    • XRPL EVM
      • 💻Installation
      • ⌚State sync
      • ⌚Snapshots
      • 📬Updates
    • Zenrock
      • 💻Installation
      • 💻Sidecar (✔️Install)
      • 💻✔️config.yaml
      • 💻✔️eigen_operator_config.yaml
      • 💻Create a validator
      • 📬Updates
  • OTHER PROJECTS
    • Avail mainnet
      • 💻Installation
      • ⌚Snapshot
      • 📬Validator migration
    • Avail testnet
      • 💻Installation
      • ⌚Snapshot
      • 📬Validator migration
    • Kusama
      • 💻Decentralized nodes
      • 💻Installation
      • ⌚Snapshot
      • ⚙️Validator setup
      • ⚙️Validator migration
      • 🛠️Crunch bot
    • Polkadot
      • 💻Decentralized nodes
      • 💻Installation
      • ⌚Snapshot
      • ⚙️Validator setup
      • ⚙️Validator migration
      • 🛠️Crunch bot
    • Tangle Network
      • 💻Installation
      • 📬Validator migration
    • UOMI (GPU)
      • 💻Installation
      • ⌚Snapshot
      • 📬Validator migration
  • ARCHIVE
    • Entrypoint
      • 💻Installation
      • ⌚State sync
      • 📬Updates
    • Celestia
      • 💻Consensus Node
      • 🖥️Bridge node (Shwap)
      • 🖥️Full node (Shwap)
      • 🖥️Light node (Shwap)
      • ⌚Snapshots
      • ⌚State Sync [consensus node]
      • 🔎Analysis of the Bridge Node
    • Celestia-testnet
      • 💻Consensus Node
      • 🖥️Bridge node (Shwap)
      • 🖥️Full node (Shwap)
      • 🖥️Light node (Shwap)
      • ⌚Snapshots
      • ⌚State Sync [consensus node]
      • 🔎Analysis of the Bridge Node
    • Native [migration to SUI]
      • 💻Installation
      • ⌚Snapshots
      • ⌚State sync
      • 📬Updates
    • Nubit
      • 💻Light node
      • 📬Full Node
    • Lava network
      • 💻Installation
      • ⌚State sync
      • ⌚Snapshot
      • 📬Updates
      • ⌚Providers
    • Lava network
      • 💻Installation
      • ⌚State sync
      • ⌚Snapshot
      • 📬Updates
      • ⌚Providers
    • XAI
      • 💻Installation
    • Ojo
      • 💻Installation
      • ⌚State sync
      • ⌚Snapshot
      • 📬Updates
      • 📬Price feeder (✔️Oracle)
Powered by GitBook
On this page
  • Node installation
  • Saving keys
  • Setting network configuration
  • Adding Seed
  • Joining a validator set
  1. TESTNET
  2. Kira

Installation

PreviousKiraNextPRYSM

Last updated 1 year ago

Features of Kira

  • Validators do not save the entire block history in order to save disk space. This task should only be performed by sentinel and archive nodes

  • To participate in the test network, you must pass KYC and fill out a form. To join the set of validators, you need to install a node and find out the public address of the validator, which you will need to indicate in the form to get on the white list

  • In KIRA, double signature is the only violation that is punishable. More details and

  • There are no severe penalties for validators being disabled or temporarily unavailable. Nodes that go offline for an extended period of time will be deactivated and automatically removed from the consensus by the state machine. The network is designed to stop if ≥ 1/3 of the consensus nodes suddenly stop responding, but there should be no interruption to the network if individual nodes randomly leave and enter the consensus. As long as the number of validators does not fall below the min_validators defined in the , the chain will continue to generate new blocks

IMPORTANT - install on a new server without other nodes. Automatic installation closes all ports for other nodes in Docker and reboots the server

Node installation

adduser kira
usermod -aG sudo kira
su kira
sudo -s

We enter the command - after which we are prompted to enter the current version. We can find the current version on github -

cd /tmp && apt-get install -y wget && \
UBUNTU_AGENT="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.85 Safari/537.36" && \
echo -ne "\033[1;32m\nPlease enter version of KM to install: \033[0m" && read V && \
wget --user-agent="$UBUNTU_AGENT" https://github.com/KiraCore/kira/releases/download/${V}/init.sh -O ./i.sh && \
chmod +x -v ./i.sh && ./i.sh --infra-src="$V" --init-mode="interactive" || echo -e "\033[1;31mERROR: KM setup failed, error code '$?'\033[0m"

We agree to the terms and conditions - Y

After the initial installation we see a similar window. It provides a launch menu that allows you to configure the node, manage network parameters, upload snapshots and view the hash of the genesis file

Saving keys

During automatic installation, a mnemonic phrase is generated. Keys are saved along the path /home/kira/.secrets/

IMPORTANT - be sure to select the [M] “View or Modify Mnemonic” option before exiting the “Node Launcher” menu and then press [V] to display the main mnemonic. Write down your mnemonic phrase in a safe place

Setting network configuration

Setting up sshd_config. If you are using a non-standard port for ssh, then select the [N] option and then press [M]. Skip this step if your ssh port is 22 (default)

Adding Seed

To add Peers, select option [A]

Once we have received our Peers we can continue with the installation. To do this, select the [S] option

You can follow the process by pressing [V]

At the end of the node installation, your server will be automatically rebooted!!!

sudo -s
kira

You can follow the process by pressing [V]. At the end of the installation you should see the following

Press "Q" or "Ctrl+C" to exit, then type kira to enter KIRA Manager

Joining a validator set

After filling out the form, you can write in telegram to speed up the process of adding to the whitelist Once the team whitelists you, you will be given the opportunity to select option [J] to join the validator set in the KIRA Manager main menu. After executing this option, the node will begin to create and sign the proposed blocks

NOTE: One of the most useful features is the maintenance mode. Whenever you need to update your node or move it or perform any other operations that may cause the validator to sign the process to stop, you can select option [E] to enter maintenance mode. This will prevent the validator statistics from being reset and going into an inactive state. After completing the maintenance, selecting option [D] will disable the maintenance mode

MASTER_MNEMONIC is the only secret you will need to keep, since all other keys in KIRA are derived from it. More details

It is extremely important to add the correct Peers to synchronize with the network. You can request an IP address from any of the other validators or use the addresses specified in the corresponding section of the test network -

To join the validator set, you first need to become a KIRA tester. Your initial goal will be to determine your public validator address, which will need to be provided on the in order to be whitelisted. Once the installation process is complete, you can easily find your validator address by entering kira in the terminal to open KIRA Manager. Then select option [0] ([0] by default) and copy your validator address

💻
here
here
network properties
https://github.com/KiraCore/kira
here
https://ipfs.kira.network/ipfs/bafybeihne7fpjrx2x7ofgu2nbfnyzsht4vnjgxhnzmv3pxxmuzllsn3nfa/chaosnet-1.html
FORM