Author

Topic: Additional use of processing power? (Read 870 times)

qbg
member
Activity: 74
Merit: 10
August 06, 2011, 10:59:50 AM
#5
"noise" can still be compressed to reduce the size...

Good encryption should be indistinguishable from random strings.  What is the chance that it could be compressed by at least one byte? There are 256^n strings with a length of n bytes. Since we want to be able to recover the original string, each compressed string must decompress to one decompressed string. There are 256^(n-1) strings of length n-1 bytes. This means that only (256^(n-1))/(256^n) = 1/256 strings of length n can be compressed by one byte. For more highly compressed strings, the chances get worse. This is why trying to compress the data would be useless.
legendary
Activity: 980
Merit: 1004
Firstbits: Compromised. Thanks, Android!
August 06, 2011, 10:38:22 AM
#4
"noise" can still be compressed to reduce the size...

Sometimes it can.

If it's pretty random noise (which encryption strives for), attempting to compress it will likely result in an INCREASE of the size of the data.
legendary
Activity: 1148
Merit: 1001
Radix-The Decentralized Finance Protocol
August 06, 2011, 10:17:52 AM
#3
The key protocol data is incompressible: correctly implemented cryptography is indistinguishable from noise. I have feeling that you completely don't know what you talking about.

He probably has no idea about cryptography, but that is no reason to answer this way.
legendary
Activity: 2128
Merit: 1073
August 06, 2011, 10:05:45 AM
#2
The key protocol data is incompressible: correctly implemented cryptography is indistinguishable from noise. I have feeling that you completely don't know what you talking about.
member
Activity: 98
Merit: 10
August 06, 2011, 09:48:10 AM
#1
Would it be viable to use the processing power of the network to compress and decompress the blockchain data stored on our hard drives?

The network compresses all the data down to a really small size before we recieve it, and then the client requests for decompression as and when it's needed.
Jump to: