Billion Bit Software
Extensive testing has been conducted to validate key properties of a strong encryption system:
This encryption method is novel and does not conform to conventional cryptographic structures, making direct theoretical analysis non-trivial. It is a 5-layer transformer that leverages referential transformations, controlled entropy cascades, and layered state evolution to eliminate statistical patterns and resist cryptanalysis. Due to its unconventional architecture, empirical testing has been used as the primary validation method, with specialized modeling in progress to establish additional theoretical proofs.
⚠ Disclaimer: The randomness tests were conducted to determine whether encrypted outputs are statistically consistent with random data.
These results alone do not prove security, nor were they intended to. The objective is to establish whether the encryption produces ciphertext free of detectable patterns or structure.
An approach towards perfect encryption security can be possible, wherein ciphertext that provides no foothold for analysis, pattern recognition, or key inference provides security both theoretically and practically. The results presented here support this hypothesis by a 4-pillar rule:
When applied together and equally, these principles approach the theoretical and practical limits of encryption security by removing all known routes of attack via ciphertext analysis, cleartext manipulation, pattern recognition, bias detection, and key inference.
A carefully chosen approach and methods were designed to provide both broad coverage of test types as well as deep analysis for each type.
Encryption Keys in this algorithm are a randomized permutation of values – keys are not large numeric values.
Key sizes in this algorithm are not fixed and can be any size by this rule: 2^N elements where N also equals the number of bits per element.
Key size is an inherent secret as a byproduct of the key itself.
A 2^8 key (256 bytes) was used for all tests.
A total of 4 randomly generated keys were used.
Each key was used once per analyzed file.
A total of 803 unique cleartext selections of varying sizes were created across 7 groups to provide a diverse selection of transformations.
Purpose: To check short and mid-length randomness for quality and closeness to statistically random data.
NIST STS (Assess) was configured and executed using the following parameters:
Each file analyzed by STS was created by sequentially appending encrypted outputs to the file end-on-end and without padding until it reached or exceeded 25MB. Each encrypted output appended to the file was created from the same cleartext input and the same encryption key.
Because 4 keys were created for testing, the same cleartext value was tested 4 times, meaning 4 input files created for STS and 4 executions of STS.
STS executes 188 different tests across 15 groups and all tests and subtests were allowed to execute.
The full results of all 3,212 executions – including the actual STS textual reports – and the 603,856 individual results are stored in a MariaDB database and is available for download upon request (use the form below to request).
ENT was used to provide early sanity checks on encrypted outputs to look for gross failures of entropy and randomness. While ENT is not as aggressive as NIST STS or PractRand or others, it is a quick check for determining if data should continue on and be tested by more comprehensive tests.
Nonetheless, ENT does provide another perspective of randomness validation and its results in combination (not separately) with other results help paint a comprehensive picture of the quality of the encryption output.
ENT was configured and executed using the following parameters:
Each file analyzed by ENT was created by sequentially appending encrypted outputs to the file end-on-end and without padding until it reached or exceeded 25MB. Each encrypted output appended to the file was created from the same cleartext input and the same encryption key.
Because 4 keys were created for testing, the same cleartext value was tested 4 times, meaning 4 input files created for ENT and 4 executions of ENT.