Mainnet Progress Update, Huobi Community Vote and More

In line with our previous updates, we will be supplying a progress update of the Oyster Mainnet; however, today’s post will be detailing several important developments before discussing the Mainnet progress.

Oyster PRL Included in Huobi Public Community Vote

The Oyster team is excited to announce that PRL will be added to Round 2 of Huobi’s public community vote on May 25th, 2018. We strongly encourage our community to take part in voting for our listing, and the more participants involved in this vote, the more likely PRL will be listed on Huobi, one of the largest Asian cryptocurrency exchanges. Huobi is the third largest exchange in 24-hour volume (just below Binance); thus, this listing is a massive opportunity for Oyster, and we believe that our thriving community can succeed at getting PRL listed.

NOTE: Huobi will be hosting another community vote before the May 25th community vote that PRL will be involved in. We will provide a link to the May 25th community vote once it has started.

Oyster Seeking an SEO Manager

Oyster is currently seeking an Search Engine Optimization (SEO) manager with a minimum of 3 years experience. Knowledge of Japanese or Mandarin considered a significant plus. If you are interested in applying for this job, please send your CV to Chris Bamber at [email protected]

##Oyster SHL Listed on KuCoin

For those who have not seen our Twitter or Telegram updates, SHL has been listed on KuCoin, and further information regarding the listing can be found here.

Mainnet Progress Update

Today’s progress update will focus on the week of May 13th — May 18th, 2018.

This week, the development team worked on updating the encryption of treasure payloads on the broker node and updated the web nodes’ decryption to match, and successfully recovered a few “dummy” treasures while QAing. The team also added code to the broker node to pad the treasure chunks with random trytes, making it difficult for malicious actors to determine that they are treasure chunks. Additionally, the team fixed some “busy buffer” and “deadlock” errors on the broker node associated with the broker node’s database and updated encryption and decryption on the web interface, allowing the system to store a full 1kb in every chunk.

Further work was completed on the claiming, burying, and sending transactions that interact with the OysterPearl smart contract and the Oysterby test network within the broker nodes, as well as the claiming API used in the broker node. The team also worked on the Subscription of Transactions which involves determining whether the results are true/confirmed, false/failed, unconfirmed, or a timeout.

In addition to the work mentioned above, the development team worked on optimizing CPU usage for proof of work, as well as preparing documentation for the QA process involved in the Mainnet. Additionally, the team trialed several different approaches to implementing the ‘fragile loop’ that will stop a user’s device from completing proof-of-work if too much computing power is used. Finally, the team added gas price recommendations to the web interface when sending PRL to the designated address.

We will continue to update the community on Mainnet progress every week leading up to the launch date of May 29th. Any questions or comments are encouraged to be posted to our Reddit, or Telegram channel.

Website
Medium
Reddit
Twitter