MultiversX Validators Announcements

🎬 Registration has ended. The battle is starting. Hello Nodes team, The form has officially been closed. No more registrations from this point onwards. Nodes registered in the form which are online, running the latest version and unjailed will become validators in the imminent next patch. ⚠️ High TPS starts after the patch. The Purge is coming 👇 🚨 Nodes Jailed on Sunday 23:59 UTC or which unjailed more than 1 time will be removed from the competition and not allowed to continue ⚔️ See you on the battle #fiedl ! 🛡 🌐 Useful links: Start Here | Explorer | Wallet | GitHub | Docs | Issue | Winning | Stake

🔔 Reminder: The Purge is coming Hello Nodes team, A quick reminder that The Purge is coming. After the registration ends in a few hours, a new patch will be released and a high TPS environment will be started. Low performing nodes will have trouble keeping up and will end up being 🔐 Jailed. We will purge low performers so from Monday onwards we start the Battle in earnest. 📋 Participants that register until Saturday 13 June 06:00 UTC will be accepted - small extension as a courtesy to our 🇫🇷 French newcomers, brought in by Hasheur ⏱ New patch & High TPS environment starts Saturday 13 June ~12:00 UTC 🔐 Only 1 unJailing transaction allowed over the weekend 🚨 Nodes Jailed on Sunday 23:59 UTC or which unjailed more than 1 time will be removed from the competition and not allowed to continue 🖥 Stay in the competition by allocating enough resources to your nodes 🚀 Battle of Nodes: Onchained starts in full force with all high-performance nodes on Monday 15 June 📊 Scoring break starts Friday 12 June 23:00 UTC. Scores will uploaded after registration ends 💰 Courtesy rewards to be distributed for online nodes which are purged ⚔️ See you on the battle #fiedl ! 🛡 🌐 Useful links: Start Here | Explorer | Wallet | GitHub | Docs | Issue | Winning | Stake

⚔️ Battle of Nodes: Onchained - Week #1 report • Anti-flood mechanism prevented consensus in high TPS • Redundant validator setup caused double-signing edge-case & fork 🌎 1609 validators & 1838 nodes ⚡️ 13000 max TPS 🛡 3 attacks foiled by the protocol 🆕 6 releases in 7 days 🛠 14 improvements & 16 bug fixes Learning 1: High TPS is not flood Our anti-flood mechanism was configured too tightly and flagged valid consensus messages as spam due to the high TPS environment in a geographically dispersed setting. As a result, we raised the peerMaxMessagesPerSec to 5 in order to avoid the consensus topic being blocked by the topic flood preventer component. Learning 2: Redundant setups can do more harm than good A node operator deployed two nodes with the same key and triggered a specific double-signing scenario that caused a fork. We have addressed this by improving our ForkDetector component. "We are convinced there are many other possible situations that can hinder the proper functioning of a blockchain. As we are deploying the first truly sharded architecture proof of stake architecture, we are the first ever to face certain specific problems, and thus the first to solve them. We are thankful to our community for their valuble contributions, and will remain vigilant for any other issues that might be discovered." Lucian Mincu, Elrond CIO Read the full report: https://medium.com/elrondnetwork/battle-report-7-days-2-major-issues-2-fixes-improved-resilience-7c582aa5ecb0 RT: https://twitter.com/LucianMincu/status/1271438869771292675?s=20

📣 Release v1.0.130 is out Hello Nodes team, This latest patch reduces the effective in-use memory by 600MB by tweaking the default size of the caches and adds a peer info route to provide relevant peer information such as known addresses, hex key or black list status. ⏱ Genesis time: Thursday 11 June 23:00 UTC. 👍 Nodes which prior to this release were online, running the latest version v1.0.129 and not jailed will make it into this patch automatically as Validators. We kindly ask the others to try and keep up - the purge is coming. 🏳️ Cease-fire extended until Monday 15 June - We welcome newcomers until Friday, let's help them settle in first. No attacks please. ⚠️ IMPORTANT: We are grateful for the high number of nodes connected. But not all are running the required system specifications. After the registration ends on Friday, we will run a high TPS environment over the weekend. Low performing nodes will be permanently removed from the competition moving forward. We will keep purging the lower nodes until only worthy nodes are left standing on the battle field. And then we start our countdown. 📊 Scoring resumes as of Thursday 11 June 23:00 UTC, ending the break started on Thursday 11 June 12:30 UTC 🚧 Elrond Infrastructure is undergoing planned maintenance. The explorer, wallet and foundational nodes will be intermittently offline. ⚔️ See you on the battle #fiedl ! 🛡 RT: https://twitter.com/LucianMincu/status/1271204683948924928?s=20 🌐 Useful links: Start Here | Explorer | Wallet | GitHub | Docs | Issue | Winning | Stake | Unjail

