With k, n reed solomon erasure encoded data the first k pieces simply represent the original content. With storj that means the first 29 pieces could be whatever the malicious uploader would want them to be and only the remaining 51+ would be generated by erasure encoding. So it is very well possible to simply repeat the same incriminating data for each of the first 29 pieces without encryption and then generate the erasure encoded remaining pieces and be able to survive audits as well as repairs.
I’m theory it would be possible for nodes to detect those pieces as they will have relatively low entropy due to the lack of encryption. But as far as I know no such checks are in place.
I believe that refers mostly to the legal implications, but not the technical feasibility of such an “attack”.
That may be true, but for now it is unclear for SNOs how to proceed should this situation occur or even hoe to know that such a situation has occurred on their nodes.
Unfortunately not just a hypothetical. There are images of child abuse on the bitcoin blockchain apparently. Though I don’t think that’s reason to not address these questions for Storj. I don’t consider it a major concern personally because there is nothing to gain from anyone attempting something like this and quite a bit to lose as they would be incriminating themselves more than anyone else. But I still hope we can get a more in depth response regarding technical and procedural mitigations as well as legal implications, should something like this happen. Because unfortunately become people just want to see the world burn and malicious intent can’t be excluded and the existence should be assumed in networks like this.