What the chain sees
What a Log entry holds and what it leaves out, where to look at one, and what is public about your wallet.
Every message in Talaria is one transaction on Solana, and anyone can read every one. This page goes through what such a reader finds, where to look for yourself, and which of your actions are public.
A Log entry#
The chain holds each message as a Log entry. It has these parts, in this order:
| Part | What it is |
|---|---|
| Proof | The proof that some pass in the pool sent this message, today, within its daily limit. It doesn't say which pass. |
| Root | The state of the pool the proof was made against: a fingerprint of every pass bought up to then. |
| Day | The day the message was sent on, counted in UTC days. |
| Nullifier | A one-time number that lets a pass send only its daily limit. Nothing in it points to the pass, or to any other message of the same pass. |
| Key slots | Two locks on the message: one your reader's keys open, one your own devices open. Neither says whose keys they are. |
| Ciphertext | The message itself, locked: the text, who wrote it and when, readable only through a key slot. |
| Relay | The relay that carried it. Its signature is the only one on the transaction. |
Around those parts, the transaction has what every transaction has: its signature, its slot, its time and its size.
What is not in it#
- Your wallet. You never sign a message; the relay does.
- Your reader's wallet, or their inbox key.
- Which pass sent it.
- Anything that ties two messages together: two messages of yours look as unrelated as messages of two strangers.
- Whether it went to one wallet, to a room or through a private link, and who is in a room.
Your address does travel with the message, inside the locked part, so your reader knows who wrote. Only the reader's keys and your own open it.
Turning a message over in the app#
Beside every message in a thread is its signature, cut short. That is its On chain control. Press it and the panel opens with This is everything the chain holds for the message you are looking at. It lists Signature, Slot, Time, Relay, Day, Nullifier, Proof, Key slot 1, Key slot 2 and Ciphertext, and ends on Of this, what identifies the writer or the reader: Nothing.
A message sent in parts was several transactions; the panel has Part 1, Part 2 and so on, one tab each. Open this entry in the Log opens the entry on its own page.
The Log#
/log shows every message as it lands, newest first, to anyone. Each row has its Time, UTC, its Relay, its size in Bytes and its Nullifier, and opens the entry. The status reads Live while entries stream in; Pause holds the list still and Resume goes on. All relays and All days narrow the list to one relay or one day.
Beside the list: Passes in the pool, Messages today, Messages, all time, Entries per relay, Entries per minute, and the Fee account balance, the protocol's share of pass sales that buys and burns TALARIA.
One entry#
/log/<signature> is one message in full, as the chain holds it. What the chain holds shows every part with all its bytes. Verification says whether its proof checks:
| It shows | What it means |
|---|---|
| Verified | the proof checks against this entry's public values |
| Invalid | the proof does not check against them |
| Not checked | the checker can't be reached right now; the proof and its values are on the page to check yourself |
Public inputs lists the values the proof was checked against, and Open the transaction opens it on a Solana explorer.
Make a proof yourself#
/proof shows what every proof states, in plain terms beside the rule that states it. Press Prove and your browser makes a real proof with a demonstration pass: the stages read Loading the prover, Proving, Verifying, and the page shows the Proving time, the Proof size and The proof verifies. No wallet is needed and nothing is sent. It is the same work your device does at Proving for every message.
What is public about you#
Three things you do are signed by your wallet, and each is public like any transaction:
| You | Anyone can see |
|---|---|
| open an inbox | that this wallet has an inbox, its inbox key, and when it opened it |
| rotate your inbox key | that this wallet's key changed, and when |
| buy a pass | that this wallet bought a pass, its messages a day, its days, its price and when |
That is how anyone can write to you: the app reads that your wallet has an inbox and shows Inbox open.
What is not public#
- Who wrote to whom. No message names its writer or its reader, and no server keeps a list.
- Which messages are yours. Your device downloads the Log, the same as every other device, and finds what its keys open. No one is told which entries those were.
- Which pass is yours. Your device reads every pass in the pool to find its own.
- Which wallet you looked up. The app keeps a copy of the whole inbox directory on your device and answers from it.
- Who is in a room, and which wallet owns a private link.
- What you accept or block. That stays on your device.
How each part works, for developers: The Log, The proof and Scanning.