yakmesh 1.4.0 → 1.5.1

package/CHANGELOG.md

@@ -2,6 +2,67 @@
 
 All notable changes to YAKMESH will be documented in this file.
 
+## [1.5.0] - 2026-01-17
+
+### 🔧 Critical Fix: Network Identity Unification
+
+This release fixes a fundamental issue where nodes running identical code were generating different node IDs, preventing them from recognizing each other as peers on the same network.
+
+#### The Problem (v1.4.0 and earlier)
+- Node IDs were derived from **random public key** entropy
+- Each node got a unique ID regardless of codebase
+- Nodes couldn't verify they were on the same network by comparing node IDs
+
+#### The Solution (v1.5.0)
+- Node IDs now composed of TWO parts:
+  1. **Network Name** - Derived from codebase hash (SAME for all nodes on network)
+  2. **Instance ID** - Derived from public key (UNIQUE per node)
+- Format: `node-[network-name]-[instance-id]`
+- Example: `node-qubit-lattice-prism-pq-a7x9`
+
+#### Human Verification
+- All nodes on the same network share the same **network name** and **verification phrase**
+- Users can verbally verify: "Are you on qubit-lattice-prism?"
+- If network names match = same code = can peer
+
+### Changed
+- `identity/node-key.js` - Node ID generation now uses codebase hash for network name
+- `server/index.js` - Oracle initialized BEFORE identity (provides codebase hash)
+- `node-key.json` now stores `networkName`, `verificationPhrase`, and `codebaseHash`
+- Identity automatically regenerates if codebase changes
+
+### Added
+- `setCodebaseHash()` / `getCodebaseHash()` exports from identity module
+- `getNetworkIdentity()` method on NodeIdentity class
+- Codebase change detection - warns and regenerates identity on code updates
+
+### Breaking Changes
+- Existing `node-key.json` files will trigger identity regeneration
+- Old node IDs are no longer compatible with v1.5.0 network naming
+
+---
+
+## [1.4.0] - 2026-01-16
+
+### 🔐 Yakmesh Annex - Post-Quantum Encrypted P2P Channels
+
+#### Annex: Autonomous Network Negotiated Encrypted eXchange
+- ML-KEM-768 (Kyber) key encapsulation for quantum-resistant key exchange
+- AES-256-GCM authenticated encryption for message confidentiality
+- Perfect Forward Secrecy - session keys rotate every 5 minutes or 10,000 messages
+- Replay protection via sequence numbers in AAD
+- Three-message handshake: INIT → ACCEPT → CONFIRM
+
+### Added
+- `mesh/annex.js` - Complete Annex implementation (744 lines)
+- AnnexEnvelope class for encrypted message wrapping
+- AnnexSession class for per-peer session management
+- Annex main class for channel orchestration
+- Documentation at `website/docs/annex.html`
+- Whitepaper section 3.4 for Yakmesh Annex
+
+---
+
 ## [1.3.2] - 2026-01-17
 
 ### Added
@@ -44,26 +105,26 @@ All notable changes to YAKMESH will be documented in this file.
 
 ### 🌟 Major New Systems - "A Beacon in the Darkness"
 
-#### ECHO™ - Encrypted Coordinate Heuristic Oracle
+#### ECHO - Encrypted Coordinate Heuristic Oracle
 - Privacy-preserving network topology discovery
 - Virtual coordinate system for latency estimation
 - Encrypted timing probes (AES-256-GCM)
 - Route optimization through coordinate-based pathfinding
 
-#### PULSE™ - Precision Universal Latency Sync Engine  
+#### PULSE - Precision Universal Latency Sync Engine  
 - Mesh heartbeat system with cryptographic proofs
 - Node liveness detection (alive/suspect/dead states)
 - Network partition detection with confidence scoring
 - Raft-inspired leader election using heartbeat chains
 
-#### PHANTOM™ - Post-quantum Hidden Anonymous Network Transmission
+#### PHANTOM - Post-quantum Hidden Anonymous Network Transmission
 - **First-ever post-quantum onion routing implementation**
 - ML-KEM-768 (Kyber) key encapsulation per layer
 - Multi-layer encryption with temporal padding
 - Decoy traffic injection (10% probability)
 - Fixed packet sizing to prevent length analysis
 
