Topic: [ANN]🔵🔵 OYSTER 🔵🔵 Anonymous Storage Generates Revenue for Websites - page 39. (Read 73403 times)

Of course Oyster doesn’t *have* to give more money than ads, that is just what I’m wondering - will oyster be economically motivated or will it be motivated through other means (security, privacy, etc)

I just love it! Yesterday Oyster took the tenth place in the vote for listing on Bibox, now we are in third place. Keep it up, Oyster!

It's an cyclical ecosystem. It requires both sides to work. Website monetization and storage adoption

That's why I linked that response. Website owners can call themselves lucky if they get 35% of the web revenue cut.

The whole electricity argument is moot. Who cares if one webnode is operating at a loss. The website earns PRLs based on paralleling many many webnode's PoW. Website visitors are spending electricity either way by just being on their compute

Oyster Development Update

Today’s development update focuses on the work completed for the week of June 24th to the 29th.
This week the development team has continued to work on the jobs that use Oyster’s eth_gateway and interact with the Ethereum blockchain. The team finished QAing the claim_unused_prls task from the previous week and are now working on a new task called claim_treasure_for_webnodes. With this task, instead of immediately invoking ClaimPRL() when a Webnode has done the PoW and claimed a treasure, the team will add the claim to a table in the database and have a task run which will call methods needed to claim the PRL for the website owner. This way, if the first attempt to claim the PRL does not succeed, the broker node can keep trying until the PRL are successfully claimed. Also, for various bury/claim operations, the team has to send a small amount of gas to the affected addresses. Over time this could add up to a lot of wasted ETH if the bury/claim calls don’t use all the ETH that was sent. Thus, the team has added a method to retrieve leftover gas if there is enough left to justify making a new ETH transaction to get the leftovers, making the system more economical.

In addition, the team has continued to work on integrating a streamable module for the front-end to handle larger uploads. Additionally, the team has been working to establish engineering practices with the goal of increasing the development velocity and code stability. Furthermore, the team has continued work on the Badger DB integration and fixed several related unit tests that were failing, as well as worked on Code Climate refactoring and unit testing the changes for the next broker node release. Also, the team worked on automating the deployment of the broker nodes in a staging environment

Further work has been completed on the python reference implementation of the ‘rev2’ update to the Oyster Protocol. The team focused on bringing every feature to a functional state (right now metadata works fine for any arbitrary number of files, along with data map generation, password protection, etc.) and documented every function and method using the same standard currently in place for the Oyster development team to improve readability.

The development team has been focusing on optimizing developer activities to increase efficiency and code quality. The team added automated code quality checks on Oyster’s central repositories, so developers have visibility/impact of their pull request on the code base. They also documented how to work with Travis CI locally to simplify debugging of build scripts and created and documented a TypeScript migration plan so the team can start adding types to our code. The team will continue working through the weekend to start boosting the team’s E2E tests. Finally, the team has been working on upgrading to Webpack 4.

Bibox Community Vote

For those community members not yet aware, PRL has been included in the Bibox exchange’s community vote. The top three projects will be listed, and there is currently a 400K PRL voting reward in place if PRL finishes in the top three. Votes are submitted using the Bibox Token (BIX). The reward will be distributed based on the total number of votes, as well as the individual votes per user (i.e., 400k/total votes * a user’s votes).

We ask our community to note that any BIX token used for voting will only be refunded if the project for which a user has voted for does not place in the top three, and subsequently does not win the community vote.

https://medium.com/oysterprotocol/june-29th-development-update-e3f27058f839

Another week with lot of coding for front-end enhancement and overall stability of the Oyster Protocol has been continuing. This weekly development series is so much interesting that I wait for next immediately after reading actual one. Great work is being done and built on this platform which needs only more time to make it successful in future.

Voted just now. Currently we ranked number 2! We can maintain this momentum by voting in the last day. Great job to the community participants. OYSTER got an awesome community behind their back.

It is nice to see voting is active now even we are at low position but hopefully by end of this competition it will get succeed to get nice position and will win this round. We must support this token to make it list on that exchange and get rewarded from prize pool.

Do this 400k PRL came directly from developers funds? Or is it just a promotion of Bibox when it hits the top 3 ? Thank you in advance.

A voting reward of 400K PRL has been added to the @Bibox365 community vote! Help get $PRL into the top 3 to receive the reward.

Can a big website with alot of visitors copy/paste the oyster protocol, create a new coin which they own all of and let the user do pow for them to get free storage. And is scaling even needed for that?

Voting for listing on the Bibox exchange goes well. Oyster is now in 10th place, but the gap with the third place is only one and a half thousand votes. There is a chance.

PRL has participated in the voting for listing activity in Bibox, support us and voting for the rewards! https://www.bibox.com/cinformation?id=700

The BIBOX voting has started.

https://www.bibox.com/votelist

First PRL must be in a solid state to begin the SHL development. Before that it doesn't make any sense to start a big front on the development of SHL, since it is using the same web nodes to establish the meshnet. Plus, the web nodes aren't utilized on any website yet - So TL;DR: PRL must be rock solid before we start to thinking more in-depth development of SHL If. you have any questions regarding the whitepaper and usecases, I would still be glad to help you out

I don't know that, I'm sorry. You could go to the look out and see which other projects taking part in the voting if you want. We will see in at latest tommorow

Oyster aims to fully decentralizing it while making it anonymous/encrypted. The data will be stored on the IOTA tangle and PRL will be pegged to a storage value via a smart contract. In the end it will be most likely the most decentralized form of storage there is...

Community's support is pretty well available for PRL to make its way on new exchange. We have seen good fight i previous voting contests and this time need little extra effort than last time. It is good that we have more time and community started to prepare mentally already to take PRL at Bibox.

Let's make it Happen! Let's spam out this one to all community channels of OYSTER. This will surely make a difference when it hits Bibox exchange. This time, we gonna get in to this exchange.