Peer-to-peer//Encrypted//Base

KLEEM

Encrypted messaging and a self-custodial wallet. No servers. No phone number. No trace.

NET online

KEYS local

CHAIN base

STATUS listening

Own your keysNo middlemen — noneNothing to seizeMessages routed, not storedIdentity is a keyBuilt on Base Own your keysNo middlemen — noneNothing to seizeMessages routed, not storedIdentity is a keyBuilt on Base

01 — What it is

A messenger, a wallet, a door to Base.

Kleem runs on a distributed network. There is no company in the middle, no account to create, no server holding your history. You hold the keys. You hold the messages. Everything else is noise.

░▒▓█ KLEEM ▓▒░ ▚▞▚▞ 0x4B4C45 ░▒▓ NO SERVERS ▓▒░ ╱╲╱╲ ENCRYPTED ▚▞ P2P ░▒▓█ KLEEM ▓▒░ ▚▞▚▞ 0x4B4C45 ░▒▓ NO SERVERS ▓▒░ ╱╲╱╲ ENCRYPTED ▚▞ P2P ░▒▓█ KLEEM ▓▒░ ▚▞▚▞ 0x4B4C45 ░▒▓ NO SERVERS ▓▒░ ╱╲╱╲ ENCRYPTED ▚▞ P2P

02 — Capabilities

Four functions. No decoration.

/ 01

Messages

End-to-end encrypted by default. Carried across a distributed network, never through a central point.

/ 02

Wallet

Self-custodial. Only you hold the keys. Send and receive on Base directly inside a conversation.

/ 03

Identity

No phone number. No email. A cryptographic key is your name, and it belongs to no one else.

/ 04

Communities

Token-gated spaces, run by the people inside them. Owned by members, not by a platform.

All features →

03 — System state

What the network holds.

Servers

Keys held by you

100%

Metadata stored

NONE

Encryption

E2E

Account required

Settlement chain

BASE

▞▚▞▚ SIGNAL ░▒▓ ▐▌▐▌ 01001011 ▓▒░ SEALED ╱╲ ROUTED ╱╲ OPENED ░▒▓█ ▞▚▞▚ SIGNAL ░▒▓ ▐▌▐▌ 01001011 ▓▒░ SEALED ╱╲ ROUTED ╱╲ OPENED ░▒▓█ ▞▚▞▚ SIGNAL ░▒▓ ▐▌▐▌ 01001011 ▓▒░ SEALED ╱╲ ROUTED ╱╲ OPENED ░▒▓█

04 — Token

$KLEEM

The network token. Governance, access, and settlement — issued on Base. Held by the people who use the network, and directed by them.

0x————————————————————————————————————————

pending

View on DexScreener →

ChainBase

StandardB20

SymbolKLEEM

SupplyTBA

RoleGovernance / access

05 — Phases

A sequence, not a promise.

KeysClient, encryption, self-custodial identity.

[██████████]live

MeshPeer routing and offline delivery across nodes.

[██████████]live

Token$KLEEM issued and governed on Base.

[█████░░░░░]pending

CommunitiesToken-gated spaces owned by members.

[███░░░░░░░]next

BridgeCross-chain wallet, one interface.

[█░░░░░░░░░]planned

06 — Manifesto

The rules do not bend.

Privacy is the default, not a setting.

Your keys are yours. So are your words.

No servers to seize. No one to trust.

The network belongs to those who run it.

ENTER

Free. Open source. No account. Take your keys and go.

iOS Android macOS Windows Linux

Features

FEATURES

One tool for messaging, value, and identity — with no account behind it. Everything Kleem does, and everything it refuses to.

01 — The pillars

Four things, done fully.

/ MESSAGES

Talk in private

Encrypted 1:1 and group chats. Nothing readable ever leaves your device unencrypted.

/ WALLET

Hold your own value

A self-custodial wallet on Base, right inside the chat you're already in.

/ IDENTITY

Be a key

No phone, no email. You are the key you generate and carry.

/ COMMUNITIES

Member-owned spaces

Token-gated channels with no platform owner standing over them.

/ 01 · Messages

Sealed end to end.

Every conversation is encrypted before it leaves your device and only reopens on the other person's key. No relay in the middle keeps a readable copy, and no metadata trail is left to reconstruct who spoke to whom.

End-to-end encryption on by default — you can't turn it off
Direct messages and group chats
Media, files, replies, reactions
Disappearing messages with per-chat timers
Delivered even when the recipient is offline — peers hold it
No read logs, no message history on any server

/ 02 · Wallet