-#### BEACON™ - Broadcast Emergency Alert Channel Over Network
+#### BEACON - Broadcast Emergency Alert Channel Over Network
 - Priority message propagation (ROUTINE → CRITICAL)
 - Flood-based protocol with intelligent deduplication
 - Proof-of-receipt for delivery confirmation
@@ -96,7 +157,7 @@ All notable changes to YAKMESH will be documented in this file.
 ## [1.2.0] - 2026-01-15
 
 ### Added
-- **TME™ (Temporal Mesh Encoding)** - Novel packet resilience system
+- **TME (Temporal Mesh Encoding)** - Novel packet resilience system
   - Encodes data across TIME, not space
   - Temporal slicing with cryptographic chaining
   - Predictive reconstruction from timing proofs

package/README.md

@@ -180,7 +180,7 @@ See [TRADEMARK.md](TRADEMARK.md) for trademark usage policy.
   <strong><a href="https://yakmesh.dev">yakmesh.dev</a></strong>
   <br><br>
   <p>
-    <a href="https://discord.gg/E62tAE2wGh">💬 Discord</a> •
+    <a href="https://discord.gg/8mSPfbJB8N">💬 Discord</a> •
     <a href="https://t.me/yakmesh">📱 Telegram</a> •
     <a href="https://x.com/yakmesh_dev">𝕏 Twitter</a>
   </p>

package/announcements/discord-v1.4.0.md

@@ -0,0 +1,86 @@
+# 🦬 YAKMESH™ v1.4.0 — Annex Encrypted P2P + Trademark Cleanup!
+
+Hey everyone! Fresh release just dropped:
+
+## ✅ What's New
+
+### 🔐 Yakmesh Annex - Encrypted Point-to-Point Messaging
+**A**utonomous **N**etwork **N**egotiated **E**ncrypted e**X**change
+
+Finally! Secure direct messaging between peers with:
+- **ML-KEM768 (Kyber)** - Quantum-resistant key exchange
+- **AES-256-GCM** - Authenticated symmetric encryption
+- **Perfect Forward Secrecy** - Auto re-keys every 5 minutes
+- **Replay Protection** - Sequence numbers + authenticated data
+
+```javascript
+// Send encrypted message to peer
+await node.annex.send(peerId, { 
+  type: 'private',
+  data: 'Only you can read this!' 
+});
+
+// Receive encrypted messages
+node.annex.onMessage(({ from, payload }) => {
+  console.log(`Secret from ${from}:`, payload);
+});
+```
+
+**Use cases:**
+- 🔔 Beacon acknowledgments with encryption
+- 📦 Authenticated content delivery
+- 💬 Private peer-to-peer chat
+- 🔑 App-specific secure payloads
+
+### ⚖️ Trademark Cleanup
+We did a legal sweep and removed ™ claims from protocol names that conflict with existing trademarks:
+- Yakmesh Phantom (was PHANTOM)
+- Yakmesh Beacon (was BEACON)
+- Yakmesh Echo (was ECHO)
+- Yakmesh Pulse (was PULSE)
+- Yakmesh Annex (new!)
+
+**YAKMESH™ remains our registered trademark** - we own the patent! 🎉
+
+### 🐛 Bug Fixes
+- Fixed gossip propagation for content distribution
+- Messages now properly wrapped with type field for routing
+- Multi-node content sync working reliably
+
+## 📊 Protocol Stack
+
+```
+┌─────────────────────────────────────────┐
+│ HTTP API        │ Public CDN layer      │
+├─────────────────┼───────────────────────┤
+│ Annex          │ ML-KEM768 + AES-256   │  ← NEW!
+├─────────────────┼───────────────────────┤
+│ Gossip         │ ML-DSA-65 signed      │
+├─────────────────┼───────────────────────┤
+│ Beacon         │ Flood + signed        │
+├─────────────────┼───────────────────────┤
+│ Phantom        │ Onion + multi-KEM     │
+├─────────────────┼───────────────────────┤
+│ Mesh           │ ML-DSA-65 + Code Proof│
+└─────────────────┴───────────────────────┘
+```
+
+## 📦 Install
+
+```bash
+npm install yakmesh@1.4.0
+```
+
+## 🔗 Links
+- 🌐 Website: https://yakmesh.dev
+- 📖 GitHub: https://github.com/yakmesh/yakmesh
+- 📦 npm: https://npmjs.com/package/yakmesh
+
+---
+
+**What's next?**
+- Test Annex with multi-node encrypted messaging
+- Deployment packages for easy self-hosting
+- More protocol integrations
+
+Questions? Drop them here! 🦬

