Ephemeral rooms
Random codenames by default, optional room phrases, participant votes, and leases that disappear after the session ends.
Daemonet Communications
Private conversations should belong to the participants.
Build direct chat, voice, video, one-use file handoff, signed wallet-request handoff, and accountless persistent contact capsules. Participants can carry their own pseudonymous identity while the provider remains outside identity, transcript, payment-target, and settlement custody.
Communication without a provider biography
Create the session. Carry only what you choose.
A capability phrase can identify a temporary room without a public profile. Participants who want continuity can present a portable pseudonymous identity and keep encrypted contact capsules locally; 1Man receives neither the identity proof nor history shares.
Participant-gated history
Each device keeps ciphertext and one random history-key share. Saved text remains blurred until both matching identities reconnect and cooperate.
Opt-in media
Negotiate authenticated peer media only after both participants accept the network and recording boundary.
One-use secure handoff
Read a separate phrase over an active call, accept one transfer start, verify integrity, and keep encrypted file bytes out of coordination storage.
Wallet-to-wallet request
Send a signed BOLT 11 or BIP 321 request through the peer room, then let external wallets perform and independently verify settlement. Status messages are coordination, not proof of payment.
Temporary assistance
Grant a narrowly scoped, expiring support session without handing over permanent credentials or the rest of the network.
Withhold by contact
Appear offline for a saved capsule to withhold future history cooperation. This cannot hide an already-established connection or recall a revealed share.
Authenticated events
Use signed delivery triggers as a separate API primitive while the application keeps its actual state and authorization rules.
Session lifecycle
The coordinator introduces. The participants communicate.
Short-lived coordination makes the direct path possible without retaining the conversation. If a direct connection cannot be established, the current demo stops visibly.
Create a room
The browser generates fresh cryptographic state and a phrase with enough entropy to resist guessing.
Join deliberately
Each participant accepts safety warnings and can bind a holder-owned identity to the fresh direct session.
Combine only together
Both identities commit random custody shares before reveal; the saved transcript key exists in memory only when both cooperate.
Communicate directly
Messages, accepted file chunks, and signed payment requests cross the authenticated peer channel. Closing either peer re-blurs split-custody history and clears payment coordination.
Responsible use
Encryption cannot control the person on the other screen.
Recipients can copy messages, photograph a screen, record a call, or retain a file after viewing it. “View only,” expiration, and download counts communicate policy; they are never DRM guarantees.
DaemonChat is not an emergency service, evidence vault, abuse-report archive, identity verification service, or promise of anonymity. Network operators can observe encrypted traffic metadata even when they cannot read content. Bitcoin activity remains visible on its public ledger, while a card issuer or on-ramp may retain identity and transaction records; a VPN does not erase either trail.
Legal boundary
Participants are responsible for what they send and for having the right to share it. Do not use the service for emergencies, imminent-harm reports, unlawful content, or situations requiring a durable evidentiary record.
Try the direct model