Safe to Safe Messaging
Overview
Safe to Safe Messaging is a fortress of encrypted autonomy, enabling Sovereign and HighRisk tier users to send post-quantum encrypted messages, attachments, and executable commands between UnoLock vaults, ensuring zero-trust privacy and operational sovereignty. With client-side execution and metadata anonymity, this feature transforms vaults into secure, untraceable communication hubs, while Free tier users can reply securely to initiated messages. Available in Sovereign and HighRisk tiers with reply-only support in the Free tier, it redefines secure coordination for the digital age.
How It Works
- Vault-to-Vault Communication: Sovereign and HighRisk users send encrypted messages, attachments (up to 5GB), or commands (e.g.,
ROTATE_KEY,SELF_DESTRUCT) directly between UnoLock Safes, with no external service dependency. - Post-Quantum Encryption: Messages are encrypted with ML-KEM-1024 and signed with ML-DSA (Dilithium), ensuring future-proof security and sender authenticity without exposing identity.
- Client-Side Decryption: Messages are decrypted and executed only within the recipient’s Safe, ensuring UnoLock’s servers have zero visibility into content or commands.
- Trusted Safes Access Control: Each Safe maintains a Trusted Safes List, validating senders and command execution, enforcing strict access permissions.
- Free Tier Reply System: Free tier Safes can reply to messages from Sovereign or HighRisk Safes using encrypted Bloom filters, ensuring anonymous, zero-knowledge responses.
Security Implications
- Zero-Trust Privacy: Client-side execution and post-quantum encryption ensure no third party, including UnoLock, can access message content or metadata, preserving absolute privacy.
- Metadata Anonymity: Randomized, unlinkable identifiers and secure S3 URLs prevent any linkage between senders, recipients, or message content, thwarting tracking attempts.
- Command Execution Safety: Strict validation via the Trusted Safes List ensures only authorized commands (e.g.,
REVOKE_ACCESS) are executed, protecting vault integrity.
Use Cases
- Mission-Critical Coordination: Distributed teams can securely exchange encrypted instructions or files, ensuring operational integrity without third-party risks.
- Cryptocurrency Management: Investors can send signed commands (e.g.,
ROTATE_KEY) to trusted Safes, automating secure wallet updates across vaults. - Anonymous Collaboration: Activists or journalists can communicate sensitive information or attachments anonymously, leveraging metadata anonymity for safety.
Why It Matters
Safe to Safe Messaging empowers vault holders to operate as sovereign entities, orchestrating secure, untraceable communication and automation in a zero-trust world. This feature delivers future-proofed digital sovereignty, ensuring privacy and control endure for decades.
FAQs
Can UnoLock access messages sent between Safes?
No, messages are encrypted and decrypted client-side using post-quantum cryptography, ensuring UnoLock has zero visibility into content or metadata.
How does the Free tier reply system work?
Free tier Safes can reply to Sovereign or HighRisk messages using encrypted Bloom filters, allowing secure responses without initiating communication.
Are Safe to Safe commands safe to execute?
Yes, commands are validated against the recipient’s Trusted Safes List, ensuring only authorized actions (e.g., SELF_DESTRUCT) are executed.
Compliance & Privacy Regulations
- GDPR Compliance: Safe to Safe Messaging supports GDPR by using zero-knowledge encryption and metadata anonymity, ensuring no personal data is exposed during communication.
Integration with Other Features
- Post-Quantum Encryption: Leverages ML-KEM-1024 and ML-DSA for future-proof security, ensuring messages and commands remain protected against quantum threats.
- Bitcoin Payment: Supports Safe to Safe Messaging by enabling anonymous payments for Sovereign or HighRisk tier access, enhancing financial privacy during setup.