package/announcements/discord-v1.5.0.md

@@ -0,0 +1,45 @@
+# Yakmesh v1.5.0 - Network Identity Unification
+
+**🦬 Yakmesh v1.5.0 is here!**
+
+This release introduces **Network Identity Unification** - a fundamental improvement to how nodes identify themselves and verify they're running the same code.
+
+## 🔑 What's New
+
+### Network Identity Unification
+Node IDs now contain TWO components:
+- **Network Name** - Derived from codebase hash (SAME for all nodes on network)
+- **Instance ID** - Derived from public key (UNIQUE per node)
+
+Format: `node-[network-name]-[instance-id]`
+Example: `node-grid-carbide-reveal-pq-QHZx`
+
+**Why this matters:**
+✅ Nodes running identical code share the same network name
+✅ Visual verification: same network name = same code = can trust peer
+✅ Each node still has a unique instance identifier
+✅ Human-readable verification phrases for extra confirmation
+
+### Automatic Port Fallback
+No more "port in use" crashes! If default ports (3000, 9001) are occupied, the node automatically finds the next available port.
+
+### Process Management Script
+New `scripts/start.sh` for proper background process management:
+```bash
+./scripts/start.sh start   # Start in background
+./scripts/start.sh stop    # Clean shutdown  
+./scripts/start.sh restart # Stop + start
+./scripts/start.sh status  # Check if running
+./scripts/start.sh logs    # View logs
+```
+
+## ⚠️ Breaking Change
+Existing `node-key.json` files will trigger identity regeneration on first v1.5.0 startup. This is expected - the new format ensures network name derivation from codebase hash.
+
+## 📦 Install/Upgrade
+```bash
+npm install yakmesh@1.5.0
+```
+
+---
+🔗 https://yakmesh.dev | 💬 Discord: https://discord.gg/8mSPfbJB8N

package/announcements/telegram-v1.4.0.md

@@ -0,0 +1,43 @@
+# Telegram Post for v1.4.0
+
+---
+
+🦬 **YAKMESH™ v1.4.0 Released!**
+
+**🔐 NEW: Yakmesh Annex**
+Encrypted point-to-point messaging between mesh peers!
+
+**A**utonomous **N**etwork **N**egotiated **E**ncrypted e**X**change
+
+✨ **Features:**
+• ML-KEM768 (Kyber) quantum-resistant key exchange
+• AES-256-GCM authenticated encryption
+• Perfect forward secrecy (auto re-key)
+• Replay protection
+• Integrated into server startup
+
+**💡 Use Cases:**
+• Private peer-to-peer messaging
+• Encrypted beacon acknowledgments
+• Authenticated content delivery
+• App-specific secure payloads
+
+**🐛 Also Fixed:**
+• Gossip content propagation
+• Multi-node sync reliability
+
+**📦 Install:**
+```
+npm install yakmesh@1.4.0
+```
+
+**🔗 Links:**
+• GitHub: github.com/yakmesh/yakmesh
+• npm: npmjs.com/package/yakmesh
+• Website: yakmesh.dev
+
+---
+
+*"Changes pass through math alone"* 🔐
+
+#YAKMESH #PostQuantum #P2P #Cryptography

package/announcements/telegram-v1.5.0.md

@@ -0,0 +1,13 @@
+🦬 Yakmesh v1.5.0 Released
+
+Network Identity Unification - nodes now share network names when running identical code.
+
+New ID format: node-[network-name]-[instance-id]
+
+• Same network name = same codebase = can peer
+• Automatic port fallback
+• Process management script
+
+npm install yakmesh@1.5.0
+
+https://yakmesh.dev

