MultiversX Validators Announcements

Hello Nodes Team, 📊 Leaderboard for days 3 and 4 of the event have been updated, check it out! ⏱ The displayed scores are current as of Sunday 13 October 07:00 UTC. Changes after that time will be reflected on the next update. 📉 A 10% penalty has been applied for the time a server has been running an outdated version of the client 14 hours after the latest patch. There will be one more update on Monday to also include the score until Sunday 13 October 23:59 UTC, when Round 1 of Phase 1 officially ends. 👌 Fix: An issue with same score standings dynamically updating due to "Online" for the last 24 hours changing has been fixed. Same score nodes are now ordered alphabetically by operator "Nickname" To do: - display the time & date of last update 👉 The leaderboard is not a live action score, it represents the standings at the last calculated interval 👉 Round 2 signup ends in a few hours, add your first node(s) or up to 6 per existing account in this form. ⚔️ See you on the battle #fiedl 🛡

Battle of Nodes Day 3 update Hello Nodes Team, 👌 24 hours after launching the patch, more than 90% of the registered nodes are updated already, good job! 👉 If you didn't update your node yet, please do so, to avoid taking too much penalty. As announced in our scoring philosophy and patch announcement, the 24 hours grace period has ended on Friday 11 October 15:30, after which a 10% scoring penalty is applied for nodes that did not update. 📊 The Leaderboard has been updated with the scores for Day 2. Interesting to see how the top 500 scoring nodes have perfect or close to perfect uptime, which means well prepared programmatic updates! Check out the Validators chat for hints about how to use one as well or even build your own. 👉 Reminder: Leaderboard updates are done once per day and show the status at the end of each Round 1 day, aka at 15:00 UTC. i.e. now you see the status for Friday 11 October 07:00 UTC. That was before the patch, so client Version penalties will be reflected with the next update, 🔎 New Search feature added for our Leaderboard. 🌤 Missions are not ready yet and no new patches are in sight, so we can look forward to a calm weekend. ⚔️ See you on the battle #fiedl 🛡

📣 Preparing for Phase 1, Round 2 📣 Hello Nodes Team! Round 1 has barely started and already a lot of things are happening. Round 2 is coming! If you are already in Round 1 and want to add more nodes, up to 6 per account, you can do so now. If you are new to Battle of Nodes, welcome, it's still early! Please fill in this form by Sunday 13 October 23:59 UTC Newcomers please also go through the KYC process, set up your node(s) and then check out these relevant links: - Dedicated forum - FAQ - Validators Telegram channel - Testnet Explorer ⚔️ See you on the battle #fiedl 🛡

📊 Leaderboard v1.0 is live 📊 🎉 We have released the first official Leaderboard with scoring for Day 1 (Wednesday 09 Oct 07:00 UTC - Thursday 10 Oct 06:59:59 UTC) Features: rank, validator nickcname, node name, shard, key, version indicator, uptime, status and score. Please be aware that currently the info displayed is not live, but based on periodical snapshots taken every few hours. 👉 Because of the synch and client issues, we decided to only give points for the time a node was online. So a lot of perfect scores. 🤝 Why: Nodes with issues we fix via the patch could not validate transactions and receive rewards, thus would have gotten an unfair reduction in rewards. 🧐 Please do: if your Leaderboard uptime does not reflect your actual node’s uptime, get in touch with us. Node downtime due to issues 1. b and 1. c is verifiable, so we could fix your score if you can prove your node was affected by those issues. 🙏 We will announce every decision to adapt our scoring philosophy to unforeseen conditions, so as to be both 100% transparent and at the same time keep things fair by those affected by problems outside of their control. 👨‍💻 In development: search and filter functions, faster updates. ⚔️ See you on the battle #fiedl 🛡

📣 Client version 1.0.24 released 📣 We have released a new client version, which fixes the following bugs: - Bugfixed slow sync - Bugfixed node crash due to a concurrent map write - Bugfixed out of memory due to heartbeat monitor trying to write continuously. Added a batch size of 300 on the storer in config.toml 👉 Please do: Backup your keys, then update your node to the latest version: ▪️ Linux update script location - update.sh : automatically updates an existing node, give the option to keep the database (recommended), does not delete the keys 🔹 Windows update script location - upgrade.bat : automatically updates an existing node, makes backups and restores your keys and database ▫️ MacOS installation guide - no update script yet 😔 Backup your keys, set up a new node as per the guide, restore your keys ⚠️Be aware: as of Thursday 10 October 15:30 UTC, you have 24 hours to update your client. After Friday 11 October 15:31 UTC, nodes with an older node version that 1.0.24 will receive a 10% score reduction. ⚠️ If you experienced issues due to the fixed bugs, your score will not be affected. More on that soon. ⚔️ See you on the battle #fiedl ! 🛡

👋 Hey guys, we know you're super busy so here's a summary of the Telegram chat over the last 24 hours: - 700-ish of nodes joined and are online and kicking. Woooo! - We have synch issues: out of synch nodes take forever to re-synch (downloading the latest version of the database) -> patch is coming today. We tried implementing a community workaround, but it can't be done. We will test, release and announce the patch. Soon(tm) - Please have a sneak preview at leaderboard.elrond.com - a teaser, not official, scoring is not calculated yet, nothing is official, just a look & feel. We only accept look & feel feedback at this time, the included info is not official or accurate. Soon(tm) - There is an unofficial Telegram bot @BoNmonitorBoT 🤖 - @DrDelphi created it. We love it, but it incorrectly tracks "leaderboard" - it is not official nor reporting correct figures. But it is very promising and we encourage its future development! The info it provides is not official! - There is a memory leak issue reported by many users - we're looking into that - @alwin05 has a nice nurse 👩‍⚕️ helping him to recover from his cold - get well soon Alwin! - We have the scoring philosophy published, please read it here - Sign-up form for Round 2 is coming today - new nodes only, so existing nodes don't have to do anything Make sure you join our Battle of Nodes Telegram chat and announcements channels, all hot info is posted and discussed there. ⚔️ See you on the battlefield! 🛡

