Hexlish Alphabet for English, Constructed Languages and Cryptography: Automatic, Structural Compression with a Phonetic Hexadecimal Alphabet
DOI : https://doi.org/10.5281/zenodo.13139469
Hexlish is a legible, sixteen-letter alphabet for writing the English language and for encoding text as legible base 16 or compressed binary. Texts composed using the alphabet are automatically compressed by exactly fifty percent when converted from Hexlish characters into binary characters. Although technically lossy, this syntactic compression enables recovery of the correct English letters via syntactic reconstruction. The implementer can predict the size of the compressed binary file and the size of the text that will result from decompression. Generally it is intuitive to recognize English alphabet analogues to Hexlish words. This makes Hexlish a legible alternative to the standard hexadecimal alphabet.
@cryptography@lemmy.ml @crypto@infosec.pub
#Hexlish #Conlang #Alphabets #Encoding #Cryptography #Ciphers #Crypto
If you are referring to MEGARAND, no. There is no need for that since all of that has already been done over the years for the underlying primitives:
/dev/urandom … b2sum … shuf … chacha20 …
These primitives have been run through the gauntlet for years and are known to produce or use very good entropy. Chacha20 is especially prized for this and taking already random data and running it through the chacha20 cipher with random keys and/or salts is a very nice hedge against patterns and biases. Megarand stretches these primitive outputs to build a much larger pool for wherever you might want a big initial pool for pads, tokens, seeds, whatever.
If you’re paranoid you can run dieharder tests on the output, but it would just be placebo at this point.