Keys never
leave your device.
From hardware chip to local model, every layer is built on "data stays put." Not a "we promise not to upload" — a "physically can't upload."
Three-pillar hardware trust root.
Three independent hardware anchors guard private keys and identity. If any one pillar is compromised, the other two can recover.
USB Security Chip
Native Windows support · Device-level private-key carrier · PIN-protected · Auto-locks after repeated failures. Every critical signing requires physical confirmation.
SIM-borne Keys
USIM + 5G super-SIM across three carriers · PQC firmware preloaded · OMAPI / eSIM API · Your phone is your hardware wallet.
Trusted Execution Environment
Hardware fingerprint binding · Isolated sensitive computation · Redundant with U-Key / SIMKey · Resistant to OS escalation and cold-boot attacks.
Data flow, with visible boundaries
Solid lines show paths the data actually travels. Dashed lines show paths that are physically severed.
U-Key
USB security chip — Windows uses Koffi FFI to talk directly to the SIMKey SDK.
Keys are generated and used inside the secure chip; they never leave the hardware. Signing, encryption, and database key management all require physical U-Key confirmation; repeated PIN failures auto-lock. macOS / Linux fall back to software simulation.
SIMKey
SIM-card hardware security via Android OMAPI / iOS eSIM API.
Leverages secure elements built into SIM cards across all three Chinese carriers' USIM and 5G super-SIM cards. 12 security enhancements: eSIM OTA, NFC offline signing, deep TEE integration, post-quantum readiness, satellite-comm SIM, joint HSM authentication.
AES-256 · SQLCipher
Full-database local encryption — keys guarded by U-Key.
SQLite + SQLCipher with WAL mode + busy_timeout for concurrency, parameterized queries to prevent injection. Keys are never stored in plaintext on disk — every unlock requires a hardware signature.
Signal Protocol
P2P end-to-end encrypted messaging · Double Ratchet.
Forward and backward secrecy. Offline message queue with automatic retry. Combined with libp2p + WebRTC for NAT traversal.
Local Ollama
Sensitive data is forced through local model inference.
LLMManager smart routing: sensitive-tagged content → Ollama; general tasks → user-chosen provider. 14+ cloud LLMs available but never default. All prompt / response history stays local.
Post-Quantum Cryptography
ML-KEM key encapsulation · ML-DSA signing · full RSA / ECDSA replacement.
Built on NIST FIPS 203 / 204 standardized algorithms, with SLH-DSA (FIPS 205) hash-based signing as a fallback. Ed25519 / X25519 hybrid mode covers the transition period — current certificates are already forward-secure against quantum threats.
Zero-Knowledge Proofs
zk-SNARK Groth16 · zk-STARK generated locally.
Proofs are generated on the user's device — raw data never reaches the verifier. Use cases: age / identity / asset-threshold proofs, compliance reports, cross-chain bridge security. STARK is post-quantum secure; SNARK is compact and efficient — the system selects per use case.
Hardware Standards & Wallets
FIPS 140-3 compatible · Unified HSM interface.
Plug-and-play with major hardware wallets (Yubikey / Ledger / Trezor). Enterprise edition integrates Thales / Utimaco / Chinese-domestic HSMs. The unified interface hides backend differences — threshold signing, multi-sig policy, key escrow share one API surface.
Compliance
MLPS Level 3 · 4 invention patents · group-standard co-author.
Co-author of the AI group standard T/ZGCMCA 023—2025. Enterprise edition supports full audit logging, DLP policy engine, SIEM export (CEF / LEEF / JSON), and automated SOC2 evidence collection.
Merkle Tree Certificates (MTC) — post-quantum size compression
Drawing on the IETF PLANTS WG protocol, MTC compresses post-quantum signature blowup (SLH-DSA-128f single-cert ~17 KB) back down to ~700 B — a ~97% saving.
- Batch issuance + RFC 6962 Merkle trees + domain-separation prefixes (replay-attack resistant)
- Split-view attack defense (same namespace + tree_size with different roots → MTCA_DOUBLE_SIGNED rejection)
- Multiple transports: in-memory / filesystem drop-zone / real libp2p (TCP+Noise+Yamux) + gossipsub
- Verifier daemon
cc mtc serveauto-subscribes + persists + detects tampering - Marketplace publisher daemon
cc mtc publish-skills(fingerprint diff + atomic state file + auto seq) - Audit-log dual-track signing scaffold
cc audit mtc *(real-time Ed25519 + batch MTC inclusion proof, idempotent batching, 60s/3600s dual compliance paths) - FIPS 205 SLH-DSA-128F real signing —
cc mtc * --alg slh-dsa-128fopt-in PQC,cc mtc verifyauto-detects algorithm - V6 Preview Shell top-bar MTC status widget — audit state / batch queue / signature algorithm visualization
- Phase 3 full release (v0.5): Federation MTCA M-of-N multi-sig landmark —
cc mtc federation join/leave/status/discover, supports heterogeneous Ed25519 + SLH-DSA membership, filesystem drop-zone (NFS / Syncthing / USB) + libp2p gossipsub dual transports for service discovery - Q-ENG-2 backend canary (v0.5):
backend/project-servicebridgesaudit.mtc.*dual-write per tenant rollout; OpLog per-row "pending batch close" badge syncs with web-panel
Phase 0–4 fully landed (476 tests all green, six layers: unit / integration / e2e / desktop-renderer / web-renderer / backend). Audit production blockers cleared on 2026-05-01 (Q-COMP-1 + Q-COMP-2 legal sign-off). Scaffolding ships with enabled=false — each tenant opts in explicitly. Federation discovery supports filesystem (LAN / NAS) and libp2p gossipsub (real P2P) transports. See the user guide and design doc.
Need stricter security guarantees?
For finance, healthcare, and government clients we offer threshold signing, HSM integration, PQC migration, and multi-mode MTCA deployment as deep-customization options.
☎400-1068-687