Bitcoin Forum

Read the Announcement:

https://medium.com/oysterprotocol/dawn-of-a-new-era-3ca2e2f5a1c6

Read the Whitepaper:

https://oysterprotocol.com/#whitepaper

Oyster Shell: SHL Explanation

https://youtu.be/of5C76y5sYU

Quick explanation:

Shells(SHL) are used to pay for connectivity and Dapp operation across the Oyster meshnet, whilst Pearls are used for static data retention on the tangle. Shell is not pegged to storage like how Pearl is. In the future you will be able to use Shells to access the decentralized web, connectivity that entirely bypasses ISPs and centralized infrastructure.

Potential use case scenarios:

You want to call your friend in a decentralized and secure way. The app on your phone looks for peer-to-peer connections (Bluetooth and WiFi) with other phones running Oyster nearby and a meshnet call is made, therefore bypassing the ISP. SHL is used to pay for connectivity instead of a monthly ISP bill. No third party can trace, block or listen into the phone call.

The Oyster chat group migrates from Telegram/Slack to the Oyster chat Dapp. The Oyster team pays the Oyster network in SHL and PRL to run the group chat Dapp.

You want to access content that is blocked by your ISP and avoid getting tracked, your computer connects directly to the Oyster meshnet by finding a peer-to-peer neighbor (Bluetooth, WiFi, LiFi). Your SHL wallet is used to fund connectivity and bandwidth usage.

Oyster SHL Snapshot Complete:

Oyster is happy to announce that the Oyster Shell (SHL) blockchain snapshot has been successfully completed at block number 5436000.

Contract Address: 0x8542325b72c6d9fc0ad2ca965a78435413a915a0
Symbol: SHL
Decimals: 18

https://medium.com/oysterprotocol/oyster-shl-snapshot-complete-e1afb0219146

Oyster Protocol. Bitcointalk:

https://bitcointalk.org/index.php?topic=2222507.0

Social media:

Telegram: https://t.me/oysterprotocol
Twitter: https://twitter.com/OysterProtocol
Website: https://oysterprotocol.com

Note: I am not a part of the Oyster team and am not a point of contact for this project. For any questions related to the project, kindly contact brunoblock on Bitcointalk forum or the team members via Telegram.

Political motivation from giant Corporations like Facebook and Google and large ISP’s, who are the gatekeepers of net neutrality, are breaking the Internet for the common individual

Oyster SHELL circumvents this control by creating a distributed meshnet. 

Users can now access the internet at a fraction of the cost completely anonymously and from any global  location away from prying eyes of these politically motivated establishments
 
If PEARL is like the foundations of a house, SHELL is like the electricity supply
 
SHELL enables efficient, encrypted low cost, internet access and peer-to-peer communication between any two endpoints that participate in the meshnet.
 
SHELL enables the decentralized execution of javascript dapps.
 
As more people join the network via IOTA then Oyster protocol will act as a massive organic super computer, with PEARL facilitating long term persistent storage and SHELL facilitating volatile memory, instruction execution and data communications.

Thus removing the need the for centralized infrastructure of ISPs

Oyster SHELL and the distributed meshnet is the future of the Internet as know it!

MrRedPanda:

Great project! I do not quite understand how this will work, but the idea is simply excellent. Good luck!

The distribution of SHL tokens for users holding their PRL in personal wallets (e.g., MyEtherWallet, Eidoo, etc) will begin next week. Users will need to add the custom token information for SHL in order to view it in their wallet once SHL has been distributed. That information is listed below:

Contract Address: 0x8542325b72c6d9fc0ad2ca965a78435413a915a0
Symbol: SHL
Decimals: 18

For those holding their PRL on KuCoin, SHL tokens will be distributed to your exchange wallets in the following weeks.

KuCoin supported this airdrop, does this mean that the new token will immediately be traded on the KuCoin? It would be convenient, you do not need to wait for additional listing

Take a look at the post #3

This is perfect move to separate the discussion for SHL to be treated differently. This will be helpful for people to understand more better way the usage and purposes of the SHL token inside the platform. I see huge benefits both strategic and promotional in these measures taken by team. It is really a new dawn for independent future for everyone.

It sounds nice the team is moving forward with great spirit you should keep it up it will be worth for it. Congrats for this big success snapshot has been taken smoothly and I hope the process of distribution method will happen on time.

I also bought some PRL's because of the snap. But after the snapshot I sold them and now I'm waiting for my SHL's. That will certainly take a few weeks. Let's hope she will develop SHL well. The market is already recovering.

Can you explain to me the difference and main differences between PRL and Oyster Shell (SHL) in terms of functionality, goals, etc.? Which token do you consider more attractive for purchase at the moment?

You can watch video from the very first post there is explanation about Shell (SHL) token and the main token Pearl (PRL). We are already in new week now all eyes are on next big events of distribution and launch of Main Net with this month. This means in maximum two weeks platfrom should be up fully functional.

That is Kucoin's announcment regarding the SHL airdrop:

https://news.kucoin.com/en/oyster-shell-airdrop-for-all-oyster-pearl-holders-on-kucoin/

Hi!
I am still waiting for oyster shell airdrop. Am I alone?

Oyster PRL is meant to be a stable asset, due to the peg to anonymous decentralized encrypted storage.

However, the dapp layer of Oyster is a part of the oyster roadmap and was already mentioned in the whitepaper of PRL, but due to the peg, PRL cannot be used to pay for operations and connectivtiy on the Oyster meshnet formed by webnodes.

Therefore another token is needed. Oyster SHL will be used to pay for the dapp operations and connectivity in the Oyster meshnet (and so PRLs keep restricted to the peg of storage.)

This could be links to your interest, if you want to know more about Oyster SHL:

https://medium.com/oysterprotocol/dawn-of-a-new-era-3ca2e2f5a1c6 - Medium post
https://medium.com/oysterprotocol/shell-shl-update-and-new-hires-87978ad687a9 - SHL announcment

Our two explanation videos should help you to get a general idea of the usecases of botch tokens and how they differ from each other:

https://www.youtube.com/watch?v=5j3_kbEOZZU - Oyster PRL Explanation video

https://www.youtube.com/watch?v=of5C76y5sYU - Oyster SHL Explanation video

Hi, the Oyster Shell (SHL) blockchain snapshot has been successfully completed at block number 5436000. The SHL smart contract was deployed earlier Apr 14, and can be viewed here: https://etherscan.io/token/0x8542325b72c6d9fc0ad2ca965a78435413a915a0#readContract

The distribution of SHL tokens for users holding their PRL in personal wallets (e.g., MyEtherWallet, Eidoo, etc) will begin next week. Users will need to add the custom token information for SHL in order to view it in their wallet once SHL has been distributed.

thanks for the information
I'm very happy with this, I'll see a video of your project so I can understand about your project..

Roadmap 2018-2019:
Decentralized Oyster Applications

After the web node mesh net has matured, Decentralized JavaScript applications can be easily written and executed on the Oyster Network.

Oyster Competition:

https://docs.google.com/spreadsheets/d/1nps9uBWfl9ODg8JZv7iX4jyZfNLPzn2OaOg3M2GDe9k/htmlview#gid=0

A Detailed Drive Into Oyster Protocol:

https://www.reddit.com/r/Oyster/comments/89uf3t/a_detailed_dive_into_oyster_protocol/

Im glad that Kucoin choose to support the SHL airdrop. That being said, will Kucoin add SHL later on?