Value in the chat.

A self-custodial wallet built on Base. Send and receive without leaving the conversation, and swap between tokens without handing custody to anyone. Your keys sign every move; nothing leaves without you.

Self-custodial — only your keys move your funds
Native to Base, with room for more L2 networks
Send and receive inside any chat
Swap tokens without a third-party custodian
Hold B20 tokens and collectibles
Routing that weighs gas before it moves

/ 03 · Identity

A key, not a number.

There is no sign-up. You generate a keypair and that is your identity — portable, disposable, and tied to nothing about you. Run one identity or many; none of them ask for a phone number.

No phone number, no email, no sign-up
Your key is generated and stored on your device
Multiple identities, cleanly separated
Human-readable names on top of your key
Portable across every device you own

/ 04 · Communities

Owned by members.

Spaces are opened with a token and run by the people inside them. Entry, roles, and rules are set by members — not granted by a platform that can revoke them.

Token-gated entry using $KLEEM or your own token
Roles and permissions set by the community
No central moderator you didn't choose
Public channels and private rooms
Governance and treasury tie back to the token

02 — What it refuses

The list of nevers.

NOadsNOtrackersNOtelemetryNOphone numberNOemailNOserversNOlock-inNOdata soldNObackdoors

Get Kleem How it's secured →

Security & Privacy

SECURITY

Privacy is not bolted on. It is the shape of the whole system. Here is exactly what is protected, and what is not.

01 — What we can see

Nothing. By design.

Held by Kleem

Held by you

Message content

Never

On your device

Your contacts

Never

On your device

Who you talk to

Not visible

Yours alone

Your keys

Never

Only you

Phone / email

Not collected

Not needed

IP / metadata

Not logged

Minimized

02 — How it holds

Layers, plainly.

End-to-end encryption

Every message is sealed on your device and can only be opened by the recipient's key. No middle layer holds a readable copy.

Forward secrecy

Keys rotate as you talk. A key exposed today does not unlock the messages you sent yesterday.

No central store

Messages move across a distributed network and rest only on your device. There is no server to breach or subpoena.

Metadata minimization

The network is built so that no participant needs to know who is talking to whom. What can't be collected can't be leaked.

Open to inspection

The client is open source. Anyone can read exactly how the encryption works — trust is verified, not asked for.

03 — Keys & recovery

Yours to hold. Yours to guard.

Self-custody cuts both ways. No one can seize your keys, freeze your account, or read your messages — and no one can recover them for you. Your backup is the only backup.

Generated locally

Keys are created on your device and never transmitted. Kleem never sees them.

You back them up

A recovery phrase is yours to store safely. Lose it, and no support desk can restore access — that is the trade for real ownership.

Device is the edge

Encryption protects the message, not a compromised phone. Guard the device the way you guard the keys.

04 — The guarantees

Fixed, not negotiable.

Central servers

Message logs

NONE

Backdoors

NONE

Encryption

E2E

Source

OPEN

Audits

ONGOING

Disclosure & bounty. The client is open to review, and independent audit reports will be published here as they complete. Found a vulnerability? Report it privately through the channels under Socials — responsible disclosure is rewarded, not punished.

05 — Straight answers

No fine print.

?Can Kleem read my messages?

No. They are encrypted on your device against the recipient's key. We never hold a readable copy.

?What happens if I lose my keys?

Access is gone. There is no recovery by us, because there is no copy for us to hold. Back up your recovery phrase.

?Do you keep logs?

No message content, no contact graph, no IP logs. The network is built to not need them.

?Is there a backdoor for law enforcement?

No. A backdoor for one is a backdoor for all. There is nothing to hand over.

Protocol

PROTOCOL

How a message crosses the network without ever passing through a center.

01 — A live session

kleem — session

    o───o─────────o───o
    │ ╲ │ ╲     ╱ │ ╱ │
    o───o───o───o───o
    │ ╱ │ ╱   ╲ │ ╲ │
    o───o─────────o───o
      ╲   ╲     ╱   ╱
        o───o───o───o

no center · no owner

02 — Four moves

Seal · shard · route · open.

Seal

The message is encrypted on your device against the recipient's key before it ever leaves.

Shard

It is broken into fragments so that no single hop carries the whole.

Route

Fragments pass peer to peer across the network. If the recipient is offline, peers hold the pieces until they return.

Open

Only the recipient's key reassembles and unlocks it. Everyone in between saw noise.

03 — The network

A web, not a hub.

/ Topology

No hub to cut.

