Skip to content
Open app

Using TalariaPrivate links

Private links

Share a link that lets anyone write to you without learning which wallet is yours.

A private link lets someone write to you without learning which wallet is yours. It carries a key of its own, registered to no wallet, so nothing on chain or on any server ties the link to you. Whoever opens it writes to that key, and your devices find what they write.

Open Keys at /app/keys. Under Private links, type a Name for a new link, or leave it empty, and press Create link.

The name is at most 40 characters, and it travels in the link: anyone who holds the link can read it, and the page they open shows it as who they are writing to. Leave it empty to say nothing.

Creating a link signs nothing in your wallet. It sends one message from your pass to your own inbox, a note that every device of your wallet reads, so each of them learns the link. While the note is sent, the four stages show under the field: Encrypting, Proving, Relaying, Landed. Then the link joins the list, by its name or as Unnamed link, with Copy link and Revoke. If the note fails, the reason shows under the field and no link is made.

Create link needs a pass with a message left today. Without one, the button is off and the line under the field says so.

Share it#

Press Copy link and send the link however you like. It is an address on this site's /l page, with the link's key and name after the #. A browser never sends the part after the # to any server, so the key and the name stay with whoever holds the link.

From New thread, or the field on /app, a pasted link shows A private link and Open link, which opens the same page.

Opening a link lands on /l. The page asks for what the visitor doesn't have yet, one step at a time:

What the page showsWhat it meansWhat to do
This link can't be opened.the address has no key after the #, or it was cut short when it was copiedask for the whole link; Open the app goes to the app
Connect walletno wallet is connectedconnect one
Make your keysthe wallet hasn't signed the key message on this devicepress Sign the message
Open your inboxthe wallet has no inbox; the owner's device needs it to check who wrotepress Open my inbox
"You need a pass to send."the wallet has no passpress Buy a pass
"Write to" and the link's name, or Write to the owner of this linkreadywrite and send

A wallet that already has an inbox reads the Log on this device before the page opens, with the entry it has reached. A wallet that opens its inbox here receives the welcome from talaria.sol first, and Start writing opens the page.

Sending through a link moves through the same four stages as any message, and uses one message from the visitor's pass for each part. The owner pays nothing. Once it lands, the page reads "Delivered." and the visitor's copy stays on their device. If it fails, the reason shows with Send again.

The visitor's device encrypts to the key in the link and never looks for a wallet behind it, so it never learns which wallet is the owner's. The Log entry is a proof and a ciphertext like any other.

What the owner sees#

The owner learns who wrote: every message carries its writer's wallet inside, for its reader alone. A message through your link lands in your thread with the wallet that wrote it, under Requests if that wallet is new to you, marked "via" and the link's name. In the thread list, the link's name shows before the last message.

When you reply from that thread, the reply is an ordinary message from your wallet to theirs, so the writer then learns which wallet is yours.

Press Revoke beside a link. It reads Revoking… while it sends one message from your pass to your own inbox, a note every device of your wallet reads. From then on your devices stop looking for messages to that link: what is written to it afterwards lands in the Log and is never read. What already arrived stays.

Revoked links are listed under the live ones, with "Your devices no longer scan for" them. If the note fails, the reason shows under the list and the link stays live. Revoking signs nothing in your wallet and needs a pass with a message left today, the same as creating.

Each link's key comes from your wallet's signature, and each link's note is in the Log. Every device of your wallet therefore holds the same links with the same names, revoked ones marked revoked, whether or not anyone has written to them. Your keys and devices covers a second device.

What each action uses#

ActionWho paysMessages from the pass
Create a linkyou1
Revoke a linkyou1
Write through a linkthe visitor1 per part
Receive through a linknobodynone

How link keys are derived, for developers: Cryptography.