How Quocom works

Quocom is the website. There is nothing to sideload and nothing for an app store to gate. If a browser loads, you can take a call.

1. You open the site. Any browser. Any WiFi. That’s your phone.
2. You connect. Sign in and you have a number — your 0x.
3. You spend $QUOCOM for minutes. That’s the utility. Bridge if you need to. ETH and USDC still work. Minutes stay on your wallet.
4. You send a link or an address. quocom.network/dashboard?dial=0x…
5. They open Quocom and you ring. Their tab plays a phone-style ringtone. While you wait, you hear ringback — the two-tone wait of a real phone. They tap Accept. Encrypted P2P voice.
6. You hang up. Talk time bills in whole minutes. Leftover reservation returns to you.

Phone companies issue you a rented identity, store it in a database, and can port it, recycle it, or SIM-swap it. Quocom never issues a number. The 0x you already hold is the line. Connect, and you can be reached. Nothing to mint, nothing to squat, no second name for the timeline.

That identity stays on the wallet across devices. New laptop, café machine, friend’s spare handset — open quocom.network, connect, same 0x. Minutes you already bought are still sitting there. The plastic SIM never entered the story.

There is no public directory of who you called. You share a 0x the way you already share a receive address. Private by default means we did not build a phone book for strangers.

Quocom is not a carrier with a website painted on. It is also not “voice on a blockchain.” A call uses three planes that must stay separate, or you get either a surveillance product or an unusable toy.

Settlement is on Ink: you spend $QUOCOM (ETH and USDC still work), minutes sit on the paying wallet, a hold is taken when you ring, and whole minutes are billed when you hang up. That ledger is a receipt. It is not the conversation.

Signaling is Quocom noticing that one wallet is ringing another. Your dashboard asks the site, on a short interval, whether anyone is calling your 0x. There is no phone company paging a radio in a locked pocket. If their Quocom tab is not open, they will not hear the ring. That is an honest constraint, not a missing setting.

Media is real-time audio in the browser, using the same family of protocols the open web already uses for live voice: WebRTC. Your microphone becomes a live audio track. Camera stays off on purpose. The two browsers connect through a media node that forwards packets; they do not dump speech onto a chain and they do not send uncompressed audio through Quocom’s application servers as the listening path.

Why a mesh of nodes, not one company’s PBX

A conventional call product terminates every conversation in one vendor’s data center. That is simple to operate and simple to subpoena, throttle, or take offline. Quocom’s voice layer is a dePIN: independent operators run media nodes. Those nodes register on a public on-chain registry so they can be discovered, paid for bandwidth, and replaced if one drops. Community-operated infrastructure instead of a single HQ box.

There is no fixed public media URL baked into the website. A static websocket to one region would be a phone company with extra steps. When you start or accept a call, Quocom’s server looks up a suitable node using your public IP — geographic routing so you land near a node on your continent, not a default machine an ocean away. Typical in-region latency is well under 100ms. Across continents the path is still a live call, not a voicemail product.

Nodes are selective forwarders, not conference recorders. For a Quocom 1:1 call that means: take the encrypted audio you published, send it to the other wallet’s browser, and do the reverse. The node does not mix you into a webinar, does not transcode you into a livestream, and does not keep a copy for “quality.” If a node disappears, you hang up cleanly and leftover reserved minutes return. You try again.

What happens the moment you hit Ring

1. Quocom checks that you have enough prepaid minutes and that the target is a wallet, not yourself.
2. Those minutes go on hold. They are not spent yet. A miss or a decline puts them back.
3. The server opens a private room for the two 0x addresses and mints a short-lived access token bound to your wallet, that room, and permission to publish and subscribe to audio. Signing happens with Ed25519 on the server. Keys never ship to the browser.
4. The server asks the node network which media endpoint is closest to you, then returns only what the browser needs: the token and a websocket URL for that node.
5. Your tab connects, disables the camera, and publishes the microphone. You hear ringback while their inbox shows the incoming call.
6. When they tap Accept, they get their own token to the same room on a node chosen for their network path. Two people, two short-lived grants, one room.
7. Both browsers send and receive audio over WebRTC. UDP first. If a hotel NAT or a hostile firewall blocks UDP, the stack falls back to TCP and, if needed, a relay (TURN) so the call can still complete. Adaptive sending keeps the stream matched to the path — you do not blast a café connection with a studio bitrate.
8. Hang up, drop, or hit the reserved time: the room tears down, Quocom bills whole minutes actually talked, and unused hold returns to the caller. The person who picked up is not charged and is not paid.

What the browser is allowed to do

The site asks for the microphone. That is the only media permission. Camera is forced off for the call — not a toggle we hope you find. If the browser blocks autoplay when the other person starts speaking, you get a “tap to hear audio” control; that is a browser rule, not Quocom storing the call.

Mute and speaker controls act on your local tracks and on the remote audio element. They do not rewrite history on chain. Reconnect handling is in the media client: if the websocket blips, it tries to come back. If the other wallet disconnects, the call ends. We would rather hang up than pretend a dead path is still a conversation.

Why this is cheaper and harder to shut off

