Our Jungle story
From the very beginning of our activity in the EOS community as a candidate for the block manufacturer, finding a stable testnet and participating in it were our most important tasks.
Optimizing hardware requirements and developing an appropriate work ethic as BP is undoubtedly crucial, especially in the initial stages of the mainnet.
We were able to find all this on Jungle Testnet (you can check the current monitor here), created and relentlessly administered by @cryptolions, which we would like to thank for, outstanding job guys!!!
We are even more excited that also after starting the mainnet, Jungle will continue to be a testnet, hence to be a testing ground for Block Producers and developers wanting to create dapps.
EOS Emerge Poland performance in Jungle
Our accounts on subsequent versions of Jungle Testnet were: racoon and creazyracoon (after all it’s a Jungle ;). Currently, emergepoland also joined the rest of the accounts and is based on the current snapshot and EOS 1.0.1
Our main objective at Jungle Testnet was to stay constantly available, adjusting the configuration to the latest updates and maintaining constant communication through the Telegram group - even at the expense of a good night sleep ;) This is what allowed us to be able to track any emerging problems and solve them asap.
With a clear conscience, we can admit that in the last, busy month, our EOS Emerge Poland servers worked flawlessly and without stopping, which partly shows the strength of the testnet.
During this time, we managed to maintain an efficient network constantly producing blocks, but our greatest satisfaction was from the restoration of chain, without the necessity of its complete restart, thanks to the collective work of all jungle members.
And yes, there were bad moments:
...But after every storm, there is a rainbow
Our configuration composed of hidden producer and fullnodes behind load balancer has passed the test excellently, working without any hiccups and providing constant, full connection.
Stress tests
In our activities, we were also actively involved in checking the network performance, by connecting our nodes constantly spamming the network with transactions (a tool provided by Crypto Lions https://github.com/CryptoLions/TX-test-sender. )
From the moment when testnet started to work stably for a long time, it became clear that the next important step would be to check the strength of the network for the pressure of the transactions - particularly with launch right around the corner.
To our joy, with each successive test, the results were more and more satisfactory - even though we broke the testnet couple of times during these tests ;)
Our spamming badbadracoon in action ;)
Thanks to one of these tx-parties with our participation, the network reached a record performance of 1475 TXs per second
Bnet nodes testing
The above result was somewhat possible thanks to the bnet nodes we tested (new multithreading p2p protocol)
What we have learned?
In summary, the production of blocks on Jungle Testnet, confirmed our belief that in the work of the block producer, the most important is not the equipment itself, but communication.
Human factor is most often unreliable, so we have approached Jungle production with the same commitment as we would approach the production on the mainnet.
It was particularly important to develop a specific sequence of actions in the event that the network encounters a bug or it is otherwise impossible to move last irreversible block. It was mostly about working out a code of emergency progress to which block producers must adhere to deal with the problem with the least possible detriment to the smooth operation of the blockchain:
Worked-out restart sequence: restart the nodeos -> if it fails -> replay -> if it fails -> hard replay -> if it fails -> resync (last resort and not recommended)
- In our opinion, nothing is better able to prepare for the challenges waiting for the block producer than to get the correct skillset on the testnet. We hope that - like us - other candidates for block producers also realize that this is a 24/7 work, regardless of time zones, especially in the initial period of the mainnet.
That being said, with the knowledge we have gained, we are fully ready for it, with full awareness of the enormity of effort and work that will have to be put in.
We were honored to be able to exchange views on daily basis with core devs, including Greg Lee and bytemaster himself. Their participation and priceless insights each day allowed us to better understand what EOS blockchain is all about.
At Jungle Testnet, together we have managed to gather an excellent group of people actively working for the development of the EOS ecosystem, and watching its development was something special.
And this is the best testimonial by far:
Go EOS!
Contact:
E-mail: support@eosemerge.io
Website: https://eosemerge.io
BP Listing: https://bp.eosgo.io/listing/eos-emerge-eos-poland-2/
Steemit: https://steemit.com/@eosemerge
Telegram: https://t.me/eosemerge
Twitter: https://twitter.com/eos_emerge