⚠️ Battle of Nodes important patch arrives soon ⚠️ Hey Nodes Team, Onboarding so many of you is bringing us all the benefits we could have hoped for and more: a lively community, cool new people to exchange ideas with, and exposure of limitations in our current implementation. Here's an important one: 🐌 Issue: An out of synch node can't seem to "catch up" and instead synchronizes indefinitely, thus not validating blocks and earning rewards 👩‍💻 Cause: It was identified it and it will be documented 💊 Fix: We will release a patch in the next 24 hrs 👉 What to do: watch https://t.me/BattleOfNodes for the official announcement of the patch. People affected by this issue will not lose score because of that. We have good ideas about how to compensate, we will communicate on this further. 📣 Rember the scoring rules - there is a 10% score penalty for not updating your client - stay fresh! Thank you for your understanding and patience. See you on the Battlefield!

Battle of Nodes: Scoring & Rewards 🔹Earn rewards for maintaining node(s) and completing missions 🔹Earn special prizes for successful attacks, bug discovery and excellent behavior 🔹Points are awarded for each node daily and added up at the end of the event 🔹Prize pool split between special prizes and uptime rewards 🔹Surprise & secret missions for bonus points 🔹Track your nodes on the leaderboards The $50.000 prize pool will be split into two categories: 🏆 Special Prizes will be awarded for the following categories: ⏱ Uptime - The highest scoring node per account - 7 prizes ⚔️ Attacks - The best executed attacks on the network 🕺 Community - Members that stand out throughout the event 👾 Bugs - The most critical bugs or issues discovered 📊 Leaderboards will track the ranking of nodes based on their added daily score, a sum of: - Rewards - 3 points per earned reward - Online - 1 point per 1 minute spent online - Missions - 1.000 points per mission (variable) - Client version - penalty for not updating Check out the full explanation in this detailed post by our CEO Beniamin Mincu!

The Battle has begun! The Elrond test network is officially online with more nodes than we've seen before. - 721 nodes connected to the network - 693 validators - 2889 transactions processed in 10 minutes - 87 blocks mined Check out the live action on our Validators Page

Kickstarting Phase 1, Round 1 Alright guys, this is happening! The number of community nodes registered for the event is… are you sitting down? 6️⃣8️⃣1️⃣ This is an astonishing number! Your interest in the Elrond network humbles us, thank you! ⚠️ Your action is needed to be able to start in Round 1: backup key files, update nodes, restore key files, start node ⚠️ Backup your keys - this is crypto, keys are important. Locate the files ⚠️initialBalancesSk.pem and initialNodesSk.pem ⚠️ and save them somewhere safe! They are in the config folder next to your node executable. Update & restart your node(s) before ⚠️ Wednesday 09 Oct 06:59 UTC ⚠️ - Use the right tutorial: Linux | Windows | MacOS - Restore key files from backup - Start your node Countdown to Phase 1, Round 1

Battle of Nodes - Phase 1 detailed Schedule ⚠️ The new client release is still pending, we are starting the update period late - 23:59 UTC. We are keeping a +24 hour update period, so the monitoring will start Wednesday 07:00 UTC ⚠️ So, you KYC-ed for the event, set up your node(s) and registered it(them) via the form. Well done! What next? 📣 Join the BoN announcement channel: https://t.me/BattleOfNodes Phase 1, Round 1: 07 - 13 October ✋Sunday, 06 Oct 23:59 UTC: end registration for P1, R1 👨‍💻Monday, 07 Oct 23:59 UTC: update* your node(s) (24h period) 🚀Wednesday, 09 Oct 07:00 UTC: P1, R1starts 🛑Sunday, 13 Oct 23:59 UTC: P1, R1 ends ⏱Uptime monitoring: 08 Oct 12:00 UTC - 13 Oct 23:59 UTC Phase 1, Round 2: 14 - 20 October ✋Sunday, 13 Oct 23:59 UTC: end new** registration for P1, R2 👨‍💻Monday, 14 Oct 12:00 UTC: update* your node(s) (24h period) 🚀Tuesday, 15 Oct 12:00 UTC: P1, R2 starts 🛑Sunday, 20 Oct 23:59 UTC: P1, R2 ends ⏱Uptime monitoring: 15 Oct 12:00 UTC - 20 Oct 23:59 UTC Phase 1, Round 3: 21 - 27 October ✋Sunday, 20 Oct 23:59 UTC: end of new** registration for P1, R3 👨‍💻Monday, 21 Oct 12:00 UTC: update* your node(s) (24h period) 🚀Tuesday, 22 Oct 12:00 UTC: P1, R3 starts 🛑Sunday, 27 Oct 23:59 UTC: P1, R3 ends ⏱Uptime monitoring: 22 Oct 12:00 UTC - 27 Oct 23:59 UTC ✅Sunday, 27 Oct 23:59 UTC: Phase 1 is complete! *We will provide detailed instructions about how to update **For new participants to the event only. Nodes from the previous round will automatically be registered to the next.