Herman Jacobs aka Seraphim, CEO of Cherry Labs’ update to the Cherry community that can be watched back here
Jump to:
Highlights:
“As mentioned, the team has been busy. The work has, let's say, not been what we've relayed over the past many months. I would say the engineering work has taken a back seat. On Cherry, of course, it is the primary goal of Cherry, which is to develop a viable and, more than that, more than viable, sustainable, usable decentralized storage platform.
[…] today's the beginning of a series of updates that will focus on the positioning of Cherry.
Certainly it's more of a core objective of ours (to develop our platform, develop our technology) than has been overall the pattern of the industry in the past years of bear market. I did mention we are changing, or I called it putting the technical progression in the back seat, but whereas many of the updates in the past were developments and tech technically related, today's the beginning of a series of updates that will focus on the positioning of Cherry and the development and/or rather redevelopment of the Cherry brand to finally get these products built over the past many years into the hands of people with the least friction possible. This is granted by the superb and rigorous effort put in technically, but also by spreading awareness of Cherry to customers that may need it but may not yet know about Cherry.
Cherry will become strictly a storage protocol. It'll be rebranded as such; […] for developers and people who seek a more simple way of explaining Cherry, become a storage platform. It'll be decentralized, it'll be distributed and trustless, and it'll be interoperable with all the other systems as we described and discussed and announced.
The exact strategy will be sort of unfolding by itself. I don't want to preempt. I don't want to signal too much in advance. However, the overall strategy, the overall trajectory will be the following: Cherry will become strictly a storage protocol. It'll be rebranded as such, and thus, you can expect new brand material such as new documentation that will affect Cherry not so much for its broader mission of creating a distributor network that is an execution layer in its own right, and instead Cherry will be more simply, and I think far more intuitively, for developers and people who seek a more simple way of explaining Cherry, become a storage platform. It'll be decentralized, it'll be distributed and trustless, and it'll be interoperable with all the other systems as we described and discussed and announced and developed ad-nauseum over the past many years. However, all these principles will belong to the Cherry storage or to the storage module, and that's all that everybody needs to know.
Cherry will be, therefore, shifting away from a network and a network brand, and more so to a service brand where we maintain storage oracles across other general purpose networks much like Chainlink and The Graph.
Everything else which basically describes how Cherry does storage in this unique and new way (such as bridging and relaying information from general-purpose networks to its own execution layer, maintaining execution layer based on a substrate with layer zero infrastructure and its own specialized parachains that deploy specialized computation on arbitrary data, data that is fetched and then returned to external networks) - all this description is just ancillary, it's just a detail on how Cherry fundamentally does storage. Cherry will be, therefore, shifting away from a network and a network brand, and more so to a service brand where we maintain storage oracles across other general purpose networks much like Chainlink and The Graph. Whereas Chainlink and The Graph provide oracles for data streams like financial information and other sorts of truth, it shall be much more basic, much more foundational as a technology where the information it processes, it receives and returns, and the operations it helps developers perform on these data is entirely arbitrary and it resides in the structure, resides in the programming the data owners assign to it.