Integration: w3myPQ & BennyPQ Standalone ClientIt is coming lovely and cool people!
Starting in version 3.1.4, the w3myPQ plugin integrates natively with the cross-origin BennyPQ standalone client application layer
By leveraging a zero-knowledge cryptographic handshake, users can stream encrypted chunked archives from their local hard drives straight into the server’s REST API gateway. This works over standard connections or behind TOR, VPNs, and Proxies. The server automatically validates user permissions, enforces rolling storage quotas, and authenticates the sender’s identity via a pure-PHP lattice verification process before a single byte touches the secure disk vault.
== Decentralized Architecture ==
The w3myPQ ecosystem is completely decentralized. Identity is bound cryptographically to the user’s post-quantum keypair, rather than being locked into a centralized database. A user sharing a payload via an email tied to their key can use that same email to share the exact same (or a different) payload across entirely different WordPress sites—as long as those sites have the matching ML-DSA public key loaded and run w3myPQ.
This allows for seamless, multi-node cryptographic federation across separate, independent server vaults worldwide.
== Zero-Trust & Anonymity Pipeline ==
Because encryption happens entirely client-side, the system operates on a strict Zero-Trust model. You do not need to trust the network, the server, or even the system administrator.
Users who have the same email and KEM public keys loaded into different WordPress nodes can receive ciphered files securely into any independent WordPress vault. For maximum security, users can share their public keys with each other privately via email. The server merely facilitates the chunked transport layer, remaining completely blind to the underlying protected payload data.
== Prevention of Public Key Injection & Impersonation ==
To completely eliminate the risk of public key injection, user impersonation by a compromised server, malicious administrators, or Man-In-The-Middle (MITM) attacks, users can share files using the BennyPQ standalone client integration gateway.
BennyPQ uses the exact same core cryptographic code as w3myPQ. However, since it is a standalone file loaded locally and NOT served by WordPress, an untrusted administrator or compromised server has absolutely no way to tamper with or modify its source code. This ensures that the integrity of your key validations and encryption routines remains fully secure in your local browser sandbox, regardless of the hosting environment’s status.