search

EOSIO / eos

An open source smart contract platform
https://developers.eos.io/manuals/eos
MIT License
11.27k stars 3.76k forks source link

Better Compression for Smart Contracts #1292

Closed jjxtra closed 6 years ago

jjxtra commented 6 years ago

Just read Dan's steemit post about zlib compression for smart contracts. I would suggest that either ZStandard or LZMA2 with max compression levels be used for the compression, as these will give better compression results compared to zlib.

The ZStandard license (BSD) is more friendly than tha LZMA2 license (GNU LGPL).

Having a compression type field in the smart contract data structure would allow more compression types in the future. Who knows, in 5 years a new compression type may come out that is much better than even ZStandard or LZMA2.

When adding new compression types, you would roll out the decompression support first, wait several months until everyone updates, then roll out the compression support.

If memory use is a concern, ZStandard could be used over LZMA2.

Thanks for reading and considering.

wanderingbort commented 6 years ago

We have already set this up to support multiple compression types in the future. Zlib was merely a convenient proof of concept.

On Feb 3, 2018 4:34 PM, "Jeff Johnson" notifications@github.com wrote:

Just read Dan's steemit post about zlib compression for smart contracts. I would suggest that either ZStandard or LZMA2 with max compression levels be used for the compression, as these will give better compression results compared to zlib.

The ZStandard license (BSD) is more friendly than tha LZMA2 license (GNU LGPL).

Having a compression type field in the smart contract data structure would allow more compression types in the future. Who knows, in 5 years a new compression type may come out that is much better than even ZStandard or LZMA2.

When adding new compression types, you would roll out the decompression support first, wait several months until everyone updates, then roll out the compression support.

If memory use is a concern, ZStandard could be used over LZMA2.

Thanks for reading and considering.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/EOSIO/eos/issues/1292, or mute the thread https://github.com/notifications/unsubscribe-auth/ACYR4qPNt8XGt60e3QsH3Z7sWa02nCmKks5tRNDPgaJpZM4R4Vca .