3 ms·

The whitepaper: http://storj.io/paper/storj.pdf http://storj.io/paper/storj.pdf Where can I find some precise protocol specifications? The whitepaper is full o

by leni536 12y ago

The whitepaper: http://storj.io/paper/storj.pdf http://storj.io/paper/storj.pdf Where can I find some precise protocol specifications? The whitepaper is full of handwaving about the critical parts (namely Proof of Resource).

tinkerrr 12y ago
I think they are mostly waiting for MaidSAFE to solve that problem, which is a group that's actually serious about the intricate technology that needs to go into this, and all the special cases (e.g. how many times do you need to replicate a chunk of data to make sure it isn't lost when people turn off their computers). See https://github.com/maidsafe https://github.com/maidsafe
- Taek 12y ago
  I've been mostly unimpressed with MaidSAFE approach to the storage problem. They (last I checked) are approaching the problem by using quadruple redundancy, no erasure coding. This opens some attack vectors, because an attacker only needs to control 4/4 pieces, something that takes a probability of (attacker control)^4 . Their proof of storage also seems to use nonce's, which require precomputation before uploading the file, and means a limited amount of proofs before you have to fetch the file and compute a bunch of other nonce's. The biggest problem with MaidSAFE's stuff is that it's all over the place. There's no concise document that explains proof-of-storage. Their approach seems enormously complex, which to me indicates a huge likelihood of undetected vulnerabilities (complexity is bad when you want security).
super3 12y ago
You would have to take a look through our code on githhub. http://github.com/storj http://github.com/storj That paper was written before decentralized storage was really just a new idea. I've since implemented a baseline core algorithm, and we have one application running. I'm in the process of rewriting the whitepaper. Hopefully will put out a draft in two weeks(I'll be at conferences all this week). From there I want to actually collect network data(after all I'm trained as a researcher and what is good paper without any data?) before putting out a solid draft to be peer reviewed.

by leni536 12y ago

tinkerrr 12y ago

I think they are mostly waiting for MaidSAFE to solve that problem, which is a group that's actually serious about the intricate technology that needs to go into this, and all the special cases (e.g. how many times do you need to replicate a chunk of data to make sure it isn't lost when people turn off their computers). See https://github.com/maidsafe https://github.com/maidsafe

Taek 12y ago
I've been mostly unimpressed with MaidSAFE approach to the storage problem. They (last I checked) are approaching the problem by using quadruple redundancy, no erasure coding. This opens some attack vectors, because an attacker only needs to control 4/4 pieces, something that takes a probability of (attacker control)^4 . Their proof of storage also seems to use nonce's, which require precomputation before uploading the file, and means a limited amount of proofs before you have to fetch the file and compute a bunch of other nonce's. The biggest problem with MaidSAFE's stuff is that it's all over the place. There's no concise document that explains proof-of-storage. Their approach seems enormously complex, which to me indicates a huge likelihood of undetected vulnerabilities (complexity is bad when you want security).

super3 12y ago

You would have to take a look through our code on githhub. http://github.com/storj http://github.com/storj That paper was written before decentralized storage was really just a new idea. I've since implemented a baseline core algorithm, and we have one application running. I'm in the process of rewriting the whitepaper. Hopefully will put out a draft in two weeks(I'll be at conferences all this week). From there I want to actually collect network data(after all I'm trained as a researcher and what is good paper without any data?) before putting out a solid draft to be peer reviewed.