Maria System does not use a key in the classical sense — it does not rely on a static bit string shared across the entire message. Instead, it uses a dynamic process key, created during system execution and inseparable from the symbol deformation process.
This approach is fundamentally different from AES, RSA, ECC and classical cryptographic methods, where the key:
In Maria System, the key does not exist as data — it exists only as a process.
A process key is a set of dynamic parameters that create a unique deformation context for each individual symbol.
Process key = a deformation state that arises during symbol processing and never exists as a single storable entity.
This is a fundamental difference:
A sequence of binary transitions describing how a symbol decays in the deformation rhythm.
This is the “movement map” of the symbol that the receiver must reconstruct.
Each character has its own number of bits n:
Variable length = variable local per-symbol key.
This already provides resistance similar to One-Time Pad, but generated procedurally.
The external file fazy_deformacyjne.txt acts as a “trajectory dictionary”.
A time/sequential factor that changes how trajectories are interpreted.
It may depend on:
The rhythm is an extra source of entropy.
Each of the above would be only a parameter on its own. The process key appears only when the interpretation logic becomes part of the key.
How the system uses:
… is itself part of the key.
In cryptographic classification:
A key is any parameter necessary to reverse a transformation.
In Maria System, in order to recover the original symbol, the receiver must have:
Without these, not even a single character can be recovered.
This fully satisfies the definition of a cryptographic key.
The difference is that the key is:
| Feature | Classical key | Process key (Maria System) |
|---|---|---|
| Form | static bit string | dynamic process state |
| Number of keys | one per message | one per symbol |
| Existence | before and after | only during execution |
| Extractability | high | practically zero |
| Leak impact | catastrophic | useless |
| Algorithm separation | separate | inseparable |
| Entropy | constant | grows with each symbol |
Because it does not exist as data.
Impossible to achieve in static algorithms.
One-Time Pad (OTP) is theoretically perfect, but requires:
The process key applies the same logic, but generates keys locally and dynamically, without storage.
There is no single object called “the key”.
There is only a process.
Example: an attacker obtains the phase library.
Without:
…it is useless.
(easy to quote in technical papers)
A process key is a set of dynamic deformation states that arise during symbol processing and determine its final representation. The process key does not exist as a static value, is not stored, and is not transmitted — it is generated and consumed in real time during algorithm operation.
Maria System does not use a classical key.
Instead, it uses a process key that emerges during the processing of each character.
This key is distributed across trajectories, phases, rhythms and indexes.
It does not exist as a file, number or bit string.
It is practically impossible to steal and cannot be stored.
Each symbol has its own unique key, providing security unavailable in classical algorithms.
This is a completely new key model, unique to Maria System.