The project’s announcement gives examples such as a wallet that includes a conversation alongside a token transfer, an event app where attendees can form groups, and an AI application with a built-in chat.
According to the announcement, Meshline is intended as an alternative to sending users to platforms like WeChat or Telegram, building a messaging system from scratch, or adopting a hosted chat SDK with usage-based fees. The project compares its approach to email, where different providers share common standards.
Applications that implement compatible parts of the protocol and connect to the same registry contract could let their users message one another, though the project notes that this depends on how each product handles identity, permissions, and compatibility.
Neo N3 accounts without on-chain transactions
Meshline account IDs follow the CAIP-10 standard, using the Neo identifier format that Zhang registered under CAIP-2 in August. Each ID takes the form neo:<network magic>:<address>, where the address is a standard Neo N3 address derived from the account’s public key.
Users don’t send blockchain transactions to use Meshline. Setting up an account publishes identity and device information to a relay. Only relay operators send transactions to the chain, while apps just read the relay list from it.
The account key authorizes up to eight devices, each with its own signing and encryption keys for everyday messaging, so a wallet doesn’t need to stay online once a device is authorized. According to the project, the account’s private key is never uploaded to a relay.
Messages require consent. A sender needs a contact approval or invite from the recipient, or the recipient must opt in to public discovery, and the protocol prohibits relays from turning users’ contacts into a public directory.
Relays and the on-chain registry
Relays are the servers that store and forward messages. Private chats and encrypted groups are encrypted on users’ devices, and a relay cannot read their content on its own, although relays still process routing information such as who is messaging whom and when.
The project’s website states, “End-to-end encryption does not mean complete anonymity.” Group hosts also see group names and member lists, and channel posts are public.
Public relays are listed in MeshlineRegistry, a Neo N3 contract that stores each relay’s identity, endpoint, and status. On Neo N3 MainNet, the contract currently charges a 100 GAS registration fee and lists one active relay.
According to the contract’s published source code, a governance owner account can suspend relays, change the fee or set it to zero, transfer ownership, and upgrade the contract. Only a relay’s own key can change its endpoint or switch it on and off.
Because identity is held in the user’s keys rather than by a relay, users can move their account to another relay. Message history isn’t copied in a move, and groups and channels stay on the relay that hosts them.
SDKs and tools
The SDKs are MIT-licensed. The .NET SDK, published on NuGet, has had nine releases, from v1.0.0 on Sept. 27 to v1.8.0 on Nov. 4, and includes an optional adapter for signing with NEP-6 wallets.
A TypeScript SDK for Node.js, browsers, and Expo (React Native) is in alpha, with its latest release on the same day. It has so far been tested on Windows with Node.js and on Android, with Linux and iOS still unverified.
The meshline command-line client, a development preview at v0.3.0 for Windows and Linux x64, is designed for people, scripts, and AI agents. It offers JSON output, a background daemon, and an interactive mode that accepts commands through standard input.
Early-stage status
The Meshline v1.0 protocol specification is still a draft, available in English and Chinese. The .NET SDK has been tested offline against simulated peers, but live-relay interoperability and cross-platform validation remain pending, according to the project.
With one relay registered, cross-relay delivery and relay migration have not yet been verified. The project’s website describes its relay software as implemented, with source code that is not public.
Jimmy Liao, Neo core developer and R3E Network founder, opened a security audit issue on the specification in September. It lists five protocol-level findings, including the possible replay of revoked device state across relays and the absence of forward secrecy, which protects past messages if a device key is later compromised.
The issue is still open, and the specification separately states that group messaging claims neither forward secrecy nor post-compromise security.
Development continues in the SDK repository, where commits on Nov. 9 and Nov. 10 added portable encrypted backups that have not yet shipped in a release.
The original announcement can be found at the link below:
https://medium.com/@meshline.growth/meshline-an-open-protocol-for-in-app-messaging-04d5c0a910b3