🚧 Configurations for this patch need tweaking, reset soon Hello Nodes team, The current patch fixed a lot of things and is super strong, as you can see from the moderate TPS environment we're in at ~2k TPS - yes, we did just call TWO THOUSAND TPS moderate 😎 But some parameters of the patch do not fit our scoring principles. ⏳ For example the 24h epoch means a new joiner will have to wait that long to become a Validator after a staking transaction. 🧂 Some well configured nodes did not automatically become Validators due to minor errors we can help them address 🔥 So we will turn up the TPS heat for the fun of it for a while and then release a new patch to address all of the above 📊 Scoring break from Thursday 11 June 12:30 UTC until the next patch 💥 13k TPS max, check https://explorer.elrond.com ⚔️ See you on the battle #fiedl ! 🛡 🌐 Useful links: Start Here | Explorer | Wallet | GitHub | Docs | Issue | Winning | Stake | Unjail

📣 Release v1.0.129 is out Hello Nodes team, This latest patch makes it so nodes are shuffled around based on a hashing mechanism instead of using a XOR operation, to further increase randomness in all scenarios. Some bugs & fixes are included in the full notes, go check them out. ⏱ Genesis time: Thursday 11 June 12:30 UTC. 👍 Nodes which are registered in the form, online, running the latest version v1.0.128 and not jailed will make it into this patch automatically as Validators. We kindly ask the others to try and keep up - the purge is coming. 🏳️ Cease-fire extended until Monday 15 June - We welcome newcomers until Friday, let's help them settle in first. No attacks please. ⚠️ IMPORTANT - The Purge: We are grateful for the high number of nodes connected. But not all are running the required system specifications. After the registration ends on Friday, we will run a high TPS environment over the weekend. Low performing nodes will be permanently removed from the competition moving forward. We will keep purging the lower nodes until only worthy nodes are left standing on the battle field. 🔒 Jailed - nodes whose rating goes down dramatically due to low performance are Jailed. Ensure enough resources are available for your nodes and check their status on ⚔️ See you on the battle #fiedl ! 🛡 🌐 Useful links: Start Here | Explorer | Wallet | GitHub | Docs | Issue | Winning | Stake | Unjail

🏆 How to win Battle of Nodes: Onchained Hello Nodes team, The increased $60k USD in $ERD prize pool & registration extension were excellent decisions - we see a steady influx of new nodes joining the battle field. A warm welcome to all! 🙏 Here's how you win BoN: Onchained, starting from the biggest rewards: ⚔️ Attacks - steal xERD, mint it out of thin air, make it so other Validators don't get selected for consensus & get all the rewards yourself, stall the network, break consensus & anything else you can think of to break our blockchain. We pay handsomely for any such successful feat. Don't break any laws and don't social engineer participants. Focus on tech. Get in touch with @SeverMM to schedule an attack, lest you overlap with another and can't claim the results. 🚧 Bugs & Issues - test the functionalities of our protocol & tools and submit the issues you find in our Github (link) dedicated templates. Check out the other submissions before - only the first well reported issue of its kind is eligible for rewards. ⏱ Uptime & Performance - have each of your nodes operating on 2CPUs, 4GB RAM, 80GB HDD, 100 Mbps network. Be online 100% of the time, upgrade to the latest version asap and have a good rating. 🎖 Missions - we have a series of educational, challenging & fun missions lined up. Ranging from easy (i.e. set-up Keybase) to medium (i.e deploy and/or interact with a smart contract) to hard (i.e. set up monitoring), they will add to your Uptime score and help you climb the leaderboards. Bonus outside of the prize pool: 🏋️ Community challenges - Elrond supporters are organizing themselves with specific challenges meant at furthering the ecosystem. Sometimes there will be Validator-specific ones that we will share. Do not count for score. There is one ongoing where you can already join to earn some $ERD - join here (link) ⚠️ IMPORTANT: We are grateful for the high number of nodes connected. But not all are running the required system specifications. After the registration ends on Friday, we will run a high TPS environment over the weekend. Low performing nodes will be permanently removed from the competition moving forward. We will keep purging the low performers until only worthy nodes are left standing on the battle field. And then we start our countdown. 👌 A small portion of the rewards will go to purged nodes as appreciation for honoring our invitation. The largest portion of the prize-pool however will go to those who put up the resources and put in the work. 📊 Scoring, rewards & more details are to be announced soon after the registration ends and we are able to compute the formulae based on observed conditions. ⚔️ See you on the battle #fiedl ! 🛡 🌐 Useful links: Explorer | Wallet | GitHub | Docs | Issues