Centralized real-time stacks price like phone companies because they run the whole footprint. A mesh of independent nodes competes on bandwidth. Operators earn a majority share of what the media path costs to deliver; you are not financing a single vendor’s video roadmap. Quocom only uses that path for 1:1 voice. No STT pipeline listening in, no TTS bot in the room, no livestream layout. A phone.

Censorship resistance follows from the same design. Borderless connectivity is the default: the node you reach is whoever is registered and close, not a national interconnect agreement. There is still a Quocom website in front — someone has to mint the room token and hold the minutes — but taking down one marketing domain is not the same as seizing every media node, and seizing one node is not the same as seizing the number. The number is the wallet you already protect.

The conversation is encrypted in transit. WebRTC wraps media in DTLS-SRTP: the path between your browser and the node, and onward to the other browser, is not sent as raw samples on the open internet. Quocom does not put the waveform on Ink. Explorers will never be a transcript.

What is visible, if someone already knows the wallets, is the boring part of a phone bill: that minutes were purchased, that a call was reserved, that a hold was released. That is a receipt. It is not “what was said.” We do not keep a carrier-style call graph for advertisers. There is no SMS identity and no contact-list upload to “find friends.”

End-to-end in the strong sense — keys that even the forwarding node cannot use — is the direction of a private 1:1 product. Transport encryption is on from the first packet. Quocom’s application layer never needs the audio to bill you: billing is minutes, not a recording. If a node cannot produce speech, it cannot sell speech. That is the incentive we want.

Practical hygiene still applies. Café WiFi can see that you opened a site. A compromised laptop can still hear a speaker. Quocom removes the carrier from the identity path and the phone company from the media path. It does not make you invisible to the room you are sitting in. Camera off is part of that: a private call, not a face on the hotel wallpaper.

$QUOCOM is how you buy talk time. That is the token’s job. You pick a pack, pay on Ink, and the minutes sit on the paying wallet. ETH and USDC still work at checkout. After that, nothing is ringing yet. You still have to dial.

When you ring, Quocom holds the minutes for that attempt. A hold is not a spend. If they decline, miss, or never had the tab open, the hold returns. If they pick up, talk time bills in whole minutes. Leftover reservation — you reserved ten, you talked for three — returns to you. When the pack hits zero, you stop ringing until you buy again. That is a wall you can see, not an overage plot twist.

The person you call does not get a payout and does not get a bill. Incoming never debits the receiver. If your friend has a huge pack and you have zero, you still cannot place the call. Buy. That asymmetry is how a phone works, and how we avoid a surprise invoice on pickup.

Minutes do not transfer to another 0x as a gift feature. They buy, or you place the call. The object stays simple: pack on a wallet, spend by ringing.

$QUOCOM is how minutes are supposed to be bought. ETH and USDC are still accepted so someone can get talk time without hunting a pool first. That does not mean those checkouts sit idle as a second currency. When someone pays for minutes in ETH or USDC, that value is used to buy $QUOCOM on the open market — the same Uniswap / DexScreener markets that price a $QUOCOM checkout.

The point is one utility loop. Spend $QUOCOM, get minutes. Spend ETH or USDC, still get minutes — and the protocol turns that payment into a $QUOCOM buyback so demand for talk time still hits the token. The person who paid does not have to wrap, swap, or wait on a chart. Quocom does the conversion after the minutes are already on their wallet. Buybacks and burns are posted on /burn as they land on-chain.

Checkout amounts still track USD. A five-minute pack costs the same in dollar terms whether you pay in $QUOCOM, ETH, or USDC. The $QUOCOM button charges however many tokens that USD is worth at the live pool price. ETH and USDC charges are the same USD, then those proceeds buy $QUOCOM. Missed rings still return minutes. None of this changes who pays for a call: the caller.

Checkout spends on Ink. If your funds are sitting somewhere else, bridge first, then buy minutes, then dial. Parallel optimism — bridging while already ringing — is how people get a hold they cannot cover. Arrive, buy, dial. In that order.

The Quocom bridge is the same two-wallet flow you already know from a serious bridge: connect the wallet you are sending from, confirm the wallet you want to receive at (your Quocom 0x, unless you type another), and send. For major tokens you can also send to a deposit address without connecting the origin wallet. Funds go only to the receive address you confirm. If a quote ever names a different recipient, Quocom cancels it.

Supported origins include Ethereum, Base, and other EVM networks, plus Bitcoin, TON, Tron, XRP, and more. You are moving value onto the chain where minutes settle. You are not moving the voice path. Audio still runs in the browsers after you have talk time.

A mobile carrier can wake a radio in a pocket. Quocom cannot, because we are not a carrier. Both people keep quocom.network open — or come back within about forty-five seconds of the ring — to accept. Missed and declined rings return the reservation. Try again when both wallets are on the site.

When someone dials you, the incoming screen plays a bright mallet ringtone, in the character of a modern phone, so you actually hear it. The caller hears classic ringback (two tones, then a pause) until you pick up, decline, or the attempt times out. Tones stop the moment the call connects or ends. If the browser has not been clicked yet, it may wait for a tap before it can play sound — that is autoplay policy, not a missing ringer.

Keep the dashboard tab alive if you want to be called. Share your 0x or your call link. They open a site, not a store listing. That is the whole introduction.