DaemonChat™ · Daemonet capability demonstration
Talk directly.
Leave no provider inbox behind.
Create a direct room for text, opt-in calls, one-use DaemonCache file transfers, and noncustodial DaemonPay wallet handoffs. Carry an optional pseudonymous identity and keep saved history gated by both participants, or choose an ephemeral session. In the current launch path, 1Man introduces the browsers, then leaves the application-data path.
- Accountless
- Direct today
- Split custody by default
- 90-second lease
One short, explicit workflow
Start without an account.
Choose a job here. DaemonChat opens a focused setup dialog, asks only for the current decision, then gets out of the way when the direct room is ready.
Ephemeral room · step 4 of 4
Waiting for peer
Signed lease active · no peer data path yet
Room controls
Your call stays live. Read the separate phrase aloud, switch back to Call whenever you like, and wait for the one-use collection receipt.
The first accepted transfer consumes this cache. “One use” is session policy, not remote deletion or DRM: a recipient can retain, copy, or modify anything received. Use a trusted VPN first if peer-visible network addresses are unacceptable.
DaemonChannel runs in an isolated first-party frame. This room can ask it to stop and receives only three booleans: active, live quorum, and sharing. It cannot read names, invitations, participants, choices, keys, map data, or locations.
Location is off. Opening the panel never starts sharing.
Not an emergency or evidence service. A recipient can record anything they are allowed to see. Hiding this panel, leaving the room, or closing the page sends a stop request; the child also independently stops on hidden-page and quorum-loss events.
The request travels only inside this direct, app-encrypted peer session. Your wallet—not this page—must validate the invoice, destination, amount, fees, expiry, and settlement. Peer “sent” and “received” notices are coordination, not cryptographic proof.
Use your wallet’s own card/on-ramp flow. The independent provider and card issuer may require identity, fees, jurisdiction checks, and transaction metadata; a VPN does not make a card purchase anonymous.
No payment requests in this peer session.
Payment requests are deliberately excluded from personal and split-custody chat history. They remain visible in this tab until the direct session ends. Wallets, card providers, the Bitcoin network, Lightning participants, peers, screenshots, clipboard history, and device compromise can still create records or linkage.
No invitation or message history will remain after this tab closes.
- Your session key
- Generated when the room starts
- Peer session key
- Available after direct connection
Unlock a self-custody identity before choosing the capsule mode.
Split a local file into equally sized XOR shares. Every share is required to reconstruct it; this demonstrates privacy splitting, not erasure coding or backup redundancy.
Your identity. Their half. No provider account.
Self-custody chat list.
Create a downloadable pseudonymous identity and participant-gated chat capsules. Offline capsules show only a blurred local indication; both matching identities must reconnect directly before either transcript key can be reconstructed in memory.
Build on the trigger authority
Ephemeral coordination is an API.
DaemonChat exercises a reusable signed lease and encrypted-envelope service. It can introduce peers and then disappear from their data path.
portable identity + fresh session keysNo provider account is required. Split-custody history uses an optional durable identity locked by the holder.
POST /v1/daemonchat/rooms/*The host controls lock, expiry, matching, transfer, and close.
offer + answer ≤ 2 min1Man cannot read the SDP capability envelope.
WebRTC DTLSChat and payment-request events add signed application encryption; calls use SRTP; files use AES-GCM. None traverse 1Man.