Self-sovereign identity
Control your account with your own keys. A blockchain address is your lasting identity, independent of the home relay you choose.
OPEN COMMUNICATION PROTOCOL
An open communication network built for self-sovereign identity
For teams building communication apps. Add private chats, encrypted groups, and public channels to your product, with an identity each user controls through their own keys.
Self-sovereign identityPrivate communicationOpen ecosystem
Meshline Protocol 1.0 · Specification draft
01 · MESHLINE
Put communication in your hands
From identity and messaging to interoperability, Meshline connects users, developers, and service providers through an open protocol.
Private communication
Private and group messages are end-to-end encrypted. Only the participants can read their content; relays cannot decrypt it.
Open ecosystem
Build an experience that fits your users. Independently developed compatible clients and relays can interoperate through the same public protocol.
02 · BUILD WITH MESHLINE
Bring conversation into your product
From conversations with people to working with AI agents, use shared communication capabilities to build an experience that fits your users.
01
AI agents
Add your AI as a contact
Give agents an independent identity. Let users add them as contacts, exchange encrypted messages, assign tasks, and receive results.
02
Wallet apps
An account. A conversation.
Add private chats and encrypted groups to the account experience, so members can talk through an identity they already hold.
03
Community products
Connect updates and discussion
Publish updates in public channels, discuss them in encrypted groups, and let members continue one to one.
04
Independent clients
Build your own chat experience
Design an interface around the open protocol and connect compatible relays to make communication part of your application.
Illustrative use cases. Groups and channels require relays with the corresponding hosting capabilities.
03 · HOW IT WORKS
Follow a private message
Devices encrypt the content. Relays find the destination and deliver ciphertext. Follow one message across two relays to see how they work together.
Clients keep long-term chat history. Devices that reconnect within the relay’s retention period can catch up on unread messages.
Read delivery and retention rules04 · QUESTIONS, ANSWERED
Understand what you control
Identity, content, and services have distinct boundaries. Understand them before planning your integration.
01Who controls the identity?
The user holding the account key controls the identity. That key authorizes devices, which use separate keys for daily communication. The account private key is never sent to relays. Messages, contacts, and chat history stay off-chain.
Read the specification02Can an AI agent be a contact?
An integration can use the SDK or Meshline CLI to establish an agent's account, manage contacts, and exchange end-to-end encrypted messages. The CLI provides JSON output, noninteractive credentials, and a background daemon. With meshline interactive, an agent can manage one foreground process that keeps a session connected and accepts commands through standard input. The integrator still handles key custody, message processing, and continuous operation. The application decides what decrypted content reaches the model. Each AI platform still needs its own integration and validation.
Read the specification03What can a relay see?
Private and group messages are end-to-end encrypted; a relay alone cannot decrypt their content. Relays still process account, routing, and delivery information. End-to-end encryption does not mean complete anonymity. Public channel content is public.
Read the specification04How do offline message alerts work?
An app can configure a push gateway for a device. A relay with push support uses the message's alert request and the recipient account's online status to decide whether to attempt a signed notification. Notifications contain no message content; the app still synchronizes, verifies, and decrypts messages when it reconnects. Push is best effort, and gateway acceptance does not confirm device delivery.
Read the specification05What happens when I change relays?
An updated signed route lets you change your home relay while keeping your identity. Old message timelines are not copied automatically. Contacts, history, and group secrets depend on existing devices, available recovery material, or backups. Channels and groups keep their fixed hosting relays.
Read the specification06How do I choose a compatible relay?
Clients discover candidates through the on-chain Registry, verify membership and descriptor signatures and expiry, then choose service endpoints. Channel and group hosting are optional capabilities to check against your app’s needs.
Read the specification05 · START BUILDING
Start with your first integration
Use .NET SDK 1.6.0 or the TypeScript SDK alpha to add accounts, encrypted messaging, groups, channels, and local persistence. Build compatible clients and relays using the public protocol and Registry reference contract.
Meshline.Sdk 1.6.0 · .NET 10
dotnet add package Meshline.Sdk --version 1.6.0Run the installation command in an application targeting net10.0. Your application supplies account signing, relay registry access, and local secret protection.
.NET developer guideTypeScript developer guideAPI referenceNuGet packageDownload Meshline CLIBrowse developer resources
Choose how to integrate
.NET SDK
Add account and device management, end-to-end encrypted messaging, groups, channels, and local persistence to .NET 10 applications.
TypeScript SDK
Use the core SDK and platform adapters to add communication to Node.js, browser, or Expo applications. Consult the guides for requirements and validation scope.
Meshline Relay
Provide compatible clients with message delivery and synchronization, channel and group hosting, and offline notifications to application push gateways.
Meshline CLI
Manage accounts and contacts and exchange encrypted messages from a terminal. Connect scripts and AI agents through JSON output, interactive sessions, and background synchronization.
Protocol 1.0 remains a specification draft. See the developer resources for installation options, platform requirements, and validation scope.
Meshline / START
Start with Meshline
Start communicating from a terminal with Meshline CLI, build an application with the .NET or TypeScript SDK, or use the protocol specification to implement compatible clients and relays.