Every participant is a node. Messages hop from peer to peer with no central relay to sit between them. Remove any node and the traffic routes around it — there is no single point to block, seize, or switch off.

Every client is a node in the mesh
No central relay, no chokepoint
Traffic routes around any node that drops
Offline recipients are served by peers holding fragments
The more nodes, the more resilient the whole

Single point of failure

NONE

Central relay

NONE

Censorship-resistant

YES

Offline delivery

YES

Metadata carried

NONE

Transport

P2P

04 — Strengthen it

Run a node.

The network is only as strong as the people relaying for it. Running a node carries traffic, holds messages for offline peers, and makes the whole harder to disrupt. The setup lives in the docs.

Read the docs →

Contents[ menu ]

Docs / Reference

DOCS

Everything needed to use Kleem, build on it, or run part of the network. Open source, end to end. Pick a section on the left.

Getting started

Introduction

Kleem is an encrypted messenger, a self-custodial wallet, and a gateway to Base — with no account behind any of it. It runs on a distributed network: no company in the middle, no server holding your history.

These docs cover the whole surface, from sending a first message to running a node. Every part is open source; nothing here asks you to trust a claim you can't verify in the code.

No phone number, no email, no sign-up
End-to-end encryption on by default
Keys, messages, and funds live on your device

Getting started

Quickstart

Clone the client, build it, and run it locally.

# clone and run the client git clone https://github.com/kleemapp/kleem cd kleem pnpm install pnpm dev

Prefer a packaged build? Every platform is on the Download page — no toolchain required.

Getting started

Installation

Kleem ships for mobile and desktop. Grab a signed build and verify the checksum before you run it.

iOS — iPhone / iPadOS 16+
Android — Android 9+, APK
macOS — Apple Silicon and Intel
Windows — Windows 10+, x64
Linux — AppImage and deb

# verify a download against the published SHA-256 shasum -a 256 kleem-2.38.AppImage

Getting started

Create your identity

There is no registration. On first launch, Kleem generates a keypair on your device. That key is your identity — it is created locally, stored locally, and never transmitted.

Back up your recovery phrase somewhere safe. It is the only way to restore access; no one can recover it for you.

Getting started

Your first message

Add a contact by their key, or scan a code, and start talking. Every message is sealed end to end.

import { Kleem } from '@kleem/sdk' const kleem = new Kleem() await kleem.keys.generate() // your identity, on-device await kleem.connect() // join the mesh await kleem.send({ to: '0x…', body: 'sealed on this device', })

Core concepts

Keys & identity

Your identity is a cryptographic keypair. The public key is your address; the private key never leaves your device. You can run several identities, cleanly separated, and put a human-readable name on top of any of them.

Generated and stored on-device
Chat keys and wallet keys are separate
Portable across every device you own

Core concepts

Encryption model

Every message is encrypted against the recipient's key before it leaves your device. No relay in the middle holds a readable copy. Keys rotate as you talk, so a key exposed today does not unlock what you sent yesterday.

End-to-end by default, not optional
Forward secrecy through key rotation
Open source — the whole path is auditable

Core concepts

The mesh network

Every client is a node. Messages hop peer to peer with no central relay. Remove any node and traffic routes around it — there is no single point to block, seize, or switch off. If a recipient is offline, peers hold the fragments until they return.

o───o───o ╱ mesh · no hub ╲ o───o───o───o───o

Core concepts

Message lifecycle

Four moves carry a message across the network without a center.

Seal — encrypted on your device against the recipient's key
Shard — split so no single hop carries the whole
Route — passed peer to peer; held for offline recipients
Open — only the recipient's key reassembles it

Core concepts

Self-custody

Self-custody cuts both ways. No one can seize your keys or read your messages — and no one can restore them for you. Your backup is the only backup. Guard the device the way you guard the keys; encryption protects the message, not a compromised phone.

There is no reset link. Store your recovery phrase offline. Losing it means losing access — that is the cost of real ownership.

Wallet

Wallet on Base

Kleem includes a self-custodial wallet built on Base. Only your keys move your funds. Hold B20 tokens and collectibles, with room for more L2 networks over time.

Wallet

Sending & receiving

Send and receive without leaving the conversation. Value moves inside the chat you're already in; every transfer is signed by your key.

await kleem.wallet.send({ to: '0x…', token: 'KLEEM', amount: '25', })

Wallet

Swaps

Swap between tokens without handing custody to a third party. Routing weighs gas before it moves so you're not overpaying to settle.

Communities

Token-gated spaces