Who is interested must watch for refreshing the concept by looking at the comparison chart. It is amazingly different and of course will be great competitor to already service providers in these fields. Oyster platform is ahead of its competitors plus revenue generation feature makes is unique with high potential.

Only way to stock up these tokens will be buying at Kucoin most probably. I am interested to pick up some being quite hopeful to see the same kind of behavior of opportunists to sell us cheaper and make quick money to go away. Those who are able to make difference among projects know the really value of these tokens. It was supposed to be distributed this week and we are heading towards weekend. Guess, it is near to see these tokens appearing in wallets.

Awesome work guys ! I can see following smart contract address that distribution has begun couple of hours ago. A small portion of addresses have been credited and remaining will receive their Oyster Shell tokens over the next few hours. It will be great to see market opening for SHL in shortest possible time once the airdropped is done. Keep up great work team constantly !

kukoin is one of my favorite exchanges i hope shl will be listed as soon as possible on this exchange, so the distribution is started, very well

I like to trade on this exchange too and have many pleasant and profitable trades on Kucoin. For example, my trades PRL token

Few hours ago I also received mine. It is one of the best airdrop which has real use case and key role inside the ecosystem. There were around 17k addresses who were holding PRL tokens. It means distribution is completed already or very few remained. It is appreciable to give direct benefit to holders and those will come later will have to buy from exchanges.

Agree with you! The earlier you start, the more you'll gain at hte end!

SHL Airdrop Complete

https://medium.com/oysterprotocol/shl-airdrop-complete-f1faca7fbfa9

This is very good news that distribution is completed successfully. What is next on the table about opening of market for SHL and main net launch of course are two things being heavily awaited and expected. This step was handled highly professional way like everything for this project once again.

Oyster is creating the future of website monetization by building a new protocol for the internet economy and eliminate ads from websites. Podcast:

https://www.futuretechpodcast.com/podcasts/chris-garner-advertising-evangelist-oyster/

Oyster is looking for beta testers:

https://medium.com/oysterprotocol/oyster-is-looking-for-beta-testers-f583c380095

1. Applicants must be the owner of the website or mobile application, and ideally, have a firm handle on the English language.

2. Applicants must have an audience base of over 100,000 monthly visitors/active users for three months of the last 12 months. This visitor base must be verifiable by Google Analytics or some other verifiable analytics tool.

3. Applicants’ websites must not be hosting any form of adult content, and absolutely no type of illicit content to qualify.

Bill C:

I think the same way as you about this project, highly professional and always great communication. Difficult to find in the Crypto space. Happy that I now have the SHL and I'll be following for updates, excited for the main net launch.

OysterProtocol => SHL => KuCoin:

https://etherscan.io/tx/0x679d47f90044af274e10eb5cc56fc06913a1c7efd48eebfea613ea8ba48da8e2

Now we have any chance to see this market active there or it could take few more days to trade this token there. I hope kucoin will distribute these token very soon now it is all depend on them anyway good luck for this amazing project.

CODE AUDIT MARCH (Top-200 GitHub):

https://i.redditmedia.com/XjfGTvK7m7viSsgXUUu4QcIh1-az1_DhvusF7Rw1b04.jpg?s=7f9c395b1773972140db787a1f8bb5a3

#53 Oyster Pearl ! Great job, team!

It was nice to see new tokens on my wallet, thank you. Now will wait for the listing on the exchange, the launch of the product and a good price for the tokens

Good news this is beginning of the new era soon this will enter on new exchanges and Kucoin will show its interest to open this market for trading. I hope price will be on same level like PRL it's brother project.

At the moment SHL is very cheap on only exchange IDEX where some lucky mates already picked up some tokens. I also have eyes to increase my position if the situation allows me. Also launch of mainNet is due which can be anytime announced. I hope these price will last at least couple of days more.

This is probably one of the most amazing potentialities. Nowadays you cannot really trust any service provider to keep your conversations private, versus sharing them with NSA. Therefore, this trustless solution is more than welcome!

When you have some working solution and the explanation is simple everyone understands and realize the potential. I ma glad I have invested in a project where majority of people are serious and mature investors both small and bigger. It still may take time to deliver but things are rolling out on schedule this is appreciable at first hand.

Oyster Mainnet Update

Tell OKEx what token you want them to list: OKEx (https://support.okex.com/hc/en-us/articles/360002984752)

Simply go to their telegram: @okexofficial_en

Then copy and paste: I want RFR: Oyster Pearl (PRL)

(1 vote per person)

This is not a listing. The five winners, are selected for the OKEx giveaway. You can read more in the link above. But this is good exposure for Oyster. They are asking what token people want to see listed.

This contest ends 18:00 Apr 26, 2018 (Hong Kong time).

I always figured IOTA would be the weak link in the Oyster ecosystem. Hope they can get their act together so it doesn't hold up the PRL team further.

Thanks for pointing that out. I've done that.
I am curious how it will go on with PRL and SHL.
Airdrop has arrived  :)

Statement from Bruno:


https://www.reddit.com/r/Oyster/comments/8exrt4/my_complaint_against_the_community/

https://www.youtube.com/watch?v=5j3_kbEOZZU - Oyster PRL Explanation video

https://www.youtube.com/watch?v=of5C76y5sYU - Oyster SHL Explanation video

 ;)

That is some hard statements from the dev. I didnt find anything wrong in his words as most of the community is just using the market for pump and dump. I have trust in the oyster protocol and will see a better future with it.

It is a common problem for Crypto in general, not enough people invest in the tech or the potential use cases, all they see is a quick way to make some profit. There is only so far that this scenario will play out, as it is a bit like a pyramid scheme, the people that get out early profit and the rest lose. As they are essentially just gambling on speculation and inflating a bubble that will eventually burst. I only invest in things that interest me, something I believe in and I always do my homework and take the time to understand the core concepts and what the project aims to achieve.

Everyone can have their own approach. Someone believes in technology, but someone wants to make money while there are such opportunities. But I also choose projects for investment which I believe.

I also think that even if there are people in crypto who are only interested in making a profit. But this is not bad, it makes crypto more popular. Over time, everything will change.

Bruno Block:

Oyster Mainnet Progress Update #1




https://medium.com/oysterprotocol/oyster-mainnet-progress-update-1-78ea6583cc87

This is awesome piece of writing about the current status of development. Oyster's development team is very talented this is what keeps us here to support the concept which is huge. After reading this article one can easily understand what's going on even with minimum technical knowledge because of its simple language and explanation. I must say great work is being done here.

oyster shell can do a x10 easy this year.

Meet the champ. Oyster Pearl - cryptocurrencies to watch in Q2 2018:

https://www.cryptocurrencyguide.org/10-cryptocurrencies-to-watch-in-q2-2018/

Good news! Would it be possible to add SHL to Coinmarketcap? I don't know what the requirements are for that

Soon.  ;)

Oyster Protocol - An Alternative To Ads

https://youtu.be/i0pZxPdg3LY

Bruno Block:

This is at what price SHL will make x10? We got it for free, it was airdroped to all owners of the PRL. Or was this token sold too?

Oyster Shell (SHL) has been distributed via airdrop.
https://idex.market/eth/shl - marketplace.

24hr Change:

+74.08759124%

 :)

