Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/28/2019 in all areas

  1. 7 points
    Hello, my name is Sever and I am from the internet. I am a firm believer that cryptographically secured decentralized immutable trustless automation will change the world for the better. In the Elrond team I tell stories and manage projects. In crypto I like reading about all the new exciting tech and adoption developments.
  2. 6 points
    Official guide for setting up a node: https://docs.elrond.com/start-a-validator-node/start-the-network Community enhanced official scripts: https://github.com/ElrondNetwork/elrond-go-scripts Community tutorials: “FAQ running Elrond Network node for the first time” by Jose F. Aznar https://link.medium.com/4ime0uLMn0 “Fast Install & Update Elrond Nodes” by Jose F. Aznar https://link.medium.com/pQxZjzOMn0
  3. 6 points
    Battle of Nodes “It is not the strongest of the species that survives, but the one that is most adaptable to change” - Charles Darwin In order to make Elrond a sustainable layer that will stand tall in the face of any challenge, we are building antifragility into its core. Right from the first testnet phase we invite everyone to discover what it means to run a node, get rewards, and put the network through a trial by fire so it will emerge stronger. The Battle of Nodes will feature a Testnet-as-a-Battleground environment where test node operators will be rewarded for supporting the network and even more so for trying to break it. Goals of the Event The purpose of this exercise is to: Stress test our sharded proof of stake architecture and its inherent complexities in preparation for launching our mainnet; Prepare our node validators for operating in real conditions that will include unfavorable conditions and adversity; Collect newly discovered bugs, learn about potential attacks and use the findings to further strengthen our network. Reward pool: $50.000 Schedule: Registration: 01 October 2019 - 06 October 2019 Build: 07 October 2019 - 27 October 2019 Challenge: 28 October 2019 - 10 November 2019 Assault: 06 November 2019 - 20 November 2019 Who can join? The event is an opportunity for anyone looking to get an early start to earning in the new distributed economy. You will learn more about decentralized networks and how to leverage their infrastructure to generate income while you sleep. A coffee stained laptop, basic computer skills and a good dose of curiosity will be enough to join, as plenty of support will be offered along the way. The event will reward all those who contribute their time and resources in meaningful ways. We are calling out for tech wizards to find new bugs & smart ways of attacking or protecting the network, wise elders to provide the team & community with their support, content & guidance and for all eager warriors to prove their worth in battle. Together, we will push the Elrond network to its limits and beyond so the mainnet launches not as a newly built castle but as a fortress that has withstood the fiercest of assaults, The Battle of Nodes! Terms of engagement The event will run in consecutive stages that will happen over the course of 2 months. Rewards will be accumulated through every stage and displayed live on the leaderboards. This is a test of endurance for the Elrond network but also for you, so make sure to stay active from start till end to maximize your gains! At the end of the event we will grant special prizes to the top scoring nodes, as well as to participants that have distinguished themselves in notable ways, such as helping others, providing valuable insights, creating relevant content and so on. A guide for earning rewards and scoring details will be published in due time. Register (01 Oct - 06 Oct) - Sign up for the event starting with Tuesday 1st of October by accessing this link. We welcome all submissions until Tuesday the 22nd of October. We will kindly ask you to go through a KYC procedure and agree to necessary terms and conditions. You should: Fill a registration form; Provide KYC documents; Receive confirmation. Start setting up your node Build (07 Oct - 27 Oct) - At this stage, the Battle of Nodes testnet is officially online. Rewards calculation for uptime and missions will start on Monday the 7th of October. Nodes can however join the Battle of Nodes testnet before this date, immediately after the initial announcement. Collecting maximum rewards will only be possible if your node is properly configured and online on the 7th of October. You should: Maintain uptime for your node Send out transactions Run periodic missions Challenge (28 Oct - 10Nov): Stress testing the network begins. We will ask participants to perform various tasks such as sending batches of transactions, accessing smart contracts and some other surprise missions. The primary objective is to observe the performance of the network and its resilience under heavy workload conditions. You should: Send transactions of varying complexity; Ensure high uptime for your node; Help stress the network; Check for new tasks and updates at least once per day Assault (06 Nov - 20 Nov): The battle begins! What goes up must come down. Is this true for the most innovative mix of blockchain technologies? Let’s find out! In this stage, participants will be encouraged to try and slowdown, hijack or crash the network. To maximize your rewards, you should accrue as many rewards as possible, by any means. Keep doing Phase 2 (Challenge) missions as well. You should: Try to attack the network and other nodes; Keep your node running at all costs; Maximize your rewards by any means (within the Rules). Registration for the event starts on Tuesday the 1st of October. Make sure to spread the word - challenge your friends and rivals to compete in the Battle of Nodes for epic rewards in the form of mainnet ERD tokens, everlasting glory etched in unique Elrond non-fungible tokens and above all for ultra-nerd non-stop fun! Thank you, and may the best node runner win! The Elrond Team --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Joining the Battle of Nodes event - cheat sheet! 🕵️‍ Pass KYC 💻 Setup node(s) 📑 Fill Form 🧐 Read FAQ 💬 Join Validators TG 📣Follow the forum Additional information can be found at these links: Official Battle of Nodes discussion board Frequently Asked Questions Rules of engagement How to set up a node Battle of Nodes landing page
  4. 4 points
    Hi guys. I am Lucian. I am a serial technology entrepreneur and angel investor, with more than 15 years experience in Internet and tech related businesses. I took the first step towards entrepreneurship in 2001, when, as a 21 years old student, launched the first website that later became known as Soft32.com. In 2002, I decided to drop The Bucharest University of Economic Studies where I was specializing in Finance, Insurance, Banking and Stock Exchange in order to focus on building and expanding the Soft32 platform that, at its peak, listed more than 150 000 apps and was visited by more than 10M users each month. Soft32 was acknowledged in 2014 as one of the fastest growing tech startups in Europe and EMEA. I was involved in several other tech startups activating in mobile payments, gaming, travel or mobile advertising. As an angel investor I invested in several companies: Smartbill - the most used Romanian invoicing and accounting SaaS platform; TypingDNA (Techstars NYC'18 Company) offering typing biometrics and 2FA solutions for securing devices and web applications; Homefresh, the pioneer meal kit delivery service. In the last 2 years I focused on blockchain projects as well. At Elrond I am more focused on the operational and financial side, but I am also managing a user-focused project, soon to be launched.
  5. 4 points
    I make here a simple tutorial on how to run multiple node on single machine and changing shard id https://medium.com/@jeff.penaflor1983/tutorial-on-how-to-run-multiple-elrond-node-in-one-machine-for-windows-changing-shard-id-173392bd2f35
  6. 4 points
    Hi all, A few interesting general resources about Elrond: General https://info.binance.com/en/research/ERD-2019-06-20-d893c3.html https://messari.io/asset/elrond#profile “Elrond Validator Economics Proposal” by Beniamin Mincu https://link.medium.com/kFq41x9On0
  7. 3 points
    If you're not familiar with Mission 6, let me tell you what needs to happen: When the snapshot will be performed on Monday 23 December 12:00 UTC, your wallet balance should be as close as possible to ZERO. You can do whatever you want with your ERD, voting for articles will be the most popular approach, BUT, in the spirit of Shadow Shards, you could be attacking other players, filling their wallet for the snapshot. Having ERD in their wallet can send someone way down on the Leaderboard, this means better chances for you! I'm putting a target on my back!! In a last attempt to have some fun, I challenge you to keep my wallets full for the snapshot. I will try my best to defend my castle and empty the wallets, but depending on the timing, you have a pretty good chance to knock me out of the leaderboard. What can I gain from this? Well, some battle scars :)) and funds for voting, or attacking others! There are no rules in this mission, everything goes!! Here are my wallets: Turtle: 5f06bfe68e78edc52bc642e2bfc56074b98678e7219cfeacfdb6b45fbcf23442 Weasel: 767b0cfd471501c760d3338e5dcb16836f7e9cd7366387851b92022ac6cba020 Eagle: cf51fc9eab73998545e2390a563c7a11603e37d0b581ee18bd1c5b1dc1343563 Raven: 1f59999f81032463036b7414ab65ffbca003542582ec78ebd8032c44ddc7024c Panda: 0f66deababd94d0de7fc205fed533f5bc6a31f9f21f3889f793f8f742ef3f41b Snake: 84fb6cd51e5b5e0c557018bd869a953e645d4e58de0e562acd42f6dd6e0ed2e4 Good luck and have fun! PS: This is also a publicity stunt, so, if you liked my article you can also send your ERD to the voting address at 640e7e30c684aafc3c959881b38ee6bc510798267e7cdc78a314f05ae5294a40. Cheers!!
  8. 3 points
    I made a guide on medium for elrond BON mission 2. Maybe useful to you guys https://medium.com/@jeff.penaflor1983/bon-mission-2-guidelines-a2471f498956 Thank you.
  9. 3 points
    We have discovered a flaw in our finalization algorithm where the finalized block notarized in the metachain was different than the block seen as final in a shard. Based on our findings from shard 3 I will try to describe shortly what happened and how shard 3 got stuck. The current view of a validator in shard 3 at 17:50 UTC looks like this: In shard 3 the latest seen header from the metachain has nonce 18685, which contained the highest finalized block nonce in shard 3 with nonce 17175. Looking in the blockchain explorer on shard 3 page 3 we see the block 17175 at the bottom which was the latest notarized final header for shard 3. The shard worked further with no problems until block 17179, which was sent to the metachain and made block 17178 final in the view of the metachain for shard 3. Starting with block 17179 no blocks were created in Shard 3 for 15 minutes. Because no metachain headers had been added to any block in shard 3, as no blocks were created, shard 3 considered block 17175 as final and tried rolling back to it. During the latest stall in our network, where the metachain stood still, we have built in a mechanism to fix the stalls, so that all nodes in the shard revert to a lower nonce (nonce-1) and try to create a new block with the lower nonce. If they again do not succeed, the nonce is being decreased, until the latest finalized header from the metachain, 17175. During the 15 minutes where no blocks had been accepted in shard 3, the revert from block 17179 to 17175 happened. Then shard 3 started producing new blocks starting again with block number 17175 and created a fork. This fork went on until block 17230 in shard 3. During this fork duplicates of blocks 17176, 17177, 17178 were created and the new 17179 was created in the shard, but could not be notarized in the metachain because it built on top of another block 17178. When we do the rollbacks of the blocks, the blocks are taken out from the persistent storage into our datapools, and deleted from the storage. This is what caused the current issue to be unrecoverable, because, e.g. block 17178 was removed from the shard 3 datapool after some rounds. Afterwards, shard 3 tried to add metachain headers in their blocks, but couldn’t advance with the latest finalized block nonce above 17178, because the metachain would not accept the blocks because they were built on top of a fork. We got to a deadlock, where shard 3 could not advance with its finalized blocks. We are working on a fix, because now we know what went wrong. We’ll keep you posted with updates.
  10. 3 points
    Dear community memebers, Here is an overview on the scoring and rewards methodology. 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 weighted sum of: Rewards Proposed blocks Uptime Missions Client version - penalty for not updating The philosophy behind the Battle of Nodes scoring is to reward each node according to their individual conditions, so at the end of each day, node scores are comparable. This is done by factoring in all the many variables of each shard and determining a daily "shard optimum" - the average score possible under the given conditions. Actual results are compared to this optimum to obtain the daily score. Read below to get a better understanding about how we make this fair for everyone. Scoring explained The leaderboards will be the place to follow your nodes' performance and how you compare to other participants. The ranking will be done based on score. Score is accrued individually for each node and is calculated on a daily basis. Each phase will have slightly different scoring methods, as we look to incentivize different behavior. The score at the end of each round is added up towards a final score. The prizes and rewards are given based on the final standings on the leaderboards, at the end of the Battle of Nodes even. Phase 1 Scoring In the Build phase, participants should maintain their node(s) online with the latest client version and do the periodic missions to earn points. Points are given for: Number of Earned Block Rewards Online (minutes) Missions Latest client version Daily score is: Daily Score = ((1 x Percent Uptime + 3 x (Number of Earned rewards / Hitrate * Max Number of Earned Rewards) + 6 x (Proposed Blocks / Maximum Proposer Rate) + 1 x Mission) * Client Version)/11 * 10.000 Registered Nodes in shard - at the start of each Phase & Round in Battle of Nodes, the total number of registered nodes is split evenly across the number of shards. Not all nodes will be 100% online during the event, which will mean a reduced Hit-Rate (see below) Maximum rewards - For every mined block a reward is given to all the validators that participated in the consensus. A block is mined every 6 seconds, so maximum 14.400 blocks can be mined per shard per day, meaning maximum 14.400 rewards can be given in a shard. In Round 1 there were 21 validators defined in the Elrond consensus mechanism. Thus, the chance of a node to earn a reward for validating blocks is 21/(Nodes in shard). In Round 2 there were 63 validators defined in the Elrond consensus mechanism. Thus, the chance of a node to earn a reward for validating blocks is 64/(Nodes in shard) Maximum Rewards = Total Rewards per Day (14.400)* (Validators needed for consensus / Registered Nodes in Shard) In a shard with 133 nodes: 14.400 * (21/133) = 2273.684211 -> The number of rewards a node will earn, on average, if all nodes are online Rewards are counted by summing up the number of block reward transactions issued by the protocol. Hit-Rate - Indicates the liveliness of a shard, calculated by dividing the actual number of mined blocks by the total number of blocks possible in a period of time. In ideal conditions, there are 14.400 blocks in a day (86.400 seconds in a day / 6 seconds round time). A hit rate of 1 is ideal. Hit Rate = Mined Blocks / Maximum Number of Blocks Client Version - We encourage all the nodes to have the latest client version, so we may effectively deploy critical patch in short periods of time. 100% score will be awarded to nodes with the latest version. A 24 hours grace period after we officially announce a new patch. After that, a 10% penalty is added to the score earned every hour after the grace period. Missions - There will be periodical missions that earn extra points. It is not mandatory to do these missions, but they give significant score. A mission will be for example sending a transaction with a certain amount of gas or specific data encoded. Missions will be linked by nodes because they will require participants to send certain transactions from the address where staking rewards collected. There will be periodic missions, Scheduled missions, Secret Missions. Mission = 910 points Recap: The score has 11 elements: 1 x uptime 3 x number of earned rewards 6 x proposed blocks 1 x mission Daily Score = ((1 x Percent Uptime + 3 x (Number of Earned rewards / Hitrate * Max Number of Earned Rewards) + 6 x (Proposed Blocks / Maximum Proposer Rate) + 1 x Mission) * Client Version)/11 * 10.000 Node Round Score = Sum of Node Daily Scores that Round Phase Score = Sum of Round Scores Total Score = Sum of Round Scores ⚔️ See you on the battle #fiedl ! 🛡️ P.S. Leaderboards teaser
  11. 3 points
    My name is Dan, [UoE] political science undergrad + MBA. Two months after graduation I got entangled in this ambitious project. Involvement is the best way in shaping the future and this is why I’m happy to put so much time into advocating Elrond.
  12. 3 points
    If you lose the *.pem files (aka your node's identity) where you found the public keys used to register for the Battle as a Validator, you're dead! At least you chance to get that perfect score is 😅 Make a habit of backing up these files, it's really not that hard. After you have a working node, you'll find them in the config folder that sits next to your node executable. My advice is to pack initialNodesSk.pem and initialBalancesSk.pem into a zip achive, setting up an optional password that you'll not forget, and store it on a different device or on a private file locker like Google Drive. You might need this to revive your original node in case of disaster. Inactive nodes will get pruned from the shard setup when a new Testnet version is released, so your goal should be to have your registered node running 24/7. Good luck!
  13. 3 points
    The Elrond code imports a repository created by Cloudflare (bn256) for generating some private/public pairs of keys. Due to a bug in that repository, it wasn't possible until today to run a node on a Raspberry PI. But this evening, thanks to Adrian Dobrita (one of the core developers at Elrond), the bug was discovered. So in order to be able to build and run the node on linux / arm64, it is necessary to make the following modification : check line 63 in file mul_arm64.h and change from "ADDS R25, c3 " to "ADDS R1, c3 " That's all folks ! Enjoy 😉
  14. 3 points
    I have learnt a lot from you and from the entire community. I am glad that I am part of this progress
  15. 2 points
    Hello folks, Im a seasoned IT pro with long years of experience in system integration and automation. Im looking forward to play with elrond ecosystem and put it to good test. See you around! nakashu
  16. 2 points
    There's a method to update really fast and smooth your linux node. I will try to explain, keep in mind that this tutorial is useful if you had installed the node from the github repository of scripts elrond-go-scripts. If you don't have the node installed from this repository this code can be wrong. I always make the installation of elrond-go-scripts on my home, be careful with the instructions that imply this folder. 1.- Before we start make a copy of your pems: mkdir ~/backup-pems cp ~/go/src/github.com/ElrondNetwork/elrond-go-node/config/*pem ~/backup-pems 2.- Close your node: If you use screen launch you can do: screen -S nameofyourscreen -X quit 3.- Update your scripts repo: cd ~/elrond-go-scripts/ubuntu-amd64 bash get-github-repo.sh 4.- Update your node from the scripts repo bash update.sh (I guess that you're in the same folder) At this point your elrond-go-node is updated, you need to restore your keys 5.- Restore your registered keys: cp ~/backup-pems/*pem ~/go/src/github.com/ElrondNetwork/elrond-go-node/config 6.- Maybe delete db, logs and stats Only If the testnet update require to cleanup all this stuff then: rm -r ~/go/src/github.com/ElrondNetwork/elrond-go-node/db rm -r ~/go/src/github.com/ElrondNetwork/elrond-go-node/stats rm -r ~/go/src/github.com/ElrondNetwork/elrond-go-node/logs 7.- Start again your node I like to launch it on screen but it's up to you: cd ~/src/github.com/ElrondNetwork/elrond-go-node screen -AmdS testnet ./node (it creates a virtual screen with name testnet and the node running inside) If you want to see the node running screen -r testnet If you want to exit the screen without stop your node Press Ctrl+A and then press D
  17. 2 points
  18. 2 points
  19. 2 points
    I just finished writing a Medium post on how to run and maintain one or multiple nodes in Ubuntu 18.04. I hope you like it and please send me feedback for improvements! https://medium.com/@haklander/run-and-maintain-one-or-multiple-elrond-nodes-in-ubuntu-18-04-5f5c9658e580
  20. 2 points
    For installing/upgrading one or multiple nodes in Ubuntu 18.04, an alternative set of scripts can be found here. It should be self-explanatory (scroll down for instructions), but if there are questions, I'd be happy to answer them! https://github.com/ahakla/elrond-nodes This may be integrated in the official ElrondNetwork 'elrond-go-scripts' repository, but until then you can just use the link above.
  21. 1 point
    We can discuss here about the tests of running the nodes on raspbian OS with Raspberry Pi devices
  22. 1 point
    Hello everyone, I'm Randy Aranta Lika and I'm from Indonesia. I'm older than how I look. Bachelor of Science majoring in Bioinformatics, master dropout due to series of unfortunate events. I had some experience on graphic design, web design, machine learning & big data analysis back in my pre-postgradute dropout days. Since then I went to make Android apps, virtual tour website, graphic designing, and video editing on my own. Now I do all this part time. I also like cooking so I ran a food stall full time around 2 years ago, but on the way doing it I realise I only enjoy cooking for people I love so I stop doing it 😄 I came from a Taoist leader family so I know alot about chinese philosophy. I'm also curious about other philosophy all around the world and ended up becoming a Nietzsche fan. Somehow I ended up to be an optimistic nihilist but I'm forcing the optimistic part. I'm quite a deep thinker so I can't help not to depress myself all the time 😂 I also learn about metaphysics and fortune telling due to my family background, and on the way, I also learn deeper about human psychology. I use these skill to do a private consultation, psychology reading, and fortune telling to help people in need using Instagram with my girlfriend 😄 I like the internet culture. I like how it can break the boundaries between human and pushes forward to innovate human's life. I've only been a Blockchain enthusiast for about 6 months. I love Elrond as a project, what it is trying to do, and the direction the project takes. IMO Elrond has what it takes to be a top leading blockchain protocol and is supposed to be used all around the world. However, a great project needs a great support in order to be adapted by the masses. If you are already invested in Elrond just like I did, let us all work together to help Elrond Network to achieve success together 😁
  23. 1 point
    Hello to all of you, wish the entire team success. I'm sure the project will succeed. 😀
  24. 1 point
    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!
  25. 1 point
    Guys, I'm now running my nodes with the scripts os SebastianJ. In htop (install with apt install htop ) I can kill one of the node's processes with F9 (SIGTERM) and then after a second I see the node process starting again. It's awesome what systemd does, I think. 🙂 What you do for, say, 3 nodes is: 1) You zip your pem files for each node ( keys-8080.zip for your 1st node, keys-8081.zip for your 2nd node, keys-8082.zip for your 3rd node) 2) You create 3 folders to hold your zipped pem files: mkdir -p ~/elrond/keys/8080 mkdir -p ~/elrond/keys/8081 mkdir -p ~/elrond/keys/8082 3) You copy each zip file to the right folder, one of the three folders you created in step 2 4) You stop your nodes with: tmux kill-server 5) You run Sebastian's scripts with bash <(curl -s -S -L https://raw.githubusercontent.com/SebastianJ/elrond-tools/master/setup/setup.sh) --nodes 3 --display-name YourName --start --systemd This will create 3 running nodes with node names: YourName-1, YourName-2 and YourName-3. --------------------------------------- You can see all your nodes' statuses with: systemctl status elrond@808*.service You can restart (stop and restart) all your nodes with: systemctl restart elrond@808*.service You can stop all your nodes with: systemctl stop elrond@808*.service You can start all your nodes with: systemctl start elrond@808*.service If you just want to do these things for just 1 node, don't use 808*, but for instance 8082. Instructions and code can be found here: https://github.com/SebastianJ/elrond-tools/tree/master/setup
  26. 1 point
    Elrond blueprint wallpaper. All the download links for wallpapers here. Since forum compresses - Full resolution download link: Blueprint - https://i0.wp.com/tarantulo.lt/wp-content/uploads/2019/09/The-Erlond-blueprint.jpg Rasperry Pi - https://i0.wp.com/tarantulo.lt/wp-content/uploads/2019/09/Erlond-rasberry-4k-Dark.jpg Bubbles wallpaper - https://i0.wp.com/tarantulo.lt/wp-content/uploads/2019/09/Elrond-desktop-4K.jpg
  27. 1 point
    Elrond blueprint wallpaper. Since forum compresses - Full resolution download link: https://i0.wp.com/tarantulo.lt/wp-content/uploads/2019/09/The-Erlond-blueprint.jpg
  28. 1 point
    📣 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 ! 🛡
  29. 1 point
    🌤 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! 🛡
  30. 1 point
    🚧 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 ! 🛡
  31. 1 point
    Have registered 5 more nodes. Will be running all 6 for this round! 🙂
  32. 1 point
    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
  33. 1 point
    I am very happy to belong this great community. We are going higher everyday.
  34. 1 point
    Welcome Sever from the internet! Great to have you with us 🙏
  35. 1 point
    I made this guide guys on how you will update your node .. https://medium.com/@jeff.penaflor1983/tutorial-on-how-to-update-your-elrond-node-on-the-latest-version-windows-version-c13deac00b0?sk=6c0f8763bea4a3774f8ba27baeac43d1
  36. 1 point
    If you're already in Round 1 and don't want to add more nodes, you don't have to submit this form!
  37. 1 point
    Awesome! I've started making a living as a validator:
  38. 1 point
    Week #40 | Monday, September 30 – Sunday, October 6, 2019 1. Preparations for the Battle of Nodes (improvements, bugfixes, benchmarks, tests) 2. Initial implementation of a System VM and smart contract for validator staking, that will allow nodes to join the network real-time, through a fast protocol built-in mechanism 3. VS Code extensions can handle WASM smart contracts written in C and Rust. Work in progress to enable debugging of such code in the IDE 4. First flood attack on our testnet v1.0.19 made us tweak the libp2p's parameters and craft additional anti-flooding capabilities 5. Fixed the arm64 build so we can now run validators on raspberry pi4 6. Refactoring of shard processor in order to remove duplicate code and group all arguments in a single structure 7. Snapshot of the trie for saving the current state of the trie in a separate database. 8. Compaction of miniblocks to allow us to add more transactions in a block and decrease the data that needs to be propagated to metachain. Throttled mini blocks creation to a defined maximum value, to avoid bottlenecks with blocks with a too higher number of miniblocks 9. Added a local cache of meta blocks, used for processing current shard block, to avoid situation when a full pool of meta blocks (happening especially when a node is bootstrapping), would generate situation when needed meta blocks are in fact evicted from pool 10. Validator's uptime statistic improvements for the Battle of Nodes 11. Added more data in Elastic Search related to consensus group, will be visible in the testnet explorer 12. Economics rewards metrics for termui. Soon an estimation of how many ERDs you can earn 13. Fixed bug that caused in some situations the block to be rejected due to missing reward transactions 14. Fixed a bug after merging with the economics part which didn't allow the node to start 15. Further bugfixes and improvements
  39. 1 point
    I think everyone should know, Sever Moldovean is one of the reason this forum can exist. He designed and created the forum. Salute to you man!
  40. 1 point
    Hi guys , I dare you to take a selfie wilth elrond and put the hashtag #selfieElrond Here's mine
  41. 1 point
    Hi! I followed Fast Install & Update Elrond Nodes” by Jose F. Aznar. No problem!
  42. 1 point
    I emoted a sad thingie to your post, @Danny Serb. Will change to smiley if you upload a profile pic!
  43. 1 point
    I think that it can be good idea to put some media resources in elrond webpage. To make easy to the community to have the logo, some staff fotos, headquarters, fonts, and so on. It's really useful for content creators to have one official media set. Usually it goes in the footer of the main website. On this way if for example "ccn.com" wants to write a new about elrond network, they can go to get official media images.
  44. 1 point
    yes, of course! This should have been copy-pasted from docs.elrond.com. Good catch, will fix!
  45. 1 point
  46. 1 point
    Level 2, discover the possibilities:
  47. 1 point
    The Telegram link to BattleofNodes mentioned in this article seems to be broken 😞 https://t.me/BattleOfNodes
  48. 1 point
    stay updated mate by following their social media channels and also by joining on their telegram group.
  49. 1 point
    Interesting thread Alwin. I will post here one of the best videos that I know. The interview of Brad Laurie to Beniamin Mincu
  50. 1 point
    Hi Force! Yes, the Elrond code is completely open source, this was decided in June, see “After Exceeding 10k TPS in Testnet, Elrond Is Going Open Source” by Beniamin Mincu https://link.medium.com/XQdqfSkMn0. The complete Elrond source code can be found here: https://github.com/elrondnetwork. Best regards, Alwin
This leaderboard is set to Bucharest/GMT+03:00
×
×
  • Create New...