Еженедельное обновление прогресса по разработкам на 22 июня 2018 года:
https://medium.com/oysterprotocol/oyster-development-update-june-22-2018-b6fcb5a54ad3

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.

 

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.

Насчет быков, мастерлюк, предупреждал еще зимой. Раньше девятнадцатого года он их не ждет. У нас глаз замылен, именно поэтому сейчас, мы и не осознаем масштабы этого булрана в будущем. Будем посмотреть, а пока график майкрософта:

ЕОS, повторяюсь, не имеет ничего общего с децентрализацией. Децентрализация или масштабируемость. На данный момент только так, с имплементацией шардинга возможно ситуация изменится и технические характеристики классических медленных чейнов поднимутся. Группа из 21 недобросовестного пользователя стоит на границе «доверия» сети. Это не про независимость.

A nod’s as good as a wink to a blind horse. Xandry, there's no place you can hide... 

Oyster mainnet now online:
https://medium.com/oysterprotocol/oyster-mainnet-online-522e865a59f1?source=user_profile---------4-------------------

Must-read:
https://medium.com/@taylor.f

Основная масса людей опасается скама тезера. Мол негативное влияние на рынок, очередное черное пятно в истории рынка и тому подобное. По крайней мере, такие мысли часто слышу от новичков. Я лично вижу огромный зеленый кол в небо по XBT, на который «фиатчики» будут лезть перегрызая глотки друг-другу, если крах тезера всё-таки произойдёт. Но, думаю нам не подкинут таких дровишек.

HADAХ добавлен на CMC.
31 место по объемам торгов, 40,8 миллионов/сутки.

Лидер по торгам Content Neutrality Network? Сделал 250% за неделю.
Посмотрим, пока не впечатляет. Неинтересно, вот BiBox... вполне. Но всё-таки однозначный лидер среди биржевых BNB, роль личности очень важна всё-таки. Выкатят декс, где BNB будет газом сети и возможны новые горизонты.

Это топовый мем.
Хранилище работает в бета-режиме, поэтому выгрузка файлов с мобильных устройств может не работать. (скорость загрузки и лимиты будут, естественно, увеличены) В любом случае, альтернативным вариантом является созданный нами @pearlbot , куда вы отправляете handle (ключ к файлу) приватным сообщением и бот выгружает его из тангла, отвечая уже файлом.

О чем ты?

Заявленные тех.характеристики и потенциальные возможности NEM Catapult:
https://medium.com/nemofficial/welcome-to-catapult-29afe8e1e57c

Проекты, использующие блокчейн NEM:
https://github.com/Sateetje/awesome-nem-projects

Провальный маркетинг? Это называется «не хайповый»
https://mobile.twitter.com/NEMofficial

Читая ваши комментарии, к сожалению, становится страшно за состояние рынка. С такими микроорганизмами никакого оживления и нормального развития экосистемы не предвидится. Ну ничего, караван идет...

 

На этом рынке, пассивный доход от хранения токенов (за исключением нескольких классических понци-схем) это как поезд летящий в обрыв, но с бесплатным вагоном-рестораном. Если коротко, того не стоит. Мне не нравится доебываться к каждому, поверьте, просто борюсь за инвесторов потенциальных, которые принесут ликвидность настоящим рабочим проектам.

 

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

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

 

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

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

 

Очередной подкаст Криса Гарнера, директора по маркетингу Oyster Protocol:
https://podcast.hodldaily.com/48352ea5

 

Очередной подкаст Криса Гарнера, директора по маркетингу Oyster Protocol:
https://podcast.hodldaily.com/48352ea5

Есть план, есть ресурсы денежные и временные. Подготовка к голосованию на Huobi началась заранее, проект поддерживался одним супер-узлом и успешно, на мой взгляд, занял четвёртое место в общем зачете, и вошел в «призы» по европейской зоне, заслужив листинг. Потом он оборвался из-за нарушения договорённостей по депозиту, со стороны биржи. Команда среагировала на это оперативно и подписала новый контракт на листинг, биржа из двадцатки по объемам, анонсируют в течение этой/следующей недели. Бинанс подвергнулся случайно.

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.

 

Вот она, пресловутая массовая адоптация. Хранилище не требует никаких личных данных, номеров телефонов и прочего. Никаких регистраций. Есть ваши данные, анонимное перемещение в тангл, децентрализированное хранение и ваша отвественность за ключи к файлам. Новая парадигма. Напоминаю, что в данную секунду, где-то на просторах интернета, проводятся тестирования протокола монетизации пользовательского трафика, информация о тестировщиках не является публичной, так как команда хочет видеть реальные цифры и работать с ними, публичный тест (оглашение списка веб-сайтов) вызовет искусственный рост посетителей.

Голосование дает право побороться за листинг на крупнейшую биржу, в данном случае Binance. Очевидно, что на этот раз мы проходим мимо. Но, два месяца назад, проекты Elastos и WePower, занявшие первое и второе места, соответственно, были дисквалифицированы из-за нарушения регламента голосования (использование ботов, анонсирование дропов и тд.) и листинг выиграла, занявшая третье место, Zilliqa (к слову, за которую, я усиленно призывал голосовать, как за единственный толковый проект из представленных тогда)