Edit: thinking about this a bit more just now, I think perhaps the value these investors see in this is that if they change the model to one where proof-of-storage is also signed with a known identity, then the Sybil attack is eliminated and such a system becomes a way to have a homogeneous market composed of many competing vendors. So Google would see this as a way to expand their cloud storage business and economies-of-scale. I am nearly certain the project is headed this way. In other words, forget the dark markets crap and think of this as a system for large server farms to offer a unified service model.
But I doubt that means anything stupendous for the Storj token and marketcap long-term (of course there will be a spike on this news). The most widely-used crypto-currency will end up being used with such a technology. Note the $3 million was not for tokens, it was for investment in the company.
But I doubt that means anything stupendous for the Storj token and marketcap long-term (of course there will be a spike on this news). The most widely-used crypto-currency will end up being used with such a technology. Note the $3 million was not for tokens, it was for investment in the company.
Note the edit. I have PM'ed @super3 and asked for his comment.
I suppose this is also relevant:
Btw, I presume we don't know what quality of redundancy we are buying, i.e. the quality of the hosts. Are these home computers that are unprofessionally (un)managed or data centers? So if we compare that $1.30 to Google's $6.99, are we comparing apples-to-apples. What about access bandwidth costs? If I request the data a zillion times per month.
The reason we have 100s of shitcoins (even speculators don't realize they are shit, e.g. MaidSafe) and nothing really substantial is because nothing other than PoW (and its flaws) can function without whales:
http://bitcointalksearch.org/topic/m.17950272 (<--- read all my comments in the linked thread, not just the linked one)
http://bitcointalksearch.org/topic/m.17950272 (<--- read all my comments in the linked thread, not just the linked one)
Maidsafe is crap? I would love to see you post that on their forum instead of this shit-hole. C'mon Shelby, it's too easy to make a comment like that in this wasteland. Do it! Just Do it!!!! Grrrrrrrrrrr! Lamo!
It isn't worth my time to go argue with them. Carry on with that delusion and you will eventually (another 5 years of promises, technobabble nonsense, and hand waving?) reap what you've sown.
There is nothing wrong with the concept of a Torrent like Dark web network for distribution of files that are otherwise difficult to obtain on more efficient server farms. But we won't be mainstreaming content storage on home computers. Server farms will always be more efficient and mainstream. As for the token and earning money from hosting content on your home computer harddisk, brouhaha. Even a rough estimate on a napkin would indicate it is not viable to resell your Internet connection bandwidth for more than you pay for it, especially since you pay orders-of-magnitude more than it costs Google
The main criticism is that even to the extent that we could create a more efficient cloud storage system comprising a common system incorporating a myraid of vendors by incorporating a signed proof-of-storage along with a blockchain record, the monetization of the system with a token is nonsense (other than as a gambling casino for speculation), because the most widely used crypto-currency will end up being the one the market prefers to use to pay for the cloud storage. These tokens (Sia, MaidSafe, Storj) are not going to be very long lived (because they haven't solved the major problems of crypto-currency), even though their proof-of-storage technology might end up being useful and used. Likewise, the technology for proof-of-storage will end up being used with the blockchain that solves the major problems of blockchains (e.g. centralization of consensus, etc). These projects are just incubators of experiments in cloud storage homogenization technology, not long-lived token+blockchain systems.
In addition to my prior critique of "proof-of-storage", I see some additional flaws in the idea expressed as quoted below:
None of these quoted are objectively provable to the public-at-large, i.e. on a blockchain. For example, proof-of-storage can work from the perspective of the owner of the data to be stored, but not from a public perspective.
Network performance can't be proven. This is one of the fundamental reasons we have to deal with Byzantine fault tolerance on networks. How do you prove to a blockchain that the ping time you measured was accurate. You can't. How do you prove downtime. You can't. If you say voting, then you have Sybil attacks on voting. Byzantine agreement can't remain unstuck without a hardfork or whales. Etc..
Sorry this is entirely impossible. It violates the basic research and fundamentals. Much more detail is in my unpublished white paper wherein I start from first principles and try to explain these fundamentals (but ends up being far too much to summarize to laymen, so I don't know if that version of the whitepaper will be the one I end up publishing).
So this is what I mean with my criticism that proof-of-storage can't even really work well even for file storage in the Storj model where each user encrypts the data to be stored (in multiple variants), because it is impossible to insure fungible performance for the data retrievability.
Coins are issued by the network based on the following formula:
-1 coin = 1gb hosted for 1 month.
-Any downtime (detected by pinging) reduces profit 10x (ie, if your mining machine is down for 1 day, you lose 10 days worth of profit for that uptime month)
-100% of your "storage" has to be downloadable by the network within 1 hour, tested by the network randomly 4 times per month (uptime month of 30 days, not calendar). If you fail this test your profits over this period are reduced by double the amount of failed download, eg, you are hosting (mining with) 4gb of space, a random download attempt occurs and only 90% of the 4gb is downloaded, then your profits are reduced by 20% untill the next random download test.
-When you start mining you do not receive profit for the first uptime week of 7 days (this is to stop people that had some downtime simply creating a new miner on a new wallet straight away)
- Ping checks are performed every 15 minutes, you need to fail 2 to be considered "down". Thus you can install an update and restart without "down time".
- Miners are also rewarded the transaction fees of the network, spread evenly to the miners based on earning.
-1 coin = 1gb hosted for 1 month.
-Any downtime (detected by pinging) reduces profit 10x (ie, if your mining machine is down for 1 day, you lose 10 days worth of profit for that uptime month)
-100% of your "storage" has to be downloadable by the network within 1 hour, tested by the network randomly 4 times per month (uptime month of 30 days, not calendar). If you fail this test your profits over this period are reduced by double the amount of failed download, eg, you are hosting (mining with) 4gb of space, a random download attempt occurs and only 90% of the 4gb is downloaded, then your profits are reduced by 20% untill the next random download test.
-When you start mining you do not receive profit for the first uptime week of 7 days (this is to stop people that had some downtime simply creating a new miner on a new wallet straight away)
- Ping checks are performed every 15 minutes, you need to fail 2 to be considered "down". Thus you can install an update and restart without "down time".
- Miners are also rewarded the transaction fees of the network, spread evenly to the miners based on earning.
None of these quoted are objectively provable to the public-at-large, i.e. on a blockchain. For example, proof-of-storage can work from the perspective of the owner of the data to be stored, but not from a public perspective.
Network performance can't be proven. This is one of the fundamental reasons we have to deal with Byzantine fault tolerance on networks. How do you prove to a blockchain that the ping time you measured was accurate. You can't. How do you prove downtime. You can't. If you say voting, then you have Sybil attacks on voting. Byzantine agreement can't remain unstuck without a hardfork or whales. Etc..
Sorry this is entirely impossible. It violates the basic research and fundamentals. Much more detail is in my unpublished white paper wherein I start from first principles and try to explain these fundamentals (but ends up being far too much to summarize to laymen, so I don't know if that version of the whitepaper will be the one I end up publishing).
So this is what I mean with my criticism that proof-of-storage can't even really work well even for file storage in the Storj model where each user encrypts the data to be stored (in multiple variants), because it is impossible to insure fungible performance for the data retrievability.
