PING Wallet · Topic 01Open the wallet →

The memos

A memo is an end-to-end encrypted text message: it leaves your device already sealed, crosses the federation's network of nodes — which carry it without being able to open it — and is only read on the device of whoever received it. Once there, it waits to be dispatched: it opens a pending call on the tape of the other person, and a pending item only leaves the tape once it is answered or ignored. That is the nature of a memo — not a message piling up in a list, but an act that stays open until somebody decides on it.

All of this makes the memo the most basic transaction in the wallet: like every transaction, it leaves one party, reaches another, is recorded and calls for a decision — except that what it moves is text, not money. That is why this topic uses the simplest case, the plain-text memo: the stamps you learn here are the same ones you will see when the memo carries a question with options or an attached X-DOC.

And they are the real stamps: this page loads the same stylesheet as the application, so nothing here is an illustration — it is the product, magnified.

The path of a memo

A memo is encrypted before it leaves your device and is only opened on the device of whoever receives it — along the way, the federation nodes carry a sealed package, with no key and no idea what they are carrying. A memo goes to every one of the other account's devices, and whatever none of them collects within 90 days is erased for good.

YOUR DEVICEFEDERATION NODE NETWORKHER DEVICES
01 · the sendThe memo is held in your outbox for the undo window you configure — from 3 to 60 seconds. After that, the send is irreversible.
02 · transitHeld in the federation's node network for up to 90 days, waiting for someone to collect it. No node owns the memo.
03 · distributionEach device on the other account downloads its own copy. The stamp counts how many have downloaded it.
In this topic
  1. The anatomy of a memo
  2. The send — from your device to the network
  3. Transit — from the network to her device
  4. What the other party did

01The anatomy

Every memo you send has three parts: the content, the time and the stamp. The content and the time never change after the send. The stamp does change — it is the only living part of the bubble, and it tells where the memo is.

Deal, I'll send you the file tonight.10:31in transit

Content · time · stamp

The content is what was said and it is not rewritten. The time is the time of the act — the instant you tapped send, not the time of delivery: if the memo spent the night trying to go out, the time is still the one when you wrote it.

The stamp is the only living part: above, it runs this memo's whole cycle — in your outbox, in transit, on her devices, and what she did. The sections that follow break down each step.

02The send — from your device to the distributing node network

Before reaching anywhere, the memo has to leave here. This stretch is entirely yours: nothing that happens in it concerns the other party, and none of it has been said yet.

in your outbox→ retrying→ in transit
done!10:31in your outbox — distributes in 25 s
the window you configured

In your outbox

The memo has not left your device yet. It sits there at your disposal for the undo window you chose — from 3 to 60 seconds, adjustable in the wallet's preferences. While the window runs, the send button becomes Cancel this send and the memo can be undone without leaving a trace — because nothing was said.

When it closes, the memo goes. After that it cannot be erased: what went out, went out.

done!10:3127 s
no internet

Retrying · and the countdown to the next try

With no connection, the device retries on its own, in the background, for up to 24 hours — every 5 seconds at first, doubling until it settles at every 2 minutes. The number is the time left until the next try.

There is nothing to do: the subway, the plane, the lift — it keeps trying. Once the network is back, it goes out at once. If you want to give up, the Cancel this send in the bubble's menu hands the text back to you.

done!10:31did not go
24 hours later, or on your order

Did not go

The queue gave up. The bubble is still there, marked — the text you wrote is not lost to a network error; whoever wrote it wants to resend, not retype.

If the memo had been an answer on the tape, the frame goes back into the queue and the light blinks: the tape exists to say what is missing, and an unanswered request is still missing.

Why the time does not change with every try. Resending is not a new act — it is the same sentence, insisting. If the time were rewritten with every try, the record would start lying about when that was said.

03Transit — from the node network to her device

Once out of your device, the memo is held in the federation's distributing node network until some device on the other account downloads it. There are two different stamps on purpose: “reached the post office” and “reached the house” are not the same thing.

done!10:31in transit
one dash

In transit

The memo has left your device and is in the distributing node network, waiting for the other party to download it. A single dash: it is no longer yours, but not hers yet.

Here the send is over — what is left no longer depends on you or on your connection.

done!10:312 devices
two dashes

Downloaded by N devices

It arrived. The number tells on how many of that account's devices the memo already sits — phone, computer, tablet. Really delivered, not “handed to the post office”.

This does not mean it was read: reading is another matter, and it is in the next section.

done!10:31recipient not found
90 days later

Recipient not found

The network holds the memo for 90 days waiting for someone to collect it. The window is generous on purpose: holidays, a broken phone, a change of device. Once it is past, no device on that account has shown up — the account is abandoned and the memo will not be read.

The window expires, but the bubble does not disappear. The text stays, only the stamp changes: proof that erases itself is not proof.

Why one dash does not turn into two on its own. If “delivered” only meant “reached the network”, the 90-day window would turn the stamp into a lie: you would hold delivery proof for a memo nobody received. The two states exist precisely so that the expiry can be said to your face.

04What the other party did

From here on the stamp no longer speaks of transport, but of decision. None of these states fire when the conversation is opened: leafing through your own archive is not an act towards whoever sent it. They are born when the memo is touched on the tape — the one instant in which the person was actually confronted with your request.

Can you review it today?10:31skipped
heard it and put it off

Skipped

The other party heard your memo on the tape and left it for later. It is not a refusal: your request is still in her queue, and it will come up again.

This stamp exists to kill the ambiguity of silence. Without it, “has not seen it yet” and “saw it and did not want to” look alike — and whoever is waiting reads both as a refusal.

Can you review it today?10:31ignored it
closed it without answering

Ignored

The other party closed this memo without answering. It was a decision, and it is recorded on her tape with a time — it is not inattention or forgetfulness.

It comes highlighted in yellow, like someone running a marker over it and closing the matter. Never in red: it is a legitimate choice of hers, not a failure of yours.

Can you review it today?10:312 devices
I can — I'll send it to you by 6 pm.10:44
the best case

The answer

When the other party answers, the answer arrives quoting your memo — it is the quote that ties the “yes” to the question. Months later, nobody has to reconstruct what that “I can” referred to.

The answer beats every stamp before it: it is the strongest receipt there is.

Why opening the conversation announces nothing. A read receipt that fires on an accidental tap is noise: it forces a choice between reading and owing an answer. Here the state is born of a deliberate act on the tape, and that is why it means something.

Cover of the Communication Pack on the X-Hub: a blue bird flying with an envelope in its beak, a ringing bell and a cassette with its tape unspooled, in a starry night sky. on the X-Hub Communication Pack The memo in this topic does not come alone: Memo, Reminder, Tape and X-DOC share the same seat — and are born with every wallet. See it in the store →