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

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).