Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. Hi guys, I've written a Medium post about how to secure your VPS (Ubuntu) by: - using SSH keys with Ed25519 encryption - setting a non-default SSH port - setting the firewall so that only outside access through a single SSH port is allowed - disabling root access from the outside - switching to user root with a simple `su -` command, without a password Check it out at: https://medium.com/@haklander/how-to-secure-your-ubuntu-vps-for-running-an-elrond-node-a5e0493646b6
  3. Yesterday
  4. I will give you the details in screenshot
  5. 📊 Leaderboard update Hello Nodes Team, Updated scores for the first 2 days of Round 2 are uploaded. Scores are current as of Friday 18 October 06:59 UTC. We used only uptime information, no earned rewards, for this scoring. 📈 Normal scoring rules were applied to all nodes before the time of the attack, which was estimated to have started Wednesday 16 October 15:00 UTC. 👌 All nodes that were online during the attack & up to the patch v1.0.31 grace period - Friday 18 October 21:00 UTC - will be awarded full score, even if they weren't 100% online during that time. 👍 This is to make sure scoring stays fair and in line with the staged approach of our event: from setting up to all our war. We're still setting up! 👉 Please update to patch v1.0.31 if you haven't already, scoring penalty starts with Friday 18 October 21:00 UTC. ⚔️ See you on the battle #fiedl ! 🛡
  6. Yes, I have gotten it right. I have submitted the my form. Thanks
  7. 📣 Preparing for Phase 1, Round 3 📣 Hello Nodes Team! We had a lot of fun in Round 1, there is incredible excitement in Round 2, and we are looking forward to an even better Round 3! If you are new to Battle of Nodes, welcome, it's still early! Sign up and join the battle for massive fun and epic rewards. If you are already in Round 1 & 2, your existing nodes will be carried over to Round 3. You can add more nodes for Round 3 (up to 6 total) - fill in the form. ⚠️ We're cleaning house: nodes with 0 uptime until the end of Round 2 will not be carried over automatically. If you registered a node but did not operate it yet and you want to do so from now on, register it again in the form. 👉 Please fill in this form by Sunday 20 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 👉 This is the last registration form for Battle of Nodes. If you didn't join yet, now's the last chance to do so! ⚔️ See you on the battle #fiedl 🛡
  8. 📣 Preparing for Phase 1, Round 3 📣 Hello Nodes Team! We had a lot of fun in Round 1, there is incredible excitement in Round 2, and we are looking forward to an even better Round 3! If you are new to Battle of Nodes, welcome, it's still early! Sign up and join the battle for massive fun and epic rewards. If you are already in Round 1 & 2, your existing nodes will be carried over to Round 3. You can add more nodes for Round 3 (up to 6 total) - fill in the form. ⚠️ We're cleaning house: nodes with 0 uptime until the end of Round 2 will not be carried over automatically. If you registered a node but did not operate it yet and you want to do so from now on, register it again in the form. 👉 Please fill in this form by Sunday 20 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 👉 This is the last registration form for Battle of Nodes. If you didn't join yet, now's the last chance to do so! ⚔️ See you on the battle #fiedl 🛡
  9. 🛡 Post-skirmish update 🛡 Hello Nodes Team, After the v1.0.31 patch, the blockchain is synching again! Great job to our developers for solving a number of interesting situations that were unearthed by the attack from two days ago. Look forward to them publishing a series of excellent findings and how they addressed every one of them. 👉 Please remember to upgrade your node to v1.0.31 ⚠️ If you updated but have issues synching, restart your client until it starts synching. Why: if your synch partner is a v1.0.28 node, you will not move on. Restart until you get a v1.0.31 synch partner. This will actually be automated in a future patch! 🧟‍♂️ 37 nodes with v1.0.28 still remain. Come on guys, let's upgrade so we move on to the next battle! 📊 Scoring for Wednesday 16 October will be done as follows: - regular scoring from 07:00 UTC (time of start) until 15:00 UTC (time of attack) - nodes that were online at 15:00 UTC get full score for the next period - nodes that came online after 15:00 UTC get full score starting with their respective online time, but nothing for not being online before ⚔️ See you on the battle #fiedl! 🛡
  10. Last week
  11. 📣 Client version 1.0.31 released We have released a new client version, which fixes the current synch issues. 👉 Please do: Backup your keys, then update your node to the latest version: Linux | Windows | MacOS 👉 Keep the existing databases for faster sync. 🔎 Using scripts? Neat, here are the proper tags: v1.0.31 & BoN-ph1-w2-p1 ⏱ This patch is in effect as of Thursday 17 October 21:00 UTC. Please update before Friday 18 October 20:59 UTC to avoid getting a score penalty. ⚔️ See you on the battle #fiedl ! 🛡
  12. I will give you the details in screenshot
  13. Hey Renars, we're relying on you guys to come up with all the attack vectors we didn't think of or are possible without us knowing. Start reading 🙂 I personally like this one https://arxiv.org/pdf/1904.03487.pdf - very deep start
  14. Collin, how can we help you? Do you have some errors or screenshots of your problem?
  15. Hey VN Beat - your node is registered with us and should be a validator in this round. At the time when you posted this, Round 2 had not started yet, it only began Wednesday 16 October 07:00 UTC. You should see it as validator now.
  16. Hello Nodes Team, 👉 In the aftermath of the first Battle of Nodes attack and subsequent patch to address the exploited issue, the testnet is momentarily unstable. We are currently investigating the situation and will share our findings. ⚠️ Updating to this latest patch is not mandatory. 📊 No penalties to scores. ⏱ We will release another statement in 12 hours - circa 09:00 UTC ⚔️ See you on the battle #fiedl 🛡
  17. Hi Sorin, great question! We will give each individual node a score, every 24 hours. The score is accrued and carried over throughout the event. The node identifier is its block signing public key (the one from initialNodesSk.pem). We don't give out awards per round, only for the final standings. But we are looking into showing performance for each round, this is cool for all to see how we progress and get better each week. Does this answer your question, @Sorin Pop? Stay sharp on the battle #fiedl
  18. 📣 Starting Round 2 of Phase 1 Hello Nodes Team, 🎉 Round 2 of Phase 1 has officially started! 🔎 Monitoring has started Wednesday 16 October 07:00 UTC and will end Sunday 20 October 23:59 UTC. Throughout this period the main goal for node operators will remain to maintain uptime as much as possible. Scoring for this round will also take into account the number of earned rewards! You can maximize uptime & number of earned rewards by maintaining your node online and running the latest version of the client. 🤩 Missions will be launched soon! Sneak peak: they have to do with our wallet, cool times ahead. Some awesome facts: - 982 nodes in the current network (getting close, boyz!) - 36 new people joined for this round - 292 people registered for the event - 316 people in validators chat - block 0 was not proposed by Chuck Norris 📊 Leaderboard will be updated tomorrow, after the first 24 hours period of Round 2 Known issues that we are fixing as we speak: - some online members are displayed offline in the Leaderboard - testnet.elrond.com times out in the Validators section The time is upon us. ⚔️ See you on the battle #fiedl 🛡
  19. Guys I am not familiar with script writing. Will be there some scripts provided for spamming, attacking etc?
  20. Thanks for this explanation! I have no idea how e.g. attack can be executed. Hope we will have some guide or general scripts.
  21. What if we create a pop quiz event similar like binance english's red package distribution? Random question will come out on our telegram channel every one hour and members have to answer it for points.
  22. Yes, unfortunately you've missed the Second registration window and you'll have to wait for the Third, the dates will be announced soon.
  23. Hi, is it too late for a new registration now? I want to join this battle.
  24. If this round another node of mine gets the top score/uptime, will this be added to the top score from previous round or to the exact node's score/uptime? Does an individual node identity matter for overall uptime/score/rewards? Or top score at the end end will be sum of personal top scores so far. Thanks
  25. Great. I also wanted to join for the battle of the node, but my system having issue with the Git.Sereral attends fail and I just to let go.
  26. 📣 Client version 1.0.25 released 📣 We have released a new client version, which fixes minor bugs and has all the needed configs for moving to Round 2 of Phase 1. ⚠️ Everyone needs to update to this one, even if you already updated yesterday 👉 Please do: Backup your keys, set up the latest version of the node, restore keys, start node ▪️ Linux installation guide 🔹 Windows installation guide ▫️ MacOs installation guide 👉 We had to add some missing key files into the genesis file, so a new update is needed, even if you patched yesterday. 🔎 Check your scripts before updating, latest tags are v1.0.25 and BoN-ph1-w2-p1 Remember, official uptime monitoring starts Wednesday 16 October 07:00 UTC, 24 hours from now, be sure to update your nodes before that time. ⚔️ See you on the battle #fiedl ! 🛡
  27. Hi Admin, I had registered this identity in the Battle of Nodes, why my instance type is observer and my node is connected to 0 peers? This is my node, it already, right?
  1. Load more activity
×
×
  • Create New...