📣 Release v1.0.128 is out Hello Nodes team, This latest patch fixes an edge case where double-signing (two validators running the same key propose a valid block at the same time) happening in a specific interval would cause a fork. Please read the full patch notes for the other fixes and improvements. ⏱ Genesis time: Tuesday 09 June 23:00 UTC. 🚧 We encountered an edge case today related to double signing in between metachain and shard finality attestation. We have found a solution and implemented it. An in-depth post about this topic and how we solved it will be released soon. 👌 Nodes that have been registered in the form and have been online Tuesday 09 June at 19:00 UTC have automatically become Validators. 🙋‍ Registered a node but it's not a validator yet? We're happy to help, ask in the Validators chat. Please provide the node keys you have registered and a wallet address. You will receive xERD for staking and making your node into a Validator. 📊 Scoring for the new participants who joined after Tuesday 09 June 06:00 UTC will be made based on the form registration timestamp, to compensate for the transactions issues. 👉 Please do: check your node's version and make sure to bring it up to date as soon as possible. The default auto-update job included in the setup scripts should save you the trouble. Moving forward, nodes which do not update within an hour of the start of the latest patch will receive a 10% score penalty for the duration of the time they were out of synch with the rest of the network. 📋 Registration is still open. We will help registered nodes to become Validators, ask in the Validators chat 💰 Earn $ERD by reporting valid issues & bugs using this GitHub template. Check the open issues before submitting a new one, only the first claim regarding a valid topic will be eligible for rewards. RT: https://twitter.com/LucianMincu/status/1270469939086974976?s=20 🌐 Useful links: Explorer | Wallet | GitHub | Docs | Submit an issue ⚔️ See you on the battle #fiedl ! 🛡

Battle of Nodes: Onchained Prize Pool Increased to $60.000 Our announcement of the incentivized testnet event has brought 1700 nodes to the network in only 6 days. We are therefore increasing our prize pool to $60k to keep the stakes high throughout the competition. There remains high interest which is yet to materialize into online nodes. As such, we are extending the registration period until Friday 12 June. 🏆 20.000 USD added to the prize pool 📆 Registration open until Friday 12 June 23:59 UTC 🌎 1700 nodes connected to our network 🛡 3 Attacks foiled by our protocol ⚡️ 6.689 peak TPS ✅ 1M transactions in dry-run test 🦾 The latest patch is a Mainnet Release Candidate Read the full announcement: https://medium.com/elrondnetwork/battle-of-nodes-onchained-prize-pool-increased-to-60k-registration-extended-194fa5c95683 RT: https://twitter.com/ElrondNetwork/status/1270269301497438208?s=20 👉 Join the battle at https://battleofnodes.com ⚔️ See you on the battle #fiedl 🛡

📣 Release v1.0.127 is out Hello Nodes team, This latest patch allows nodes to use a defined range of ports used for interacting with the network by changing the Port option the p2p.toml file. The default port range is 37373-38383. Randomly selecting ports at startup created issues for certain setups. This config will now allow predictable operations alongside a tightly configured firewall. The Antiflood component has also been improved to protect the node even under extreme loads. ⏱ Genesis time: 19:00 UTC 👌 Nodes that have been registered in the form and have been online at 15:30 UTC have automatically become Validators 🙋‍ Registered a node but it's not a validator yet? We're happy to help! 👇 • Provide your public node (BLS) key with a request for xERD • Registered BLS keys which are not Validators will get 2.500.100 xERD per node 📊 Active Validators during the Dry-Run have already been accumulating score as a bonus for joining early 📋 Registration is still open. We will help registered nodes to become Validators, ask in the Validators chat ✅ No need to change any firewall configurations 🌐 Useful links: Explorer | Wallet | GitHub | Docs RT: https://twitter.com/LucianMincu/status/1270052473823285248?s=20 ⚔️ See you on the battle #fiedl ! 🛡