package/announcements/x-v1.4.0.md

@@ -0,0 +1,58 @@
+# X (Twitter) Post for v1.4.0
+
+## Main Tweet
+
+🦬 YAKMESH™ v1.4.0 is live!
+
+🔐 NEW: Yakmesh Annex - Encrypted P2P messaging
+• ML-KEM768 quantum-resistant key exchange
+• AES-256-GCM authenticated encryption
+• Perfect forward secrecy
+• "Changes pass through math alone"
+
+npm install yakmesh@1.4.0
+
+🧵👇
+
+---
+
+## Thread
+
+### Tweet 2
+What is Annex?
+
+**A**utonomous **N**etwork **N**egotiated **E**ncrypted e**X**change
+
+Point-to-point encrypted channels between mesh peers. No plaintext on the wire - only quantum-resistant ciphertext.
+
+### Tweet 3
+Use cases for Annex:
+🔔 Encrypted beacon acknowledgments
+📦 Authenticated content delivery  
+💬 Private peer-to-peer messaging
+🔑 App-specific secure payloads
+
+All while maintaining mesh topology!
+
+### Tweet 4
+Also in v1.4.0:
+✅ Fixed gossip content propagation
+✅ Multi-node sync now reliable
+⚖️ Trademark cleanup (legal housekeeping)
+
+YAKMESH™ is our only trademark - protocol names are descriptive.
+
+### Tweet 5
+The full protocol stack:
+
+HTTP → Annex → Gossip → Beacon → Phantom → Mesh
+
+Each layer adds security. Annex gives you encrypted P2P on top of our post-quantum signed mesh.
+
+📖 https://github.com/yakmesh/yakmesh
+📦 https://npmjs.com/package/yakmesh
+
+---
+
+## Hashtags
+#PostQuantum #Cryptography #P2P #DecentralizedWeb #WebDev #NodeJS #OpenSource #Kyber #MLKEM

package/announcements/x-v1.5.0.md

@@ -0,0 +1,17 @@
+🦬 Yakmesh v1.5.0: Network Identity Unification
+
+Node IDs now tell you if peers run the same code:
+
+node-grid-carbide-reveal-pq-QHZx
+     ^^^^^^^^^^^^^^^^^ unique
+     network name      instance
+
+✅ Same network name = same codebase = trustable peer
+✅ Auto port fallback when ports busy
+✅ Process management script included
+
+Breaking: Nodes regenerate identity on first run (expected)
+
+npm install yakmesh@1.5.0
+
+#PostQuantum #P2P #DecentralizedWeb #OpenSource

package/deploy-packages/yakmesh-full/start.sh

