Jump to content

Sever Moldovean

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Sever Moldovean

  1. 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
  2. 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!
  3. ๐Ÿ“ฃ 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-from-linux) installation guide โš ๏ธ Does not work on Windows โ–ซ๏ธ MacOs (https://docs.elrond.com/start-a-validator-node/start-the-network/connect-from-macos) installation guide โฑ This announcement is in effect as of Saturday 30 November 19:00 UTC. Official uptime monitoring starts Monday 2 December 19:00 UTC, 48 hours (because of the weekend) from the announcement. Be sure to update your nodes before that time. โฒ The genesis time was Friday 29 November 11:00 UTC โš™๏ธ Relevant tags: v1.0.41 and BoN-ph2-w2 ๐Ÿ‘ป Remember: we removed ghost nodes. We defined a node as "ghost" if it was offline for 7 days or more during Rounds 4 & 5 from Phase 1 ๐Ÿ‘จโ€๐Ÿณ The installation & auto-updater tool are still in the oven, our chefs are cooking around the clock ๐Ÿ–ผ Bye-bye Windows! This patch will not work. This is the last call to move to Linux! "I've ran out of emoticons." - not Sever โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  4. ๐ŸŽฌ 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 done and it will be included in the next patch. So we grow! ๐Ÿ“ก An automatic update script is being tested right now. We will offer it to you guys on Monday 25 November 12:00 UTC (estimate). From that point over, all nodes will have 24hrs time to opt into using the script. After the 24 hour grace period, a patch will be issued. The Latest Version penalty will henceforth be decreased from 24 hours to just 1 hour. ๐Ÿง Why an auto-updater: This is so we can release patches faster, restart the blockchain faster and overall be more confident about spamming the network. Remember that Phase 3 is coming as well, recovering from those deadly attacks will be interesting! ๐Ÿ‘‰ Please do: make sure you watch this announcement channel in the 24 hour period starting with Monday 25 November 12:00 UTC and onwards for the autoupdater instructions. ๐Ÿ‘ป While we wait for the hot new rating system to clean out offline nodes and low performing ones, ghost nodes will be purged. 70-ish nodes haven't been online in a while, so we will remove them in Round 2 of Phase 2. They can be re-added to the next Round, if you decide to turn them back on. "Some say Mondays are terrible. Nothing a new patch can't fix." - aspiring ex-smoker โš”๏ธ See you on the battle #fiedl! ๐Ÿ›ก
  5. ๐ŸŽฅ 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 nodes updated within 1 hour from the new patch. "x" = soon(tm) ๐Ÿ“Š To even out scoring between those who had full uptime but no time for missions and those who dilligently did missions even if they couldn't maintain 100% uptime, we're normalizing the score for the coming period. Please check the current calculations here (https://docs.google.com/spreadsheets/d/1Z1oMYll6ileduuvxZ0pzLuGhVKd5PwnzMdfWIeeVMPk/edit?folder=1K6Jr6_pMZWYr9Ev4kbL6Y8VMNV8R5B93#gid=0) - feedback welcome! ๐Ÿ’Œ In the meantime, our war correspondent writes home to his wife about his experiences on the battle #fiedl. A romanced recap of the Battle of Nodes event so far: https://medium.com/elrondnetwork/tales-of-war-a-letter-from-the-front-line-950ff6b5b465 (https://medium.com/elrondnetwork/tales-of-war-a-letter-from-the-front-line-950ff6b5b465)"The toughest mission so far challenged the trust we have in one another and had us doubt our comrades. They wanted to re-enact the Byzantine Generals problem and have us risk it all on trusting just a few of us. But we pulled through, thanks to our field medic and his heavy lifting robot." โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  6. ๐ŸŽ– "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 earning everyone's trust and honorably fulfilling out your destiny! ๐Ÿค” The results are extremely interesting, because while the bot managed everything, it was still down to the player's tactics to decide how to allocate their points. Some chipped in as much as they could for their one node, some distributed points evenly between their multiple nodes, others boosted just one of them, while apparently others pooled more than 6 nodes to boost just one. ๐Ÿง The figures can be observed on the blockchain explorer here (link) (https://explorer.elrond.com/address/f41cbb0cb63d5dfbdbaea7a9dc220828523a362592e9cd6f89e517f173c4387a)and perused in a simpler form in this spreadsheet (link) (https://docs.google.com/spreadsheets/d/1XXFJHARKIUmBCPMe-tF2bB1dnHQX0ODM4sCa_7WHPsA/edit?folder=1gtQ6Z9c0SR8LiGlLQIEjd4REYVoROlXa#gid=287687019). ๐Ÿ“Š Obviously the mission rewards topple some expectations and create some interesting Leaderboard action. The goal of this event is of course to have fun and excitement, but above all to test the Elrond blockchain, make it better, more secure and to make sure you guys have all the right knowledge. ๐Ÿ‘‰ As we move into our more intense testing & adversarial phase, scoring will be adjusted to reward performance much more than just the uptime and missions so far. ๐Ÿ•ต๏ธโ€โ™€๏ธ Our working balance approach is to make Phase 1 total max score = Phase 2 + Phase 3 total max score. This will balance the efforts so far with the intense task of running a node in a high TPS & adversarial environment โฑ Round 1 of Phase 2 will be running until we announce a new patch, which is estimated on Thursday. Scoring continues until the official announcement of the end of Round! "Man and machine, power extreme!" โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  7. ๐ŸŽ– "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), we consider that as baseline with the changes below ๐ŸŽ– Mission scoring for the first 4 days of Phase 2 will be decided via one single transaction from each shard. The originating wallet must be in the shard for which points will be distributed. The minimum value of the transaction is 500 000 ERD, without considering gas. The transaction with the highest value, without gas, is victorious. The data field must include the public key of nodes and points assigned to each of them. ๐Ÿ“Š Scoring in the first 4 days of Phase 2 will be split as 50% mission, 50% a mix of uptime, earned rewards and proposed blocks. Max score per day is 10.000 points, so you can get max 20.000 points for mission and max 20.000 points for uptime + rewards. Check the formula as below: First 4 days score = ( (1 x Percent Uptime + 2 * Number of Earned rewards / (Hitrate * Max Number of Earned Rewards) + 3 * Proposed Blocks / Maximum Proposer Rate) /6) * 20.000 + Mission #5 score) ๐Ÿ’ฐ 2.920.000 score points allocated for each winning transaction. Why? (Number of community nodes online * mission score for 4 days) / (5, the number of non-meta shards) ๐Ÿงฎ Click HERE (link) (https://docs.google.com/spreadsheets/d/1oO2Y-4nd2PDl9IQFN-u_vzbO_YiM5e4r3WniFA6rpr4/edit#gid=0)for a spreadsheet with figures and examples and HERE (link) (https://forum.elrond.com/topic/66-scoring-rewards/) for an explanation of the terms โฑ Please send the transactions by Tuesday 19 November 18:00 UTC โ€œThe great mass of humankind possesses an unmistakable unit-identity. It can be one thing. It can act as a single organism.โ€ โš”๏ธ See you on the battle #field ! ๐Ÿ›ก
  8. ๐Ÿ“ฃ 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 guide โ–ซ๏ธ MacOs (https://docs.elrond.com/start-a-validator-node/start-the-network/connect-from-macos) installation guide ๐Ÿ‘Œ No need to keep any old databases โฑ This announcement is in effect as of Thursday 14 November 14:00 UTC. Official uptime monitoring starts Friday 15 November 14:00 UTC, 24 hours from the announcement. Be sure to update your nodes before that time. โฒ The genesis time is Friday 15 November 14:00 UTC โš™๏ธ Relevant tags: v1.0.40 and BoN-ph2-w1 ๐Ÿ–ผ Still running on Windows? You're OK and getting 100% score for Round 1 of Phase 2. Please consider migrating towards Linux for Round 2 of Phase 2, we will only award 80% of score for Windows clients starting then (date not announced) โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  9. ๐Ÿ“ฃ 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 angry that in spite of your scripts and expensive VPSs, you lose points. We heard you. ๐Ÿคฉ We applied a flat 2.5% bonus score to everyone, without exceeding the maximum 10.000 points per day score. This fixes the tiny differences between our 100% operators while nod doing anything for people who are offline for longer periods of time ๐ŸŽ– Mission #1 scoring - because of our "Nobody gets left behind!" philosophy, we decided to award partial scores to people trying their best in the mission. We split it in 4 parts: Transaction with proper amount, Transaction with proper info. Filling in the form, Starring the Repo. Doing at least one of those was scored. Obviously people who did the full mission got full points and are way ahead of the rest. ๐Ÿ‘‰ Please check the Leaderboard (https://leaderboard.battleofnodes.com/), check if your nodes are in the Mission #1 issues list (https://docs.google.com/spreadsheets/d/1xR1279hEw5kzcyAX_Z-qjsj4a9AutyGIrftQdZnDvT8/edit#gid=0), and get in touch with @SeverMM to fix anything related to transactions. No GitHub or Forms issues, I already did my best to address that individually with everyone I could. ๐Ÿ“† Patch is almost ready, testing it one more time overnight. Expect Phase 2 announcement on Wendesday and actual start on Thursday. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  10. ๐Ÿ“Š 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, perhaps slightly different figures (i.e. minimum transaction amount). Keep scheming. โš ๏ธ Round 2 of Phase 2 (next week) will have an interesting scoring feature - validators running on Linux and MacOS will get 100% of the score, while validators running on Windows will get 80% ๐Ÿง Why? Our innovative Virtual Machine uses 3rd party dependencies that do not play well with Windows (https://twitter.com/SasuRobert/status/1193875547375521792) at the moment. The mainnet therefore won't have a Windows native client. ๐Ÿ‘จโ€๐Ÿ’ป You can still run validators on your Windows machines, but with a Linux virtual machine (https://techsviewer.com/best-free-virtual-machine-software-2018/) on top. We will share an official tutorial. Stay tuned for the Phase 2 start announcement. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  11. ๐ŸŽฌ 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 bonus for uptime in Shards 1 & 3 to account for the restarts ๐ŸŽ– Mission #5 is cancelled in its current form due to issues with Shards 1 & 3. It will come back next week ๐Ÿ‘‰ Please do: make sure nodes are running up until Sunday 10 November 23:59 UTC for maximum uptime and keep your eyes on the announcements channel for the start of Phase 2! ๐Ÿ“† Overall schedule at this point is 2 weeks over the initial estimates. Thank you for you continued support as we make incredible progress! ๐Ÿ‹๏ธโ€โ™‚๏ธ Prepare your nodes - Phase 2 will feature constant transactions that we will send over the network at varying rates, with scoring tuned to discourage sub-par systems General scoring - thank you all for the feedback about uptime fairness. Our goal is to encourage everyone to run a node for as much as possible, not to aggravate those who do their best to maintain uptime but get a "hiccup" due to conditions outside of their control. ๐Ÿคฉ We will apply a retroactive 0.7% bonus (~10 minutes / day) for daily uptime scores, without going over the maximum possible. This evens out the scores for those who do their best to maintain high uptime, and does virtually nothing for those who turn on their nodes occasionally or are offline for longer periods of times due to other conditions. โš”๏ธ See you on the battle #field ! ๐Ÿ›ก
  12. ๐ŸŽ– 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 treachery, things really get interesting. ๐Ÿ“„ If you love reading, check this 1982 research paper (https://people.eecs.berkeley.edu/~luca/cs174/byzantine.pdf) by Leslie Lamport, it will give you some insights into how old the problem is, how old the actual math solution is and maybe even make you wonder what took Satoshi so long to implement it? ๐Ÿงโ€โ™‚๏ธ Blockchain technology solves this problem with neat mathematical variations that help decentralized networks achieve consensus. At Elrond we invented something we call Secure Proof of Stake, read more about it here (https://docs.elrond.com/learn/secure-proof-of-stake). If you want a fun & practical example, here it is: ๐Ÿ“Š The scoring over the weekend will be decided via one single transaction from each shard, so 5 transactions decide all the scoring. The originating wallet must be in the shard for which points will be distributed. The minimum value of the transaction is 1.000.000 ERD, without considering gas. The transaction with the highest value, without gas, is victorious. The data field must include the public key of nodes and points assigned to each of them. ๐Ÿง Example of payload: 004b262af9256b4fb09964c32489cb193bc75553ce96fd635de56afa2cb105 15000 d60b64080d7e27f09947d65a86ef42cc4d2d7f011cbe5252cd983be2373a5 10000 221a61101b89427432d107f1deef094b71f1d59bc246e3b94eb8ca888917 5000 With the above we will assign points to the nodes which registered with those public keys (initialBalancesSk.pem) as instructed: 15k, 10k, (anything 2.412.000 or less). ๐Ÿ‘‰ Send the transactions to this wallet: 801b47492f5df19493fdd6e36a958aad390e9bb54a517c1a8d21cd90812cc255 โฑ Mission #5 ends Monday November 11 20:00 UTC. Transactions received after that are disconsidered. ๐Ÿ’ฐ The transaction, per shard, with the highest amount of ERD, wins ๐Ÿ“Š Each winning transaction per shard gets to assign 2.412.000 points by assigning each node points in the data field, as explained above ๐Ÿงฎ Why 2.412.000? Maximum score per day is 10.000. We will do this mission over 3 days. 50% of scoring will be uptime, 50% will be mission. So 5.000 points each day will go to the mission. 3 days x 5.000 points per node x 804 community nodes = 12.060.000 points, split by 5 shards = 2.412.000 ๐Ÿคด The transaction decides everything and is final, no mistakes. Anything goes - a single node can get all the points from all transactions and any possible combination you can imagine ๐Ÿš€ If you think 1.000.000 ERD is too much, keep your eyes on that TPS counter over the weekend - more transactions, more fees, more block proposer fees! โš–๏ธ In case more than 2.412.000 points are assigned in the data field of the winning transaction, we will only award points in the order received, until reaching 2.412.000, no more after that ๐Ÿ˜ฑ "But why should I entrust my money and identity and chance to succeed to complete strangers, that's crazy!!!" Yes, it is. And yet we do it, every single day of our lives. Blockchain is important. โ€œHe who controls the ERD controls the universe.โ€ โ€• Frank Shardbert, Dune โš”๏ธ See you on the battle #field ! ๐Ÿ›ก
  13. ๐ŸŽ– 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 transaction with 900 ERD and your NodeDisplayName in the Data field to b96bb87913469147272ddceb69dfb6041817ea9e0c6b16558bc25b1b57f5432a โš ๏ธ Send 1 transaction for each node, don't group or split โฑ Mission #3 is in effect as of Wednesday 06 November 16:00 UTC and will end in 24 hours on Thursday 07 November 16:00 UTC. Please make sure to correctly send out the transactions by then 2๏ธโƒฃ Perhaps aptly named "number 2", according to some opinions, yesterday's mission was both challenging and tedious. Due to these reasons we decided to give those of you who didn't have a chance to complete Mission #2 in time a chance of doing so. ๐Ÿ‘‰ You can complete Mission #2 untill Thursday 07 November 04:00 UTC with a 50% score penalty. ๐Ÿ“Š Leaderboard update is in progress. @SeverMM is old and we're still teaching him how to use computers. He spent his last two days trying to guess his own password before asking for help. ๐Ÿคฆโ€โ™‚๏ธ ๐Ÿ’ฐ Bonus points if you change your node's name to something that breaks something (https://xkcd.com/327/), somehow โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  14. 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 represents all the accounts and their balances. So Elrond30's state is a list that looks like: Account 1: 500 ERD Account 2: 200 ERD ... Account 30: 900 ERD When a "round" happens, we move from one state (current list of accounts and balances) to the next state. In a round we have transactions, so Account 1 sends 100 ERD to Account 30, then the next state is something like: Account 1: 400 ERD ... Account 30: 1.000 ERD Easy when we only have 30 accounts, my Casio watch from 1984 could do that. But when we have bazzillions of gazillions, hmmm, things get messy. So why not "shard" them, or split them up? This way, instead of all the nodes in the Elrond network keeping track of all the bazilions of gazillions, we make "teams" of nodes to keep track of a portion of the bazzillions. Let's go back to Elrond30. It has 30 accounts and we split them in 3 shards. As per the architecture, we have Shard 0, Shard 1 and Shard 2 as the 3 shards, and the metachain to account for cross shard transactions and all that. So now we split the 30 accounts in 3 shards. Accounts 1-10 are in Shard 0 Accounts 11 - 20 are in Shard 1 Accounts 21 - 30 are in Shard 2 (more) [In reply to Sever | TL;ERD] Each of the accounts has an address, which is conveniently the public key paired with the private key used to access thhe account. So you can say, for the sake of our argument, that an account is the same as an address which is the same as the public key. - The account 9a81adb5b5f3633724e92604cbc8c79b9addd4413d814b5e3f605c1fe1a33491 has a balance of 100,004,380.8840 ERD (hue hue hue) - That balance is largely due to account c3615339baf6c19b7b9723b706b83dda35d7b173c4f7d3fe22f4dbeafd887493 sending 100.000.00 ERD to the address 9a81adb5b5f3633724e92604cbc8c79b9addd4413d814b5e3f605c1fe1a33491 - I can access that account with a private key that only I have. The public key pair for that private key is again 9a81adb5b5f3633724e92604cbc8c79b9addd4413d814b5e3f605c1fe1a33491 (turns around from the blackboard, everyone already left 15 minutes ago) OK, so let's continue For people to make sense of all of the above, the nerds that came up with all of this impossible stuff thought: hmm, we have accounts and addresses and public keys which are all the same. But something's missing. Let's add one more word that basically described the above: "wallet" A wallet loosely is similar to "account", but more often refers to the interface used by someone to access an account. That's why we have "web wallet" like myethereum.com, "mobile wallet" like the TrustWallet dApp, "hardware wallet" like Ledger, etc. But, for the sake of our example, account = address = public key = wallet.
  15. ๐Ÿ“ฃ 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 installation guide ๐Ÿ”น Windows installation guide โ–ซ๏ธ MacOs installation guide ๐Ÿ‘Œ No need to keep any old databases โฑ This announcement is in effect as of Monday 04 November 09:00 UTC. Official uptime monitoring starts Tuesday 05 November 09:00 UTC, 24 hours from the announcement. Be sure to update your nodes before that time. โฒ The genesis time is Tuesday 05 November 07:00 UTC, but scoring will start Tuesday 05 November 09:00 UTC, so as to keep our commitment of 24 hours notice for everyone. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  16. ๐ŸŒค 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 transactions, if it's the case ๐Ÿ“Š Leaderboard info is currently being processed and will be updated early next week "The worst part about war is not the fighting, but the waiting" - anonymous shopper on the eve of Black Friday, 1984 โš”๏ธ See you on the battle #fiedl! ๐Ÿ›ก
  17. ๐Ÿ“ฃ 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 above and try updating your nodes in a more automated way. ๐Ÿ”Ž Check scripts before updating, latest tags are v1.0.37 and BoN-ph1-w4-p1 โš ๏ธ If you're using your own scripts, make sure you update the binary and the p2p.toml, located in the \src\github.com\ElrondNetwork\elrond-config folder ๐Ÿ“Š Due to shards 2&3 having gotten stuck since around Wednesday 30 October 23:00 UTC, scoring from then and until Friday 01 November 11:00 UTC will disregard the block proposer rate, to keep the daily scores comparable accross shards. This announcement is in effect as of Thursday 31 October 11:00 UTC. Official uptime monitoring starts Friday 01 November 11:00 UTC, 24 hours from now. Be sure to update your nodes before that time. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  18. ๐Ÿšง 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 progressing, sometimes slower. ๐Ÿ“Š As this situation is global, no change to scoring. ๐ŸŽ– Missions: we will make sure you don't get penalized if your correct transaction, sent in the right time frame, is pending due to this situation. ๐Ÿ‘‰ Please do: keep your nodes online and watch this channel for the patch announcement. "If it's not broken, why not break it?" - ancient Round 1 proverb โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  19. 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 building. It therefore is not a surprise for anyone that Elrond is ranked high because of our very active development team. Besides the number of commits to a projectโ€™s GitHub repository, CoinCodeCap also tracks its โ€œpopularityโ€, which is measured by the number of times a project has been โ€œStarredโ€. Thatโ€™s the same as following someone on Twitter or liking a page on Facebook. Help us become more popular and make Elrondโ€™s rank on CoinCodeCap something we can all be proud of! Hereโ€™s the mission: Star our repo on GitHub Fill in this form Send one transaction for each of your nodes We will then: Look at successful blockchain transactions originating from your respective wallets Confirm the โ€œfoodโ€ in the Data field is exactly the one you provided in the form Check if the GitHub login you provided us in the form has our repo โ€œstarredโ€ Detailed tutorial Star us on GitHub Register a GitHub account, if you donโ€™t have one Go to https://github.com/ElrondNetwork/elrond-go Hit the โ€œStarโ€ button (โ€œWatchโ€ also helps us a lot, but not mandatory for this mission โ€” can get spammy) 2. Open the wallet Go to https://testnet.elrond.com/#/mywallet/ Select โ€œAccess using PEMโ€ Select the initialBalancesSk.pem file for the node you are sending for 3. Send the transaction Add this address to the โ€œToโ€ field: Bba53f97539a4a1e058362b97203024e066ce563303ca8723cedd29490690cc2 Add โ€œ800โ€ ERD in the Amount field -> 800 ERD is mandatory! Transactions with less than 800 ERD will not qualify for completing the mission Add your โ€œFoodโ€, as filled in the form, on the Data field (same character count, case sensitive, space sensitive!) 4. Repeat for each node How many points will I earn? According to our simplified scoring algorithm, a mission is worth 10.000 / 11 = 910 (rounded up) points. Scoring algorithm: These points will be considered for your Day 1 of Round 4 score. What if I have more than 1 node? In order for your node to earn โ€œmissionโ€ points, you need to send a transaction from each of your nodeโ€™s Balance wallet. 6 transactions for 6 nodes, for example. Make sure to use the same โ€œfoodโ€ in all the transactions! Why food? Everyone loves food and we love to hear what you guys enjoy in different parts of the world. We also respect your privacy and would never ask you to provide info such as GitHub login publicly via transactions anyone can see. Not the worldโ€™s biggest secret, but the principle of it is important, and we respect it. Why 800 ERD? Weโ€™re counting rewards earned, so we want to make sure you can only complete a mission if you have enough of them. Some boring math: Metachain has an advantage, they have 163 nodes in the consensus rounds, so end up earning more rewards. By when should I complete this mission? This mission is in effect as of Tuesday 29 October 13:30 UTC and will end Wednesday 30 October 13:30 UTC. Transactions sent after that time will not be considered. Does the shard I am in matter at all? Nope! Metachain nodes will have more ERD, but the threshold is achievable in this timeframe for most nodes anyway. Good luck!
  20. ๐Ÿ“Š 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: 11:00 - 18:00 UTC, so max score was 2.916 (7/24*10.000) ๐Ÿšง Glitch in the Matrix: nodes running clients older than v1.0.36 are displaying "N/A" under "Version" โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  21. ๐Ÿ“ฃ 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 ๐Ÿ‘‰ 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 ๐Ÿ‘Œ No need to keep any old databases ๐Ÿ‘‰ Node names are taken from prefs.toml instead of config.toml, starting with this patch, please edit accordingly โฑ This announcement is in effect as of Monday 28 October 07:00 UTC. Official uptime monitoring starts Tuesday 29 October 07:00 UTC, 24 hours from now. Be sure to update your nodes before that time. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  22. ๐ŸŽฌ 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 overall bonus will be included for servers that were online, to account for restarts, without going over 100% ๐Ÿต Round 4 will come next week. Phase 1 will be extended to make sure we have a stable blockchain to move into Phase 2 with. โฐ The new patch and official announcement will come on Monday 28 October during UTC business hours, with 24 hours notice before the official start of Round 4 "Blockchains are like life - whenever you feel things are not working out, you can just keep the knowledge and start from the beginning." - Aristotle โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  23. ๐Ÿƒโ€โ™‚๏ธ 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. ๐Ÿ“Š Scoring will take into account this interesting situation, a later update will come on that. ๐Ÿ… ... so Poppa tomato gets angry, goes over to the baby tomato, and squishes him... and says, 'Catch up.' โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  24. ๐Ÿ“Š Leaderboard scores for Round 2 are up! The long awaited update is finally live on the Leaderboard. A complex update, please check the details below. Round 2 scoring was only done based on uptime. Counting rewards was not an opportunity, due to the Thursday attack and subsequent blockchain halt. Periods for scoring in UTC time: ๐Ÿ”นWednesday 16 October 07:00 - 15:00 - regular scoring, based on actual uptime ๐Ÿ”นWednesday 16 October 15:00 - Friday 18 October 21:00 - grace period due to the ongoing attack and subsequent patch - all nodes that were online got max points ๐Ÿ”นFriday 18 October 21:00 - Sunday 20 October 07:00 - regular scoring, based on actual uptime + version penalty ๐Ÿ”นSunday 20 October 07:00 - 23:59 - no score - artificial network traffic prevented our observers from collecting accurate data. We removed the possibility to artificially generate traffic in that respective manner via a patch. ๐Ÿ”จ Etching notches into the wall of fame is not easy, but done. Please share your concerns so we can address them as needed. โš”๏ธ See you on the battle #fiedl ! ๐Ÿ›ก
  • Create New...