CRYPTO NEWS

Crypto-Compression Algorithms?

I was wondering, whether there exist such algorithms/enciphering procedures which both compress and encrypt the input data. That means, for starters, the output will be both smaller in size and difficult to decrypt…and if the compression algo is good, then the bits will be almost random.

Also any twin-encryption algo-s around?: by which I mean, suppose I have 2 data strings (alphanumeric only, say for now) — Using them both, and an algo, I produce the encrypted output – I take in a pair, and produce a pair. The procedure is algo-based and not key-based. Any comments on this? And how this could relate to the earlier crypto-compression problem? (One way it would relate is, if the data is not just strings of characters, but a large multimedia file, it can be compressed fast and securely apart from being encrypted)

The FAQ says “please ask questions that can be answered, not merely discussed” but I can not be more specific, atleast not now: if it had some coding, I might have posted it on stackoverflow!

All comments, with links to other Q&A are welcome. Other forum addresses are also welcome!

Can revert context be provided to frontend application for solidity’s reverts?

There is solidity code that fails here: error InvalidCheck(uint32 _check); modifier someCheck(uint32 _check) { if (check != _check) revert InvalidCheck(check); _; } My frontend application fails on this check and doesn’t provide any context about the error. "message: ‘cannot estimate gas; transaction may fail or may r…UNPREDICTABLE_GAS_LIMIT" When my contract fails due to it being::Listen

There is solidity code that fails here:

error InvalidCheck(uint32 _check);  modifier someCheck(uint32 _check) {   if (check != _check) revert InvalidCheck(check);   _; } 

My frontend application fails on this check and doesn’t provide any context about the error.

"message: ‘cannot estimate gas; transaction may fail or may r…UNPREDICTABLE_GAS_LIMIT"

When my contract fails due to it being paused:

require(!paused(), "Pausable: paused"); 

This provides the "Pausable: paused:" message to my frontend.

Is using require the solution if I want to display error context to the frontend?

Crypto-Compression Algorithms?

Shopping cart
There are no products in the cart!
Continue shopping
0