If I am not mistaking to get listed on CoinMarketCap required volume for 24 hours is $10k. It has almost $20k if we convert those 32 Ethereum into fiat. I think volume from Idex qualifies for active markets. Either way in few days after distribution people just filled their bags already with cheap SHL tokens. It is right decision by all means.

100k. As we know it.

https://coinmarketcap.com/faq/ without numbers.

good project!

Well, somebody didn't let me pick enough Shell Pearl tokens. I thought by the time of release people will not move this market but someone has swept away all cheaper tokens. This was more surprising if SHL was available this cheap continuously. Anyway who grabbed so many tokens has taste and eyes to recognize the potential.

IDEX: Trading under maintenance. Withdrawals and cancels are enabled.

Oyster Mainnet Progress Update #2:



https://medium.com/oysterprotocol/oyster-mainnet-progress-update-2-483fddbba2d0

Update

SHL Airdrop for PRL Holders Has Been Distributed
https://news.kucoin.com/en/shl-airdrop-for-prl-holders-has-been-distributed/

Withdrawals of SHL tokens from KuCoin already open and will continue to be supported until 18:00 (UTC+8) on May 20, 2018, If you are currently holding SHL please make your withdrawal on or before the closing date above.

I wanted information about your project but your visual on the first page is not there, so i think you should check it.

This is result of permanent connect and communication between Oyster team and Kucoin's team whihc made this possible so quickly. I remember people were showing deep concern over distribution because they are used to take so long other other projects. This is one of the bets thing has happened like always tradition is up.

 ;)

Pretty high withdrawal fee, isn't it?
Moreover it looks like kucoin is not going to list trading pairs for SHL soon.

Rob DaMan:

MrRedPanda:

I was also a little surprised. I thought that the new token will be immediately available for trading after the airdrop, but for now we will wait

Don't so hurry, just wait, mostly exchange which involved in a snapshot on airdrop will automatically list that token on their exchange, hope Kucoin will added SHL on their exchange soon.

Thx KuCoin for such gift: usually most of all exchanges don't share any forks/airdrops with users and keep everything to themselves.
Got SHL both on the ETH address and on the KuCoin  :)

Check out:
https://youtu.be/Psr98QFNqCg

Oysterprotocol

All the exchanges get greedy eventually, trade fees are not enough for them it seems, even with some of the crazy listing fees some of these exchanges charge.

Check out:
https://youtu.be/qeq06oBh1NM
18:55

 ;)

https://globenewswire.com/news-release/2018/05/09/1499745/0/en/Oyster-Protocol-Reaches-Milestone-1M-Transactions-of-Decentralized-Storage-in-Beta-Testing.html

This is great achievement by reaching more than 1 million transactions on test net. This is excellent example of awesome work after so many participants in testing which are 1k testers and enormous transactions systems and platform's capacities and required feedback is visible by this article. Team is looking highly confident and professional in their work of high quality.

is SHL trading anywhere yet except ForkDelta: https://forkdelta.github.io/#!/trade/0x8542325b72c6d9fc0ad2ca965a78435413a915a0-ETH

wondering how to arrive at an appropriate value...

https://idex.market/eth/shl 🍭

Coinmarketcap will list SHL after we meet the criteria stated in their FAQ and hit at least 100k in 24hr volume VOL
https://coinmarketcap.com/faq/

Mainnet Progress Update #3

https://medium.com/oysterprotocol/mainnet-progress-update-3-108c18d8e05b

With a little under three weeks until the Oyster Mainnet launch, the Oyster development team has been extremely diligent in completing all the work necessary to ensure a successful launch. Today’s post will detail the work completed for the week of May 6th — May 11th.

This week, the development team made further efficiency improvements to the polling logic on the web interface as well as implemented and QA’d encryption and decryption on the broker node and web node to ensure the algorithms produced the same outputs for the same input. Additionally, the team implemented a logic change so that the frequency of the broker nodes’ chunk processing task would dynamically adjust based on the broker nodes’ proof-of-work performance.

Further work was completed on the treasure-claiming logic associated with the broker nodes, which is needed for the revenue-generating potential of the Oyster protocol. For example, in order for the web node to earn treasure for a website owner, the web node reports that it finished the proof-of-work for a sector of the data map of an uploaded file. Then, the broker node will query the private tangle to ensure the web node did the proof-of-work within the last epoch (e.g., the current year).

The development team also completed implementing circular treasure hunting flow on the web nodes and continued work on the treasure-claiming logic after a sector has finished uploading. Additionally, the development team has been working on ensuring that a web node does not overuse a device’s resources when performing intensive tasks like proof-of-work or treasure-hunting. Furthermore, the team is working on offloading the work to a background job and throttling CPU usage when necessary.

Finally, the team worked on OysterPearl contract integration with broker nodes to allow method calls to enact the various smart contract functions. The team also worked on unit testing the broker node Ethereum gateway and Oysterby network configuration, adding two new peer nodes to the internal network. Also, the team completed working on updating the web storage interface for the Mainnet release, as well as building the Oyster consent overlays that will be displayed to website visitors when they visit a site using the Oyster protocol.

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

Good afternoon,
What happens if I do not remove my oyster shell from kucoin, will I lose them? Sorry for my ignorance, thanks.

I don't understand you guys... Why in the world would you wanna keep SHL tokens on the KuCoin? There's no guarantee that they will list SHL. Even if they list it, you don't know when will that happen. It costs 5 or 10 SHL to withdraw them to your own wallet so why don't you do it? So you can complain when they get stuck on the KuCoin and some other exchange list them?

Plus, why did you keep PRLs on the KuCoin in the first place? It costs $0.7 (1 PRL) to withdraw it to your wallet and now you would have SHL on that wallet too.

which wallet do you use?

Probably they will open trading market for SHL once the main net goes live at the end of this month. They credited people's account very quickly what usually they don't do. If people want to keep SHL there this may also play important role to make them decision seeing interest of traders. I expect good thing coming out from Kucoin from this airdropped token.

SHL withdrawals will be closed temporarily for 24 hours due to wallet maintenance. Users can rest assured all funds are safe and that normal transactions will get re-open soon.

There will be another annoucement if SHL withdrawals open earlier than estimated.



https://news.kucoin.com/en/shl-withdrawal-temporarily-closed-for-24-hours/

we must withdraw shl from kucoin to mew or no ?

As Main Net is matter of days now seeing the interest of people in this project Kucoin should not keep this market off anymore. They have already tokens and can easily make space for one more market if they want. Why are they facilitating withdrawals and aren't showing interest to open trading market all this is bit strange. I can't understand this kind of logic but will be clear very soon.

Do anyone know what the price will be when it starts to trade at KuCoin ?

https://news.kucoin.com/en/

Do you know how exchanges work? The price will be determined by the supply and the demand. Nothing more... No one can set the starting price except for the people that will offer to sell their SHL tokens first.

The more the exposure is on many trading platform the better it will produce results. Kucoin as exchanges has its own importance and will provide this market to thousands of traders. For start it is big achievement after successful airdropped completion. I expect this listing on more exchanges will be among top priority tasks for team.

Dev is caring about this token too and finally it get listed on Kucoin as in previous update they said soon positive response will come about this. Kucoin is right place for this token now it will get stable and start rising into good direction.

https://www.kucoin.com/#/trade.pro/SHL-BTC  ;)

Does this mean no need to transfer SHL to MEW or wallet before MAY 20th??

No, you can leave them there and you can also trade SHL on KuCoin now.

Thanks much!

