ZeqText — Phrase-to-Equation Encrypted Messaging

ZeqText is a secure, real-time messaging application where your mathematical equation IS your identity. No phone numbers, no emails, no passwords — just physics-native authentication powered by the Zeq OS framework.

Overview

ZeqText combines the TESC (Temporal Equation Secure Channel) encryption protocol with Equation Key authentication to deliver a messaging experience that is both cryptographically secure and deeply integrated with the HulyaPulse 1.287 Hz temporal heartbeat.

Every message is encrypted with AES-256-GCM and authenticated with Phase-Locked Authentication Tags (PLATs) — cryptographic tags that are temporally bound to the Zeqond in which the message was sent. This means a message cannot be forged, replayed, or attributed to a different time window.

Launch: Open ZeqText

How It Works

Authentication

ZeqText uses Equation Key authentication — the same system as Zeq Auth:

1. You create a mathematical equation (e.g., x^2 + sin(y*pi) + phi)
2. The equation is evaluated at x = 1.287, y = 0.777 using a safe recursive descent parser
3. SHA-256(equation + ":" + result) produces your unique ZEQ ID (first 12 hex chars)
4. Your equation is never stored — only the hash

Your ZEQ ID is your messaging address. Share it like a phone number.

Encryption

Every message passes through the TESC encryption pipeline:

Layer	Algorithm	Purpose
Symmetric encryption	AES-256-GCM	Message confidentiality
Key derivation	PBKDF2 (SHA-256, 100k iterations)	Derive encryption key from shared secret
Authentication tag	PLAT (Phase-Locked)	Temporal binding to Zeqond tick
Message integrity	GCM built-in 128-bit tag	Tamper detection

Real-Time Communication

ZeqText uses WebSocket connections for instant message delivery. The server (port 3009) handles:

• User authentication and session management
• Real-time message routing between connected clients
• Conversation history storage (encrypted at rest)
• Online presence indicators
• Typing indicators

Built-in AI Assistant

ZeqText includes Zeq AI, an integrated physics and mathematics assistant. Mention @Zeq AI in any conversation to get help with equations, unit conversions, proofs, and general science questions — all without leaving the chat.

Key Features

• Equation Key Identity — Your math equation is your login. No passwords, no emails, no phone numbers.
• AES-256-GCM Encryption — Military-grade symmetric encryption for every message.
• Phase-Locked Authentication — Messages are cryptographically bound to the HulyaPulse temporal tick.
• Real-Time WebSocket Messaging — Instant delivery with typing indicators and presence.
• Zeq AI Integration — Built-in math/physics assistant powered by DeepSeek.
• Conversation Management — Create, archive, and search across conversations.
• Responsive Design — Full glassmorphic UI optimized for desktop and mobile.
• Cross-Tab Session Sync — Login once, authenticated everywhere via localStorage events.

Architecture

┌─────────────────────────┐
│   ZeqText Client (SPA)  │  HTML / CSS / JS
├─────────────────────────┤
│   TESC Encryption Layer  │  AES-256-GCM + PLAT
├─────────────────────────┤
│   WebSocket Transport    │  Real-time messaging
├─────────────────────────┤
│   ZeqText Server (:3009) │  Express + ws + SQLite
├─────────────────────────┤
│   Zeq Auth (:3015)       │  Identity verification
└─────────────────────────┘

Key Operators

Operator	Formula	Role
TESC-ENC	AES-256-GCM(plaintext, key, IV)	Message encryption
TESC-PLAT	HMAC-SHA256(tick ∥ ciphertext)	Temporal authentication
AUTH-HASH	SHA-256(equation + ":" + result)	Identity derivation
AUTH-ZID	zeq- + hash[0:12]	Unique user identifier

Running ZeqText

Via Nginx (Recommended)

http://localhost/apps/zeqtext/

Standalone

cd apps/zeqtext
npm install
node server.js
# → ZeqText running on port 3009

Environment Variables

Variable	Default	Description
ZET_PORT	3009	Server port
ZET_DB	./zet.db	SQLite database path
DEEPSEEK_API_KEY	—	API key for Zeq AI assistant

Security

• Equation is never stored — only its SHA-256 hash
• Parser uses no eval() — safe recursive descent with function whitelist
• All encryption uses the Web Crypto API (browser) or Node.js crypto (server)
• Messages are encrypted in transit (WebSocket) and at rest (SQLite)
• Session tokens expire after 7 days

Related Documentation

• TESC Messaging Protocol — Full TESC encryption specification
• Equation Auth — Complete guide to equation-based identity
• Zeq Auth — The authentication service powering ZeqText