WebRTC Voice & Text Chat Rooms
Browser chat rooms with low-latency WebRTC Opus voice calls, chunked file sharing, and Ethereum wallet (SIWE) access. Sign in with a free wallet signature and unlock paid access on Ethereum Mainnet to create or join any room.
Access & Pricing
1. Free Wallet Sign-In (SIWE)
Connect an EIP-1193 Ethereum wallet and sign a free off-chain EIP-4361 message. This signature only verifies wallet ownership and costs no gas or ETH.
2. Paid Access Unlock
Send 0.001 ETH on Ethereum Mainnet (Chain ID 1) to 0xeff121f128e0e64c0e64ae8eb6eb042a0e5aa81c to unlock 30 days of access across all chat and voice rooms and claim your persistent nickname.
Featured Chat Rooms
Shared rooms available to members with active paid wallet access:
Key Features
- URL-Addressed Rooms: Every path under
/chat/{room}is an independent room you can bookmark or share with other active members. - WebRTC Voice Calls: Low-latency browser Opus voice chat backed by a Rust & GStreamer media pipeline.
- Binary Protobuf & File Sharing: Stream messages and chunked file attachments with real-time upload and download progress over Protobuf WebSockets.
- Persistent Wallet Nicknames: Reserve a unique lowercase nickname tied to your verified Ethereum wallet across all rooms.
Frequently Asked Questions
How do I invite people to a room?
Share any room URL such as /chat/my-team. Members who already have active paid access open the room directly; visitors without an active paid session are redirected to /chat?room=my-team to sign in with their Ethereum wallet and unlock access before entering the room.
Are messages and voice calls end-to-end encrypted?
No. Web and WebSocket traffic is protected in transit over HTTPS/WSS and WebRTC voice streams use DTLS-SRTP transport encryption in transit, but room messages, file chunks, and audio routing are processed by the server and are not end-to-end encrypted.
Are chat rooms indexed by search engines or made private by noindex?
Only the /chat overview page is publicly crawlable and listed in the sitemap. All /chat/{room} routes require an active paid session, redirect unauthenticated requests to onboarding, and emit a noindex robots directive. The noindex directive only tells compliant search crawlers not to list a URL in search results; it is not a privacy or room-access guarantee. Room access is enforced by server-side session and payment verification.