It is successful opening market seeing 30 Bitcoin's volume for the first 24 hours approximately. Interest is keep growing in buying and small correction is also going on at the same time to provide floors. This buying on every level is good thing happening for SHL tokens. Keep the great work up continuously.

Oyster Shell (SHL) on coinlib.io:
https://coinlib.io/coin/SHL/Oyster+Shell

Vote for the next crypto report, PRL:
https://coinonomic.com/category/research/

SHL will do very important into that ecosystem it is nice to watch the video dev has rock solid plan about the future of this token. It is good investment for long term plan there is wonderful plan which drive great value towards this token. I would like to support this project and hodl this because it is worth for it.

Oyster Shell (SHL) has now been listed on CoinMarket Cap:
https://coinmarketcap.com/currencies/oyster-shell/

This is another best thing happened today to see Shell Oyster (SHL) token on the CMC to have exposure and making its own independent identity. Even both projects are correlated but use cases are different so treating them as separate markets will be much more better to gain the benefits in the long run. It has decent volume for last 24 hours cycle.

Perfect project undervalue $1-$3 is easy for this project.

Volume of any market is basic tool realize the interest of traders in that particular project. I think there is nothing to be contrary that people should good interest so far in Shell Oyster as well. People talk about dumping while I watch that as filling orders because you have bids where to sell on. It has very powerful usage within the future platform so expecting more increase is realistic approach.

Huobi Community Vote Begins May 26th!

https://medium.com/oysterprotocol/huobi-community-vote-begins-may-26th-db01fbf9f119

Mainnet Pre-Release Progress Update

https://medium.com/oysterprotocol/mainnet-pre-release-progress-update-9bb5a2ef29df

Vote for PRL:
https://www.hadax.com/ru-ru/vote/for_votes/?id=147

Even competition among candidates is tough seeing the number of votes but this doesn't mean to give in. We should keep the project pushing forward without caring of the results. True efforts and work is in itself reward of satisfaction. I also have gave my vote every single vote is important so everyone should do small effort to make this happen.

PRL is currently ranked 11th overall, and in 2nd place for the European and Australia Edition of the HADAX/Huobi Community Vote. We encourage our community to continue the great effort in getting PRL to 1st in the European and Australia Edition! Vote here: https://www.hadax.com/ru-ru/vote/item/?p=147

https://twitter.com/OysterProtocol/status/1000396989975052289?s=20

PRL has gained over 1 million votes since our last Twitter post, and is currently ranked 7th overall, and 2nd for the Europe & Australian Edition! PRL is less than 40,000 votes away from regaining first place. Every vote counts!


Vote here: https://www.hadax.com/vote/item/?p=147

That interview on Oyster protocol by IOTA team Hispano is amazing. If anyone is interested to polish his knowledge or want to know more deeply about the project should go other thread for the link. It was great reading of the day I read with such pleasure twice. PRL/SHL has been discussed in detailed explanation there.

Exclusive interview to the Oyster protocol team before Mainnet release:

www.iotahispano.com/2018/05/28/exclusive-interview-to-the-oyster-protocol-team-by-iota-hispano-before-mainnet-release/

https://www.hadax.com/ru-ru/notice_detail/?id=1686

 ;)

After the release of main net and first thing will be to see everything working stably and safely. An immediate benefit of this launch will be for PRL while enhanced featured for SHL will be undergoing at the same time. It is big success and game changing move for Oyster project to deliver the promised and stunning product finally.

Oyster Mainnet Online

https://medium.com/oysterprotocol/oyster-mainnet-online-522e865a59f1

The Oyster team is proud to announce that the Oyster Mainnet is now live! Users can now host their files using the Oyster Mainnet.

The Oyster Mainnet web interface can be accessed here. oysterstorage.com

Oyster Team Supplying PRL During Open Beta

The Oyster team will be supplying the PRL to be used in the open beta of the Oyster Mainnet. Thus, for the time being, users will be able to store their files on the Oyster protocol for free.

Revenue Beta-Testing has Begun

We are happy to announce that we have begun beta testing the revenue generation side of the protocol with many different beta testers. The combined monthly unique users of all our beta testers are over two million, ensuring that there will be plenty of web traffic to test the resilience of Oyster’s back-end.

Temporary File Size Limit

As we mentioned in a previous post, there is a temporary limit for uploaded files on the protocol. This limit is currently set at 5 MB per file. This file size limit is significantly higher than the threshold featured in both Oyster testnets, and our development team has done an incredible job pushing the infrastructure of the Tangle to accept file uploads of this magnitude.

We previously mentioned that the file size limit would be 25MB per file. Due to the 11th hour bugs the development team ran into that ultimately delayed the May 29th launch, the file limit was reduced to 5MB per file. We want to ensure our community that this file size limit will only increase over time, as the development team already has several plans ready to alleviate the limit. Currently, the development team is working on adapting the IRI to accept a higher throughput of transactions in order to push the file limit higher. We will provide further communication regarding this progress as information is made available.
To stay consistent with our previous transparency with the community, below we will outline the reason why the file limit exists. Using our current method of client-to-broker communication, we’ve realized some inefficiencies in the way we’re processing data with MySQL. We are currently refactoring the database access and storage methods to eliminate the bottlenecks, and we are confident the client side interface will become even faster and more responsive in the near future. Now that the Mainnet is live, and the open beta of the protocol has begun, the development team will be continually iterating on the protocol, and continue to improve on all aspects of the web storage interface, including but not limited to: download speed, upload speed, and accepted file size.

Initial Storage Amount per PRL Set

Additionally, the 64GB storage amount per PRL for one year has officially been set, and the transaction for this action can be found here. Please note that this storage amount is subject to increase in the future.

Chris Garner on the Cryptoconomy Podcast

On a separate note, Oyster’s CMO Chris Garner was featured on the Cryptoconomy podcast. The episode featuring Chris can be streamed here. https://anchor.fm/cryptoconomyme/episodes/Ad-Alternatives-w-Chris-Garner-CMO--Oyster-Protocol-e1i8e9/a-a3oajh

Summary

A considerable amount of time and effort has been placed into getting the Oyster Mainnet ready for today’s release, and we are excited to hear from our community regarding their experience with the Oyster Mainnet. The Oyster team will be implementing a banner on our website that will display some metrics regarding the protocol, including but not limited to, the number of web nodes operating on the protocol, and the amount of PoW that has been completed by all the web nodes in the network. We will be informing our community once that banner is ready and live.

As always, we encourage any questions or comments to be posted to our Telegram channel or our Reddit.

Must-read

https://oysterprotocol.com/assets/pdf/ShellWhitepaper.pdf

Dual-Sig Contract Announced with Bug Bounty  ;)

https://www.reddit.com/r/Oyster/comments/8o9t3o/dualsig_contract_announced_with_bug_bounty/

This is great development to creating own multi-signature variant smart contract to move the funds of team and development to that later. That bug bounty of 5 Ethereum will encourage people to dig in the smart contract to find bugs and vulnerabilities which probably will not. Why I am confident because Oyster team is doing every thing very carefully. It will endorse the safety and security of smart contract.

Dual-Sig Contract Deployed:

Today marks a significant milestone in Oyster’s history. We have finally transferred all ETH, PRL, and SHL belonging to the Oyster treasury into the dual-sig contract.

https://medium.com/oysterprotocol/dual-sig-contract-deployed-ecaa612663ea

