Today’s update focuses on the work completed between August 5th — August 10th.

This week, the development team has continued work on pulling all data_maps and completed_data_maps rows out of SQL and putting all chunk data in badger. By migrating this data to Badger, this will make the broker nodes more efficient. Currently, uploads and downloads are working, but more QA is still needed, and the unit tests for the broker nodes need to be updated. Additionally, the development team (Rebel, specifically) recorded a video of the broker node and web node working together to claim a treasure. This video can be found here.

The team has also continued to experiment with doing PoW and broadcasting in AWS Lambdas as well as doing QA and measuring to see how much this can help speed up uploads, especially when concurrent uploads are happening. The team is interested in using AWS Lambdas in the Oyster backend, because they can allow for more PoW for batches of data chunks to run in parallel, increasing the throughput of the Oyster Storage platform.

In addition to the work mentioned above, the team has also been working on finding implementation alternatives for the web node to support iOS devices. The Oyster community had brought to our attention that the current web node demo that was released last week does not work for iOS devices, and so the team is currently looking for alternative methods to solve this issue.

The development team also completed work on updating methods on Oyster streamable so that polling can resume on upload progress when a user leaves the Oyster Storage page. For example, by decoupling the logic to check upload progress from the logic to upload a file in the streamable library, this will allow the Oyster infrastructure to poll any upload based on the handle, ultimately allowing users to navigate away from the page without interrupting their file upload. Users would be able to bookmark their upload page and return to that page to access their Oyster Handle required for downloading the file at a later time. The team will implement changes to the Oyster Storage’s frontend once these changes have been deployed to Oyster streamable.

Finally, the team has been QAing the smart contract unit tests to exercise all methods of the contract with all the setup included for each scenario, and the team has been working on improving the error response time for users (as opposed to continuing to process the request, the web interface will instead return a 400 error to the client).

As always, we encourage our community to post any questions or comments regarding these development updates to our Reddit or Telegram channel.