Threads and requests
Writing to a wallet by its address or .sol name, the thread list, and first contact from wallets you have not accepted.
A thread is a conversation between two wallets. You start one by writing to a wallet's address or its .sol name. Each message in it is one transaction on Solana, and that transaction names neither of you.
Write to a wallet#
Press Write at the top of the list, or open New thread at /app/new. With no conversation open, /app shows the same field in the middle of the screen, under Write to an address or a name.
Type an address or a name into Wallet address, .sol name, or a private link. The app looks it up as you type:
| What you see | What it means | What to do |
|---|---|---|
| Looking it up… | the app is reading the wallet's inbox | wait a moment |
| That is not a wallet address or a .sol name. | the text is neither | check what you pasted |
| No wallet holds this name. | the .sol name belongs to no wallet | check the spelling |
| Inbox open and Start thread | the wallet can be written to | press Start thread |
| No inbox and "It can be written to once it opens one." | the wallet has not opened an inbox, so there is no key to encrypt to | ask its owner to open one in Talaria |
| A private link and Open link | you pasted someone's private link | press Open link; see Private links |
The lookup runs on your device. The app keeps a copy of every inbox and resolves .sol names itself, so looking up a wallet tells no server which one you are about to write to. A thread started with a .sol name keeps showing that name on this device.
Send a message#
The field at the bottom of a thread reads Write a message. Enter sends; Shift+Enter starts a new line. Before you type, the line under the field reads Encrypted on this device · Enter to send. As you type, it says what the text will use from your pass:
- 1 message, or the number of parts and "one transaction each" for a long text
- how many messages you will have left today after this one
- "only" the number left today, when the text needs more parts than your pass has left today. Send stays off until the text is shorter.
A message moves through four stages in the thread: Encrypting, Proving, Relaying, Landed. It shows dashed until it lands, then with its time in UTC and Landed. If the first relay doesn't answer, the stage line says trying another relay and the app carries on.
Sending costs no SOL. Each part uses one message from today's limit on your pass, and the relay that carries it is paid by the pool. Passes gives the limits and the day.
In place of the field, the thread says why it can't be written to:
| What the thread says | What to do |
|---|---|
| "You need a pass to send." | press Buy a pass |
| "Your pass expired on" and a date | press Renew |
| "Today's limit of" your limit "messages is used. It resets at 00:00 UTC." | wait for the next day, or press Pass to buy another |
| "This wallet has not opened an inbox, so there is no key to encrypt to." | wait until it opens one |
When a send fails, the reason shows under the message with Send through another relay when another try can work, and Discard. When something fails covers each reason.
Long messages in parts#
One part carries 700 bytes of text: 700 plain Latin letters, fewer when the text has accents, other scripts or emoji, which take more bytes each. A longer text is split into parts, and each part is its own transaction and uses one message from your pass.
While it sends, the message shows which part is on its way, for example "part 2 of 3". The reader sees nothing until every part has landed, then one message marked with its number of parts. If a part fails, sending it again carries on from that part: the parts that landed are not sent again and use nothing more from your pass.
The thread list#
The list is headed Threads, with what your pass has left today beside it, or Get a pass to write when you have none. Search filters the list by name and by last message as you type. Below it the list has up to three groups:
| Group | What it holds |
|---|---|
| Requests | first contact from wallets you have not accepted, and room invitations, with their count |
| Messages | your threads, newest first |
| Rooms | rooms you have joined; see Rooms |
Each row shows the wallet's .sol name, or a shortened address, the time of the last message in UTC, the last message itself (yours start with "You:"), and the number of unread messages. A message that reached you through one of your private links shows the link's name before it. With nothing yet, the list reads No conversations yet with Write your first message.
Opening a thread marks it read. Unread counts are kept on each device.
New messages arriving#
While the app is open, your device reads each new Log entry as it lands and tries your keys on it. A message for you appears in its thread without a reload, and a notice rises at the foot of the screen: From and the name, or Request from for a new wallet, with the first line. Press it to open the thread, or × to dismiss it; it leaves on its own after a few seconds. With sound on, the received sound plays.
Nothing is pushed to you, and nothing is read while the app is closed. The next time you open it, your device reads on from where it stopped, and everything written to you in the meantime arrives.
Requests#
The first message from a wallet you have not written to lands in Requests. The welcome from talaria.sol, the first message every new inbox receives, waits there too. Opening a request shows a Request mark beside the wallet, and in place of the field: "First contact from this wallet. Accept to move it to your threads, or block to drop its messages on this device."
- Accept moves the thread to Messages, and you can reply.
- Block drops the wallet's messages on this device and takes the thread off the list. The wallet appears in Keys under Blocked wallets.
Neither signs anything, sends anything or tells the writer. Both are kept on the device where you pressed them. A thread you have written in is accepted on every device of your wallet, because your own messages come back to each of them. Your keys and devices gives what each device keeps.
Blocking and unblocking#
A blocked wallet's messages are dropped as your device reads them: no thread, no notice, no unread count. They still land in the Log, and they still used the writer's pass.
To unblock, press Unblock beside the wallet in Keys under Blocked wallets, or open its thread, which reads "You blocked this wallet. Its messages are dropped on this device." and press Unblock there. The thread returns to your threads, and new messages from the wallet arrive as usual. Messages it sent while it was blocked were skipped; Restore in Keys reads the Log again from its first entry and finds them.
What the reader sees#
Your reader sees the text, your wallet (by its .sol name if their device knows it), the time in UTC, and the number of parts. Their device accepts the message only if it was written with the inbox key your wallet registered, so no other wallet can write into a thread under your name.
The chain sees a Log entry: a proof and a ciphertext, signed by a relay, with no field for you or for them. The short code beside each message is On chain: press it to see everything the chain holds for that message, part by part, and Open this entry in the Log to see it on the Log. An entry that has just landed may read Not yet indexed. for a moment; Read again looks once more. What the chain sees covers the entry.
How a device finds its messages in the Log, for developers: Scanning.