KAS directly in KBeam
KBeam combines private communication with a self-custody Kaspa wallet. You can send and receive KAS while ordinary messages and media continue to work without a balance.
Outlook: Vincent pays digitally after dinner while Elena holds his free hand. KAS remains optional for ordinary messaging.
Optional
KAS payments in the messenger
0 KAS
required for ordinary messages and media
Self-custody
instead of custody by KBeam
01
Anyone who only wants to write, send voice messages, photos or videos does not need to buy coins. Fast Push provides lightweight encrypted delivery without requiring a KAS balance.
When value should be transferred, the Kaspa wallet can send and receive KAS. Communication and payment remain deliberately separate decisions.
02
Kaspa is a public BlockDAG. Payment addresses, amounts and transactions may be publicly traceable according to the addresses and network data used.
KBeam therefore does not promise automatic payment anonymity. The Wallet V2 roadmap aims for stronger practical unlinkability through separate compartments and fresh addresses.
03
Today, direct sending and receiving of KAS within the KBeam experience is the focus. NFC and point-of-sale processes are part of the outlook and will only be presented as available once a concrete integration path has been published and verified.
This keeps the boundary clear between what can be used now and what remains in development.
FAQ
Ordinary messages and media do not require a KAS balance. A KAS transaction only occurs when you deliberately use a payment or another on-chain function.
No. KBeam is non-custodial. Payment authorization is based on keys under your control.
Kaspa transactions are public. Wallet V2 is intended to separate contact and payment compartments more strongly, but it is still in development and does not replace careful consideration of public blockchain data.
Install KBeam and decide for yourself whether you only want to communicate or also use Kaspa payments.