Jump to content

Sever Moldovean

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Sever Moldovean

  1. Hey guys, I see some of you are looking at the status of the Genesis Staking contract and have questions about it. The "Contract state: Validating" means your staked ERC20 ERD tokens have been swapped to eGLD on day 1 of the mainnet (30 July, 1 mont ago), and that it is used for "validating" - meaning it is staked on the network for Validators to operate and secure the network. You should be checking your Elrond wallets instead, the erd1... addresses that you have used when staking in the first place. You will find the eGLD rewards accrued before the mainnet launch already unlocked t
  2. I am loving this, Sorin. The "No, Thanks" bit of the mission came from "No, thanks" where the winner is the one with the lowest score. https://boardgamegeek.com/boardgame/12942/no-thanks
  3. If Medium is not the right medium for your Rate My Node article, go ahead and post it here. May the most wicked-sick setup win!
  4. πŸ“£ Official Patch Release and Round 2 of Phase 2 Start Hello Nodes Team, Weekends are great - everyone recognizes your right to be left alone and do the things you love most. Which we embrace fully, so we can focus on our work. We're counting on you guys being normal people, so even if we're launching the patch on a Saturday, we will only start monitoring on Monday. πŸ‘‰ Please do: Backup your keys, delete the old database, set up the latest version of the node, restore keys, start node β–ͺ️ Linux (https://docs.elrond.com/start-a-validator-node/start-the-network/connecting-fro
  5. 🎬 Closing Round 1 of Phase 2 Hello Nodes Team, Round 1 of Phase 2 is now over! It was a very good run, thanks for all your participation. We had the epic 5 Generals mission, our longest round yet, TPS was nice, some new errors were found, fun was had by all. πŸ“Š Monitoring has stopped Friday 22 November 14:00 UTC, exactly 1 week after the start of Round 1. It is now safe to turn off all nodes until Monday (please read below) 🚧 Shard 2 had troubles adding new blocks for the last 14 hours or so. We actually know why for a long time and the development for the improvement is
  6. πŸŽ₯ Battle of Nodes Recap & Next Steps Hello Nodes Team, We're working to bring you a very friendly and non-intrusive Validator client auto-update tool. In the meantime we're increasing and decreasing TPS and interpreting results. πŸŽ– The next mission will be to update your node in under 1 hour from the patch release with this tool. The tool will be released at time "x", then a new patch will be issued at time "x + 24 hr" and mission scoring will happen at time "x + 25hr". You will have a 24 hours interval to deploy the auto-update tool on your node and then we plan to see all
  7. πŸŽ– "5 Generals" - Mission #5.2 updates & Phase 2 Timeline Hello Nodes Team, The "5 Generals" mission had some very interesting outcomes, with all of you working together as a team, with the help of Dr. Delphi and his bot. The now famous duo that are thus awarded the completely fictitious and extremely well deserved πŸ₯* drum roll * πŸ₯ πŸ‘‘πŸ€–πŸ‘‘ "Cyber-Crown of the 5 Shards" πŸ‘‘πŸ€–πŸ‘‘ - a ceremonial headpiece worn by the traditional mechs assembled from 5 Byzantium generals & their elephant robots back in the 11th century. Congratulations @drdelphi & @BoNmonitorBoT for
  8. πŸŽ– "5 Generals" - Mission #5.2 updates Hello Nodes Team, The current version of the testnet seems stable so we've turned up the heat a bit more. We're hovering at around 900 TPS right now, so far so good. We're going to keep the current version of the testnet for a few more days and gradually increase the TPS count. In the meantime, let's get back to scheming! "5 Generals" is back, as announced on Friday. We're changing some things a bit, to make it more interesting and relevant, full details below. 🧐 The original Mission #5 is HERE (link) (https://t.me/BattleOfNodes/54),
  9. πŸ“£ Announcing Round 1 of Phase 2 Hello Nodes Team, Hungry for more BoN action? Looks like meat is back on the menu! We have patch v1.0.40 for you guys, come and get it! 🎟 Nodes that participated in the previous rounds are whitelisted by default πŸ‘‰ Please do: Backup your keys, set up the latest version of the node, restore keys, start node β–ͺ️ Linux (https://docs.elrond.com/start-a-validator-node/start-the-network/connecting-from-linux) installation guide πŸ”Ή Windows (https://docs.elrond.com/start-a-validator-node/start-the-network/connecting-from-windows) installation
  10. πŸ“£ Updates about Phase 2 start, Scores and Mission #1 Hello Nodes Team, The Leaderboard (https://leaderboard.battleofnodes.com/) is now updated with all the scores from Rounds 3 & 4, including Mission #1. We uploaded the instances where the scores awarded for the Mission were less than full here, go check it out. ⏱ Uptime bonus: as previously announced, we decided to grant an uptime bonus to clear up the issues from a missed network package or failed heartbeat for whatever reason. Uptime scoring is meant to encourage you guys to keep nodes running all the time, not make you
  11. πŸ“Š Leaderboard (https://leaderboard.battleofnodes.com/) update & next steps Hello Nodes Team, We updated the scores to include Round 4 & Mission #1, go check it out. Still to do: Round 5 score and Round 1-3 uptime bonus, as decided earlier (https://t.me/BattleOfNodes/57). πŸ“† Round 1 of Phase 2 starts this week, likely on Wednesday. Throughout this round there will be a constant transaction flow from Elrond, giving nodes in Shards 0-4 the chance to earn as much as the Metachain, due to capturing transaction fees. πŸŽ– Mission #5 will be back with exactly the same idea
  12. 🎬 Closing Round 5 of Phase 1 and Phase 1 overall! Hello Nodes Team, What an eventful Round 5! We had a stable network, 3 full missions and the start of perhaps one of the coolest mission so far. But we also tried turning up the heat and increasing the TPS count beyond what is presently reasonable. 30k TPS though, HOW COOL IS THAT?? Anyway, back to Earth, for now. We close Phase 1, start with Phase 2 next week and re-start Mission #5 as well 🎬 Round 5 of Phase 1 ends Sunday 10 November 23:59 UTC πŸ“Š Scoring for Round 5 will be made of uptime & completed missions. Small
  13. πŸŽ– Battle of Nodes Mission #5 Hello Nodes Team, Perhaps one of the biggest wonders of blockchain is that it provides an efficient solution to the Byzantine Generals Problem. Byzantium was so filled with wars and political infighting, that the term "byzantine" became synonymous with complexity and deceit. 🏰 The Byzantine Generals Problem (https://www.youtube.com/watch?v=A-mNgqJETQg) is when a bunch of generals from the Byzantium empire surround an enemy city to attack it. Success will only be achieved if they coordinate so all attack at once. With no phones and a propensity for
  14. πŸŽ– Battle of Nodes Mission #3 & other updates Hello Nodes Team, Mission #3 will be a bit easier than the previous one. The goal here is to get you guys looking a bit under the hood of your nodes, see what happens when you mess around with things. Simple things first - node display name. πŸ•΅οΈβ€β™€οΈ NodeDisplayName represents the friendly name a user can pick for his node in the status monitor. You can change it in the prefs.toml file located in the elrond-config folder πŸ‘‰ Give your node(s) a name, if you haven't already, by updating your prefs.toml file(s) πŸ‘‰ Send a tra
  15. Understanding accounts & addresses & public keys & wallets alright! *cracks knuckles* There are 2 to the power 256 accounts possible in Elrond. That's a silly number I can't even pronounce. Bazzilions of trillions of milli-gazillions of mega-millions of billions-trillions. Let's just say there are only 30 accounts possible, instead. So Elrond30 has account 1, account 2, ... , account 30 Each account can be accessed with a private key and can be identified publicly by its public key. Now, let's go back to what I wrote before about state and how it represent
  16. πŸ“£ Announcing Round 5 of Phase 1 & Latest Patch Hello Nodes Team, We trust you got a good rest over the weekend and are back with fresh energy for Round 5 of Phase 1! We have launched patch v1.0.38 which contains a series of fixes and improvements. ⚠️ Reminder: This is a Phase 1 - Build extension. We're aiming for a stable network and a few missions, no stress testing or attacks. 🎟 Nodes that participated in the previous rounds are whitelisted by default πŸ‘‰ Please do: Backup your keys, set up the latest version of the node, restore keys, start node β–ͺ️ Linux
  17. 🌀 Battle of Nodes will resume after the weekend Hello Nodes team, Testing the current patch is taking more time than initially estimated, mainly due to the complexity of the issues addressed requiring proper care and tinkering. The dev team informed us that they are not ready to release now. So let's enjoy the weekend and stay tuned for an announcement on Monday. πŸ‘‰ Please watch the announcements channel for an update πŸŽ– Mission transactions sent in time but not executed due to the issues will be considered. Please DM @SeverMM with the TX link or a screenshot of pending tr
  18. πŸ“£ Client version 1.0.37 released Hello Nodes Team, The latest patch is here! It removes the cause of the "too many open files" error nodes running on Linux experienced, which will allow all nodes to be able to initiate the recovery process and get the shards with issues unstuck. πŸ‘‰ Please do: Backup your keys, set up the latest version of the node, restore keys, start node πŸ‘‰ Please do not delete the database β–ͺ️ Linux scripts πŸ”Ή Windows scripts ▫️ MacOs scripts πŸ‘† Scripts make your life as a node operator easier, when used properly. Please follow the links abov
  19. 🚧 Too many open files error Hello Nodes Team, Several Linux nodes are throwing a "too many open files" error. This is because TCP connections are treated as open files and counted towards a max, which is 1024. So when connected to 1.000-ish nodes, Linux won't open more files and let our validator software do its thing. We've prioritized the implementation of the feature to prevent this. Patch coming! πŸ‘¨β€πŸŽ¨ Coding Artist Iulian Pascalau explains: https://t.me/ElrondValidators/21471 🌏 The issue is manifesting overall and is causing delays to some transactions. The shards are
  20. Hello Team Nodes, Your continuous support and involvement in Battle of Nodes is both making us humble and more responsible. We want you to be proud of us and we need your help to make that happen. So for our first Battle of Nodes mission we decided to try and align our incentives. Here’s what this is all about. Elrond has recently been listed on CoinCodeCap.com. The name is a clever play on CoinMarketCap.com, but instead of tracking token price and trading volume, it tracks GitHub activity. This is a very good indicator about a project’s liveliness and the team’s commitment to keep b
  21. πŸ“Š Leaderboard scores for Round 3 are up! Hello Nodes Team, Scores for Round 3 have been uploaded to the Leaderboard, go see where you stand! Due to the metachain synch issues last week which pretty much started right after kicking off Round 3, we only used uptime information. πŸ‘‰ We applied the version penalty for nodes that updated after the 24 hour grace period which ended Friday 25 October 09:00 UTC πŸ‘Œ We granted a 30 minutes bonus to all scores on Friday, to cover for extra restarts that were performed while troubleshooting ⏱ Friday scoring spanned 7 hours:
  22. πŸ“£ Announcing Round 4 of Phase 1 & Latest Patch Hello Nodes Team, We trust you got a good rest over the weekend and are back with fresh energy for Round 4 of Phase 1! We have launched patch v1.0.36 which contains a series of fixes and improvements, as well as the genesis for Round 4, which will officially start Tuesday 29 October 07:00 UTC, +24 hours from now. ⚠️ Reminder: This is a Phase 1 - Build extension. We're aiming for a stable network and a few missions, no stress testing or attacks. 🎟 Nodes that participated in the previous rounds are whitelisted by default
  23. 🎬 Round 3 of Phase 1 ends early Hello Nodes Team, The patch was too little too late for recovering the blockchain from its earlier issues. Recovering it via an accurate orchestration of all node operators simultaneously would be both beautiful and impractical. Battle of Nodes is a tough competition but it also is ~350 people from 43 countries who are looking forward to the weekend. So, we're calling it now and starting fresh next week. ⏱ Official end of Round 3 is Friday 25 October 18:00 UTC πŸ“Š All scoring for Round 3 will be done based on uptime. A 30 minutes per node ove
  24. πŸƒβ€β™‚οΈ We're catching up! Hello Nodes Team, Following a successful campaign by our very own Lucian, Iulian, Sebastian & the rest of the team, the metachain is finally recovering. Good job to them and to all of you involved to make this recovery possible. πŸ‘‰ If you haven't patched already, please do so, grace period has ended Friday 25 October 09:00 UTC. πŸ”Ž What's happening right now: The metachain is presently notarizing the blocks in the other shards at block height ~8.000, whereas in reality they are at ~20.000. We estimate it will properly catch up in 8 -12 hours.
  • Create New...