---

The Math of Absolute Lock-Down

CinciaKeys v3.0 wraps your raw ML-KEM 1024 or ML-DSA 87 private keys in a hardened, multi-layered cryptographic fortress:

• The 700000-Iteration Key-Stretching Bottleneck: When you type your recovery passphrase, the engine forces it through a brutal 700000-iteration hashing loop powered by SHA-512. This deliberate computational wall severely throttles brute-force attempts. Automated GPU or dictionary cracking scripts are rendered completely useless against this time-work factor.
• Authenticated Symmetric Ciphers (AES-256-GCM): Your private data is natively encrypted using military-grade AES-GCM (AEAD). Without your exact passphrase sequence, the data is mathematically unreadable, while the integrated Galois tag guarantees that no one can tamper with a single byte of your file.
• The Structural CSPRNG Matrix: The encrypted ciphertext is split and dynamically hidden inside a structured 97-row text matrix. The other 95 rows are backfilled with genuine cryptographic entropy via crypto.getRandomValues(). Because fake rows perfectly mimic the real ones, your data remains statistically indistinguishable from background noise under advanced analysis.

How to Use the Cincia keys vault

1. Creating your Nest File

1. Open the Cincia keys vault panel within BennyPQ.
2. Enter your custom Secret Phrase.
3. The engine will instantly assemble the mixture of 95 decoys and 2 altered key fragments.
4. Download the resulting file, which saves by default as a harmless-looking nest.txt.

2. Rebuilding your Private Keys

1. To encrypt, sign, or decrypt files, you must first reconstruct your identity.
2. Load your nest.txt file into the BennyPQ interface.
3. Provide your exact Secret Phrase.
4. The Cincia code will read the phrase, isolate the 2 correct fragments from the 95 fakes, revert the changed bytes to their original state, and rebuild your ML-KEM and ML-DSA private keys in secure memory. Once rebuilt, they are automatically loaded into the proper input based on their type (KEM or DSA), so you do not have to load them manually.

Even if a malicious actor steals the nest.txt file, they are looking at a digital haystack. They cannot run standard cryptographic attacks because they don’t know which data is real, and even if they guess the right fragments, the keys remain broken until the exact byte-mutation logic is reversed by the secret phrase.

---

📝 Summary Checklist for Maximum Local Security

To make sure your files remain absolutely un-cracking while sitting on your filesystem, keep these rules in mind:

• Always use a long passphrase: The 700000-loop slowdown relies heavily on entropy. A phrase with 5-6 random words Upper and lower case makes your local file mathematically irreversible.
• Use the Firefox browser in Private mode.

---

When you use Firefox in Private Browsing mode, the browser does not save your browsing history, cookies, search history, or temporary cached files to your disk.

Here is exactly how it handles memory and data:

• Volatile Memory (RAM): While the private window is open, it keeps active session data (like temporary cookies and cache) in your computer’s short-term memory (RAM).
• Automatic Cleanup: As soon as you close all private windows, Firefox immediately wipes this data from the RAM and completely cleans up the session.

You may know that bridging modern content management systems with secure community platforms is only half the battle. The real frontier of the modern web lies in Data Sovereignty and Post-Quantum Cryptography (PQC).

Recently, has been released version 3.0.8 of the w3myPQ WordPress Plugin, featuring the local file obfuscation engine: CinciaKeys (v2.0).

While it beautifully masked plaintext private keys, a recent, rigorous structural review led me to a critical conclusion: character-shifting transposition methods, no matter how clever, are ultimately vulnerable to targeted static analysis. They are reversible under the right conditions.

---

🛡️ Why use CinciaKeys to secure keys on the local filesystem

Standard encryption tools hide your private key by locking it inside a heavy iron safe left right in the middle of your room. An attacker scanning your hard drive can instantly flag it and try to crack it. CinciaKeys v3.0 doesn’t just lock the key; it dissolves it into a crowd of 95 identical decoys.

Here is how it outperforms traditional storage methods on the same device:

• Strips Malware of a Target Signature: Traditional encrypted files leave clear patterns that automated drive-scanning malware can easily flag. CinciaKeys maps your real data into a matrix alongside 95 fake rows (95 decoys and 2 altered key fragments) built with cryptographically secure random numbers (crypto.getRandomValues()), making the entire file look like uniform background noise.
• Neutralizes Intersection Attacks: Reusing passphrases on older versions allowed hackers to compare files and spot matching row patterns. The new Base-36 framework (0-9, a-x) combined with AES-256-GCM scatters characters across an expanded alphabet that standard keys never natively use, rendering cross-file comparison algorithms useless.
• Crushes Local GPU Brute-Forcing: If a bad actor physically steals your nest.txt file from your filesystem, they will try to run high-speed cracking scripts to guess your password. The 700000-iteration SHA-512 key-stretching loop forces their hardware to run a massive computational workload for every single guess, grinding automated cracking speeds to an absolute crawl.

Why 97 rows in the nest.txt file?
The number 97 was chosen because it is the largest two-digit prime number. In cryptography, prime numbers are highly effective at preventing predictable structural patterns that an attacker might try to exploit. While the code currently uses 97 rows (95 fake fragments + 2 real pieces) to keep the file lightweight and ensure instant loading in any browser, it could easily be expanded to use larger three-, four-, or multi-digit prime numbers for even higher entropy.