Has anyone ever talked about compressing the blocks?
Dunno... What about using pointers? The question would be where do you store the stuff pointed to?
there's already some miners that use a method of compressing blocks.
The p2p protocol presently only supports propagation of solved blocks in full; i.e., blocks are not compressed.
However, the Corallo Relay Network does support a sort of compression. Rather than transmitting all the transactions in a solved blocks, since most the other miners know about them already, it just transmits indices that refer to each transaction (sort of like a map for how the TXs fit in the block). Greg Maxwell claims that the Corallo Relay Network attains a coding gain of about 250 (1 MB is compressed to about 4 kilobytes); however, I believe it is less in practice.
Techniques like invertible bloom lookup tables (IBLTs) could also be used to compress solved blocks in the future; Rusty Russell is presently researching this possibility.
However, the Corallo Relay Network does support a sort of compression. Rather than transmitting all the transactions in a solved blocks, since most the other miners know about them already, it just transmits indices that refer to each transaction (sort of like a map for how the TXs fit in the block). Greg Maxwell claims that the Corallo Relay Network attains a coding gain of about 250 (1 MB is compressed to about 4 kilobytes); however, I believe it is less in practice.
Techniques like invertible bloom lookup tables (IBLTs) could also be used to compress solved blocks in the future; Rusty Russell is presently researching this possibility.
That's not compression.
your right, but still its 250 times faster then sending out the whole block
the network could be optimized further by compressing each TX's before sending it out on the network
might not get much coding gain trying to "zip" TX its just ~300 very random bytes
All of this doesn't avoid the necessity for the network to handle the full weight of these blocks. It's a transmission method and nothing more.
agreed
what we don't agree on is what is an expectable max weight for a block
i think its close to 500MB maybe 1GB
Do you figure you're smarter than everyone or that all of us are retarded?
No one agree on any size but certainly you're the only coming up with that type of numbers. Maybe you'd like to consider you simply don't understand the issue well enough?
i didn't pull this number out of my ass
its what a typical home connection is able to download in 10mins
maybe what we should do is find the node with the shittesty connection on the network currently ( a node from china) see how much it can download in 10mins, half that and use that as the upper limit
i bet that would be about 50MB
