NEM Symbol - Community Stress Test planned for 28th Jan 2021

Hi all,

Quick post to ensure everyone has seen the announcements from NEMTus today, any questions please speak to @h-gocchi and the team at NEMTus.

Thankyou to NEMTus for co-ordinating a global testing event that all of the community can get involved in, this is an important step towards ensuring the platform is ready for launch.



The top level current information (text version of the image above):

  • Testnet patch (complete)
  • NGL automation testing on empty network (complete - all open source)
  • NGL 100tps stress test on empty network (complete)
  • NGL 150tps stress test on empty network (complete)
  • NGL 400tps stress test on empty network (complete)
  • Public release and reset (complete)
  • Community nodes come online (ongoing but mostly complete)
  • Community testing (ongoing)
  • NEMTus Test event (28th January)
  • NGL final stress test after we have community nodes and data on the network from above (awaiting above)
  • Assessment of results from community and final NGL stress test, snapshot and launch date decided and announced
  • General soak to launch

The Stress Testing Fest organized by NEMTUS is a community event and the fest. Therefore, we will do the possible tests within this event.

After this testfest, if we find any bugs or other issues, we will report them to NGL, who will then investigate and analyze the causes, make improvements and fixes, and test them.

Therefore, this testfest is not the “final test” of Symbol, and there will still be NGL testing after the testfest. However, there is a misunderstanding in the community that test fest is the “final test”.
Also, some people think that the snapshot date will be decided after the test fest, but you will find out that this is not the case.

The above is correct, right?


Thanks @h-gocchi

The above is correct, summary below:

  • The NEMTus testing is not the “final test” and never has been communicated as such (or if it has it was unintentional). It was originally planned independently of any other testing or launch plans.

  • If issues are found they will be raised on Slack2 in a specific template that NEMTus have or Github and assessed by Core Devs + NGL

  • We will not know any issues are serious until they have been assessed, if they are we will need to plan accordingly how to resolve them etc

  • The NEMTus Test Fest performs a couple of important roles. It brings community nodes and data onto the chain and distributes a load test more widely than can be done be a single entity and is very helpful for Mainnet simulation.

However, there is a misunderstanding in the community that test fest is the “final test

  • I have not seen this personally, if it is the case then it is incorrect, although it is a very important step in the revised testing plan since the issues have been fixed following the Dec stress test.

  • For the avoidance of doubt, the final testing will be after any issue resolution from the NEMTus test and NGL will run a final stress test after the NEMTus event, exact timing to be decided once we see if/how many issues are found and what impact that may have on resolution timelines.


Thank you for your clear reply!


Does that mean there will be no official statement after the NEMTus test? All insights how the test has runned and if at all and what are the issues are? I would ask you please to make an statement/report after the NEMTus test even if you dont know is there are serius issues or not. I think the community has rights to know it in first place as well as the team members, or I think some concers about insider thoughts will come out again from NEMbers just like it was last time. Please.

1 Like

Insights on how the testing ran, what issues were found etc will be known by the people running it and logging them (the community).

Im sure the NemTus team have a plan for summarising how it all went and I am happy to support with that. NGL is not running the test and wont have any non public info on how it ran.

If anything extra is known short term we will communicate it but I dont expect to have much if anything to add until any issues are looked at. Hence the statement above.

I agree the community does have a right to know…and has a mechanism to do so, as stated above…all the issues are logged in public on Slack and/or Github and the community is running and monitoring the test.

There is (and has been) no inside info as suggested, it takes time to look at issues as they are occur, understand them and be able to clearly communicate what happened/can be fixed.

It is also worth noting that everyone is free and encouraged to contribute to that process. The code is open, issues are open, nodes can be run and debugged by anyone with the skills/interest to do so. The “official” tech teams do that and communicate as soon as practical while doing it, other developers in the community also do it and submit fixes for issues.


The NEM2Slack has not been very active lately.
Hopefully there will be a few more participants.


I agree, I would like to see more participants in Slack.

Some people may have seen the recent update from NEMTus on Twitter/website/telegram:

The process to get to the Testfest has been (simplified in my own brain)

  1. NEMTus created the tooling for the original test, and updated it over the past few weeks for this one, the tools were tested as part of this

  2. Some pre-testing was done by NEMTus over the past 1-2 days to allow the public test to run smoothly

  3. The public Testfest runs on 28th.

An issue has been found at step two (yesterday) and has now been reproduced by NEMTus on Testnet. As I understand it, testing will continue as planned but try and avoid that known issue, the issue is being looked at by the tech teams.

The issue can be followed here:


How can i create an email with domain so i can follow this? Or slack is only for teammebers?

2 Likes doesnt need a email address and is publicly available.

I’ll ask someone to track down an invite link and post it

1 Like

You should be able to join via this link


Thank you it works for me!

1 Like

The community test ran successfully today, load was sustained for approx 3.5 hours

Final tweet as it closed from NEMTus is below. @h-gocchi and the NEMTus team will now absorb and summarise the results and post them so they can be assessed.

Final tweet:

This was a really well run event and a credit to everyone involved, it ran smoothly, was well attended and definitely put the network under load, which for the most part appears to have run well under load (the known issue was reproduced at the end of the test successfully and on purpose, to allow further investigation on it).

Next Steps

  1. NEMTus will collate and report findings, and post publicly when done
  2. Tech teams will assess the findings and work out if anything is critical etc and post findings
  3. Snapshot and Launch will be assessed but entirely dependent on point 1 and 2.

It is likely to take until early next week for point 1 and 2 to happen and point 3 won’t happen until they are complete and any resolution is known (if resolution is needed)


I have said many times, the next launch date you announce should be a confirmed date. We no longer need a launch schedule that includes the possibility of delays. Let’s be clear about this.


How long does it take at least to start symbol?

Good job!

I’m confused if you actually want the price to go up. Continuing to spew fake FUD doesn’t help. Maybe try being a little more positive. Good for your mental health :+1:

Quick update on the “Daoka-Canon” issue that affected some harvesting nodes.

The issue has been identified and a resolution is being tested over the weekend. It is likely we will issue a patch release prior to the final NGL Stress Test to resolve that issue beforehand, further updates early next week.


How long does the final NGL Stress Test plan to last and what kind of testing will be done?