544: Oyster Protocol The Crypto With a Working Product and a Real-World Use
By Neil C. Hughes - Tech Podcast and Startup Stories

https://open.spotify.com/episode/2XImFCTorRQmusb9yaXOrW?fo=1

Oyster — Our Next Phase

https://medium.com/oysterprotocol/oyster-our-next-phase-3e3221dbb8e4

 ;)

This project is packed with great innovative ideas and endless possibilities powered by blockchain technology, i see the concept of it and i must say am fascinated by it all, i think this will surely attract investors looking for great and innovative project, but seem to be on the high side though.

A well planned goals are all these to take these tokens to top 30 exchanges for that one big plus even now at this stage. After reading main focused countries will be Japan,China and South Korea we can expect large community and best markets for SHL and PRL in coming weeks or months. Just keep the work like you did till now and community is here to support too guys.

Oyster Development Update June 3 — June 9, 2018

https://medium.com/oysterprotocol/oyster-development-update-june-3-june-9-2018-ed2e43976c2d

https://amp.reddit.com/r/Oyster/comments/8prxt0/pearl_bot_the_telegram_bot_for_oyster_is_back/?ref=share&ref_source=twitter&__twitter_impression=true

From: https://www.reddit.com/r/Oyster/comments/8qrw9c/i_think_this_may_be_end_of_oyster/e0lxx07/

Follow our progress:
https://github.com/oysterprotocol

 ;)

Check out this writeup on Oyster Storage by @johnpaulwalton

https://medium.com/ethex-market/oyster-launches-i-tried-it-out-you-should-too-d107787c05a2

 ;)

Vote for Oyster Pearl (PRL)

https://www.binance.com/vote.html

 ;)

Exclusive:
Rowlings610a524190db8fb35168560e059202049f6286fe8098949451cce7039f5337c4Hw6obkd H

You can use @pearlbot to retrieve a file, or https://www.oysterstorage.com

Chris Garner, CMO of Oyster, was recently featured in a Rowlingstone interview in the latest edition of their newsletter. Big thanks to @ottoRS and the Rowlingstone team for the coverage!

Oyster Development Update, Exchange Info, and More

https://medium.com/oysterprotocol/oyster-development-update-exchange-info-and-more-e52c53e697e0

 ;)

Rowlingstone.com Freemium Report Issue 23 has been released featuring an exclusive interview with Chris Garner - CMO of Oyster Protocol. Click on the link to access:

https://mobile.twitter.com/Rowlingstone1/status/1007722281387331584

Amazing interview which clears team's dedication for mid to long term goals to get integration in more websites which are up to $1 million dollars revenue generators. When you read with little bit interest then it takes no time to realize things are 100% on track. Team is aware of the fact valuable tokens are key for larger adoption and that is what will come in future.

That is good news they are working continuously and trying to make it most trusted project. Listing on a new exchange will drive more traffic towards this token and it will catch attention of new investors. I would like to appreciate your efforts and wish you more success.

That write up on storage on Oyster is very interesting and enhanced and polished my knowledge by arising other points and advantages of the protocol. Other development article also has spoken lot of things for near future. When you read every single write up or review you watch using other angles than traders. This is everywhere visible and here is too.

Vote for PRL:
https://www.binance.com/vote.html

 ;)

It seems of this business will be preferably in the offing! Blameless idea, reasoned approach, riveting job!

NEW ROADMAP Exclusive:

Oyster_L517a40ea698dcf603a51a061d6a06ce42768fdb36d3559fe0665c4450c5c2926FtmcfEH Z

(https://www.oysterstorage.com to retrieve a file) or @pearlbot (telegram)

 ;)

Hello! Project Tokens can be purchased only for btc and ETH or for fiat, too, is possible?

Fiat gateway. Oyster Protocol will provide the option to buy storage directly with e.g. PayPal/Stripe. Oyster puts the PRL in place for the customer. Each upload is still paid in PRLs in the background.

 ;)

35 —💲 Getting paid to disable ads with Oyster Protocol CMO Chris Garner

https://podcast.hodldaily.com/48352ea5

 ;)

Oyster Development Update June 22, 2018
https://medium.com/oysterprotocol/oyster-development-update-june-22-2018-b6fcb5a54ad3

The development team has made further progress in optimizing the web node script. The previous web node build had a total size of 1.8 megabytes, which is a significant amount of JavaScript to parse through (this was an issue originally submitted by an Oyster community member). The development team has since taken this concern from the community into consideration and has managed to reduce that build to 575kb (a decrease of 70%). By reducing the size of the web node script, the response time for clients will be much shorter, as the necessary data to be downloaded client-side to run the protocol is now significantly smaller.
In addition, the development team has made significant strides in the Ethereuem-related functionalities of the broker nodes, as well as fixed bugs related to gas limits and nonces. Furthermore, QA has been completed on the bury_treasure_addresses task. This task does three things (and for the interest of our community, this post will include the Etherscan transactions that show this task in action).
First, the treasure is sent to a treasure address

(https://etherscan.io/tx/0x896b8d39ae6b1e89f8b931e5a6a49a12e33922c3d62290fc94b9b2c0582579db).

Then, a tiny amount of ETH is forwarded to the treasure address to be used as the gas for the bury() call

(https://etherscan.io/tx/0x54233b4b520bc7634475b786a2306727a5c7dbe737c939508db9550b56c1a2a9).

Finally, the eth_gateway method is invoked and calls the bury() method on the Oyster PRL smart contract

(https://etherscan.io/tx/0x0a7f9427d61e8a4040d5b428f0042996f1ea16a58c7baa23a0174b4b7be6c174).

The transaction ids provided detailing the bury_treasure_addresses task are examples created during testing; thus, the gas prices used in these transactions are relatively high to ensure the transactions are confirmed within a reasonable time frame. In production, these gas prices will be much lower. With the bury_treasure_addresses task working correctly in testing, the development team has moved on to testing the claim_unused_prls task, which will invoke some of Oyster’s eth_gateway methods so that the broker can retrieve any PRLs that were leftover and not needed for treasures.

The development team has also been working on finishing the design for ‘rev2’ and writing proof-of-concept code in Python to use as a reference implementation in other languages later on. The team has started on documenting how rev1 (the current build in production) works to support legacy clients in the future as well. ‘Rev2’ is an exciting future improvement to the Oyster Protocol, as it will give the protocol the capability to offer multi-file uploads in a single session to a single handle. Moreover, each file has the potential of having its own password that the user needs to remember on their own (completely optional feature) and also enables features like media streaming due to a change in how treasures are buried. The design changes in ‘rev2’ of the Oyster protocol will ultimately help wide-spread adoption of the protocol for commercial-grade data storage, as well as lead to a more favorable user experience.

The development team has also added a universal error page to the web storage interface which users will be rerouted to if an error occurs trying upload or retrieval of a file. Additionally, the team has continued testing the integration of Badger DB into the system and are actively working on solving some issues related to this integration. Further work has been completed on integrating a streaming implementation of file uploads to handle larger files. In conjunction with the broker node performance improvements of saving binary data outside of the SQL database, this streaming implementation will significantly help with scalability.

Finally, the team has been working on in-browser previews for Oyster files, and some small improvements on streamable have been made, most notably download progress can now be tracked and displayed visually.

 :)

Mind blowing update on current features which are being developed or polished to increase their performance. You can talk more than many points from the whole update but I will draw attention of everyone on the last line which tells in-browser file view feature is under development alongwith other other stuff.

Follow our progress:

https://github.com/oysterprotocol

https://medium.com/@taylor.f

 ;)

Oyster $PRL is scheduled to be listed on BitForex! Trading will open at 11am HKT, June 26th, 2018 (11PM EST, June 26th, 2018). Initial pairing will be PRL/USDT, with PRL/ETH to be implemented soon after.

Nice  ;)

