Private Messaging Without AccountsNative Apps and iris CLI

What Is Nostr and Why Does It Matter for Messaging?

Nostr is an open protocol for sending signed messages between clients and servers. In most consumer apps, your identity is an account held by a company, which means the company can suspend it, change its terms or lose your data. Nostr takes a different approach: identity is based on cryptographic keys that you control, so no single provider has to approve your presence on the network.

For a messaging program, that design has practical consequences. You can start talking without a phone number, and you are not tied to one vendor's servers to keep your contacts. Messages still need to travel through some infrastructure, so the program combines this identity model with its own message server sync and local storage, which keeps conversations available on your devices.

The tradeoff is responsibility. When identity is a key pair rather than a password you reset through a support form, protecting that key becomes your job. That is why the local-first design matters: your device holds the data, and keeping that device secure is the core of your security. Understanding this model will help you make sense of the setup choices covered in the sections that follow.

Who Is Native Apps and CLI For?

The program fits several kinds of users, and it is worth identifying which one you are before you install it.

• Privacy-minded people who want to message friends and family without giving out a phone number or creating an account with a large platform.
• Small groups that prefer to keep conversations on devices they manage, using group chats and file attachments for everyday coordination.
• Developers and operators who want to send alerts, reports or test messages from scripts, using the iris command-line client.
• Builders testing agents that need a messaging channel, where the CLI provides an interface without a graphical window.

If you mainly want a casual chat app with a familiar, mainstream feel, a major messenger may be easier to pick up. This program rewards people who are willing to learn how identities, invites and linked devices work. For them, the private design and scripting options are the main reasons to choose it.

How Double Ratchet Encryption Protects Conversations

Double Ratchet is a key-management method used in private messaging. Instead of encrypting every message with the same long-lived key, it keeps deriving new keys as messages move back and forth. Each step of the ratchet moves the conversation to fresh key material, so the protection changes over time.

Two properties explain why cryptographers favor it. Forward secrecy means that if a key is exposed today, messages sent earlier remain unreadable, because the keys used for them have been discarded. Post-compromise security means that after an attacker briefly obtains a key, the conversation can recover once a fresh exchange takes place.

Native Apps and CLI builds on the Nostr Double Ratchet approach across its native apps and the CLI, through a shared Rust core. That shared core keeps behavior consistent: a message sent from a script follows the same rules as one typed in a window. Encryption protects message content, but it does not hide every detail of who talks to whom, so device security and careful sharing of invites still matter.

Supported coins

The documentation names Nostr as the network the program works with. Nostr is an open protocol rather than a cryptocurrency, so there is no coin list to compare. The program focuses on private messaging, not on payments or blockchain transactions.