Join the discussion in DAOBet Telegram groups:
Join our social media to keep up to date with all the announcements: Twitter, Facebook, and LinkedIn.
“During the Game of Stakes on DAOBet, we discovered and fixed bugs, identified flaws in the documentation, and gained invaluable experience. We thank all the participants of GoS for their active involvement and will be delighted to see them all again in the DAOBet mainnet!” – comments the DAOBet team.
Game of Stakes has come to an end, and we are delighted to announce our finalists!
- EOSRIO
- FELVALIDATOR
- KAISERLABS
The Top-10 also included the following teams:
- P2PVALIDATOR
- EVERSTAKE
- MIXBYTES
- MINTERCAP
- WESTAKING
Throughout the 10 days of the game, we learned a lot about how DAOBet behaves under combat conditions as the DAOBet blockchain survived several combat benchmarks.
The participants performed their own tests of DAOBet, deployed contracts for testing, and loaded the network with transactions.
During the course of GoS, the DAOBet blockchain reached 12,000tps at some point. This is a great indicator. We saw how RANDPA behaves in the real world, where validators are located in different parts of the world and have different configurations of equipment. The participants deployed additional nodes, communicated, collaborated in the game, and shared their expertise.
The game began at 15:00 UTC. At 17:00 UTC, the activated stake exceeded 15% and the validators got the opportunity to produce blocks and earn VPs.
Launching a decentralized network, where the nodes are located in different corners of the planet and have different time zones is an interesting task. But our validators were able to join the game in just a couple of hours. At the beginning, the players were given a version of the GoS node in the form of a docker. But many ignored this and built their nodes based on source files. This helped them maintain the node in combat mode, as later, bugs interfering with the production of blocks were found in the node.
Over the next few days, we loaded the network with transactions. These benchmarks affected the positions of the players on the tournament scoreboard.
The players’ nodes skipped blocks and did not earn any VPs. Also, the validators themselves did not disregard attaining benchmarks for the sake of getting to the top.
Some time later, more than 6,000 transactions were identified in blocks 769,051 and 769,052. Later on, the participants also loaded the network. One of the participants deployed the benchmark EOS contract for online transactions.
Join the discussion in DAOBet Telegram groups:
Join our social media to keep up to date with all the announcements: Twitter, Facebook, and LinkedIn.
Top comments (0)