Check out this write-up on Oyster by @WPeaste:
https://bitsonline.com/oyster-protocol-storage-web-revenue/

 :)

PRL is included in the Bibox community vote! Vote for $PRL here:
https://www.bibox365.com/cinformation?id=700

 ;)

Good night, guys. Waiting for something above amusing here.
Excellence idea, in right mind logo!

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.

 ;)

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

We should not take it easy as competition has just started and Pearl Oyster already is at third position at this moment. Community should stay active to make this happen again bu showing strength to take PRL to Bibox with current contest. It will not be easy of course but can be done with little extra efforts.

We need your support now:
https://www.bibox365.com/cinformation?id=700

Voting rules:
https://bibox.zendesk.com/hc/en-us/articles/360003616113

 ;)

Development Update

Today’s update will focus on the work completed between July 1st — July 6th, 2018.
This week, the development team finished up treasure index hashing. The treasure index of a sector is now chosen by hashing the average of the indexes selected by the alpha and beta node. The hash ensures that the treasure index is genuinely random within the sector. In addition to the hashing function, the index selection method now supports variable sector size and has guards to ensure the treasure index is valid. The team has also started working on production database migrations.

Additionally, the team continued to QA ETH/PRL transactions triggered by the broker node, made small fixes, and updated unit tests. The development team is now at a stage where they can test the web node ability to claim real PRL on the Ethereum mainnet successfully. For example, this transaction was the result of a web node submitting a claim to a broker node:

https://etherscan.io/tx/0x73dd4c3a2b7d1daa14c0c2a8bc92f9daffc98256e89bc0ee46d784d4aa30e8a0.

The team completed QA on the BadgerDB integration, as well as cleaning up some issues with the unit tests for the broker nodes. Furthermore, the team has been working diligently on fixing Code Climate issues, ultimately leading to a more standardized code base. By using Code Climate, the team can set coding standards for engineers to help keep the code base healthy while the team grows. The team has also been looking into tooling to help engineers configure and setup testing/staging environments efficiently and reliably so that the QA process is more automated and easier to perform.

In addition to the above improvements, the team is finishing up integrating streams for file uploads and will begin working on streams for file downloads. This is intended to allow users to upload or download large files in the browser while being memory efficient. Finally, the team worked on upgrading the web node from Webpack 3 to Webpack 4 and all dependent development libraries to the latest versions and worked on porting to and installing Typescript on the web node. Typescript will allow for strongly-typed JavaScript (i.e., explicitly declaring a variable type as a string, integer, etc.), which will improve Oyster’s coding standards and enhance security within the code base.

Development Goals for the Following Week

Below are a few of the improvements the Oyster development team will be working on in the following week

1. Continued focus on size/speed improvements
2. First design steps of a public api/client lib — the Oyster development team believes an API that other people can consume is needed for adoption. This will be a building block for how everyone, including Oyster’s internal services, upload data and also a building block for higher level wrappers. The team believes in the future the bulk of our storage will come from API users, not necessarily Oyster’s official storage interface.
3. Continue improving development tooling/process — cleaner code, more code coverage with testing, more end-to-end tests.

https://medium.com/oysterprotocol/july-6th-development-update-1eb1f85d7787

During last week completed work is awesome reading everything in such details anyone can watch. Whereas goals for the coming week are very interesting where more probably enhancement and making the process lot more easier for adoption and seamless user experience when it comes to interact with Oyster's storage.

Greetings team! The idea will be successful.
Impeccable website, a very detailed and profitable vision!

Development Update July 13th, 2018

Today’s development update will focus on work completed between July 8th - July 13th.

Overview of Content

Began planning process for API that will be a key aspect for strategic commercial use cases moving forward
Created proof of concept of fragile loop.
Made significant backend improvements to support larger file sizes.
Continued with frontend improvements to increase file size.
Oyster roadmap updated.
Korean and Chinese translations of PRL whitepaper added to site.
Oyster Storage API

This week, the development team worked on pulling shared functionality that could be useful in both the back-end and the front-end into a shared Golang library, which eventually can be made into a cross-compiled binary that could be distributed via Node Package Manager (NPM). Compiling this shared functionality is a step forward towards Oyster’s ultimate goal of building an application programming interface (API) that will significantly increase the appeal of Oyster Storage as a platform for commercial use. For example, consider Amazon’s S3 service. S3 is a standard cloud storage service that supplies a flexible API, allowing users and developers alike to interact with the Amazon S3 service without having to use the user interface provided by Amazon. If you used Dropbox during the company’s first eight years of production, you were using Amazon’s S3 service to store your files in the cloud. Although the interface users interacted with was completely Dropbox’s creation, the actual storage location of the users’ data was on cloud infrastructure provided by Amazon (Dropbox has since moved to their own cloud infrastructure platform).

The Amazon S3 API has become a sort of standard for cloud storage, and many other cloud providers build their own cloud storage services to be “S3-compliant.” However, despite the efficiency provided by Amazon S3, there is still a glaring issue associated with the service: S3 does not come pre-configured to be completely secure. In fact, some of the prominent data breaches that have occurred in the last few years have been the result of misconfigured Amazon S3 Buckets (An “S3 Bucket” can be thought of as the overarching file directory where your uploaded files are stored). To use Amazon’s S3 service securely, a user has to have some understanding of how to use Amazon’s cloud services and put in the necessary effort to secure their S3 buckets (to Amazon’s defense, they have offered several options to help in this respect via their “Config Rule” service, but that requires even more knowledge of the AWS platform!). Ultimately, Oyster will develop an API that is “S3-Compliant”, such that it provides a user-friendly interface to interact with our storage capabilities; however, unlike Amazon S3, Oyster will be able to offer secure and encrypted file storage without the need of user configuration. Users/Developers that use the Oyster Storage API interact with the very same backend used on Oyster Storage’s web interface. Thus, any file that is uploaded via the API is just as secure as the files uploaded via Oyster’s web interface.

There are three distinct benefits to building an API for Oyster Storage. First, an API will increase the appeal for Oyster to be used for commercial storage. Instead of using our web interface, companies can build wrappers around Oyster’s API to automate uploading large amounts of files, as well as managing Oyster Handles. Secondly, creating an S3-compliant API will allow companies that are currently using Amazon S3 (or some other storage service that uses an S3-compliant API) to very easily switch to Oyster. Creating the API in an S3-compliant way will give Oyster a better chance to get more commercial customers because these customers will not have to do nearly as much work to be able to use Oyster’s service. Thirdly, the Oyster API provides a whole new playground for the developer community as a whole. The Oyster community can use Oyster’s API to build whatever application they want that utilizes Oyster’s encrypted, anonymous storage capabilities. Ultimately, the Oyster Storage API will be a significant step forward in cementing Oyster’s wide-spread adoption as an alternative to current, centralized cloud storage solutions.

Oyster’s Fragile Loop Experiment

https://cdn-images-1.medium.com/max/1600/1*u3DQ5TLk5gRKtaQ-wvl1zQ.png

