Quantum-ready, grounded
Quantum-ready calls that still use real call security.
CallChat Q-Calls keep live voice and video on Matrix/Element WebRTC, DTLS-SRTP, device identity, and the configured TURN relay. The Q-Call layer adds CallChat Shield policy, PQC-ready planning, call setup evidence, and an optional server-side IonQ research hook.
- Live call layer
- Matrix / WebRTC
- Relay
- TURN configured
- Q layer
- PQC-ready policy
- IonQ
- Server-side research hook
What works today
Element-compatible voice/video calls through the live CallChat homeserver.
Relay support for more reliable mobile, desktop, and NAT call testing.
Matrix account identity, device checks, and normal Matrix E2EE where supported.
Q-Call status can connect with the hosted Shield policy layer without exposing ZMath internals.
IonQ role
IonQ is a research and attestation hook, not a browser secret.
IonQ API usage belongs on the server side only. A future Q-Call policy service can submit approved quantum experiments, record a signed result, or use quantum-assisted research outputs as part of a call security status badge. Public JavaScript never receives IonQ keys.
This is deliberately framed as PQC-ready and quantum-assisted research. It does not claim that live voice packets are quantum encrypted today.
How to test calls now
- Use two CallChat accounts. Sign in on desktop and mobile using homeserver
callchat.org. - Open a direct message or room. Use CallChat Web or official Element clients.
- Start voice or video. Test microphone, camera, and relay across different networks.
- Ask Zero Bot. In the lab room, try
!zero q-callor ask about secure calls.
Product direction
Keep Matrix and Element. Own the CallChat layer.
Matrix and Element provide the mature login, room, call, and device-verification foundation. CallChat adds the branded product surface, Zero Bot, Shield, Q-Call status, licensing, and the future native app path.