Pinned Tweet
Talaria is a shielded pool for messages on Solana.
CA:efo75jisqQsV8jghoXuseQRGwJyE5ee8AwY4z5opump
You write to any wallet. The chain gets a proof and a ciphertext, and neither wallet is in the transaction.
talaria.to
Buyback crossed 10M TALARIA burned on its 20th run.
That's about 1% of supply, all bought with fees.
Paid 0.01 SOL between two of our own wallets on mainnet, deposit to withdraw. None of the 9 transactions has both wallets in it.
The payment: solscan.io/tx/2rJm84Udaoj3JQ…
1
17
A brand new device sent its first message after pulling 36,697 bytes (SDK 0.18.0, measured locally).
Used to be the whole Log first.
36
You can send SOL in a thread now. Put an amount in the composer and it goes with the message.
Been waiting to ship this one.
1
42
Next thing we're building: your Talaria inbox inside the wallet you already use.
The module's out in SDK 0.17.0, same inbox as on talaria.to, from the wallet's own signature. Now it needs a wallet to carry it.
36
First watch alert just landed in the Log.
Our test address moved, 20 s later it was in the thread. Send Watch an address from New thread if you want one.
The relay holding our test file logged a file id and chunk numbers, that's it.
100 KB into a room of three on mainnet, our own wallets. Opened byte for byte for everyone, restored devices too.
3
141
Fixed the SDK docs, every sample was still pointing at a local address. They're on mainnet now.
Easiest first send is Receipt: it replies with the signature, slot and relay of what you sent.
talaria.to/docs/sdk-quicksta…
How your app finds your messages in a public Log: each one carries a one-byte view tag.
Your device checks the tag, skips nearly everything, and opens only what's yours. The server hands everyone the same bytes.
Rooms are one shared key. A message to the whole room is still one post, however many people are in it.
Add someone and the key shows up in their thread. Remove someone and everyone else gets a new one.
Buyback's run 6 times now. 0.488 SOL of fees in, 8,105,561 TALARIA burned.
Supply's at 991,894,437. Live count here:
api.talaria.to/stats
You can be written to without anyone learning which wallet is yours.
Make a private link in Keys and share it. Whoever opens it writes to you, and it lands in a thread named after the link. Revoke it whenever.
Why Talaria: in Iliad 24, Hermes ties on his winged sandals to get Priam through the whole Greek camp without anyone seeing.
Felt like the right name for this.
1
161
Lost your laptop? Your messages never lived on it.
Connect the same wallet anywhere, sign once, press Restore. Every thread comes back from the Log, including what you sent.
1
127
Fair question: we run the relays, so what do they know?
This is what ours got for the first mainnet message. It signed and got paid. Who wrote it and who it's for aren't in there.
And with two relays now, the one that sees your IP never sees the entry.
105
Funny thing about crypto: the deal is wallet to wallet, and the chat about it runs on an account tied to someone's phone number.
That's the part we're taking out.
89
The proof gets made on your device, not on a server.
Open /proof and it makes a real one right in your tab. About 1.4 s, 256 bytes, checked on the spot.
talaria.to/proof
90
Files work in threads and rooms now, up to 25 MB.
Encrypted in 32 KiB chunks, held by one relay for 30 days, fetched through the other. The one holding it never sees who sent it or who opened it.
Images open right in the thread.
83
Shipped the light scan.
Your device reads 210 bytes per Log entry, opens only its own, and fetches those by private retrieval. The server can't tell which entries anyone took.
It pays off past ~4,500 entries. Under that the full Log is smaller, so the app picks for you.
talaria.to/docs/scanning
72
Send a wallet a memo and you've drawn a public line between the two of you, for good.
Our first mainnet message has one signer, the relay. Go find either wallet in it:
solscan.io/tx/3mqniLtm17ibhK…
1
72












