Mojette Transform and SAFE

I am please :smiley: to see that people are ready to explore new frontier to have a better SAFE.
Be it after or before self-encryption, there is probably a sweet spot for replication + erasure code.

This is a good rule in general for encryption but here there is nothing to be weankened. Just to scare :anguished: you a little bit: why don’t you have the same concerns for the redundancy for ordinary file?

But don’t worry to much because i think that the goal of the self encryption is to randomly and uniformly assign id and obfuscate chunk prior to the distribution on the SAFE network.

Mojette Transform file will be ā€œmore secureā€ here because you do not have the angles of the projections to reconstruct the file.

In self-encryption everything is know so you can pre compute a file to find the chunk.

But maybe there is encrypted communication between node somewhere else in the SAFE network that change that picture…

thanks @digipl of course the ultimate reference… the source code.
Well the pictures are not in sync with the code…

1 Like

If you read the original paper of self encryptation they are not a unique way of using the chunks.

No, you’re right. it suffices to have the hashes, and they are already in the data map. You don’t need the full adjacent chunks. Nice one!

1 Like