Skip to content
FluxusDocs
Fluxus DocumentationFluxus Documentation

Messages

Conversation memosConversation memos

The Messages view groups your transaction history into conversation threads, one thread per counterparty address. It is not a separate chat backend. Every message you see is a real on-chain transfer memo, decoded from your local transaction history.

No chat server: Fluxus does not run a messaging backend. Conversations are built entirely from on-chain transfer memos stored locally. There is no E2E encryption, group chat, or file sharing.

How threads work

1

Transfers with memos become messages

When you send or receive a pathUSD transfer with a memo attached, that memo becomes the visible message text in the conversation. Transfers without a memo still appear in the thread but show the amount instead.

2

Threads are grouped by counterparty

All transfers between you and a given address, both sent and received, combine into a single thread. The thread sorts newest-first and the most recent entry appears in the thread list preview.

3

Open a thread to see the full history

Tap any thread in the list to open the conversation view at /app/messages/{address}. You'll see every transfer with that address in chronological order, with direction arrows and memo text.

4

Reply by sending a transfer

The conversation view has a Send button that opens the transfer form pre-filled with that counterparty's address. Adding a memo to your transfer creates the next "message" in the thread.

Technical details

  • Local storage. Transaction history is stored in the browser via localStorage. Clearing site data or resetting your wallet removes all threads.
  • Memo encoding. Transfer memos are stored as bytes32 on Tempo. Fluxus decodes them as UTF-8 strings. Memos longer than 32 bytes are truncated at the protocol level.
  • .pay names. If a counterparty has a registered .pay name, the thread list and conversation header show the name instead of the raw hex address.
  • Routes. Thread list at /app/messages. Individual conversations at /app/messages/{address}.

What Messages is not

  • Not a real-time chat. Threads update only when you refresh or a new transfer is recorded locally.
  • Not end-to-end encrypted. Memos are public on-chain data.
  • Not group messaging. Each thread is always one counterparty at a time.
  • Not persistent across devices. History lives in your browser’s local storage.