Identity in your hands
No phone number, forced email, or real name as a requirement. Identity is built from keys, ownership, and mathematical proof.
No phone number · No email · No name
Private messenger without a phone number on Kaspa
Register without a phone number, email address or real name. Private messages, voice, photos and videos work without a KAS balance.
Closeness without identity demands
You decide who gets closer
Privacy is not about shutting people out. It is about deciding for yourself who gets access to your life and your conversations.
Theo holds out his phone to Romy. But she never has to reveal a phone number, email address or name. If she chooses, she shares only her KBeam contact. Because KBeam neither uses nor collects those details, the app cannot link them to her cryptographic identity.
Chat without a phone number
Our guiding principleKAS as a key
KAS as a key
Not as a barrier
KBeam gives people control of their digital identity and private data again. The Kaspa wallet provides the cryptographic foundation without forcing every message and every action onto the public BlockDAG.
Private, yet accessible
KBeam is meant to reach people without a wallet, coins, or prior crypto knowledge. Private communication should not feel like a technical specialist project.
Technology with a purpose
The BlockDAG is strong for proof, value, and programmable logic. Fast encrypted transport is strong for private communication. KBeam uses each where it makes sense.
Cryptography should empower people, not make entry harder.
KBeam deliberately separates identity, encryption, authentication, payment capability, and transport. The wallet remains the foundation for identity, trust, KBeam Auth, and decryption. Transport stays flexible.
KBeam is for people who do not want their communication permanently analyzed, tracked, linked, or commercially exploited.
No phone numberNo email addressNo real name
KBeam does not collect these details for registration or ordinary private communication. Uploading your address book is not required for the normal invitation flow either. Contacts are created through your deliberate action.
No phone number
No email address
No real name
Cryptographic identity anchor
Your identity anchor is cryptographic
KBeam does not collect a phone number, real name or email address as account data for registration or ordinary private messaging and therefore maps none of them to a wallet address or cryptographic contact. For technical routing, the app knows only the cryptographic identity, not the person behind it, and does not disclose such a personal identity link. Like any networked app, it creates local device data and technically necessary transport metadata. With Wallet V2, the communication identity is intended to be changed or rotated selectively.
No built-in monitoring
The EU is debating rules for monitoring private communications, often referred to as chat control. KBeam responds with a product property that can be checked over time: no automated content scanning is built into the normal private chat path.
Because KBeam does not collect a phone number, real name or email address as account data, it creates no mapping from those identifiers to a wallet address or cryptographic contact. For technical routing, KBeam knows only the cryptographic identity, not the person behind it, and can neither analyze nor disclose a personal identity link it never collected.
Private messages are encrypted on your device before they reach the transport route. Optional features involving external processing must be explained separately and deliberately enabled.
The political and legal situation can change. KBeam therefore does not promise blanket immunity from regulation; it describes the concrete technical design.
Background from the European ParliamentFast Push: messaging without a KAS balance
You do not need to buy coins or maintain a KAS balance to use KBeam as a messenger. Text messages, voice messages, photos, videos and other ordinary messages can be delivered encrypted through Fast Push.
Fast Push changes only the transport route. The message remains wallet-encrypted. Using KAS as payment funds and sending through the Kaspa Chain are optional and available when proof, value transfer or programmable flows are wanted.
Core messenger features do not require a KAS balance.
In development · Wallet V2
One seed as the foundation · Four separate compartments
The image explains Wallet V2 with simple symbols: the green folio represents the wallet's secret foundation, the seed. The light card is only a symbol for Elena's KBeam contact identity. She is intended to be able to change it later without changing her payment addresses, savings or recovery data. The total balance is combined only locally on her device.
This V2 outlook is not yet released for production. The features remain behind feature gates that are off by default until testing, security review and controlled activation are complete.
Communication
Your KBeam contact identity for chats, profile and groups. You will be able to change it for selected contacts without exposing your payment addresses.
Payments
Payments are intended to use new receive and change addresses. They are not the same address as your KBeam contact.
Savings
Your savings receive their own compartment. A contact should not automatically be able to see them through your contact address.
Recovery
Wallet recovery receives its own compartment. It remains separate from chats and ordinary payments.
Selective contact rotation
A communication identity is intended to be renewed selectively. Only chosen contacts receive the new mapping end-to-end encrypted, while the previous route remains reachable during a transition period.
Contacts do not reveal funds
Contact identity and payment funds are being separated technically. A contact should not be able to derive the total balance or savings, change, and recovery addresses from the visible communication address.
Fresh payment addresses
Payment requests are intended to use signed one-time addresses and payments fresh change addresses. Local coin control is intended to prevent separate privacy compartments from being merged unnoticed.
Your messenger Your rules
No phone number, email address or real name as the price of entry. For technical routing, KBeam knows only your cryptographic contact and creates no link to conventional account details.
iOS & Android
KBeam is available for Android on Google Play; the iOS version is in TestFlight beta. A phone number is not required to register.
Encrypted on your device
Private messages are encrypted on your device before they reach the transport route. Services process encrypted content and technically necessary metadata.
Fast Push without KAS
Ordinary private messages can be delivered through Fast Push. You do not need to buy coins or maintain a KAS balance.
No conventional account details
KBeam does not collect a phone number, real name or email address as account data. It therefore creates no mapping to your wallet or cryptographic contact; KBeam knows only the cryptographic identity.
No built-in monitoring
No automated content scanning is built into the normal private chat path. Optional external processing must be explained separately and deliberately enabled.
Kaspa used deliberately
Kaspa provides the foundation for cryptographic identity plus optional payments and proofs. Ordinary chats are not automatically written to the public BlockDAG.
Vision & Security
KBeam combines KAS-based identity, private communication, KBeam Auth and strong encryption without forcing every piece of content onto the BlockDAG.
What is Kaspa?
KAS, proof of work and the BlockDAG in simple terms
Kaspa is an open proof-of-work network. Its native coin is KAS. Like Bitcoin, Kaspa is based on proof of work, open participation and no central issuer. The difference is the structure: Bitcoin uses a linear blockchain, Kaspa uses the BlockDAG.
In the BlockDAG, several blocks can be created in parallel and ordered together by GHOSTDAG. This enables very fast confirmations without giving up the proof-of-work idea.
Kaspa was fair-launched: no premine, no hidden allocation, no ICO. KBeam builds on this foundation because a KAS wallet can enable not only payments, but also cryptographic identity.
More information about Kaspa is available on the official website: kaspa.org
KBeam Vision
KAS-based identity without forcing everything onto the BlockDAG
KBeam is not a messenger that forces every message and every action onto the BlockDAG. The vision is different: users should be able to control their digital identity and private data themselves again.
KBeam is explicitly not only for people who already know crypto. A central goal is to reach users who previously had no wallet, no coins and no connection to cryptographic systems. KBeam should be a simple bridge into the Kaspa world: private everyday communication, carried by KAS-based identity, without the start feeling like a technical crypto project.
That is why KBeam avoids classic identity anchors such as phone number, forced email or real name. Instead, the Kaspa/KAS wallet forms the cryptographic foundation: an identity made not of personal data, but of keys, ownership and mathematical proof.
Cryptography should strengthen people. It is one of the most important technologies against censorship, control and personal repression. At the same time, the entry must not be unnecessarily hard. Users should be able to use private, KAS-based communication without first buying coins or understanding complex wallet processes.
The BlockDAG remains an important part of KBeam. It enables encrypted messages and information, payments, proofs, instructions, programmable flows and later more complex conditions or decisions with Toccata. But not every process has to live on public infrastructure. Private communication is often better served by a fast encrypted transport path, while the BlockDAG is strongest where proof, value transfer, durable availability or programmable logic matter.
KBeam therefore separates identity, encryption, authentication, payment capability and transport. The wallet remains the foundation for identity, trust, KBeam Auth and decryption. Transport can stay flexible: through the BlockDAG when proof, value transfer, logic or planned automated processes matter, or through Fast Push when it is better for fast encrypted delivery and lightweight free messages.
KBeam is for people who do not want their communication permanently analyzed, tracked, linked or commercially exploited.
In short: KBeam uses KAS not as a barrier, but as a key. The BlockDAG is not an end in itself, but a strong foundation for identity, proof, KBeam Auth, payments and programmable possibilities.
Data Security & Encryption
Content is protected before servers, push and transport paths see it
KBeam protects content before it reaches servers, push services or transport paths. The app separates identity, content, transport, authentication and storage.
Messages
Messages are encrypted with KBeam/KASIA based on wallet keys. Technically, KBeam uses KASIA/ECIES with secp256k1, ECDH, HKDF-SHA256 and ChaCha20-Poly1305.
In simple terms: a shared secret is derived from the recipient's public key and a temporary key. From that, the key is created that encrypts and authenticates the message. Only the matching recipient can decrypt it.
Files and media
Images, videos, voice messages, PDFs and other files are additionally encrypted per file. KBeam creates a dedicated 32-byte file key and encrypts the file content with AES-GCM.
Only the encrypted file blob made of nonce, ciphertext and auth tag is stored or transferred. The file key is protected inside the encrypted KBeam message envelope and sent to the recipient.
Own data server
For content that is not plain text messages, the user can configure their own data server, for example their own SFTP server. Files and media are then stored there encrypted. The server stores only the encrypted blob and cannot read the content in plain text.
KBeam Auth
KBeam Auth uses the wallet as cryptographic proof of identity. The user can approve logins or permissions with the wallet, without requiring a password, email address or central account. A service can verify that the user belongs to their identity without receiving unnecessary personal data.
Wallet and keys
Private keys and seed phrases are not stored in the normal app database. They are stored in the protected key area of the device, on iOS in the Keychain. The wallet remains the foundation for identity, signatures, KBeam Auth and decryption.
Push
Push is not a place for confidential content in KBeam. Push is a wake signal or transport hint. Standard push systems are transport-protected, but not automatically end-to-end encrypted. That is why KBeam encrypts content itself before it touches push, brokers or servers.
Local data
Chats, contacts, groups, outbox, read state and similar app data primarily stay local on the device. Backups or sync paths should not contain more plain text than necessary and are handled separately from wallet secrets.
Groups
KBeam Groups are also encrypted. Group content is encrypted before transmission and is not stored on the server in plain text. The server processes only encrypted group events and technical metadata for delivery, synchronization and membership management.
For private groups, the app creates a dedicated group key on the device. New members receive this key not openly through the server, but through encrypted KBeam transport paths to their cryptographic identity. The server transports these data, but does not possess the group key of private groups in plain text and therefore cannot read private group content.
Public groups are intentionally public spaces. Anyone who joins a public group or has access to the public group link can read the content. Even so, public group content is encrypted before transmission and is not stored on the server as plain text.
In short: KBeam protects not only the transport, but the content itself. Servers should be able to deliver, store, wake or forward auth requests, but should not know private messages, media, group keys or file keys in plain text.
New for websites
KBeam Auth Gateway brings wallet login directly to your website
Visitors can unlock a protected area with KBeam. The website creates the session, while KBeam only approves the short-lived login challenge.
Responsibility stays clear: KBeam does not know the protected content, and the website keeps roles, permissions, sessions and customer data under its own control.
Live QR login: self-hostable, reviewable and ready to integrate into protected areas.
Outlook
From secure login to a trusted customer layer
The first stage is intentionally simple: transparent login without passwords. The next stage is intended to add an optional customer layer that can connect support, contact and product-related workflows.
Optional customer accounts
A wallet address could later be connected to a customer account. The website keeps roles, permissions, sessions and data under its own control.
Support and direct contact
After login, users could choose to be reachable for support, follow-up questions or direct chat.
Clear trust boundaries
KBeam only approves the login challenge. KBeam does not know the protected content of the website that embeds it.
Payments outlook
NFC payments with KBeam are intended to get a public integration path
KBeam supports NFC payment flows. A future public integration solution is planned so operators can later connect these payments to their own workflows in a transparent way.
This is an outlook: the website does not claim a finished public NFC API today, but shows the development direction.
KAS
More than text
Messages that feel more human
Text, voice messages, photos, videos and files belong in the same conversation. You do not need a KAS balance for these ordinary messenger features.
HD voice messages
Record personal voice messages directly in the chat and share moments that need more than text.
Share photos
Romy captures Liv's laughter and then shares the moment where it belongs: in their private conversation.
Send videos
Share videos directly with your contacts. Private media is encrypted on your device before transport.
Files in the conversation
Share documents and other files where you already talk. Available sizes depend on the app version and transport route.
Built for real conversations
Romy, Liv, Nora and Theo laugh, talk, plan and share. KBeam keeps private communication personal without using a phone number, email address or real name as the account anchor.
Powered by Kaspa
Kaspa where it actually helps
KBeam combines cryptographic identity and self-custody with practical private communication. Kaspa is used for optional payments, signatures and selected proofs, not as public storage for every chat.
Cryptographic identity
Your wallet forms the cryptographic identity anchor. KBeam collects no phone number, real name or email address as account data for it and therefore creates no mapping from those identifiers to your wallet or cryptographic contact.
Optional payments
KAS payments can be sent directly from the self-custodied wallet. You do not need a KAS balance for text, voice, photos or other ordinary messages.
Signatures and proofs
Cryptographic signatures can confirm identity, payment requests and selected proofs without making private chat content public.
10 blocks per second
Kaspa's proof-of-work BlockDAG currently runs at ten blocks per second. Optional on-chain payments and proofs benefit from it.
Flexible message transport
Fast Push transports ordinary messages in encrypted form without automatically writing them to the public BlockDAG. The Kaspa path remains optional for suitable use cases.
Wallet V2 in development
Separate contact and payment compartments, fresh addresses and selective rotation are intended to strengthen practical unlinkability. These features are not yet released for production.
Content protected Transport separated
KBeam separates identity, content, transport, authentication and storage. Confidential content is encrypted before it reaches push services, brokers, servers or other transport routes.
Private messages are encrypted on your device before transport
No automated content scanning in the normal private chat path
Servers process encrypted content and necessary technical metadata
KBeam does not map the cryptographic contact to a phone number, name or email address
Ready for KBeam?
KBeam is freely available for Android on Google Play. You can continue testing the iOS version through TestFlight. No phone number, no SIM card — just install and communicate securely.
iOS • Android