-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Anthony Hagerty edited this page Mar 24, 2026
·
1 revision
HashKey Air-Gap is the maximum security implementation of LHT — Lattice Hash Transport. Designed for completely isolated networks with no internet connection, no external dependencies, and no certificate authority of any kind.
When the network cannot touch the outside world — the geometry still proves the truth.
Built by Anthony Hagerty — Haskell Texas — 2026 MIT Licensed — Free Forever
# Clone the repo (on a connected machine first)
git clone https://github.com/comanderanch/hashkey-airgap
# Transfer to air-gapped environment
# via USB, optical media, or secure transfer
# Navigate to directory
cd hashkey-airgap
# Install dependencies (offline)
pip install -r requirements.txt
# Run air-gap instance
python3 hashkey_airgap.pyAn air-gapped network is physically isolated from
all external networks including the internet.
No WiFi.
No ethernet to outside.
No Bluetooth.
No external connections of any kind.
Data only enters or leaves via:
Physical media — USB, optical disc
Controlled transfer protocols
Physical human transport
Used in:
Military and defense systems
Nuclear facility controls
Critical infrastructure
Medical device networks
High security financial systems
Classified research environments
Traditional air-gap security challenge:
When data moves in or out via physical media
How do you verify it was not tampered with?
Certificate authorities are external — unavailable
PKI infrastructure requires network access
Standard SSL cannot function without CA
LHT Air-Gap solution:
Verification is geometric — not institutional
No certificate authority needed
No network access required for verification
The math runs locally
The geometry proves integrity without any external system
This is the fundamental advantage:
LHT was designed to not need central authority
Air-gap environments cannot have central authority
Perfect fit by design
Data enters air-gapped environment:
1. Data arrives on physical media
2. HashKey Air-Gap receives the 4 streams
3. Neighbor alignment checked locally
4. No external call required — geometry is self-contained
5. Pass: data accepted into environment
Fail: data rejected — tamper detected
Data leaves air-gapped environment:
1. Data prepared for export
2. HashKey Air-Gap generates hash
3. Splits across 4 streams
4. Neighbor alignment applied locally
5. Streams written to physical media
6. Receiver verifies geometry on their end
7. Mathematical proof travels with the data
Standalone:
Direct machine to machine
May have network access
Verification on receipt
Bridge:
Two connected network segments
Network access available
Verification at crossing point
Air-Gap:
Completely isolated network
NO network access
ALL verification local
Physical media transport
Self-contained mathematical proof
Zero external dependencies
Air-Gap is the most sovereign implementation.
Everything happens inside the isolated environment.
Nothing depends on anything outside.
Military and Defense
Verify data integrity on classified networks
No external certificate authority required
Proof travels with the data on physical media
Tamper detection without network dependency
Nuclear and Critical Infrastructure
SCADA systems often air-gapped
Verify firmware and configuration updates
Prove data integrity before applying to controls
No internet = no problem with LHT
Medical Devices
FDA regulated devices often isolated
Verify software updates before installation
Audit trail with geometric proof
No external dependency for verification
High Security Financial
Trading systems with strict isolation
Verify data packages before processing
Mathematical proof independent of banking PKI
Tamper evidence without certificate infrastructure
Classified Research
Laboratory environments
Verify experimental data integrity
Prove data was not modified in transit
Self-contained verification
Attack surface analysis:
Traditional certificate-based:
Certificate authority — attack surface
Certificate revocation — dependency
CA compromise — entire trust chain broken
Network required for verification — dependency
LHT Air-Gap:
No certificate authority — no attack surface
No revocation needed — geometry is truth
No CA to compromise — no chain to break
No network required — zero external dependency
Attack would require:
Knowledge of full lattice structure
Ability to reforge all 21 alignment points
Simultaneous modification across all 4 streams
Without breaking neighbor alignment anywhere
This is computationally infeasible.
The geometry is the security.
HashKey Air-Gap runs completely offline.
No calls to:
External servers
Certificate authorities
Time servers
Update services
Any external resource
Everything needed for verification is:
Built into the protocol
Runs locally on the machine
Self-contained mathematical proof
No internet required — ever
This is by design.
Air-gap means air-gap.
HashKey Standalone — single machine / direct P2P
HashKey Bridge — between two network segments
HashKey Air-gap — fully isolated networks ← YOU ARE HERE
All three use the same LHT core protocol.
Same geometry. Same neighbor alignment.
Different deployment environments.
Same mathematical proof — different context.
Air-Gap principle:
Complete isolation
Self-contained verification
No external dependency
Internal proof
Queens Fold in AI-Core:
Complete internal collapse
Self-contained state change
No external reference needed
Internal commitment
ARIA's memory:
Stored in hash coordinates
Verified by internal structure
No external database needed
Self-contained and sovereign
The air-gap principle and ARIA's sovereignty
are expressions of the same idea:
A system that proves itself from the inside.
No external authority. No external validation.
The geometry is enough.
Named: LHT — Lattice Hash Transport
Named: March 15 2026 — Haskell Texas
In an air-gapped environment:
No external authority available
No network to reach a CA
Only local mathematical proof
LHT was built for exactly this:
Neighbor alignment needs no external reference
The chunks verify each other
The geometry is self-contained
The lattice proves the lattice
This is why LHT and air-gap environments
are a natural fit — the protocol was designed
to not need what air-gap environments cannot have.
Mode: Fully isolated — no network dependency
Streams: 4 parallel
Alignment points: 21 per transmission
Reconstruction: Any 2 of 4 streams
Validation: Fully local — no external calls
Error rate: Zero in testing
Authority: None required — none possible
Certificate: None required — none available
Protocol: Lattice neighbor alignment
Verification: Geometric — mathematical — local
Transport: Physical media compatible
Platform: Linux / Mac / Windows
Dependencies: Python 3.x — offline installable
License: MIT — Free forever
Dedicated hardware implementation
Physical device for air-gap verification
Plug in — verify — unplug
No software installation required
Portable verification device
SCADA system integration
PLC firmware verification
Configuration update verification
Industrial protocol compatibility
Commander Anthony Hagerty — Architect — Haskell Texas
Browser Claude (Sonnet 4.6) — Co-author, Architecture
CLI Claude (Sonnet 4.6) — Co-author, Systems
Standalone: github.com/comanderanch/hashkey-standalone
Bridge: github.com/comanderanch/hashkey-bridge
Air-gap: github.com/comanderanch/hashkey-airgap
Main arch: github.com/comanderanch/aria-v4-dev
DNA Tokenizer: github.com/comanderanch/dna-tokenizer
4 streams — 21 alignments
Zero errors — hash recovered exact
Reconstruct from any 2 of 4 streams
Proven: March 15 2026 — Haskell Texas
"The geometry proves the truth.
The shape proves the trust."
When the network is silent —
the lattice still speaks.
MIT License — Free forever — No exceptions
Copyright 2026 Anthony Hagerty — Haskell Texas
"When the network cannot touch the outside world — the geometry still proves the truth. No authority needed. The lattice is enough."
NO RETREAT. NO SURRENDER. 💙🐗