📋 Battle of Nodes: Onchained - Newcomer Cheatsheet New? Here's what you need to do to get started: 1️⃣ Join the @BattleOfNodes Telegram announcements channel 2️⃣ Setup a node following the instructions - save the .pem files! 3️⃣ Perform KYC - at least Tier 1, finish Tier 2 now or later to be eligible for rewards 4️⃣ Create separate wallets for each node at https://wallet.elrond.com - never lose the .json files + passphrase / seed! 5️⃣ Register your nodes & wallets in the form 6️⃣ Make an https://Keybase.io account 📁 Create a folder named elrond in “Files > public>(keybasename)” folder 📄 For each node: create a simple file & rename it as the node BLS key - 192 char public key from validatorKey.pem ⤴️ Upload those files to the keybase/public/(keybasename)/elrond folder ✍️ Add this to your ~/elrond-nodes/node-0/config/prefs.toml file for each node:

        # Identity represents the keybase's identity
        Identity = "keybasename"

♻️ Reboot your nodes 7️⃣‍ Ask for xERD in the Validators chat and provide a single erd1... wallet address and public (BLS) keys for your nodes. After receiving the xERD do the stake transaction for each node from each of the associated node reward wallets that you registered before.

📣 Release v1.0.126 is out Hello Nodes team, The latest release adds parallel Smart Contract data tries synchronization to speed up execution, and fixes a bug. 👌 If your node upgraded to v1.0.126, you're ok 🙋‍♂️ New Observer nodes looking to become Validators, ask for xERD in the chat and do a stake transaction 🌎 1348 nodes are connected from 96 cities out of 28 countries 🗓 Registration open until Monday 08 June 08:00 UTC 👉 Please do: Keybase integration for your Validators. Make sure you use unique node names for your nodes. 🌐 Useful links: Registration | Explorer | Wallet | GitHub | Docs ⚔️ See you on the battle #fiedl ! 🛡

📣 Release v1.0.125 is out, Battle of Nodes: Onchained begins! Hello Nodes team, The latest release fixes a bug and adds a few new metrics & API routes, but most importantly, starts the dry run for Battle of Nodes: Onchained. ⏱ Genesis time: 14:00 UTC 👌 Nodes registered in the form by 12:00 UTC, which were online at that time, will become validators with this new patch ⏳ Any node that came online after that time can be made a validator by issuing a staking transaction. Share your erd... addresses for each node in chat with the kind request to get xERD for staking and we will help you. ✅ A Staking transaction tells the network you want to add your node as Validator. Instructions here (link) 👉 Please do: register a Keybase account (link) and brand your node(s) accordingly. 6 nodes per Keybase account is the rule. Teams, remember, you can use the same logo for different teams, and you can call them Team 1, Team 2, etc. Your Keybase identity will be used on the Leaderboards. 📊 Scoring starts now so people who rushed to be on time are rewarded. Coming online after that will be like starting the marathon a few minutes late, score-wise. Not perfect, but you can recover on the way. 🌐 Useful links: Explorer | Wallet | GitHub | Docs ⚔️ See you on the battle #fiedl ! 🛡

Battle of Nodes: Onchained - last preparations Hello Nodes team, First of all, a very warm welcome to our newcomers! We're happy to see so many people joining the most epic event of tech, excitement and mischief that blockchain has to offer. Special thanks 🙏 to all the admins and veterans who helped everyone to settle in. ⏱ The dry run starts Thursday 04 June 14:00 (noon) UTC <- delayed by 2 hours 👉 Please do, if not done already: 1. Perform KYC (link) 2. Install up to 6 nodes - official guide (link) 3. Register your nodes in the form (link) ▶️ As we press play, the following will happen: • a new testnet starts from scratch • all registered nodes become Validators • uptime & performance scoring starts 📆 Registration is open until Monday 08 June 08:00 UTC 🏳️ First we settle in - no attacking until Tuesday 09 June. Drastic score penalty for impatient transgressors. While you wait, you could: 🔰 Brand your validators with Keybase - up 6 nodes per entity. Teams can use groups called Team 1, Team 2, Team 3... etc 🤖 Check out @BoNmonitorBoT - unofficial tool by @drdelphi 📡 Set up some monitoring using one of these amazing unofficial guides: • Icinga2 by @ALwin79 • Zabbix by @josefco_ap with plugin by @ErAsEr21 • vilya by @flyingstone • Telegraf by @ubun3t 🌐 Useful links: Explorer | Wallet | GitHub | Docs ⚔️ See you on the battle #fiedl ! 🛡

📣 Release v1.0.124 is out Hello Nodes team, This release is a hotfix to address some outstanding issues and to add the much needed "jailed" information - soon available in the explorer as well. 💰 Hotfix means state is retained, so the previous rich are still rich. Drop your erd1... wallet address in the chat along with a polite request and you'll get test xERD 🐦 Retweet for awareness: https://twitter.com/LucianMincu/status/1267933796801929216?s=20 ⚔️ See you on the battle #fiedl ! 🛡 Perform KYC | Install up to 6 nodes | Register your nodes

