I built a private P2P voice chat in a single file—how do I make it even more secure?

I’ve been working on a small project: a zero-knowledge, E2EE audio chat that runs in a single PHP/JS file. No database, messages delete after 24h. I managed to solve the NAT traversal issues by switching from Trickle ICE to Vanilla ICE (wait-and-retry approach), which finally lets me call between a PC and a 4G phone. I’m curious—from a cybersecurity perspective, what are the biggest risks in a P2P architecture like this? Besides the obvious metadata leaks from the signaling server, what else should I be looking at to harden the privacy? Any feedback or "this is a bad idea because..." comments are welcome! v2v.site submitted by /u/Alternative-Claim-41 [link] [留言]