██╗███╗ ██╗███████╗██╗███╗ ██╗██╗████████╗██╗ ██╗
██║████╗ ██║██╔════╝██║████╗ ██║██║╚══██╔══╝╚██╗ ██╔╝
██║██╔██╗ ██║█████╗ ██║██╔██╗ ██║██║ ██║ ╚████╔╝
██║██║╚██╗██║██╔══╝ ██║██║╚██╗██║██║ ██║ ╚██╔╝
██║██║ ╚████║██║ ██║██║ ╚████║██║ ██║ ██║
╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝ ╚═╝
5 KEMs · 4-LAYER ENCRYPTION CASCADE · 2 MANDATORY PQ SIGNATURES · NATIVE RUST/EGUI DESKTOP · NO CLOUD
VGT Infinity is an experimental, Windows-first file-encryption research system. It is a functional prototype and has not received an independent cryptographic audit or certification.
Do not treat algorithm count as additive security bits.
Found a vulnerability or have an improvement? Open an issue or contact us.
VGT Infinity is a post-quantum file encryption research system built around the versioned VGT-INFINITY-1 suite. It combines five mandatory key-establishment contributions, four authenticated-encryption layers and two mandatory post-quantum signatures into a single managed vault with a native Rust/egui desktop interface.
Conventional file encryption:
Single KEM → one algorithmic failure = total compromise
Single encryption layer → no cascade defense
No post-quantum signatures → forgeable at quantum scale
No managed vault → unstructured, error-prone file handling
VGT Infinity (VGT-INFINITY-1):
5 mandatory KEMs → ML-KEM-1024, FrodoKEM-1344-SHAKE, HQC-256,
AIGIS-ENC-4, X25519 hedge
Universal Combiner → KMAC256 + HKDF-SHA3-512 transcript combiner
Domain-separated key matrix → per-layer subkeys, no reuse
4-layer encryption cascade → Serpent-256-EAX → Twofish-256-EAX →
XChaCha20-Poly1305 → AES-256-GCM-SIV
2 mandatory PQ signatures → ML-DSA-87 + SLH-DSA-SHAKE-256s (both required)
Identity protection → Argon2id (256 MiB · 3 iter · 4 lanes) + AES-256-GCM
Optional offline factor → 32 random bytes stored separately
Managed vault → searchable inventory, bounded directory jail
Native desktop → Rust/egui — no web stack, no CDN
| Algorithm | Type | Role |
|---|---|---|
| ML-KEM-1024 | Lattice (NIST PQC) | Primary post-quantum KEM |
| FrodoKEM-1344-SHAKE | Learning with Errors | Conservative PQ KEM |
| HQC-256 | Code-based | Diversity KEM |
| AIGIS-ENC-4 | Lattice | Additional PQ contribution |
| X25519 | Elliptic curve | Classical hedge |
All five contributions are mandatory — failure of any one prevents key derivation.
ML-KEM + FrodoKEM + HQC + AIGIS + X25519 + OS-CSPRNG + [Offline Factor]
│
Length-prefixed transcript
│
KMAC256
│
HKDF-SHA3-512
│
Domain-separated key matrix
(per-layer subkeys, no reuse)
Plaintext
│
▼
Serpent-256-EAX ← Layer 1
│
▼
Twofish-256-EAX ← Layer 2
│
▼
XChaCha20-Poly1305 ← Layer 3
│
▼
AES-256-GCM-SIV ← Layer 4
│
▼
Ciphertext
All four layers use authenticated encryption. Each layer uses a domain-separated subkey — no key material is shared between layers.
| Algorithm | Type | Requirement |
|---|---|---|
| ML-DSA-87 | Lattice (NIST PQC) | Mandatory |
| SLH-DSA-SHAKE-256s | Hash-based stateless | Mandatory |
Both signatures are required. Container authenticity is established only during restore, after both post-quantum signatures validate. File rows are deliberately labeled SEALED / UNVERIFIED until then.
| Feature | Detail |
|---|---|
| KDF | Argon2id — 256 MiB · 3 iterations · 4 lanes |
| Storage | AES-256-GCM encrypted identity |
| Offline Factor | Optional — exactly 32 random bytes stored separately |
flowchart LR
K1["ML-KEM-1024"]
K2["HQC-256"]
K3["AIGIS-ENC-4"]
K4["FrodoKEM-1344"]
K5["X25519 Hedge"]
E["OS-CSPRNG + optionaler Offline-Faktor"]
C["Infinity Universal Combiner"]
D["Domänengetrennte Schlüsselmatrix"]
A1["Serpent-EAX"]
A2["Twofish-EAX"]
A3["XChaCha20-Poly1305"]
A4["AES-256-GCM-SIV"]
S1["ML-DSA-87"]
S2["SLH-DSA-SHAKE-256s"]
K1 & K2 & K3 & K4 & K5 & E --> C
C --> D
D --> A1 --> A2 --> A3 --> A4
A4 --> S1 --> S2
Native Rust/egui — no web stack, no CDN, no frontend framework.
| Module | Purpose |
|---|---|
| Overview | System state and guided entry points |
| Files | .vgti container management inside the selected vault directory |
| Identity | Key mesh initialization and full attestation |
| Operations | Advanced seal/restore dialogs and offline-factor controls |
| Security | Enforced runtime invariants and full local attestation |
| Audit | Process-local opaque operational event log |
| Feature | Detail |
|---|---|
| Container Format | .vgti — versioned, authenticated |
| Inventory | Searchable container index |
| Naming | Safe, portable names enforced |
| Directory Jail | Bounded physical-directory isolation |
| Seal | One-click — all five KEMs + full cascade |
| Restore | Authenticated — both PQ signatures must validate |
| Requirement | Value |
|---|---|
| OS | Windows 10 or Windows 11, x86-64 |
| Rust | 1.95 or newer with Cargo |
| Python | 3.13 — discoverable as python3.13, python, python3 or via py launcher |
| Disk Space | ~3 GiB for first build and dependencies |
Python is used only as an isolated local provider process for HQC and AIGIS. It has no network access and no contact with the vault or identity directories.
# STATUS: DIAMANT VGT SUPREMESet-ExecutionPolicy-Scope Process Bypass
.\SETUP_WINDOWS.ps1
.\START_VGT_INFINITY.cmdThe setup script:
- Creates
.venvwith pinned provider packages - Performs a locked release build (
Cargo.lock --locked) - Excludes identity directories, containers, offline factors, virtual environments, executables and build output via
.gitignore
VGT Infinity protects files at rest when the host is trustworthy during use.
| Threat | Status |
|---|---|
| Files at rest on trusted host | ✅ Protected |
| Malware / keyloggers on host | ❌ Out of scope |
| Administrator-level memory inspection | ❌ Out of scope |
| Malicious compilers or compromised dependencies | ❌ Out of scope |
| Physical coercion | ❌ Out of scope |
Container metadata disclosure: the current format reveals original filename, size, creation time, suite, algorithms, public-key hashes and whether an offline factor is required.
| Document | Link |
|---|---|
| Technical Data Sheet | docs/TECHNICAL_DATASHEET.md |
| Binary Format Specification | docs/FORMAT_SPECIFICATION.md |
| Threat Model | docs/THREAT_MODEL.md |
| Security Audit Report | docs/SECURITY_AUDIT.md |
| Reproducibility Guide | docs/REPRODUCIBILITY.md |
| Measured Benchmark Results | docs/BENCHMARK_RESULTS.md |
| Tool | Type | Purpose |
|---|---|---|
| 🔑 VGT Infinity | PQ File Encryption | Post-quantum file vault — you are here |
| 🧠 VGT AETHEL | Sovereign AI OS | Local AI intelligence OS with operator governance |
| 🛡️ VGT GeDefense | Linux Security Fabric | Kernel-near defense, XDR, encrypted evidence |
| ⚔️ VGT Sentinel | WAF / IDS | Zero-Trust WordPress WAF |
| ⚡ VGT Auto-Punisher | IDS | L4+L7 Hybrid IDS |
| 🔐 VGT Omega Vault | Encrypted Forms | AES-256-GCM WordPress form vault |
| 🌐 GaiaCom | Communication | Post-quantum federated E2EE platform |
| 📊 VGT Dattrack | Analytics | Sovereign local analytics |
| Method | Address |
|---|---|
| PayPal | paypal.me/dergoldenelotus |
| Bitcoin | bc1q3ue5gq822tddmkdrek79adlkm36fatat3lz0dm |
| ETH / USDT (ERC-20) | 0xD37DEfb09e07bD775EaaE9ccDaFE3a5b2348Fe85 |
AGPLv3 · © 2026 VisionGaia Technology · Cologne, Germany
VGT Infinity is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, version 3. Any derivative work or network-deployed modification must be published under the same license.
Enterprise deployments, TIER-0 audits (VGT SafetySys™) and commercial exception licenses: visiongaiatechnology.de
VISIONGAIATECHNOLOGY – WE ARCHITECT THE FUTURE OF SECURITY.
VGT Infinity — Post-Quantum File Encryption Research // VGT-INFINITY-1 Suite // ML-KEM-1024 + FrodoKEM + HQC-256 + AIGIS-ENC-4 + X25519 // 4-Layer AE Cascade // ML-DSA-87 + SLH-DSA-SHAKE-256s // Argon2id Identity // Managed Vault // Rust/egui Native Desktop // AGPLv3 // Windows 10/11 x64