Repository navigation
v1.0.2
Zixt v1.0.2 Release Notes
Release Date: April 19, 2025
GitHub Repository: NetworkNerd1337/zixt
Version: 1.0.2
Zixt v1.0.2 introduces groundbreaking enhancements to our quantum-secure messaging platform, reinforcing our commitment to privacy and security. This release adds Zero-Knowledge Proofs (zk-SNARKs) for private user authentication and anonymous message metadata, and DTLS-encrypted Kademlia DHT for secure peer discovery and blockchain propagation. These features build on Zixt’s post-quantum cryptography (Kyber1024, SPHINCS+, AES-256-GCM, SHA3-512), ensuring your communications and metadata remain protected against both current and future threats.
Designed for Ubuntu 24.04, Zixt v1.0.2 offers real-time messaging, secure file sharing, a proprietary blockchain ledger, and robust user management, all secured by Let’s Encrypt HTTPS. This release refines the installation process, enhances security, and sets the stage for future scalability and privacy improvements.
🚀 What's New
-
Zero-Knowledge Proofs (ZKPs):
- Implemented zk-SNARKs using
circomandsnarkjsto enable private user authentication and anonymous message metadata. - Protects sensitive metadata (usernames, sender details, timestamps) in the database and blockchain, ensuring privacy even in case of server compromise.
- Added
user_public_key_hashtable andzkp_proofcolumn in themessagetable to store proofs securely. - Enables users to prove identity and message validity without revealing personal details, aligning with Zixt’s privacy-first ethos.
- Implemented zk-SNARKs using
-
Encrypted DHT with DTLS:
- Integrated DTLS (Datagram TLS) to encrypt Kademlia DHT traffic over UDP port 8468, securing peer discovery and block propagation.
- Protects blockchain metadata (e.g.,
thread_id,index) from eavesdropping and man-in-the-middle attacks, complementing ZKPs for comprehensive privacy. - Added DTLS certificate generation for secure node communication, using OpenSSL-generated self-signed certificates.
- Updated
app/dht.pywith aDTLSServerclass andapp/blockchain.pyto leverage encrypted DHT, ensuring robust decentralization.
🔧 Enhancements
-
Improved Installation Process:
- Replaced PyPI
oqs==0.10.1with source-installedliboqs-pythonfrom GitHub to resolveImportErrorissues, ensuring compatibility withliboqs 0.10.1. - Added explicit
libssl-devdependency to prevent OpenSSL-related CMake errors duringliboqsbuild. - Clarified admin user setup with interactive and script-based options for generating SPHINCS+ key pairs and password hashes.
- Enhanced SMTP configuration with detailed Gmail setup (App Password) and support for alternative providers like SendGrid.
- Replaced PyPI
-
Security Hardening:
- Introduced dedicated Gunicorn user (
zixtuser) to isolate the WSGI server, reducing attack surface in production. - Updated blockchain to log ZKP proofs, minimizing plaintext metadata exposure.
- Maintained post-quantum security with Kyber1024, SPHINCS+, and SHA3-512, alongside PFS via ephemeral keys.
- Introduced dedicated Gunicorn user (
🐛 Fixes
- Resolved OpenSSL dependency issue in
liboqsbuild by ensuringlibssl-devis installed, fixingCMakeerrors related toOPENSSL_CRYPTO_LIBRARY. - Fixed Gunicorn user setup to use
zixtuser, ensuring proper permissions forapp/uploadsandcertsdirectories. - Addressed PyPI
oqsreliability by switching to source installation, eliminatingImportErrorforKeyEncapsulationandSignature.
📋 Known Limitations
-
ZKP Performance:
- Client-side proof generation with
snarkjsmay be slow on low-end devices (~1-2 seconds for simple circuits). Future releases may optimize circuits or offload to server-side provers. - zk-SNARKs require a trusted setup, introducing a potential security risk. A multi-party ceremony is recommended for production.
- Client-side proof generation with
-
DTLS Overhead:
- DTLS encryption adds slight CPU and latency overhead to DHT operations, noticeable in high-traffic networks. Future optimizations may reduce this.
-
Consensus Mechanism:
- The blockchain lacks a formal consensus algorithm, relying on honest nodes. Future releases may add proof-of-stake or BFT for robustness.
-
Native Apps:
- Zixt is browser-based, with no native iOS/Android apps yet. The interface is compatible with major browsers, but native apps are planned.
-
File Size Limit:
- File attachments are capped at 15MB. Larger file support may be added in future releases.
🛠️ Installation Notes
To deploy Zixt v1.0.2 on Ubuntu 24.04, follow the updated README.md instructions, which include:
- Dependencies: Install Python 3.10+, MySQL, Nginx, Redis, Node.js, npm, and build tools.
- liboqs Setup: Build
liboqs 0.10.1and installoqs-pythonfrom source to ensure compatibility. - ZKP Setup: Install
circomandsnarkjs, and generate circuit files (.wasm,.zkey) for zk-SNARKs. - DTLS Configuration: Generate self-signed certificates for secure DHT communication.
- Admin Setup: Generate SPHINCS+ key pairs and public key hashes for secure user management.
- Gunicorn: Use a dedicated
zixtuserfor production security.
Key steps include:
# Install dependencies
sudo apt install -y python3 python3-pip python3-venv mysql-server nginx redis-server certbot python3-certbot-nginx build-essential libssl-dev libffi-dev python3-dev cmake ninja-build git nodejs npm
# Build liboqs
git clone --branch 0.10.1 https://github.com/open-quantum-safe/liboqs.git
cd liboqs/build
cmake -GNinja -DOQS_ALGS_ENABLED=ALL -DOPENSSL_ROOT_DIR=/usr -DOPENSSL_CRYPTO_LIBRARY=/usr/lib/x86_64-linux-gnu/libcrypto.so ..
ninja && sudo ninja install
# Install oqs-python from source
source /path/to/zixt/venv/bin/activate
git clone --depth=1 https://github.com/open-quantum-safe/liboqs-python
cd liboqs-python && pip install . && cd .. && rm -rf liboqs-python
# Generate DTLS certificates
openssl req -x509 -newkey rsa:4096 -keyout certs/server.key -out certs/server.crt -days 365 -nodes -subj "/CN=zixt"For full installation and usage details, see the README.md.
📖 Usage Highlights
- Register: Create an account with a SPHINCS+ public key and verify via email.
- Login: Use a public key hash and zk-SNARK proof for private authentication.
- Messaging: Send encrypted messages and files in real-time threads, with metadata protected by ZKPs.
- Blockchain: Run nodes with DTLS-encrypted DHT for secure block propagation.
- Admin: Manage users securely via the admin panel.
Example:
# Generate keys
python scripts/keygen.py
# Run blockchain node
python -m app.blockchain🚀 What's Next?
Zixt v1.0.2 lays a robust foundation for secure, private messaging. Future releases will explore:
- zk-STARKs for post-quantum ZKP security.
- Consensus mechanisms for blockchain robustness.
- Native iOS/Android apps for enhanced accessibility.
- Optimized ZKP performance for low-end devices.
- Tor/I2P integration for node anonymity.
We’re excited to continue evolving Zixt based on user feedback and emerging needs. Join the quantum-secure revolution today!
🙌 Acknowledgments
Thank you to the open-source community, particularly the Open Quantum Safe project, circom, and snarkjs teams, for enabling Zixt’s cutting-edge security features.
Join us in building the future of secure communication!
For issues, feature requests, or contributions, visit NetworkNerd1337/zixt.