Research
Why attacks fail
A positive mechanism story: each classical attack family assumes it can convert what it sees into knowledge of a secret. ENI6MA is designed so that conversion never starts. This is not an attack catalog and not a residual-risk disclosure.
Classical attack families fail when they cannot convert surface observations into knowledge of the secret.ValidatedUniform channels, session independence, envelope binding, and burn-before-validate deny frequency, correlation, relay, and replay conversions.
Replay is impossible by design.ShippingThe nonce is burned before validation in a durable ledger; it is spent even when validation later fails.Holds under the reference architecture
Frequency analysis finds a flat channel
Classical frequency analysis needs non-uniform ciphertext. Zone selection plus a private synonym keep every public symbol equiprobable given the challenge, so letter-frequency tables never appear on the wire.
Known- and chosen-plaintext intuition does not apply
There is no reusable plaintext–ciphertext pair for the secret. The protocol proves knowledge without exporting the secret as an encrypted payload an analyst can invert.
Correlation across sessions does not accumulate
Independent challenges, one-shot bearings, and burned nonces mean yesterday’s transcript does not bias tomorrow’s guess. Capture fills surface bits; effective bits stay zero.
Relay and retarget fail the binding
Envelopes bind method, endpoint, request hash, policy hash, tau, and nonce. A proof harvested for one route is not authority on another.
Replay dies at burn
Burn-before-validate spends the nonce before twin validation. A fossil envelope (even a perfect byte-for-byte copy) cannot authorize a second request.
Keylogging captures spent bearings
Nothing typed has lasting value. By the time an observer records a bearing, that round’s authority is already consumed.
Vault breach has no vault of reusable secrets
Identity is compiled into the circuit binary and controlled through registry handles. There is no shared API-key store whose leak grants lasting capability.
Brute force is undirected and rate-limited
With effective bits at zero, the remaining strategy is blind search. Ledger freshness and burn close the free-probe loop that would otherwise make guessing cheap.
Qualified evaluators who need deployment-specific threat mappings can request the Deployment Security Package.
