Hi Nav Coiners!
Time for the weekly update. It's been a pretty surreal week with the Thunderclap and Anon Launch date announcement. Lots of new interest in our project and lots of effort being put in by community members all across the globe.
Global TranslationsWe now have forum threads in multiple languages covering a range of posts
Spanish -
https://bitcointalksearch.org/topic/ann-nav-nav-coin-transacciones-anonimas-android-5-pos-1655866Dutch -
https://bitcointalksearch.org/topic/ann-nav-nav-coin-anonieme-tech-lancering-1-nov-1656770Portuguese - Coming Soon
If you are fluent in a language that you think will be interested in Nav Coin and can translate our content for us, please send me a PM. We are currently offering 1000 NAV Bounty for thread translations which we have chosen and approved.
Our Announcement Thread has also been posted on icotimeline.com check it out here:
http://icotimeline.com/blog/2016/10/23/navcoinNavtech Anon BetaWith November 1st one week away, we are closing in on the release candidate version of the anon scripts. I have just released a new version to the servers today for the beta test group and I am hopeful that this version is the one which we will release with the only addition being more unit tests.
I have successfully implemented and tested the queuing system at maximum payload. I have sent 10 x 10,000 NAV transactions within in the 2 minute processing cycle window. The server is only loaded with 50,000 NAV so it can't process the entire amount in one cycle. I expected a queue to form and for the payments to get processed in 2 cycles. This test was successful and I received all 100,000 NAV back to my wallet in the expected time frame.
I have also implemented a queue checker when your wallet requests an available incoming server. If the queue is more than 30 minutes long (eg. there is a pending transaction with 60 or more confirmations) the server will tell the wallet it is unavailable and your wallet will try the next server.
I have also done some work to refine how the outgoing servers are refilled from the incoming servers which will allow for more randomness within the cluster when it comes to choosing servers to transact with.
Navtech Anon BetaProgress Report
Phase 1: Low value transactions with small test group on single server pair - complete
Phase 2: Medium value transactions with large test group on single server pair - complete
Phase 3: Medium value transactions with large test group on multi server cluster - complete
Phase 4: Large value transactions with large test group on multi server cluster - complete
I am confident in this current version and when the beta testers are happy I will label this as our release candidate version. I will be steadily working towards my goal for November 1, to implement as many unit tests as possible.
I will keep you all updated with the progress from the beta test group and especially if we encounter any late coming issues.
Not much else to report this week. We are at the business end of the Public Anon Release, so the whole team is working hard to pull together for November 1.
To keep up with the latest, follow us on twitter and join us on slack!
Talk soon,
Craig.