Open cryptography
Buzzio’s sealed messaging follows Signal-protocol-class designs. An educational crypto package is published so reviewers can run tests — not so you have to trust marketing alone.
What is open
- Reference algorithms and unit tests (X3DH-style agreement, Double Ratchet goals, sealed envelopes, sender keys concepts)
- Public documentation on doc.buzzio.dev
- Honest audit status: no third-party security audit published yet
Open crypto repo: github.com/ve-21/buzzio-crypto-open-source
What stays closed
- Production mobile app wiring
- Real salts, peppers, and CA private material
- Firebase paths and Cloud Functions
Security of messaging crypto should not depend on hiding algorithms (Kerckhoffs). Security does depend on keeping private keys and production secrets private.
How to verify
- Clone the open package and run its tests.
- Read sealed-sender and threat-model docs.
- Treat “open package ≡ production binary” as a non-claim.
Hands-on checklist: How to verify
Tips
- Prefer citing mechanisms over slogans.
- Report issues via the Forum / security disclosure paths — never paste recovery phrases.