@@ -0,0 +1,207 @@
+#!/bin/bash
+#
+# YAKMESH Self-Contained Node - Start Script
+# Complete stack with bundled binaries (Node.js, Caddy, PHP)
+# No external dependencies required.
+#
+
+set -e
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+cd "$SCRIPT_DIR"
+
+echo ""
+echo "  ====================================="
+echo "      YAKMESH SELF-CONTAINED"
+echo "      Complete Stack - All Bundled"
+echo "  ====================================="
+echo ""
+
+# Detect OS
+OS="$(uname -s)"
+ARCH="$(uname -m)"
+
+case "$OS" in
+    Linux*)  PLATFORM="linux" ;;
+    Darwin*) PLATFORM="darwin" ;;
+    *)       echo "[ERROR] Unsupported OS: $OS"; exit 1 ;;
+esac
+
+case "$ARCH" in
+    x86_64)  ARCH_NAME="x64" ;;
+    aarch64|arm64) ARCH_NAME="arm64" ;;
+    *)       echo "[ERROR] Unsupported architecture: $ARCH"; exit 1 ;;
+esac
+
+# Paths to bundled binaries
+NODE_BIN="$SCRIPT_DIR/bin/node/bin/node"
+CADDY_BIN="$SCRIPT_DIR/bin/caddy"
+PHP_BIN="$SCRIPT_DIR/bin/php/php-cgi"
+PHP_INI="$SCRIPT_DIR/bin/php/php.ini"
+
+# Check for bundled binaries
+MISSING=()
+[ ! -f "$NODE_BIN" ] && MISSING+=("Node.js (bin/node/bin/node)")
+[ ! -f "$CADDY_BIN" ] && MISSING+=("Caddy (bin/caddy)")
+[ ! -f "$PHP_BIN" ] && MISSING+=("PHP (bin/php/php-cgi)")
+
+if [ ${#MISSING[@]} -gt 0 ]; then
+    echo "[ERROR] Missing bundled binaries:"
+    for item in "${MISSING[@]}"; do
+        echo "  - $item"
+    done
+    echo ""
+    echo "This is a self-contained package. Binaries should be included."
+    echo "Please re-download the full package from yakmesh.dev"
+    exit 1
+fi
+
+# Show versions
+NODE_VERSION=$("$NODE_BIN" --version)
+echo "[OK] Node.js $NODE_VERSION (bundled)"
+
+PHP_VERSION=$("$PHP_BIN" -v 2>/dev/null | head -1 | grep -oP 'PHP \K[\d.]+')
+echo "[OK] PHP $PHP_VERSION (bundled)"
+
+CADDY_VERSION=$("$CADDY_BIN" version 2>/dev/null | head -1)
+echo "[OK] Caddy $CADDY_VERSION (bundled)"
+
+# Create directories
+mkdir -p "$SCRIPT_DIR/htdocs"
+mkdir -p "$SCRIPT_DIR/data/content"
+mkdir -p "$SCRIPT_DIR/logs"
+
+# Create default index.html if not exists
+INDEX_PATH="$SCRIPT_DIR/htdocs/index.html"
+if [ ! -f "$INDEX_PATH" ]; then
+    cat > "$INDEX_PATH" << 'EOF'
+<!DOCTYPE html>
+<html>
+<head>
+    <title>YAKMESH Node</title>
+    <style>
+        body { font-family: system-ui; max-width: 800px; margin: 50px auto; padding: 20px; background: #f8f9fa; }
+        h1 { color: #2d5016; }
+        code { background: #e9ecef; padding: 2px 6px; border-radius: 4px; font-family: 'Consolas', monospace; }
+        .status { display: inline-block; width: 10px; height: 10px; border-radius: 50%; margin-right: 8px; }
+        .online { background: #28a745; }
+        .card { background: white; padding: 20px; border-radius: 8px; margin: 20px 0; box-shadow: 0 2px 4px rgba(0,0,0,0.1); }
+    </style>
+</head>
+<body>
+    <h1>🦬 YAKMESH Self-Contained Node</h1>
+    <p>Your complete Yakmesh stack is running.</p>
+    
+    <div class="card">
+        <h2>Services</h2>
+        <p><span class="status online"></span><strong>Web Server:</strong> <a href="http://localhost:8080">http://localhost:8080</a></p>
+        <p><span class="status online"></span><strong>Content API:</strong> <a href="http://localhost:3000/content">http://localhost:3000/content</a></p>
+        <p><span class="status online"></span><strong>PHP:</strong> <a href="http://localhost:8080/info.php">http://localhost:8080/info.php</a></p>
+        <p><span class="status online"></span><strong>Mesh P2P:</strong> <code>ws://localhost:9001</code></p>
+    </div>
+    
+    <div class="card">
+        <h2>Content API</h2>
+        <ul>
+            <li><code>GET /content</code> - List all content</li>
+            <li><code>GET /content/:hash</code> - Get content by hash</li>
+            <li><code>POST /content</code> - Store new content</li>
+        </ul>
+    </div>
+    
+    <div class="card">
+        <h2>Bundled Software</h2>
+        <ul>
+            <li>Node.js 20 LTS</li>
+            <li>PHP 8.3</li>
+            <li>Caddy 2.8</li>
+        </ul>
+    </div>
+    
+    <p><a href="https://yakmesh.dev">yakmesh.dev</a> | <a href="https://github.com/yakmesh/yakmesh">GitHub</a></p>
+</body>
+</html>
+EOF
+fi
+
+# Create PHP info file
+PHP_INFO_PATH="$SCRIPT_DIR/htdocs/info.php"
+if [ ! -f "$PHP_INFO_PATH" ]; then
+    echo "<?php phpinfo();" > "$PHP_INFO_PATH"
+fi
+
+# Install node_modules using bundled Node if needed
+if [ ! -d "node_modules" ]; then
+    echo "[INFO] Installing Node.js dependencies..."
+    export PATH="$(dirname "$NODE_BIN"):$PATH"
+    "$NODE_BIN" "$(dirname "$NODE_BIN")/npm" install 2>&1 || true
+fi
+
+echo ""
+echo "[INFO] Starting services..."
+echo ""
+
+# PID file
+PID_FILE="$SCRIPT_DIR/data/.pids"
+
+# Cleanup function
+cleanup() {
+    echo ""
+    echo "[INFO] Shutting down..."
+    
+    if [ -f "$PID_FILE" ]; then
+        while read -r pid; do
+            kill "$pid" 2>/dev/null || true
+        done < "$PID_FILE"
+        rm -f "$PID_FILE"
+    fi
+    
+    # Kill any orphan processes
+    pkill -f "yakmesh.*node" 2>/dev/null || true
+    pkill -f "php-cgi" 2>/dev/null || true
+    pkill -f "caddy.*yakmesh" 2>/dev/null || true
+    
+    echo "[OK] All services stopped"
+    exit 0
+}
+
+trap cleanup SIGINT SIGTERM
+
+# Start PHP FastCGI
+"$PHP_BIN" -b 127.0.0.1:9000 -c "$PHP_INI" > "$SCRIPT_DIR/logs/php.log" 2>&1 &
+PHP_PID=$!
+echo "$PHP_PID" > "$PID_FILE"
+echo "  ✓ PHP FastCGI started (PID: $PHP_PID)"
+
+# Start Yakmesh node
+export YAKMESH_CONFIG="$SCRIPT_DIR/config/yakmesh.config.js"
+"$NODE_BIN" server/index.js > "$SCRIPT_DIR/logs/mesh.log" 2>&1 &
+MESH_PID=$!
+echo "$MESH_PID" >> "$PID_FILE"
+echo "  ✓ Mesh Node started (PID: $MESH_PID)"
+
+sleep 2
+
+# Start Caddy
+"$CADDY_BIN" run --config "$SCRIPT_DIR/config/Caddyfile" > "$SCRIPT_DIR/logs/caddy.log" 2>&1 &
+CADDY_PID=$!
+echo "$CADDY_PID" >> "$PID_FILE"
+echo "  ✓ Caddy started (PID: $CADDY_PID)"
+
+echo ""
+echo "  ========================================"
+echo "  All services running!"
+echo "  ========================================"
+echo ""
+echo "  Web Server:    http://localhost:8080"
+echo "  PHP Info:      http://localhost:8080/info.php"
+echo "  Content API:   http://localhost:3000/content"
+echo "  Mesh P2P:      ws://localhost:9001"
+echo ""
+echo "  Logs: $SCRIPT_DIR/logs/"
+echo ""
+echo "  Press Ctrl+C to stop all services"
+echo ""
+
+# Wait for processes
+wait

package/deploy-packages/yakmesh-full/stop.sh

@@ -0,0 +1,30 @@
+#!/bin/bash
+#
+# YAKMESH Self-Contained Node - Stop Script
+#
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PID_FILE="$SCRIPT_DIR/data/.pids"
+
+echo ""
+echo "[INFO] Stopping YAKMESH services..."
+
+# Stop processes from PID file
+if [ -f "$PID_FILE" ]; then
+    while read -r pid; do
+        if kill -0 "$pid" 2>/dev/null; then
+            kill "$pid" 2>/dev/null
+            echo "[OK] Stopped process $pid"
+        fi
+    done < "$PID_FILE"
+    rm -f "$PID_FILE"
+fi
+
+# Kill any remaining processes
+pkill -f "php-cgi" 2>/dev/null && echo "[OK] PHP stopped" || true
+pkill -f "yakmesh.*node" 2>/dev/null && echo "[OK] Node processes stopped" || true
+pkill -f "caddy" 2>/dev/null && echo "[OK] Caddy stopped" || true
+
+echo ""
+echo "[OK] All services stopped"
+echo ""