I built a completely serverless, zero-telemetry E2EE chat app using WebRTC and Double Ratchet. How can I improve the P2P stability?

Hey everyone, I wanted to share a project I've been engineering called VAULT. The goal was to build a messaging hub that leaves absolutely zero footprint—no servers storing data, no emails, no phone numbers, and local identity generation. How the stack works: Messaging: Uses the Double Ratchet protocol for end-to-end encryption. Message routing and voice/video calls are handled entirely peer-to-peer (DTLS-SRTP) via WebRTC. Data Storage: Ephemeral by design. Messages have a 24-hour auto-decay window and live only in local storage. Integrations: I also integrated a non-custodial wallet infrastructure supporting Solana and EVM chains directly into the chat interface, using zk-SNARKs for private transaction rails and ERC-4337 for gasless payments so users don't need native tokens to transact. Because it's fully serverless, signaling is the trickiest part. I'm currently looking for feedback on handling WebRTC STUN/TURN fallbacks more efficiently when both peers are behind symmetric NATs. I'll drop the project link/repo in the comments if anyone wants to check out the pre-release or look at the architecture!