Communities open with a token — $KLEEM or your own — and are run by the people inside them. Entry, roles, and rules are set by members, not granted by a platform that can revoke them.

Communities

Roles & governance

Set roles and permissions per space. Governance and treasury tie back to the token, so the people holding it steer the community's direction.

Token

$KLEEM overview

$KLEEM is the network token: governance, access, and settlement, issued on Base. It is held by the people who use the network and directed by them.

ChainBase

StandardB20

RoleGovernance / access

Token

Contract & addresses

The token contract will be published here on deployment. Always confirm the address against the official channels before interacting with it.

Contractpending

NetworkBase mainnet

Verify before you trade. Cross-check the contract address on the official X, Telegram, and GitHub before sending anything.

Developers

SDK

Embed messaging and wallet flows into your own app. Generate an identity, join the mesh, send messages, move value.

npm install @kleem/sdk

import { Kleem } from '@kleem/sdk' const kleem = new Kleem() await kleem.keys.generate() await kleem.connect() kleem.on('message', (m) => console.log(m.body))

Developers

Run a node

Running a node relays traffic, holds messages for offline peers, and makes the network harder to disrupt. The more nodes, the more resilient the whole.

git clone https://github.com/kleemapp/kleem cd kleem/node pnpm install pnpm start # joins the mesh and begins relaying

Developers

Contributing

Everything is open. Read the code, open an issue, send a pull request.

Fork the repo and branch from main
Build and run the test suite
Open a PR with a clear description

Developers

Architecture

The repo is split by responsibility. Start in client/ for the encryption path.

kleem/ ├── client/ interface · encryption · keys ├── node/ mesh relay · offline delivery ├── wallet/ base · erc-20 · swaps ├── contracts/ $kleem · governance ├── sdk/ embed messaging + wallet └── docs/ you are here

Resources

FAQ

Do I need a phone number? No. You generate a key; that is your identity.

Where are my messages stored? On your device. They pass through the network encrypted and are not kept on any server.

What if I lose my keys? Access is gone. There is no copy for anyone to restore. Back up your recovery phrase.

Who runs the network? The people using it. There is no central operator.

Resources

Security disclosure

Found a vulnerability? Report it privately through GitHub security advisories rather than a public issue. Responsible disclosure is rewarded, not punished. Independent audit reports are published as they complete.

Resources

Changelog

v2.38 — mobile browser, private notifications, new L2 networks, faster cold start
v2.37 — community roles, swap routing on Base, lower battery use
v2.36 — cross-device identity sync, per-chat disappearing timers

Download

DOWNLOAD

Free. Open source. No account. Pick your platform and take your keys with you.

01 — Platforms

02 — Requirements

What it needs.

Platform

Minimum

Build

iOS

iOS / iPadOS 16

Universal

Android

Android 9

arm64 · APK

macOS

macOS 12

Silicon · Intel

Windows

Windows 10

x64

Linux

glibc 2.31+

AppImage · deb

03 — Verify the build

Trust, then verify.

Every release is signed and published with a checksum. On a self-custodial tool, matching the hash before you run it isn't paranoia — it's the habit the whole thing is built on.

// verify the download

# compare against the hash on the release page shasum -a 256 kleem-2.38.AppImage # → 9f2c… should match the published SHA-256

04 — Changelog

What changed.

v2.38

latest

Mobile browser and in-chat dApp access
Private notifications
New L2 networks in the wallet
Faster cold start

v2.37

Token-gated community roles
Swap routing improvements on Base
Reduced background battery use

v2.36

—

Cross-device sync for identities
Disappearing-message timers per chat
Bug fixes across the mesh layer

On the legacy app? Migration moves your keys and identities to the current client without a server ever touching them. The guide lives in the docs.

Socials

CONNECT

Announcements, development, and everything in between. Come find the network where it talks.

01 — Channels

Twitter / XAnnouncements and releases, first.@kleemapp TelegramThe community, in real time.t.me/kleemapp GitHubThe code, the issues, the forks.github.com/kleemapp

02 — Where to go for what

Pick the right door.

/ ANNOUNCEMENTS

Twitter / X

Releases, milestones, and network notices. The signal, not the noise.

/ COMMUNITY

Talk to other users, ask questions, watch the network grow in real time.

/ DEVELOPMENT

GitHub — Issues

Report bugs, request features, follow the roadmap in the open.

/ SECURITY

Private disclosure

Found a vulnerability? Reach the maintainers through GitHub security advisories.

These handles are placeholders. Swap in the real accounts before launch — X, Telegram, and GitHub links live in the header, the footer, and this page.