<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by HowToNode on Medium]]></title>
        <description><![CDATA[Stories by HowToNode on Medium]]></description>
        <link>https://medium.com/@lindsaycabrera1903?source=rss-fe812e718e95------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1NvO_GTshkr14HbWriUVMw.png</url>
            <title>Stories by HowToNode on Medium</title>
            <link>https://medium.com/@lindsaycabrera1903?source=rss-fe812e718e95------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:13:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lindsaycabrera1903/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Install a Zora Project Node]]></title>
            <link>https://medium.com/@lindsaycabrera1903/how-to-install-a-zora-project-node-6af371575c7d?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/6af371575c7d</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[tutorial]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Wed, 17 Jul 2024 13:22:32 GMT</pubDate>
            <atom:updated>2024-07-17T13:22:32.070Z</atom:updated>
            <content:encoded><![CDATA[<h4>Full guide for node installation</h4><p>ZORA is a universal protocol for managing media registries. It enables creators to publish their creative materials, earn from their work, and develop and distribute their content through user engagement.</p><p>The project secured an impressive $60 million in its early stage, and its current valuation stands at $600 million. It’s also notable that Coinbase, a leading player in the market, is on board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*a3se0Atk5poR8g7h" /></figure><h3>Installing a Zora Project Node</h3><p>Today, we have the opportunity to install a node for this project and potentially receive rewards for contributing to its development. Historically, such rewards can range from words of gratitude to tens of thousands of dollars.</p><p>To get started, we’ll need to create an account on the <a href="https://www.alchemy.com/">Alchemy website</a>. Click on “Sign Up” in the top right corner and authorize using your Google account. Sometimes, registration requires entering a phone number, in which case, you’ll need to provide one.</p><h3>Setting Up a Virtual Server</h3><p>We’ll also need to rent a virtual server to install the node.</p><p>The recommended specifications for the node to work correctly are as follows:</p><ul><li>200GB SSD</li><li>16GB RAM</li><li>4 Cores</li></ul><h3>Installing the Node</h3><p>After completing all the necessary preparatory steps, we can proceed with the node installation. Open a terminal and enter the following commands:</p><h4>Command 1:</h4><pre>sudo apt-get update &amp;&amp; sudo apt-get upgrade -y</pre><h4>Command 2:</h4><pre>sudo apt install curl build-essential git screen jq pkg-config libssl-dev libclang-dev ca-certificates gnupg lsb-release -y</pre><h4>Command 3:</h4><pre>sudo install -m 0755 -d /etc/apt/keyrings<br>curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg<br>sudo chmod a+r /etc/apt/keyrings/docker.gpg</pre><h4>Command 4:</h4><pre>echo \<br>&quot;deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \<br>$(. /etc/os-release &amp;&amp; echo &quot;$VERSION_CODENAME&quot;) stable&quot; | \<br>sudo tee /etc/apt/sources.list.d/docker.list &gt; /dev/null<br>sudo apt-get update</pre><h4>Command 5:</h4><pre>sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose -y</pre><h4>Command 6:</h4><pre>git clone https://github.com/conduitxyz/node.git</pre><h4>Command 7:</h4><pre>cd node</pre><h4>Command 8:</h4><pre>./download-config.py zora-mainnet-0</pre><h4>Command 9:</h4><pre>export CONDUIT_NETWORK=zora-mainnet-0</pre><h4>Command 10:</h4><pre>cp .env.example .env<br>nano .env</pre><p>Here, we need to refer to our personal account on Alchemy, where we registered earlier, and create API keys. Click on “Create new App,” name it, and click “Create App.” Open the created App, click on the API Key next to its name, and copy the middle HTTPS.</p><p>Paste this into the terminal instead of the placeholder HTTPS. Press CTRL + X, then type “y” and press Enter, followed by Enter again.</p><h4>Command 11:</h4><pre>screen -S log</pre><h4>Command 12:</h4><pre>docker compose up --build</pre><p>Command 12.1:</p><p>If an error related to the network appears after entering the previous command, re-enter the command:</p><pre>export CONDUIT_NETWORK=zora-mainnet-0</pre><p>and then repeat Command 12.</p><h4>Command 13:</h4><p>Now, we need to wait a few minutes for the setup to complete. Once we see logs running, it means the node has been installed correctly. To exit to the main section, use the key combination CTRL+A+D. To check the node’s operation in the future, use the command:</p><pre>screen -r</pre><p>Congratulations! The node is installed and operational!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6af371575c7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node installation guide for Fuel Network]]></title>
            <link>https://medium.com/@lindsaycabrera1903/node-istallation-guide-for-fuel-network-45c099896e81?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/45c099896e81</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Wed, 10 Jul 2024 15:16:02 GMT</pubDate>
            <atom:updated>2024-07-10T15:28:50.493Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quick guide for Fuel Node installation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6KLUWHJ0fdLwyTwf2jSN3A.jpeg" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@bobbiharper1951/airdrop-hunters-guide-to-fuel-network-7a51a8203e54">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><h4>Server Requirements!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*8QB82hSUI5bMcTK1.png" /></figure><h4>Download the <a href="https://mobaxterm.mobatek.net/">MobaxTerm</a> Terminal!</h4><p>Connect to the server and start setting up the node!</p><p>Enter the following commands one by one:</p><pre>sudo apt update <br>sudo apt upgrade -y <br>sudo apt install -y curl git jq lz4 build-essential <br>sudo apt install -y unzip logrotate git jq sed wget curl coreutils systemd<br>sudo apt install screen -y<br>sudo apt install git -y</pre><h4>Proceed to install the node:</h4><pre>curl https://install.fuel.network | sh<br>export PATH=&quot;${HOME}/.fuelup/bin:${PATH}&quot;</pre><h4>Generate P2P keys:</h4><pre>fuel-core-keygen new --key-type peering</pre><p>Example:</p><pre>{<br> &quot;peer_id&quot;:&quot;16Uiu2HAmEtVt2nZjzpXcAH7dkPcFDiL3z7haj6x78Tj659Ri8nrs&quot;,<br> &quot;secret&quot;:&quot;b0ab3227974e06d236d265bd1077bb0522d38ead16c4326a5dff2f30edf88496&quot;,<br> &quot;type&quot;:&quot;peering&quot;<br>}</pre><p>Make sure to save these!</p><h4>Chain Configuration:</h4><pre>git clone https://github.com/FuelLabs/chain-configuration</pre><h4>Open a screen session:</h4><pre>screen -S fuel</pre><h4>Create Sepolia RPC here: <a href="https://dashboard.alchemy.com/apps/8ev7y59i0g7xhmfx/networks">Alchemy</a></h4><h4>Start the local node:</h4><ul><li>--keypair: your generated key &quot;secret&quot;</li><li>--relayer: your Sepolia RPC</li></ul><p>Insert the example below where indicated:</p><pre>fuel-core run \<br>--service-name=Fueltest \<br>--keypair b9393ca52a12346d7315604de91e9d783798388b435f07a3b12134 \<br>--relayer https://eth-sepolia.g.alchemy.com/v2/0BY53bu3DSmCR8xN5MaLC_ke \<br>--ip=0.0.0.0 --port=4000 --peering-port=30333 \<br>--db-path=~/.fuel-sepolia-testnet \<br>--snapshot /root/chain-configuration/ignition \<br>--utxo-validation --poa-instant false --enable-p2p \<br>--reserved-nodes /dns4/p2p-testnet.fuel.network/tcp/30333/p2p/16Uiu2HAmDxoChB7AheKNvCVpD4PHJwuDGn8rifMBEHmEynGHvHrf \<br>--sync-header-batch-size 100 \<br>--enable-relayer \<br>--relayer-v2-listening-contracts=0x01855B78C1f8868DE70e84507ec735983bf262dA \<br>--relayer-da-deploy-height=5827607 \<br>--relayer-log-page-size=500 \<br>--sync-block-stream-buffer-size 30</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dGDZxZmsteJ_ZPDr.png" /></figure><p>Done, the node is running!</p><h4>Auxiliary Commands:</h4><ul><li>Detach the screen: CTRL +A +D</li><li>Check logs: screen -r fuel</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45c099896e81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node Installation Guide for Nubit]]></title>
            <link>https://medium.com/@lindsaycabrera1903/node-installation-guide-for-nubit-1abf34a5e154?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/1abf34a5e154</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Mon, 08 Jul 2024 13:44:17 GMT</pubDate>
            <atom:updated>2024-07-13T12:24:25.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIgKiFogjAZQvO9HOtQT6A.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@stevenchisholm1973/comprehensive-guide-to-nubit-c5330f8b41da">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><h4>1. Node Requirements</h4><p>Recommended server configuration from the developers:</p><ul><li><strong>CPU</strong>: 1</li><li><strong>RAM</strong>: 500 MB</li><li><strong>Storage</strong>: 40 GB</li></ul><p>Ports:</p><ul><li><strong>26657–26659</strong></li></ul><h4>2. Node Installation</h4><p>For our community users, a one-liner script was created to install the node:</p><pre>. &lt;(wget -qO- https://raw.githubusercontent.com/g7AzaZLO/nubit_auto_installer/main/nubit_auto_installer.sh)</pre><p>After executing the command, wait until you see logs similar to these:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zFzlkQLizu5Pqr8mLCV3WQ.png" /></figure><p>This means the node is installed and everything is working.</p><p>Next, reconnect to the server and download the menu script:</p><pre>wget https://raw.githubusercontent.com/g7AzaZLO/nubit_auto_installer/main/nubit_menu.sh</pre><p>Then, you need to grant execution rights to the script:</p><pre>chmod +x nubit_menu.sh</pre><p>Run the menu script:</p><pre>./nubit_menu.sh</pre><p>It will display the container ID and ask you to enter it. Simply highlight the container_id and right-click to paste it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*JaBWX9uAUYAVFHZ2AHOE1A.png" /></figure><p>Next, you will be asked which menu item you want to choose:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*8a-wm0gzkzLVHnvyqs_ijQ.png" /></figure><ol><li>Check node statistics (whether it’s working)</li><li>Display address and public key</li><li>Display mnemonic</li><li>Delete node</li><li>Check logs</li><li>Exit</li></ol><p>Select options 2 and 3 and record the information for your node. Do not lose it! Afterwards, you can check the status in option 1 and logs in option 5.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1abf34a5e154" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Allora Node Deployment Guide]]></title>
            <link>https://medium.com/@lindsaycabrera1903/allora-node-deployment-guide-22af0a7bcfe3?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/22af0a7bcfe3</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 13:50:44 GMT</pubDate>
            <atom:updated>2024-07-23T11:20:44.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*Bp08yfO2BMwKDXxWR_LKww.jpeg" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@williamforker1942/ultimate-guide-to-allora-airdrop-25a6a18bad30">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><p>In the rapidly evolving world of AI and blockchain technologies, Allora emerges as a revolutionary force, bridging decentralized AI and machine learning. This guide will help you deploy Allora validator nodes, enabling you to contribute to this innovative network and harness its potential.</p><h3>Overview of Allora</h3><p>Allora is a decentralized AI network supported by investors like Polychain, Framework, Blockchain Capital, and CoinFund. It combines cutting-edge mechanisms such as peer prediction, federated learning, and zkML, creating a reliable platform for developers and model creators.</p><h3>Requirements</h3><p>To launch a node, ensure your server meets the following requirements:</p><ul><li><strong>Memory</strong>: 16 GB</li><li><strong>CPU</strong>: 6 cores</li><li><strong>Disk</strong>: 512 GB or more</li><li><strong>Open TCP Ports</strong>: 26656, 26657</li></ul><h3>Simplifying Allora Node Installation</h3><h3>Update System Packages</h3><pre>apt update &amp;&amp; sudo apt upgrade -y</pre><h3>Install Git</h3><pre>apt install git -y</pre><h3>Install Ansible</h3><pre>apt remove ansible -y<br>apt-get install -y software-properties-common<br>apt-add-repository --yes --update ppa:ansible/ansible<br>apt install ansible</pre><h3>Check Ansible Version</h3><pre>ansible --version</pre><p>You need Ansible version 2.15 or higher.</p><h3>Project Download</h3><p>Start by cloning the project repository to access the Ansible playbook and all necessary files. Execute the following commands:</p><pre>git clone https://github.com/nodemasterpro/deploy-node-allora.git<br>cd deploy-node-allora</pre><h3>Installing Allora Validator Node</h3><p>Once all project files are ready, start the Allora node installation with this command:</p><pre>ansible-playbook install_validator_node_allora.yml -e moniker=&quot;your_moniker_name&quot;</pre><p>Replace “your_moniker_name” with a unique name for your node.</p><h3>Log Monitoring</h3><p>After deploying and starting your Allora validator node, it’s important to monitor its activity. Use the following command to display the node logs:</p><pre>journalctl -u allora-node -f -o cat</pre><p>To exit the logs, press Ctrl+C.</p><h3>Creating an Allora Wallet</h3><p>After installing the Allora node, create an Allora wallet. This component is necessary for participating in the network validation process:</p><pre>ansible-playbook create_wallet_allora.yml -e wallet_name=&quot;your_wallet_name&quot;</pre><p>Upon completion, you can find wallet information, including the private key, seed phrase, and hex address, in the file “/root/.allorad/wallets/&lt;your_wallet_name&gt;.info”. Save this information as it will be useful for subsequent steps.</p><h3>Requesting Funds for Allora Test Network</h3><p>Get funds for your wallet via the <a href="https://faucet.testnet.allora.network/">Allora faucet</a>.</p><p>You will receive 1,000,000,000 uallo. Request at least 2,000,000,000 uallo (twice) for staking and paying fees.</p><p>You can check your wallet balance with the following command:</p><pre>allorad query bank balances &lt;your_wallet_address&gt;</pre><h3>Checking Node Synchronization</h3><p>Ensure your node is fully synchronized with the Allora blockchain:</p><pre>allorad status | jq .sync_info</pre><p>Wait until the catching_up variable becomes false. The synchronization time is approximately 10 minutes. Once catching_up becomes false, your node will be fully synchronized and ready for further operations.</p><h3>Creating a Validator and Linking it to the Allora Wallet</h3><p>To perform this step, your node must be synchronized with the blockchain, and you must have 2 allo (+ gas fees) for staking, which can be obtained through two requests to the Allora faucet:</p><pre>ansible-playbook register_validator_node_allora.yml</pre><p>During this process, you will need to enter two values:</p><ul><li><strong>wallet_name</strong>: Your wallet name.</li><li><strong>moniker</strong>: Your node name.</li></ul><p>Upon completion, you will receive your validator node address. You can also obtain it with the following command:</p><pre>allorad keys show &lt;your_wallet_name&gt; -a --bech val --keyring-backend test</pre><p>You can check the status of your node with the following command:</p><pre>allorad query staking validator &lt;validator_address&gt;</pre><p>To delegate tokens to your node, use the following command:</p><pre>allorad tx staking delegate $(allorad keys show &lt;your_wallet_name&gt; --bech val -a --keyring-backend test) 1000000000uallo --from &lt;your_wallet_name&gt; --gas=auto --gas-adjustment=1.4 --keyring-backend test -y</pre><p>You can view detailed information about your node using your wallet address in the <a href="https://explorer.testnet.allora.network/">Allora explorer</a>.</p><h3>Congratulations!</h3><p>Your Allora validator node is now operational.</p><h3>Additional Information</h3><h3>Stopping the Service</h3><p>To stop the Allora validator node, execute the following command:</p><pre>systemctl stop allora-node</pre><h3>Starting the Service</h3><p>To start the Allora validator node, execute the following command:</p><pre>systemctl start allora-node</pre><h3>Removing the Node</h3><p>To remove the Allora validator node, execute the following playbook:</p><pre>ansible-playbook remove_validator_node_allora.yml</pre><p>Ensure you save all important data before removing the Allora node, as this action may delete node data.</p><p>By following this guide, you have successfully deployed and managed an Allora validator node, contributing to the network’s reliability and potentially earning rewards. Join the Allora community on <a href="https://discord.com/invite/allora">Discord</a> and <a href="https://x.com/AlloraNetwork">Twitter</a> to stay updated on project news.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22af0a7bcfe3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installation of the WARDEN Node detailed guide]]></title>
            <link>https://medium.com/@lindsaycabrera1903/installation-of-the-warden-node-detailed-guide-43258befcce0?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/43258befcce0</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 11:49:43 GMT</pubDate>
            <atom:updated>2024-07-12T12:55:16.017Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/431/1*BpSh8Fpgdw-9_Dh5keeLEQ.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@amandaeckert1919/comprehensive-guide-to-warden-protocol-e11c8f72743a">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><p>Warden Protocol is a beast created on the basis of the Cosmos SDK, which provides various execution layers to ensure compatibility, modular key management (such as tools for choosing MPS and HSM operators), and account aggregation.</p><h3>Minimum Server Requirements</h3><ul><li>32GB RAM</li><li>300GB of disk space</li><li>8 Cores CPU</li></ul><p>A brief guide on renting a server can be viewed <a href="#">here</a>. How to install multiple nodes on one server can be read <a href="#">here</a>. Detailed instructions on setting up Cosmos nodes can be found <a href="#">here</a>.</p><p>If you choose a server on Hetzner, you can use our referral link, and we will be grateful.</p><h3>Step-by-Step Installation</h3><p><strong>Update Your Server</strong></p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y</pre><p><strong>Install Additional Packages</strong></p><pre>sudo apt install make clang git pkg-config libssl-dev build-essential git gcc chrony curl jq ncdu bsdmainutils htop net-tools lsof fail2ban wget -y</pre><p><strong>Install Go and Check Version</strong></p><pre>ver=&quot;1.20.5&quot; &amp;&amp; \<br>wget &quot;https://golang.org/dl/go$ver.linux-amd64.tar.gz&quot; &amp;&amp; \<br>sudo rm -rf /usr/local/go &amp;&amp; \<br>sudo tar -C /usr/local -xzf &quot;go$ver.linux-amd64.tar.gz&quot; &amp;&amp; \<br>rm &quot;go$ver.linux-amd64.tar.gz&quot; &amp;&amp; \<br>echo &quot;export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin&quot; &gt;&gt; $HOME/.bash_profile &amp;&amp; \<br>source $HOME/.bash_profile &amp;&amp; \<br>go version</pre><p><strong>Download the Project Folder and Build the Binary</strong></p><pre>cd $HOME <br>rm -rf wardenprotocol<br>git clone --depth 1 --branch v0.1.0 https://github.com/warden-protocol/wardenprotocol/<br>cd wardenprotocol/warden/cmd/wardend<br>go build</pre><p><strong>Move the Binary</strong></p><pre>sudo mv wardend /usr/local/bin/</pre><p><strong>Set Variables (Leave CHAIN unchanged, replace others with your data)</strong></p><pre>WARDEN_CHAIN=&quot;alfama&quot;<br>WARDEN_MONIKER=&quot;your_name&quot;<br>WARDEN_WALLET=&quot;your_name&quot;</pre><p><strong>Add Variables to Bash Profile</strong></p><pre>echo &#39;export WARDEN_CHAIN=&#39;${WARDEN_CHAIN} &gt;&gt; $HOME/.bash_profile<br>echo &#39;export WARDEN_MONIKER=&#39;${WARDEN_MONIKER} &gt;&gt; $HOME/.bash_profile<br>echo &#39;export WARDEN_WALLET=&#39;${WARDEN_WALLET} &gt;&gt; $HOME/.bash_profile<br>source $HOME/.bash_profile</pre><p><strong>Initialize the Node</strong></p><pre>wardend init &lt;your_moniker&gt; --chain-id alfama</pre><p><strong>Download the Genesis File</strong></p><pre>cd $HOME/.warden/config<br>rm genesis.json<br>wget https://raw.githubusercontent.com/warden-protocol/networks/main/testnet-alfama/genesis.json</pre><p><strong>Configure Pruning (optional)</strong></p><pre>pruning=&quot;custom&quot;<br>pruning_keep_recent=&quot;1000&quot;<br>pruning_interval=&quot;10&quot;<br>sed -i -e &quot;s/^pruning *=.*/pruning = \&quot;$pruning\&quot;/&quot; $HOME/.warden/config/app.toml<br>sed -i -e &quot;s/^pruning-keep-recent *=.*/pruning-keep-recent = \&quot;$pruning_keep_recent\&quot;/&quot; $HOME/.warden/config/app.toml<br>sed -i -e &quot;s/^pruning-interval *=.*/pruning-interval = \&quot;$pruning_interval\&quot;/&quot; $HOME/.warden/config/app.toml</pre><p><strong>Set Minimum Gas Price</strong></p><pre>sed -i &#39;s/minimum-gas-prices = &quot;&quot;/minimum-gas-prices = &quot;0.0025uward&quot;/&#39; $HOME/.warden/config/app.toml</pre><p><strong>Add Peers</strong></p><pre>sed -i &#39;s/persistent_peers = &quot;&quot;/persistent_peers = &quot;2fa750223e22cc19a96391be254680e76387039c@174.138.6.105:26656,12caf2f5e3618cb6c57f45e93ac713b2bc6243b1@164.90.205.67:26656,b9c77f2a0b725fb9b48b50e5ec50d100c58514af@165.232.87.163:26656&quot;/&#39; $HOME/.warden/config/config.toml</pre><p><strong>Create Service File</strong></p><pre>tee /etc/systemd/system/wardend.service &gt; /dev/null &lt;&lt;EOF<br>[Unit]<br>Description=wardend<br>After=network-online.target<br>[Service]<br>User=$USER<br>ExecStart=$(which wardend) start<br>Restart=on-failure<br>RestartSec=3<br>LimitNOFILE=65535<br>[Install]<br>WantedBy=multi-user.target<br>EOF</pre><p><strong>Start the Service</strong></p><pre>systemctl daemon-reload<br>systemctl enable wardend<br>systemctl restart wardend</pre><p><strong>Check Logs and Wait for Node Synchronization</strong></p><pre>journalctl -u wardend -f -o cat</pre><p><strong>Check Synchronization Status</strong></p><pre>curl localhost:26657/status</pre><p><strong>Update Binary at Block 386352 to Version 0.2.0</strong></p><pre>cd $HOME <br>rm -rf wardenprotocol<br>git clone --depth 1 --branch v0.2.0 https://github.com/warden-protocol/wardenprotocol/<br>cd wardenprotocol/warden/cmd/wardend<br>go build<br>sudo mv wardend /usr/local/bin/<br>systemctl restart wardend</pre><p><strong>Alternatively, Install Version 0.2.0 Initially and Use Official State Sync</strong></p><pre>systemctl stop wardend<br>wardend tendermint unsafe-reset-all --home $HOME/.warden --keep-addr-book</pre><p><strong>Set Variables for State Sync</strong></p><pre>export SNAP_RPC_SERVERS=&quot;https://rpc.sentry-1.alfama.wardenprotocol.org:443,https://rpc.sentry-2.alfama.wardenprotocol.org:443,https://rpc.sentry-3.alfama.wardenprotocol.org:443&quot;<br>export LATEST_HEIGHT=$(curl -s &quot;https://rpc.alfama.wardenprotocol.org/block&quot; | jq -r .result.block.header.height)<br>export BLOCK_HEIGHT=$((LATEST_HEIGHT - 2000))<br>export TRUST_HASH=$(curl -s &quot;https://rpc.alfama.wardenprotocol.org/block?height=$BLOCK_HEIGHT&quot; | jq -r .result.block_id.hash)</pre><p><strong>Verify Output</strong></p><pre>echo $LATEST_HEIGHT $BLOCK_HEIGHT $TRUST_HASH</pre><p><strong>Update Config.toml if Everything is Correct</strong></p><pre>sed -i.bak -E &quot;s|^(enable[[:space:]]+=[[:space:]]+).*$|\1true| ; \<br>s|^(rpc_servers[[:space:]]+=[[:space:]]+).*$|\1\&quot;$SNAP_RPC_SERVERS\&quot;| ; \<br>s|^(trust_height[[:space:]]+=[[:space:]]+).*$|\1$BLOCK_HEIGHT| ; \<br>s|^(trust_hash[[:space:]]+=[[:space:]]+).*$|\1\&quot;$TRUST_HASH\&quot;|&quot; $HOME/.warden/config/config.toml</pre><p><strong>Restart Node and Check Logs</strong></p><pre>systemctl restart wardend &amp;&amp; journalctl -fu wardend -o cat</pre><p><strong>After Synchronization, Create a Wallet (Don’t Forget to Save the Mnemonic)</strong></p><pre>wardend keys add $WARDEN_WALLET</pre><p><strong>Recover Wallet Using Mnemonic (If Wallet Already Exists)</strong></p><pre>wardend keys add $WARDEN_WALLET --recover</pre><p><strong>Add Wallet Address Variable</strong></p><pre>WARDEN_ADDR=$(wardend keys show $WARDEN_WALLET -a)<br>echo &#39;export WARDEN_ADDR=&#39;${WARDEN_ADDR} &gt;&gt; $HOME/.bash_profile<br>source $HOME/.bash_profile</pre><p><strong>Get Funds to Wallet. Add Wallet to Keplr, Connect and Request Tokens.</strong></p><pre>wardend query bank balances $WARDEN_ADDR</pre><p><strong>Create Validator (Specify Amount Slightly Less Than Wallet Balance to Cover Fees)</strong></p><pre>wardend comet show-validator</pre><p><strong>Create Validator.json File</strong></p><pre>nano $HOME/.warden/validator.json</pre><p>Insert the following configuration and replace values with your own:</p><pre>{<br>    &quot;pubkey&quot;: &quot;&lt;output from command above&gt;&quot;,<br>    &quot;amount&quot;: &quot;1000000uward&quot;,<br>    &quot;moniker&quot;: &quot;your-node-moniker&quot;,<br>    &quot;identity&quot;: &quot;eqlab testnet validator&quot;,<br>    &quot;website&quot;: &quot;optional website for your validator&quot;,<br>    &quot;security&quot;: &quot;optional security contact for your validator&quot;,<br>    &quot;details&quot;: &quot;optional details for your validator&quot;,<br>    &quot;commission-rate&quot;: &quot;0.1&quot;,<br>    &quot;commission-max-rate&quot;: &quot;0.2&quot;,<br>    &quot;commission-max-change-rate&quot;: &quot;0.01&quot;,<br>    &quot;min-self-delegation&quot;: &quot;1&quot;<br>}</pre><p><strong>Create Validator</strong></p><pre>wardend tx staking create-validator $HOME/.warden/validator.json \<br>   --from=&lt;key-name&gt; \<br>   --chain-id=alfama \<br>   --fees=500uward</pre><p><strong>Set Validator Address Variable</strong></p><pre>WARDEN_VALOPER=$(wardend keys show $WARDEN_WALLET --bech val -a)<br>echo &#39;export WARDEN_VALOPER=&#39;${WARDEN_VALOPER} &gt;&gt; $HOME/.bash_profile<br>source $HOME/.bash_profile</pre><p><strong>Check Validator Status</strong></p><pre>wardend query staking validator $WARDEN_VALOPER</pre><p><strong>Delegate Funds from Wallet to Validator (Specify Your Amount)</strong></p><pre>wardend tx staking delegate $WARDEN_VALOPER 1000000uward --from $WARDEN_WALLET --fees=500uward</pre><p><strong>If Your Node Gets Jailed, Unjail It</strong></p><pre>wardend tx slashing unjail --from $WARDEN_WALLET --fees=500uward</pre><p>Thank you very much for your attention and time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43258befcce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installation of a Puffer Node detailed guide]]></title>
            <link>https://medium.com/@lindsaycabrera1903/installation-of-a-puffer-node-detailed-guide-ec006e0913b7?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec006e0913b7</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 11:24:44 GMT</pubDate>
            <atom:updated>2024-07-12T17:40:06.543Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quick Guide for Node Installation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jBu5VPKXk_NhtkVAJ8VKhw.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@wilsonjagger1949/comprehensive-guide-to-puffer-d2f70716821c">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><p><strong>Requirements:</strong></p><ul><li>At least 3 ETH in the Holesky network. Tokens can be mined in about 30 minutes here: <a href="https://holesky-faucet.pk910.de/">Holesky Faucet</a>.</li><li>Hardware requirements: 6–16–400.</li><li>System requirements: Ubuntu 20 or Ubuntu 22.</li><li>A white IPv4 address is also needed (usually provided with VPS servers rented from data centers).</li></ul><h4>Server Rental:</h4><ol><li><strong>Hetzner Hosting:</strong> A good hosting option for renting VPS servers, balancing price and quality, suitable for most nodes.</li><li><strong>Mevspace:</strong> An alternative that accepts crypto payments.</li></ol><h4>Server Preparation</h4><p><strong>Update the system:</strong></p><pre>sudo apt-get update -y &amp;&amp; sudo apt upgrade -y</pre><p><strong>Configure time settings:</strong></p><pre>sudo apt -y install chrony<br>sudo systemctl restart chrony &amp;&amp; sudo systemctl enable chrony<br>sudo timedatectl set-timezone Europe/Moscow</pre><p><strong>Install necessary packages:</strong></p><pre>sudo apt-get install git curl ccze jq build-essential unzip tar mc chrony htop ncdu nload screen libc6-dev libc6 libsnappy-dev pkg-config libssl-dev git-lfs -y</pre><p><strong>Install Rust:</strong></p><pre>curl https://sh.rustup.rs -sSf | sh -s -- -y<br>source &quot;$HOME/.cargo/env&quot; &amp;&amp; \<br>echo -e &quot;\n$(cargo --version).\n&quot;</pre><p><strong>Open the required ports in the firewall:</strong></p><pre>sudo ufw allow 22/tcp comment &#39;Allow SSH port&#39;<br>sudo ufw allow 30303 comment &#39;Allow execution client port&#39;<br>sudo ufw allow 9000 comment &#39;Allow consensus client port&#39;</pre><h4>Execution Client Installation (Nethermind)</h4><p><strong>Generate JWT secret:</strong></p><pre>sudo mkdir -p /secrets<br>openssl rand -hex 32 | tr -d &quot;\n&quot; | sudo tee /secrets/jwtsecret<br>sudo chmod 644 /secrets/jwtsecret</pre><p><strong>Create a directory for the database:</strong></p><pre>sudo mkdir -p /var/lib/nethermind</pre><p><strong>Install packages for Nethermind:</strong></p><pre>wget https://packages.microsoft.com/config/ubuntu/$(lsb_release -rs)/packages-microsoft-prod.deb -O packages-microsoft-prod.deb &amp;&amp; \<br>sudo dpkg -i packages-microsoft-prod.deb<br>sudo apt-get update &amp;&amp; \<br>sudo apt-get install dotnet-sdk-8.0 dotnet-runtime-8.0 -y</pre><p><strong>Download and move the latest binary version from GitHub:</strong></p><pre>RELEASE_URL=&quot;https://api.github.com/repos/NethermindEth/nethermind/releases/latest&quot; &amp;&amp; \<br>BINARIES_URL=&quot;$(curl -s $RELEASE_URL | jq -r &quot;.assets[] | select(.name) | .browser_download_url&quot; | grep linux-x64)&quot; &amp;&amp; \<br>echo Downloading URL: $BINARIES_URL<br><br>cd $HOME &amp;&amp; \<br>wget -O nethermind.zip $BINARIES_URL &amp;&amp; \<br>unzip -o nethermind.zip -d $HOME/nethermind &amp;&amp; \<br>rm nethermind.zip &amp;&amp; \<br>sudo mv $HOME/nethermind /usr/local/bin/nethermind</pre><p><strong>Create a service file for execution:</strong></p><pre>sudo mcedit /etc/systemd/system/execution.service</pre><p>Add the following content to the file:</p><pre>[Unit]<br>Description=Nethermind Execution Layer Client service for Holesky<br>Wants=network-online.target<br>After=network-online.target<br>Documentation=https://www.coincashew.com<br><br>[Service]<br>Type=simple<br>User=root<br>Group=root<br>Restart=on-failure<br>RestartSec=3<br>KillSignal=SIGINT<br>TimeoutStopSec=900<br>WorkingDirectory=/var/lib/nethermind<br>Environment=&quot;DOTNET_BUNDLE_EXTRACT_BASE_DIR=/var/lib/nethermind&quot;<br>ExecStart=/usr/local/bin/nethermind/nethermind \<br>  --config holesky \<br>  --datadir=&quot;/var/lib/nethermind&quot; \<br>  --Network.DiscoveryPort 30303 \<br>  --Network.P2PPort 30303 \<br>  --Network.MaxActivePeers 50 \<br>  --JsonRpc.Port 8545 \<br>  --JsonRpc.EnginePort 8551 \<br>  --Metrics.Enabled true \<br>  --Metrics.ExposePort 6060 \<br>  --JsonRpc.JwtSecretFile /secrets/jwtsecret<br>  <br>[Install]<br>WantedBy=multi-user.target</pre><p><strong>Start the service:</strong></p><pre>sudo systemctl daemon-reload<br>sudo systemctl enable execution<br>sudo systemctl restart execution</pre><p><strong>Check logs for errors:</strong></p><pre>sudo journalctl -fu execution</pre><h4>Consensus Client Installation (Nimbus)</h4><p><strong>Create a directory for the database:</strong></p><pre>sudo mkdir -p /var/lib/nimbus</pre><p><strong>Find and download the latest version:</strong></p><pre>RELEASE_URL=&quot;https://api.github.com/repos/status-im/nimbus-eth2/releases/latest&quot; &amp;&amp; \<br>BINARIES_URL=&quot;$(curl -s $RELEASE_URL | jq -r &quot;.assets[] | select(.name) | .browser_download_url&quot; | grep _Linux_amd64.*.tar.gz$)&quot; &amp;&amp; \<br>echo Downloading URL: $BINARIES_URL<br><br>cd $HOME &amp;&amp; \<br>wget -O nimbus.tar.gz $BINARIES_URL &amp;&amp; \<br>tar -xzvf nimbus.tar.gz -C $HOME &amp;&amp; \<br>mv nimbus-eth2_Linux_amd64_* nimbus &amp;&amp; \<br>rm nimbus.tar.gz &amp;&amp; \<br>sudo mv nimbus/build/nimbus_beacon_node /usr/local/bin &amp;&amp; rm -r nimbus &amp;&amp; \<br>nimbus_beacon_node --version</pre><p><strong>Sync with a trusted node:</strong></p><pre>sudo /usr/local/bin/nimbus_beacon_node trustedNodeSync --network=holesky --trusted-node-url=https://holesky-checkpoint-sync.stakely.io --data-dir=/var/lib/nimbus --backfill=false</pre><p>Alternative trusted node: <a href="https://holesky-checkpoint-sync.stakely.io/">https://holesky-checkpoint-sync.stakely.io</a></p><p><strong>Create a service file for consensus:</strong></p><pre>sudo mcedit /etc/systemd/system/consensus.service</pre><p>Add the following content to the file:</p><pre>[Unit]<br>Description=Nimbus Consensus Layer Client service for Holesky<br>Wants=network-online.target<br>After=network-online.target<br>Documentation=https://www.coincashew.com<br><br>[Service]<br>Type=simple<br>User=root<br>Group=root<br>Restart=on-failure<br>RestartSec=3<br>KillSignal=SIGINT<br>TimeoutStopSec=900<br>ExecStart=/usr/local/bin/nimbus_beacon_node \<br>  --network=holesky \<br>  --data-dir=/var/lib/nimbus \<br>  --tcp-port=9000 \<br>  --udp-port=9000 \<br>  --max-peers=100 \<br>  --rest-port=5052 \<br>  --enr-auto-update=true \<br>  --web3-url=http://127.0.0.1:8551 \<br>  --rest \<br>  --metrics \<br>  --metrics-port=8008 \<br>  --jwt-secret=&quot;/secrets/jwtsecret&quot; \<br>  --graffiti=&quot;YOUR_MONIKER&quot; \<br>  --suggested-fee-recipient=0x60Ba23_YOUR_EVM_ADDR<br>  <br>[Install]<br>WantedBy=multi-user.target</pre><p><strong>Start the service:</strong></p><pre>sudo systemctl daemon-reload<br>sudo systemctl enable consensus<br>sudo systemctl restart consensus</pre><p><strong>Check logs for errors:</strong></p><pre>sudo journalctl -fu consensus</pre><h4>Puffer Key Generation</h4><p><strong>Create a directory for Puffer:</strong></p><pre>mkdir ~/puffer &amp;&amp; \<br>cd ~/puffer &amp;&amp; \<br>git clone https://github.com/PufferFinance/coral &amp;&amp; \<br>cd coral &amp;&amp; \<br>cargo build --release</pre><p><strong>Create a keystore password:</strong></p><pre>mcedit ~/puffer/password.txt</pre><p><strong>Log in to the portal:</strong> <a href="https://launchpad.puffer.fi/Setup">https://launchpad.puffer.fi/Setup</a></p><p><strong>Copy the long command from the portal and change the values to:</strong></p><pre>cargo run --bin coral-cli validator keygen ... --password-file ~/puffer/password.txt --output-file ~/puffer/registration.json</pre><p>Save the console output and the file ~/puffer/registration.json on your computer.</p><h4>Create Eth Validator Keys</h4><p>(This step might be optional as the Puffer team stakes directly to your validator.)</p><p><strong>Go to the portal:</strong> <a href="https://holesky.launchpad.ethereum.org/en/">https://holesky.launchpad.ethereum.org/en/</a></p><p><strong>Connect your wallet, proceed, select Nethermind and Nimbus clients, specify 1 validator, and your EVM Withdrawal address. Download the CLI app:</strong></p><pre>cd ~/puffer &amp;&amp; wget https://github.com/ethereum/staking-deposit-cli/releases/download/v2.7.0/staking_deposit-cli-fdab65d-linux-amd64.tar.gz &amp;&amp; \<br>tar xvfz staking_deposit-cli* &amp;&amp; rm staking_deposit-cli*.tar.gz &amp;&amp; \<br>cd staking_deposit-cli*</pre><p><strong>Create keys:</strong></p><pre>./deposit new-mnemonic --num_validators 1 --chain holesky --eth1_withdrawal_address 0x04489D1_YOUR_EVM_ADDRESS</pre><p>During key creation, confirm your wallet address, set a keystore password, and save/confirm the new seed phrase. The keys will be saved at /root/puffer/staking_deposit-cli-fdab65d-linux-amd64/validator_keys. Save these keys to your computer.</p><p><strong>Return to the Holesky portal, proceed, and upload the saved </strong><strong>deposit_data-[timestamp].json file. Continue until you deposit 32 ETH to your validator.</strong></p><h4>Add Keys to the Node/Validator Client</h4><p><strong>Stop the services and import keys to the node:</strong></p><pre>sudo systemctl stop consensus.service execution.service</pre><p><strong>Create a directory:</strong></p><pre>mkdir -p ~/puffer/validator_keys</pre><p><strong>Copy the Puffer key to the required format:</strong></p><pre>cp -v ~/puffer/coral/etc/keys/bls_keys/* ~/puffer/validator_keys/keystore.json</pre><p><strong>Load keys to the node:</strong></p><pre>sudo /usr/local/bin/nimbus_beacon_node deposits import --data-dir=/var/lib/nimbus /root/puffer/validator_keys<br>sudo /usr/local/bin/nimbus_beacon_node deposits import --data-dir=/var/lib/nimbus /root/puffer/staking_deposit-cli-*/validator_keys</pre><p><strong>Restart the services and ensure everything is working:</strong></p><pre>sudo systemctl restart consensus.service execution.service</pre><p><strong>Check the log:</strong></p><pre>sudo journalctl -fu consensus.service</pre><h4>Complete Registration on the Puffer Portal</h4><p><strong>No need to wait for full node synchronization, it will sync while you are in the validator queue. Syncing takes 2–5 hours on a good VPS server.</strong></p><p><strong>Return to the page:</strong> <a href="https://launchpad.puffer.fi/Setup">https://launchpad.puffer.fi/Setup</a></p><p><strong>Proceed, buy about 2.2 ETH of Puffer, then 60 tickets. Proceed, upload the </strong><strong>registration.json file saved on your PC, select 60 days, and finish.</strong></p><p><strong>Check validator status on the dashboard:</strong> <a href="https://launchpad.puffer.fi/Dashboard">https://launchpad.puffer.fi/Dashboard</a></p><p><strong>And on the validator portal (click the three dots on the right of the status and click to view validator status).</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vy7gV_zyQmxZbFLEIODLCA.png" /></figure><p><strong>You will see a page similar to this:</strong> [https://holesky.beaconcha.in/validator/0x830dcb2c977c32..................................](<a href="https://holesky.beaconcha.in/validator/0x830dcb2c977c32">https://holesky.beaconcha.in/validator/0x830dcb2c977c32</a>..................................</p><p><strong>Status will be displayed in a few hours or days after creation because your validator hasn’t received the 32 ETH deposit yet. Just wait!</strong></p><p><strong>You can also check the validator status page to see the queue time for becoming a validator. If everything is set up correctly, Puffer key imported, you’ll see the status ‘Active’ within a few days!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGbSNv-YqNValO0PtTx6sw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec006e0913b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Guide How To Install Elixir Node]]></title>
            <link>https://medium.com/@lindsaycabrera1903/full-guide-how-to-install-elixir-node-70411be86fdf?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/70411be86fdf</guid>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Sat, 06 Jul 2024 11:10:29 GMT</pubDate>
            <atom:updated>2024-07-12T17:50:12.185Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fAz8IR_xAlp0G2r0JP2gEA.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@stevenchisholm1973/comprehensive-guide-to-elixir-99a01c490184">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><h3>Minimum System Requirements:</h3><ul><li>2 CPUs</li><li>4 GB RAM</li><li>40 GB SSD</li><li>OS: Ubuntu 20.04</li></ul><h3>Install Required Packages and Update Data:</h3><pre>sudo apt-get update<br>sudo apt-get install \<br> ca-certificates \<br> curl \<br> gnupg \<br> lsb-release</pre><h3>Install Docker:</h3><pre>sudo mkdir -p /etc/apt/keyrings<br>curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg<br>echo \<br> &quot;deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \<br> $(lsb_release -cs) stable&quot; | sudo tee /etc/apt/sources.list.d/docker.list &gt; /dev/null<br>sudo apt-get update<br>sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin</pre><h3>Verify Docker Installation:</h3><pre>sudo docker run hello-world</pre><p>You should see a message:</p><pre>Unable to find image &#39;hello-world:latest&#39; locally<br>latest: Pulling from library/hello-world<br>2db29710123e: Pull complete</pre><h3>Check Running Containers:</h3><pre>docker ps</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*GJbxiLDaT0Wx80jMMu7EzA.png" /></figure><h3>Download Dockerfile:</h3><pre>wget https://files.elixir.finance/Dockerfile</pre><h3>Edit Configuration:</h3><pre>nano Dockerfile</pre><p>The data will be displayed:</p><pre>FROM elixirprotocol/validator: testnet-1<br>ENV ADDRESS=<br>ENV PRIVATE_KEY=<br>ENV VALIDATOR_NAME=</pre><p>Fill in the values after the equal sign without quotes and spaces:</p><ul><li>ENV ADDRESS - Metamask address</li><li>PRIVATE_KEY - Private key (not the seed phrase)</li><li>VALIDATOR_NAME - Validator name</li></ul><p>To exit, press Ctrl + X and then Y.</p><h3>Create Validator Image:</h3><pre>docker build . -f Dockerfile -t elixir-validator</pre><h3>Run the Node:</h3><pre>docker run -it --name ev elixir-validator</pre><h3>View Running Containers:</h3><pre>docker container ls</pre><h3>View Container Logs:</h3><pre>docker container logs &lt;CONTAINER_ID&gt;</pre><p>Replace &lt;CONTAINER_ID&gt; with the container name.</p><h3>Create a Validator:</h3><ol><li>Go to the website — <a href="https://dashboard.elixir.finance/">https://dashboard.elixir.finance</a> and connect your wallet.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bga6UCyk0fcXo-6_J3K9Rg.png" /></figure><ol><li>Claim test ELXR tokens (test Ether is required to claim; you can request it in the channel <a href="https://discord.gg/hAPfBSjkCj">https://discord.gg/hAPfBSjkCj</a>).</li><li>After receiving the ELXR tokens, stake the tokens. Any amount from 100–1000 ELXR will do.</li><li>Then register the validator. You can press the registration button, then enter the wallet address used to run the validator in the previous steps. There might be a delay before the registration button becomes active.</li><li>Once this transaction is confirmed, check the <a href="https://dashboard.elixir.finance/leaderboard">leaderboard</a> to ensure your address is registered.</li><li>Ensure valid orders are being processed by finding your validator on the <a href="https://dashboard.elixir.finance/metrics">metrics page</a>.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70411be86fdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Guide How to Install a Berachain Node]]></title>
            <link>https://medium.com/@lindsaycabrera1903/full-guide-how-to-install-a-berachain-node-97ab1d3fa3ff?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/97ab1d3fa3ff</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Fri, 05 Jul 2024 13:13:40 GMT</pubDate>
            <atom:updated>2024-07-15T13:10:04.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*MTnER9IXgHZgy-cOcj4TBA.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@henrynash1985/comprehensive-guide-to-berachain-5b652f8f5925">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><p>Berachain is a high-performance, EVM-compatible blockchain built on the novel Proof-of-Liquidity consensus mechanism. This innovative approach aligns network incentives, fostering a robust synergy between Berachain validators and the ecosystem of projects. Berachain’s technology is based on Polaris, a high-performance framework for building EVM-compatible chains on the CometBFT consensus engine. For additional information, visit <a href="https://example.com/">Berachain’s website</a>.</p><p>Currently, Berachain is in its testnet phase. Bera Node is a fork of Polaris with additional upgrades. This guide will help you set up a node locally until the official genesis file is publicly available.</p><p>Welcome to Node Science! This guide will help you set up your node without any prior technical knowledge.</p><h3>VPS Configuration</h3><p>To run a node, you’ll need a VPS (Virtual Private Server).</p><p><strong>Minimum prerequisites for a Berachain node:</strong></p><ul><li><strong>OS:</strong> Linux</li><li><strong>CPU Architecture:</strong> amd64 or arm64</li><li><strong>CPU:</strong> 4 cores</li><li><strong>RAM:</strong> 16GB</li><li><strong>Storage:</strong> 500GB</li></ul><p>To connect to your VPS and securely run your node, download and install <a href="https://example.com/">Putty</a>, which enables a secure connection. Enter your IP address and click Open.</p><h3>Node Deployment</h3><p>Copy each command line using (Ctrl+C), and paste it into your terminal by right-clicking your mouse. Execute them sequentially, pressing Enter after each, if required.</p><ol><li>Refresh the local package index:</li></ol><pre>apt-get update &amp;&amp; sudo apt-get upgrade -y</pre><p>Install Git, Make, Screen, and JQ packages:</p><pre>apt-get install git make screen jq -y</pre><p>Download Go programming language version 1.21.4:</p><pre>wget https://golang.org/dl/go1.21.4.linux-amd64.tar.gz</pre><p>Unpack the Go binary archive:</p><pre>tar -C /usr/local -xzf go1.21.4.linux-amd64.tar.gz</pre><p>Add the Go binary directory to your PATH environment variable:</p><pre>export PATH=$PATH:/usr/local/go/bin</pre><p>Verify the Go installation:</p><pre>go version</pre><p>Download and execute the Foundry Paradigm script:</p><pre>curl -L https://foundry.paradigm.xyz | bash</pre><p>Reload the .bashrc configuration file:</p><pre>source /root/.bashrc</pre><p>Install the latest version of Foundry:</p><pre>foundryup</pre><p>Clone the Polaris repository:</p><pre>cd $HOME<br>git clone https://github.com/berachain/polaris</pre><p>Navigate to the Polaris directory and switch to the ‘main’ branch:</p><pre>cd polaris<br>git checkout main</pre><p>Start the node:</p><pre>make start</pre><p>Your terminal will display newly generated wallets associated with your node, and your node ID. Save this information! To stop your node, press CTRL+C. To launch a screen session and keep your node running, type:</p><pre>screen -S bera</pre><p>Then relaunch your node and answer n when prompted to generate a new wallet:</p><pre>make start</pre><p>Congratulations! You’ve deployed your first node on the Berachain. To detach from the screen session while keeping your node running, press CTRL+A+D. You can monitor your node by typing:</p><pre>screen -r bera</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97ab1d3fa3ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Guide to Installing a Farcaster Node]]></title>
            <link>https://medium.com/@lindsaycabrera1903/full-guide-to-installing-a-farcaster-node-02bc517e93a5?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/02bc517e93a5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Wed, 03 Jul 2024 13:13:44 GMT</pubDate>
            <atom:updated>2024-07-23T11:36:04.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*b1hPO4cGWPtOdxUjGklbsg.jpeg" /></figure><p>This guide will walk you through the process of installing a Farcaster node (Hubble) using various methods: script, Docker, and source. Follow the steps below to get your node up and running efficiently.</p><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@dannymikeska2004/ultimate-guide-to-farcaster-airdrop-ead7a90a5f6b">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><h3>Requirements</h3><p>To install and run Hubble, ensure your machine meets the following requirements:</p><ul><li><strong>RAM:</strong> 16 GB</li><li><strong>CPU:</strong> 4 CPU cores or vCPUs</li><li><strong>Storage:</strong> 40 GB of free storage</li><li><strong>Network:</strong> Public IP address with ports 2281–2283 exposed</li><li><strong>RPC Endpoints:</strong> Ethereum and Optimism Mainnet (use services like Alchemy, Infura, or QuickNode)</li></ul><h3>Installation Methods</h3><h3>1. Install via Script</h3><p>The simplest method to set up Hubble is by using the install script.</p><p><strong>Steps:</strong></p><p>Run the install script:</p><pre>curl -sSL https://download.thehubble.xyz/bootstrap.sh | bash</pre><p>Ensure Docker is installed and running if you’re using macOS.</p><p>Hubble will be installed into ~/hubble and will run via Docker in the background, along with Grafana and Prometheus for monitoring.</p><p>If you encounter any issues with the script, try installing via Docker (next section).</p><h3>Upgrading Hubble (Script)</h3><p>Hubble automatically upgrades every week via a crontab entry. To manually upgrade, run:</p><pre>cd ~/hubble &amp;&amp; ./hubble.sh upgrade</pre><h3>2. Install via Docker</h3><p>You can set up Hubble by running the Docker image directly.</p><p><strong>Steps:</strong></p><p>Check out the hub-monorepo locally:</p><pre>git clone https://github.com/farcasterxyz/hub-monorepo.git<br>cd hub-monorepo/apps/hubble</pre><p>Generate your identity key pair:</p><pre>docker compose run hubble yarn identity create</pre><p>Create a .env file in apps/hubble with your Ethereum RPC endpoints:</p><pre># Set this to your L1 Mainnet ETH RPC URL<br>ETH_MAINNET_RPC_URL=your-ETH-mainnet-RPC-URL<br><br># Set this to your L2 Optimism Mainnet RPC URL<br>OPTIMISM_L2_RPC_URL=your-L2-optimism-RPC-URL<br><br># Set this to your Farcaster FID<br>HUB_OPERATOR_FID=your-fid</pre><p>Start Hubble with Docker Compose in detached mode:</p><pre>docker compose up hubble -d</pre><p>To view the status of the sync and Hubble, follow the logs:</p><pre>docker compose logs -f hubble</pre><h3>Upgrading Hubble (Docker)</h3><p>Navigate to apps/hubble in the hub-monorepo and run:</p><pre>git checkout main &amp;&amp; git pull<br>docker compose stop &amp;&amp; docker compose up -d --force-recreate --pull always</pre><h3>3. Install from Source</h3><p>Hubble can also be built and run directly from source without Docker.</p><p><strong>Steps:</strong></p><p>Install dependencies globally on your machine:</p><ul><li>Node.js 18.7+</li><li>Yarn</li><li>Foundry</li><li>Rust</li></ul><p>Clone the repo and build:</p><pre>git clone https://github.com/farcasterxyz/hub-monorepo.git<br>cd hub-monorepo<br>yarn install<br>yarn build<br>yarn test</pre><p>Create an ID and start Hubble:</p><pre>cd apps/hubble<br>yarn identity create<br>yarn start --eth-mainnet-rpc-url &lt;your ETH-mainnet-RPC-URL&gt; --l2-rpc-url &lt;your Optimism-L2-RPC-URL&gt; --hub-operator-fid &lt;your FID&gt;</pre><h3>Upgrading Hubble (Source)</h3><p>To upgrade Hubble, fetch the latest tags, checkout the latest version, and build:</p><pre>git fetch --tags<br>git checkout @farcaster/hubble@latest<br>yarn install &amp;&amp; yarn build</pre><h3>Networks</h3><p>When installing your hub, choose a network to connect to: Mainnet (stable) or Testnet (beta).</p><h3>Testnet</h3><p>Set the following variables in your .env file in apps/hubble:</p><pre>FC_NETWORK_ID=2<br>BOOTSTRAP_NODE=/dns/testnet1.farcaster.xyz/tcp/2282</pre><h3>Mainnet</h3><p>Set the following variables in your .env file in apps/hubble:</p><pre>FC_NETWORK_ID=1<br>BOOTSTRAP_NODE=/dns/nemes.farcaster.xyz/tcp/2282</pre><h3>Monitoring Hubble</h3><p>Hubble ships with a default Grafana configuration for monitoring. Open localhost:3000 in a browser to see your dashboard. For remote servers, set up an SSH tunnel:</p><pre>ssh -L 3000:localhost:3000 xyz@1.1.1.1</pre><h3>Setting Up Monitoring</h3><p>Start Grafana and StatsD:</p><pre>docker compose up statsd grafana</pre><p>Enable monitoring on your Hub by setting this in your .env:</p><pre>STATSD_METRICS_SERVER=statsd:8125</pre><p>Restart your hub and open Grafana at 127.0.0.1:3000. Default username/password: admin/admin.</p><p>Configure Grafana datasource and import the default dashboard.</p><h3>Troubleshooting</h3><h3>Fetch Logs</h3><pre>cd ~/hubble<br>./hubble.sh logs</pre><p>Or use Docker Compose directly:</p><pre>sudo docker compose logs -f hubble</pre><h3>Restart Hubble</h3><pre>cd ~/hubble<br>./hubble.sh down<br>./hubble.sh up</pre><h3>Reset the Database</h3><pre>./hubble.sh down<br>rm -rf .rocks</pre><h3>No Peers or Incoming Gossip Connections</h3><p>Check your firewall and NAT settings. You may need to bootstrap with a non-default peer:</p><pre>BOOTSTRAP_NODE=/dns/hoyt.farcaster.xyz/tcp/2282</pre><h3>Is My Hub in Sync?</h3><p>Use the Grafana dashboard to monitor your hub. The Status tab will show the message sync percent compared to peers. If issues persist, restart the hub or seek help in the Developer Chat or file an issue on the hub repo.</p><h3>Managing Your Peer ID</h3><p>Hubble uses a key pair stored in the .hub directory. The file name contains the public key (Peer ID), while the contents contain the private key.</p><p>This guide provides a comprehensive approach to installing and managing your Farcaster node. For any further assistance or detailed explanations, refer to the official Farcaster documentation and community channels.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02bc517e93a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Detailed Guide to Running a Babylon Node for Beginners]]></title>
            <link>https://medium.com/@lindsaycabrera1903/detailed-guide-to-running-a-babylon-node-for-beginners-ee5e11f01c67?source=rss-fe812e718e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee5e11f01c67</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[HowToNode]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 12:52:48 GMT</pubDate>
            <atom:updated>2024-07-15T12:07:15.247Z</atom:updated>
            <content:encoded><![CDATA[<h4>Step-by-step beginners friendly guide</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*B8MLnkH-MAH4zYw0N7VK0A.png" /></figure><h4>keep in mind: Node running is just one possible criteria for receiving an airdrop, you can also check our <a href="https://medium.com/@cliffordbender1924/comprehensive-guide-to-babylon-testnet-25c81959780c">airdrop guide</a>, it can maximize your chances to get the rewards.</h4><h4>Prerequisites</h4><p>Before you begin, ensure your system meets the following requirements:</p><ul><li><strong>CPU:</strong> 4 vCPU Cores</li><li><strong>RAM:</strong> 8 GB</li><li><strong>Storage:</strong> 50 GB NVMe or 200 GB SSD</li></ul><h3>Step 1: Backup Existing Node Data</h3><p><strong>Update Packages:</strong></p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y<br>sudo apt -qy install curl git jq lz4 build-essential</pre><p>This updates your system and installs necessary tools like curl and git.</p><p><strong>Backup Keys (if you installing node for the first time, skip this step):</strong></p><pre>nano /root/.babylond/config/priv_validator_key.json</pre><p>Open the file containing your node’s private key.</p><p>Copy and save the content in a secure location.</p><h3>Step 2: Install and Setup Babylon Node Chain-test-BBN3</h3><h4>Install Go</h4><ol><li><strong>Download and Install Go:</strong></li></ol><pre>ver=&quot;1.22.0&quot;<br>wget &quot;https://golang.org/dl/go$ver.linux-amd64.tar.gz&quot;<br>sudo rm -rf /usr/local/go<br>sudo tar -C /usr/local -xzf &quot;go$ver.linux-amd64.tar.gz&quot;<br>rm &quot;go$ver.linux-amd64.tar.gz&quot;<br>echo &quot;export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin&quot; &gt;&gt; $HOME/.bash_profile<br>source $HOME/.bash_profile</pre><ul><li>This installs Go, a programming language needed for running the node.</li></ul><h4>Setup Node</h4><p><strong>Set Moniker (Node Name):</strong></p><pre>export MONIKER=&quot;YourNodeName&quot;</pre><p>Replace “YourNodeName” with a unique identifier for your node.</p><ol><li><strong>Remove Old Installation (if applicable):</strong></li></ol><pre>sudo systemctl disable babylon<br>sudo rm /etc/systemd/system/babylon.service<br>sudo systemctl daemon-reload<br>rm -rf $HOME/.babylond<br>rm -rf babylon<br>sudo rm -rf $(which babylond)</pre><p>Clean up any previous Babylon node installations.</p><p><strong>Download and Build Binaries:</strong></p><pre>cd $HOME<br>git clone https://github.com/babylonchain/babylon.git<br>cd babylon<br>git checkout v0.8.3<br>make build</pre><p>Clone the Babylon repository and build the binaries.</p><p><strong>Prepare Directories and Install Cosmovisor:</strong></p><pre>mkdir -p ~/.babylond/cosmovisor/genesis/bin<br>go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@latest<br>mv build/babylond $HOME/.babylond/cosmovisor/genesis/bin/<br>sudo ln -s $HOME/.babylond/cosmovisor/genesis $HOME/.babylond/cosmovisor/current -f<br>sudo ln -s $HOME/.babylond/cosmovisor/current/bin/babylond /usr/local/bin/babylond -f</pre><p>Set up Cosmovisor, a tool for managing Cosmos SDK-based blockchain nodes.</p><p><strong>Initialize the Node:</strong></p><pre>babylond init $MONIKER --chain-id bbn-test-3<br>wget https://github.com/babylonchain/networks/raw/main/bbn-test-3/genesis.tar.bz2<br>tar -xjf genesis.tar.bz2 &amp;&amp; rm genesis.tar.bz2<br>mv genesis.json ~/.babylond/config/genesis.json<br>sed -i -e &#39;s|^seeds *=.*|seeds = &quot;49b4685f16670e784a0fe78f37cd37d56c7aff0e@3.14.89.82:26656,9cb1974618ddd541c9a4f4562b842b96ffaf1446@3.16.63.237:26656&quot;|&#39; $HOME/.babylond/config/config.toml<br>sed -i -e &quot;s|^\(network = \).*|\1\&quot;signet\&quot;|&quot; $HOME/.babylond/config/app.toml<br>sed -i -e &quot;s|^minimum-gas-prices *=.*|minimum-gas-prices = \&quot;0.00001ubbn\&quot;|&quot; $HOME/.babylond/config/app.toml<br>PEERS=&quot;3774fb9996de16c2f2280cb2d938db7af88d50be@162.62.52.147:26656,b82b321380d1d949d1eed6da03696b1b2ef987ba@148.251.176.236:3000&quot;<br>sed -i &#39;s|^persistent_peers *=.*|persistent_peers = &quot;&#39;$PEERS&#39;&quot;|&#39; $HOME/.babylond/config/config.toml</pre><p>Initialize your node with the Babylon network configuration.</p><p><strong>Create and Enable Service:</strong></p><pre>sudo tee /etc/systemd/system/babylond.service &gt; /dev/null &lt;&lt;EOF<br>[Unit]<br>Description=Babylon daemon<br>After=network-online.target<br><br>[Service]<br>User=$USER<br>ExecStart=$(which cosmovisor) run start --x-crisis-skip-assert-invariants<br>Restart=always<br>RestartSec=3<br>LimitNOFILE=infinity<br><br>Environment=&quot;DAEMON_NAME=babylond&quot;<br>Environment=&quot;DAEMON_HOME=${HOME}/.babylond&quot;<br>Environment=&quot;DAEMON_RESTART_AFTER_UPGRADE=true&quot;<br>Environment=&quot;DAEMON_ALLOW_DOWNLOAD_BINARIES=false&quot;<br><br>[Install]<br>WantedBy=multi-user.target<br>EOF<br><br>sudo -S systemctl daemon-reload<br>sudo -S systemctl enable babylond<br>sudo -S systemctl start babylond</pre><p>Set up Babylon node as a system service for easier management.</p><h3>Step 3: Post-Setup Configuration</h3><ol><li><strong>Check Logs:</strong></li></ol><pre>sudo journalctl -u babylond.service -f --no-hostname -o cat</pre><p>Monitor your node’s logs to ensure it’s running correctly. Press Ctrl + C to exit.</p><p><strong>Import or Create Wallet:</strong></p><pre>babylond keys add &quot;wallet&quot; --recover</pre><p>Follow prompts to recover or create a new wallet. Save your recovery phrase securely.</p><p><strong>Get Faucet Tokens:</strong></p><ul><li>Join <a href="https://discord.gg/babylonglobal">Babylon Discord</a> and verify your account.</li><li>In the faucet channel, request tokens using: !faucet bbxxx...xxx.</li></ul><p><strong>Generate BLS Key Pair:</strong></p><pre>babylond create-bls-key $(babylond keys show wallet -a)</pre><p>Generate a BLS key pair for validator setup.</p><p><strong>Create a Validator:</strong></p><pre>sudo tee ~/validator.json &gt; /dev/null &lt;&lt;EOF<br>{<br>&quot;pubkey&quot;: $(babylond tendermint show-validator),<br>&quot;amount&quot;: &quot;1000000ubbn&quot;,<br>&quot;moniker&quot;: &quot;your_moniker&quot;,<br>&quot;website&quot;: &quot;https://yourwebsite.com&quot;,<br>&quot;security&quot;: &quot;contact@gmail.com&quot;,<br>&quot;details&quot;: &quot;description of your validator&quot;,<br>&quot;commission-rate&quot;: &quot;0.10&quot;,<br>&quot;commission-max-rate&quot;: &quot;0.20&quot;,<br>&quot;commission-max-change-rate&quot;: &quot;0.01&quot;,<br>&quot;min-self-delegation&quot;: &quot;1&quot;<br>}<br>EOF</pre><p>Fill in the details with your validator information.</p><p><strong>Check Sync Status:</strong></p><pre>babylond status | jq</pre><p>Verify the node is synced with the network.</p><p><strong>Register Validator:</strong></p><pre>babylond tx checkpointing create-validator ~/validator.json --chain-id=&quot;bbn-test-3&quot; --gas=&quot;auto&quot; --gas-adjustment=&quot;1.5&quot; --gas-prices=&quot;0.025ubbn&quot; --from=wallet</pre><p>Submit your validator registration transaction.</p><p>Follow each step carefully and refer to Babylon’s documentation or community for additional support.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee5e11f01c67" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>