Because 1.0.8 has brought with it many new changes (more detailed technical blog post about the changes soon), we need to start testing these features to make sure that we're ready for the continuation of the main network. Because of this we will start a temporary testnet which will enable exactly this.
How to get involved
It should be noted that this is mainly for the more technologically savvy people. Most importantly, you need to be able to launch IRI via the command line. If you don't feel confident doing that, don't worry as you don't have to join the testing.
For everyone else that wants to get involved, here are the steps:
- Download the latest Nostalgia from Github (https://github.com/domschiener/nostalgia) and 1.0.8 (http://188.138.57.93/IRI-1.0.8.mu.jar). Make sure to delete your entire database (all .iri files) before launching IRI.
- Join the
#nostalgia-testing channel on Slack.
- Find neighbors from that channel. Make sure that your neighbors are running
1.0.8.mu. You should not have neighbors who run a previous version (this is a private testgroup after all).
- Start breaking stuff. Detailed report on what to test follows below.
If you want to get tokens, log into an empty seed (first to do it may get a big surprise...).
What to Test
This nostalgia version was pretty much written anew and it's over 1500 lines of code, so there is a lot that could break. Luckily with this testnet we are allowed to lose our tokens. It should be noted that you can't login with your seed, as you won't have any tokens associated with it.
- Check if Nostalgia displays the correct transaction hashes, addresses, values and bundles.
- Make sure that there are the correct error messages
- Make sure that your inputs are spent correctly, search for any race conditions that may occur.
- Try everything a bit (replay doesn't work btw, haven't implemented it yet).
How to Test
Obviously the best way to test is in the group and report anything that you may find suspicious, unintuitive or if you think something is broken. This means that a) use the Slack group and b) use Github to report any issues you have.
It should also be noted that improvements are very much appreciated. So if you have any suggestion on how to improve something please let us know.
