Names Wallet on Android

A Pixel 8 ran the app unplugged overnight, idle with the screen off, and kept following the chain the whole time.

• 9 h 14 munplugged
• 100 → 31 %battery over the night
• ≈ 298 mAhused an hour
• ≈ 13¾ hfull to empty at this rate
• 629blocks followed
• 53 saverage time between blocks
• ≈ 74 MBdownloaded an hour
• ≈ 107 MBuploaded an hour

Battery through the night

Charge level, hours after unplugging

Time between blocks

Seconds between new blocks as the phone received them, half-hour averages

One run on one phone: a Pixel 8 (battery about 4,110 mAh) with app 0.5.11 on the Logos testnet. The block figures cover the 629 blocks received while unplugged. Other phones and networks will differ.

You write to a name or straight to a messaging address, not a phone number. No name is needed on either side. The message is sealed on your phone, sent by the phone's own messaging node, peer to peer, and can be opened only by the person who holds that address.

1. Find the address

   From the name's entry in the LNS registry, or typed, pasted or scanned from a QR code.

2. Seal it on your phone

   A fresh one-time key locks the message to that address. Only ciphertext leaves the phone.

3. Sent by your own node

   The messaging node on your phone passes it to other nodes in the Logos Messaging network.

4. Held until they're online

   The network keeps the sealed message, so it arrives later if they're offline.

5. Opened on their phone

   Their own node receives it. Only the holder of that address's secret can open it.

On the chain, and off it

• Messages are not put on the chain. The chain holds names and coins; messages travel beside it.
• Your phone is a node. It runs the Logos Messaging node and a Logos blockchain node itself.
• One lookup goes out: finding a name's address is one RPC call to the LEZ sequencer.

Inside one message

What travels across the network, left to right.

Ver.One-time public keyNonceEncrypted: sender, text, time, proof of senderSeal

readable by the networkreadable only by the recipient

Version 1 byte, one-time public key 32 bytes, nonce 24 bytes, then the encrypted part (up to 2,000 characters of text) and a 16-byte seal.

What's protected

• Contents: the text, time and sender are encrypted end to end.
• The sender is hidden from the network; it's inside the sealed part.
• Impersonation: every message proves which address sent it. A name shows only if it matches.
• Address changes: if a name's address changes, the app stops and asks first.
• On the phone: saved chats are stored encrypted.

What isn't protected yet

• Who received it: the network can see which address a message is for, when, and its size.
• Old messages: one long-lived key per phone. If it leaks, recorded past messages can be read.
• First contact trusts the address the registry gives at that moment.
• Spam: anyone who knows an address can write to it.
• No outside audit yet. Group chats are not in this version.

Under the hood

Key agreement

X25519, with a new one-time key for every message

Encryption

XChaCha20-Poly1305, key from HKDF-SHA256

Sender proof

HMAC-SHA256 that only the two parties can check

Address

A name's msg entry, or a messaging address given directly; pinned at first contact

Transport

Logos Messaging (Waku), node to node; one channel per recipient address

Format: Names Messages version 1, as implemented in app 0.5.11, using the @noble cryptography libraries 2.4.0. Described from the app's source. Not independently audited. Testnet software.

The Android app lives on the android-app branch of github.com/jefdiesel/logos-node-android. The repository's default branch holds a different project, the Linux web wallet.

There is no download, APK or store listing yet.