📋 Battle of Nodes: Onchained - Registration Cheatsheet 1. Perform KYC (link) 2. Install up to 6 nodes - official guide (link) 3. Register your nodes in the form (link) 4. Join Announcements & Chat 👇 Important: • Observers: will be converted to Validators with a new patch, no action needed yet • Wallet: each node must have its own wallet, for mission tracking • Form: If you made a mistake, fill it in completely again and we will only consider the latest entry • KYC: If you were in Battle of Nodes before and successfully performed KYC, no need to do it again • Email: use the same one in KYC and the form • Rewards: Both ERC20 & BEP2 addresses are fine, just no exchanges and make sure you own the private keys • Max score: have your nodes ready Thursday 04 June 12:00 UTC • Registration: open until Monday 08 June 10:00 UTC • Leaderboards, Scoring, Prizes & other details will be released soon ⚔️ See you on the battle #fiedl ! 🛡 Perform KYC | Install up to 6 nodes | Register your nodes | Announcements Channel | Validators chat

✅ We are ready. Battle of Nodes: Onchained Starts Thursday 4th of June The Elrond blockchain is ready to launch. We are submitting it for one last public round of testing to showcase its capabilities ahead of minting the 💥 Genesis Block. Battle of Nodes: Onchained will demonstrate Elrond’s readiness to fulfil the internet’s need for a layer of trust which scales with needs & expectations. “Battle of Nodes: Onchained is the final and most important step before the Elrond mainnet. Through it, we will demonstrate a robust and performant network leading to the launch. This is a remarkable milestone, and once 15 days have passed where the network runs without interruptions in a high TPS environment, we will know Elrond is ready to go live.” said Beniamin Mincu, Elrond CEO The final testnet challenge sets the stage for launching our mainnet as a catalyst for adoption exactly now when market sentiment, consumer attention and enterprise appetite are bursting with interest. Read the official announcement: https://medium.com/elrondnetwork/we-are-ready-battle-of-nodes-onchained-starts-thursday-4th-of-june-7765a8f871fe RT: https://twitter.com/ElrondNetwork/status/1267805432493551619?s=20

📣 Release v1.0.123 is out Hello Nodes team, For this latest release, we only included validators which were active and running the latest version of the Elrond software. This was how we used to do things also before the Peer Rating and node shuffling. We decided to go back to this approach due to a (small) number of nodes with issues that were forgotten on auto-pilot and creating irelevant issues. 💰 First 10 validators to post their erd1... addresses will become testnet rich. Please be kind and pass it forward to those asking for xERD, so testing can happen! 🐦 Retweet for awareness: https://twitter.com/LucianMincu/status/1267577851404001282?s=20 ⚔️ See you on the battle #fiedl ! 🛡 Guidelines for Genesis Validators | Staking Calculator | Register a Node | How to setup a node| 👉 Help us test | Submit an issue

📣 Release v1.0.119 v1.0.120 is out Hello Nodes team, This latest release is packed with improvements and bugfixes. The TxPool was rehauled for increased performance, flood protection and correct processing 💰 First 10 validators to post their erd1... addresses will become testnet rich. Please be kind and pass it forward to those asking for xERD, so testing can happen! ⏱ Genesis time 16:00 UTC ⚔️ See you on the battle #fiedl ! 🛡 Guidelines for Genesis Validators | Staking Calculator | Register a Node | How to setup a node| 👉 Help us test | Submit an issue

🌎 The Elrond Validators We’re minting the 💥 Genesis Block in good company. There is nothing left to chance in the imminent $ERD ecosystem launch. Handpicking the starting Validator line-up is a privilege not many projects have. We do have it, and we are grateful for it 🙏 “Our node runners are enthusiasts that not only understand what makes the Elrond blockchain tick but put in the necessary effort of making it do so. They challenge the team with clever questions, raise issues and ask for features.” Lucian Mincu, Elrond CIO We have selected the Validators to mint the genesis block with us. We will use the full extent of our own knowledge, the ideas of our community and the experience of our professional partners to put together the most secure, highly-available, performant and robust network to launch our mainnet on. Find out more about our Validators in our blog post https://medium.com/elrondnetwork/the-elrond-validators-df51f09ec93e?sk=a1de670061409b9aee1cc5bd2c3aa5a7 RT: https://twitter.com/LucianMincu/status/1265228915787927552?s=20