Besides the update regarding Oyster’s future storage API, the team has also been working on an experiment that showcases the ‘fragile loop’ that will be used to limit overburdening device CPUs when the Oyster web script is running. Along with the consent message, the concept of the fragile loop is the main design difference between aggressive crypto mining scripts and Oyster’s non-intrusive treasure hunting. The goal is to perform meaningful work without hogging the CPU or draining the battery of the user’s device.

Generally, this is achieved by only utilizing a fraction of the devices CPU, as opposed to going full throttle during the user’s entire stay on a website.

A CPU effectively only has the states of active and inactive. Energy saving modes aside, there is no running at, say, 30%. Instead, the CPU usage you see in the task manager means that the processor was active for a specific percentage of time over the last second or so. Thus, the Oyster team can achieve the goal of a non-intrusive web node by emulating this behavior in the browser. By splitting up the work the script has to perform into small chunks and then pausing the script between these chunks of work, the team gets an easily configurable piece of software that does not drain any batteries.

The team has prepared a demonstration of this concept for you to play around with here. Any input or criticism is welcome!

Miscellaneous Improvement

The development team has been doing some pre-deployment QA before Oyster rolls out the badger DB changes which will reduce bottlenecks on the backend and help increase the maximum file size we can support (note that the upcoming deployment of changes will not include the front-end changes which are also needed to support larger file sizes). The development team was able to upload a 200mb file using Oyster’s backend alone. Further QA is needed on the client-side of the Oyster Storage web interface before the current 5mb file size limit will be increased.

The Oyster development team has also implemented polling Oyster’s private tangle from the oyster-streamable library. Additionally, internal testing has begun with uploading files using streams on the client. Furthermore, the team has finished the rev2 client-side reference implementation, which is published here, along with writing the necessary unit tests for this implementation.

Finally, the development team has completed work on broker node/smart contract interactions with OysterPearl, as well as unit testing and QAing the associated transactions. Furthermore, the team has converted many of the React components and Redux actions in Oyster’s codebase from regular JavaScript to TypeScript.

Updated Roadmap and PRL Whitepaper Translations

The Oyster roadmap has been updated on the site, and the Korean and Chinese translations of the Oyster PRL whitepaper have been added as well.

https://medium.com/oysterprotocol/development-update-july-13th-2018-ac975ca973b6

New Roadmap:
https://oysterprotocol.com/assets/img/oyster-roadmap-v4.jpg

Hi.
The basic object that in the future it has guarantee the development of the plan!

All the goals with progress level on the reviewed roadmap are awesome. People juts need to stop by to read main objectives of those features to understand what impact of them at successful completion and implementation of those inside the Oyster Pearl system. Each week is taking the project towards more advanced and improved features with more stability.

Follow our Progress:

https://github.com/oysterprotocol

Great quotes about life...  ;)

Development Update July 20th, 2018

Today’s update focuses on the work completed from July 15th through July 20th.

Much of the work completed this week focused around deploying upgrades to Oyster Storage’s backend. One of these upgrades included optimizing the backup script that currently creates emergency backups of the data maps presently stored on Oyster’s private tangle. When attempting these upgrades, the problems arose when trying to move recent changes into Oyster’s primary database. The Go framework the development team is using includes a migration tool called Fizz which developers can use to write files which will make changes to a database. Unfortunately, Fizz is not sophisticated enough to refrain from trying to create a table if it already exists or refrains from adding a column if it already exists, which caused errors anytime the development team attempted to pull changes from the master branch and then run migrations on the production machines. Thus, the development team needed to rewrite the migrations in SQL, so that the team could check to see if a table already exists and subsequently not create a duplicate of that table, as well as not adding a column to a table if it already exists. The team had to go through several iterations of SQL migrations before the file would work on both the developer broker databases and the Aurora DBs. Oyster’s development machines use MariaDB Docker images, while the production machines use AWS Aurora DBs with MySQL 5.7 server engines, and an early iteration of SQL migrations worked on the docker image databases but not on Aurora; thus, these SQL migrations had to be re-written. These changes led to SQL migration files that would work on both the production and development machines.

Furthermore, upon attempting to perform the migrations on the production databases, it became apparent that the size of the completed_data_maps table (which stores the uploaded user data submitted via Oyster Storage) would prevent the migrations from running successfully because of the size of the table. The table is very large because the developers did not yet delete old completed data maps and because of an indexing error which allowed duplicates into the table. The team is currently working to remove duplicates from this table, which will enable the team to run migrations, subsequently leading to the production brokers being brought back online.

For the time being, the development team will be bringing an additional set of production brokers online so that Oyster Storage can remain functional while these SQL migrations are completed on the master production infrastructure. Also, our community should expect to see a significant increase in file upload size by mid next week.

In addition to the work mentioned above, the team has continued working on integrating the oyster-streamable package into the web interface. This change will allow more memory efficient file upload and downloads, which means Oyster will be able to support larger file sizes. This is in the final stages of QA and testing, and so the team is hoping to deploy this change soon. Additionally, the team has been cleaning up the oyster-streamable package such that it can be released as a software development kit (SDK) for the public to use Oyster’s storage protocol. Finally, further work was completed on installing TypeScript support in both the web node and web interface, and several bugs and issues regarding the Badger DB deployment have been fixed.

https://medium.com/oysterprotocol/development-update-july-20th-2018-5af90805542e

https://mobile.twitter.com/OysterProtocol/status/1020408934258049025

85: OYSTER PROTOCOL WITH CHRIS GARNER

www.theblockchainshow.com/85-oyster-protocol-chris-garner/

 ;)

Support:


 :)

I wonder... Why did the team create SHL token they won't start the development of that part of the Oyster network for some time now. This way the price is loooow and the volume is practically non-existent  :(

There won't be an ICO. Oyster airdropped 100% of all SHL tokens to PRL holders some time ago. Oyster had unsuccessful ICO with PRL tokens last year in November but after that the community showed their support when the lead dev (Bruno Block) sold tokens to fund the project. It wasn't a dump because he explained everything to the community and all agreed it was the right thing to do.

When websites install the one line Oyster code to monetize their website, they will earn both PRL and SHL.

I understand that. But the team said that they plan to develop PRL part of the project first and they won't develop SHL until they polish OysterStorage. They could have airdrop SHL tokens later when they start to develop it.

The Oyster development team is pleased to announce that the initial file size limit of 5MB associated with the mainnet launch of the Oyster Storage platform has been increased to 25MB.

The development team optimized several parts of the platform to increase the original file size limit from 5MB to 25MB. For example, previously the client would process the entire file before sending all the chunks. For extensive files, this would cause memory crashes in the browser because the client had to be holding the entire processed file. Now, Oyster Storage handles the file in batches, and sends the chunks in batches, avoiding the client-side out-of-memory crashes. Additionally, all the data for a chunk was stored in a MySQL row, including the “message” field which is 2187 characters long and was burdensome on Oyster’s queries. Now, the development team has moved this large field to Badger, which is a key-value database. The key for the message field is still stored in the MySQL row, but it is considerably smaller than the message field. The team plans to move further and further away from MySQL for data map chunks to further improve optimization. Another change made was that chunk data is now stored in the Badger database and other data about a chunk (status, address, etc.) is stored in MySQL. Previously, these two databases were somewhat coupled; the badger data could not be added to the broker node until the MySQL data was added. Now, these two processes are independent of one another, which means the client can go ahead and start sending chunk data as soon as the session has been created, instead of waiting for the broker node to build the data map (which can take a long time for large files).

