I am not sure how 31TB of data is being transmitted.
There are currently 29,707 token holders, each with their own unique hash which is 20 bytes long.
There are also currently 158,619 transactions, each with its own unique hash which is 32 bytes long. Each transaction also has a timestamp which can be 8 bytes long.
One logical place arbitrary data can be stored is by adding it as "private data" for each transaction. (Like reference number when making bank transfers). But I checked a few transactions, and none of them have anything added in this field.
So we are looking at 594,140 bytes of data potentially encoded as part of being a token holder and 6,344,760 bytes of data potentially encoded as part of a transaction.
I fail to see how 31TB of data can be encoded in this. Also, I dont think these hashes can be controlled - I believe they are calculated as part of an algorithm - so I am not sure you can encode arbitrary data as part of these hashes.
The best I can think is these hashes are keys to the data which is stored elsewhere. But that beats the purpose of storing everything in the block chain.
My best guess? 31 TB was a false figure to throw us off. The real data is only a few MB and contains the most explosive info - and pointer to the rest.
Its the token called WHACKD.
I am not sure how 31TB of data is being transmitted.
There are currently 29,707 token holders, each with their own unique hash which is 20 bytes long.
There are also currently 158,619 transactions, each with its own unique hash which is 32 bytes long. Each transaction also has a timestamp which can be 8 bytes long.
One logical place arbitrary data can be stored is by adding it as "private data" for each transaction. (Like reference number when making bank transfers). But I checked a few transactions, and none of them have anything added in this field.
So we are looking at 594,140 bytes of data potentially encoded as part of being a token holder and 6,344,760 bytes of data potentially encoded as part of a transaction.
I fail to see how 31TB of data can be encoded in this. Also, I dont think these hashes can be controlled - I believe they are calculated as part of an algorithm - so I am not sure you can encode arbitrary data as part of these hashes.
The best I can think is these hashes are keys to the data which is stored elsewhere. But that beats the purpose of storing everything in the block chain.
My best guess? 31 TB was a false figure to throw us off. The real data is only a few MB and contains the most explosive info - and pointer to the rest.
Okay - just found something else.
https://www.ethswarm.org/