We ask our community to note that the team is aware of concurrency limitations. If many users upload large files simultaneously, uploads will slow down considerably. We are working on addressing this issue.
In addition to this file size increase, the development team already has some ideas to push the file size limit to an even larger limit. Currently, Oyster Storage is capable of handling file uploads of ~100MB; however, there is a concurrency issue in the infrastructure, such that if many individuals try to upload files of this magnitude at the same time, it is likely that the upload will timeout before it is finished. Once the development team has implemented their ideas to deal with these concurrency issues, they will begin further testing of larger file uploads (~100Mb) to ensure that many users can upload files of this magnitude concurrently without a timeout occurring.

Some of the changes that the development team are exploring to reach larger upload sizes and higher overall throughput are:

implement round-robinning of uploads so that every user’s upload receives a little attention
continue to depend less on MySQL
switch to Hercules when it is released
use AWS Lambdas (a form of serverless functionality) to offload the Proof-of-Work burden elsewhere
add more broker nodes to Oyster’s network

The development team will be working tirelessly to improve the file size limit even further, and we will continually update our community regarding the progress made towards this goal.

Try out the new file size limit here: https://oysterstorage.com/

https://medium.com/oysterprotocol/oyster-storage-now-supports-25mb-uploads-bbf9f2deec5d?source=user_profile---------2------------------

 ;)

Development Update August 3rd, 2018 — Oyster Web Node Demo!

https://medium.com/oysterprotocol/development-update-august-3rd-2018-oyster-web-node-demo-4604915a5da6

Oyster Protocol Webnode Demo:

https://youtu.be/zdXT2HWQicM

Follow our progress:

https://github.com/oysterprotocol

Development Update August 10, 2018

https://medium.com/oysterprotocol/development-update-august-10-2018-a57c1122f755?source=user_profile---------2------------------

Meshnet 101, how can we connect without ISP?

https://www.reddit.com/r/Oyster/comments/8x4cby/meshnet_101_how_can_we_connect_without_isp/?utm_source=reddit-android

I really appreciate this question and its answer on reddit which clears the SHL and meshnet how it will work and difference between SHL and IOTA. I had idea about the functionality of SHL inside the ecosystem being built at the top of Oyster protocol but such simple and detailed reply made it more clear and understandable.

Wow, SHL has come so far. Gave it a glance a few months back and got swamped by other offering. Saw it today and decided to peek back. Oh boy, have I missed out

Development Update August 17, 2018:

https://medium.com/oysterprotocol/development-update-august-17-2018-3ad1393aeca0

Oyster team is open to any improvement and upgrading in the protocol and platform. Those mocks up from last development update explains a lot that where team thinks need changes they immediately start work on that. It's true prices are down unexpectedly but future is on what are my eyes not on current temporary phase.

Development Update August 24, 2018

Today’s development update will focus on the week completed between August 19th — August 24th, 2018.

This week the development team continued work on moving all data map chunks out of SQL and into badger. The team has been focusing on putting the badger changes behind a feature flag and updating unit tests so that all code will still work regardless of whether Oyster’s backend infrastructure is using badger or MySQL for storing the chunks. Additionally, the team is making updates to a pull request to put these changes into the master branch. Once these commits have been accepted into the master branch, the team can continue QAing.

The team also continued work on the WebGL implementation of curl.lib.js (an IOTA library) that will allow iOS devices to access and perform proof-of-work for the Oyster web node demo. The team is currently updating and QAing the web node demo to ensure that the WebGL implementation goes smoothly without any problems.

In addition, this week the team deployed a change that does PoW on separate machines using AWS Lambda, which will help with upload performance. This is still in beta; thus, the team is monitoring performance and will continue to make tweaks and improvements to it. During initial testing, the team noticed promising increases in upload speed and throughput.

The team has made progress with allowing users to return to an upload that is currently in progress (more info about this upcoming feature is available in our previous post). The team is currently making a small change to the broker node code to support this feature.

Finally, the team also completed further testing on the upload process, some code refactoring as well as prepared some units tests for the streamable library and upload process.

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

https://medium.com/oysterprotocol/development-update-august-24-2018-51ff2aa465a3

As far as I understood there is no significant role of SHL in the platform at this moment but price seems to hold the floor. Large portion of volume has been wiped out but still slow motion consolidation is undergoing. In future these tokens have important role to play. Another week full of insightful development has been completed with this update.

Development Update August 31, 2018:
https://medium.com/oysterprotocol/development-update-august-31-2018-bce7c5d97481

Oyster is also happy to announce that the redesign of the Oyster main site will be going live soon, and have included a few screenshots of the new website design below. The new website will contain much of the information from the older site, but across many pages, as opposed to the single page layout of the current site. By splitting the information across several pages, and decreasing the scrollable space, the new website design will offer a much more favorable experience to those visiting the Oyster website.

Both Oysters are very well planned and executing by the team. Hopefully, we will see the implementation of the project as its real life advantages will be more.

As i understand the idea is to eliminate ISPs by using the Oyster shell protocol. Interesting idea but i think it will be very long road to success.

This is good time to buy at low price the team is busy and developing wonderful features for this platform. I think in future this rally will add new generation of millionaire because it has good potential.

Shell is also riding the waves of appreciation continuously for last few days. Not only price are increasing but volume is doing same. This time good thing is both tokens are increasing and are doubled in value with this gradual increase. It looks like weak hands are out that's sellers are not seen active these days. Most probably interest in buying on increasing.

SHl removed from Coinmarketcap, what is the future of the project?

It will be forked in near future just like Oyster Pearl (PRL) did and now new tokens is Opacity which represents OPQ token. That is almost finished it seems that once markets are re-enabled for OPQ then the fate of this will be decided. One thing is sure this will be part of new system continuously. You have to wait and have nothing to do to get new tokens when they will be available.

I also didn't expect much from the Snapshoot from Oyster, because the Oyster project was new and had a hardfork,
this sometimes made me wonder and funny

Bruno Block:

Scenario A: Bitcoin Slowly Bleeds to Death

The fraud and manipulation chickens of tether are coming home to roost. Price and volume have an inter-dependent relationship, the real USD volume of BTC is a fraction of the Tether volume. When traders wake up to realize that Tether is worthless, all the sell pressure is going to squeeze in through the tiny door of USD volume - hence crushing the real price to triple and double digits.

This has not yet happened, watch the Tether premium here: http://www.untether.space

Scenario B: The Bitcoin Blockchain Suddenly and Permanently Freezes

Miners have been mining at a loss or a near-loss for several months now. As the tether bubble implodes, they will inevitably capitulate and pull the plug on their mining rigs since they need to pay huge electric bills in USD. If too many miners unplug their miners at the same time, the mining hash rate will fall off a cliff.

If this sudden hash drop happens whilst the difficulty readjustment period is too far away, the average block time will increase to 20 mins, 30 mins, 1 hr, until eventually that 2 week readjustment interval will turn into 2 months and then 2 years. If this vicious cycle is entered Bitcoin will never escape it, as each block will take 100 years to mine effectively freezing the blockchain and making Bitcoin not even worth $5 for ‘historic’ value. Core developers imposing a forced difficulty readjustment might lead to a contentious hard fork.

https://www.blockchain.com/en/charts/hash-rate
See ‘average block time’: https://bitaps.com