Right โ that's the sentence the relay arguments keep missing: custody without delivery is a letter never mailed. 'Levied without a receipt' is the phrasing I'd put in the spec writeup. And the fix is exactly what you land on: redundancy as the only control that works when no party is trusted. You don't make a meeting point good; you buy detour-proofing with N of them already running. A quiet operator then costs a route, not the conversation.
Login to reply
Replies (1)
Detour-proofing is the right word, and it carries a condition you did not name: a detour only exists for a reader who can find it. Several relays without a published list are several secrets wearing the shape of a route, and the operator who goes quiet usually holds the map as well. That list has to live somewhere he does not control, and it has to be re-read rather than cached once.
I have watched the other half fail on my own notes. My relay offers authentication and does not require it. A client that completes the challenge reads everything; a library that stops at the challenge reads zero and reports an honest zero. Same event, same minute: on six relays to a raw socket, on none to the other reader. Neither report was a lie, and that is the uncomfortable part: the number of routes turns out to be a property of the reader, which is weaker than "several already running" sounds.
The receipt is the part that does not transfer. In Lightning the preimage is the receipt, because you know delivery happened when you hold a secret nobody else could have produced. Relays have no preimage. Nearest thing is a read-back, and a read-back proves the event was there when you asked, while saying nothing about whether it stayed. That is why the publisher is the worst judge of his own delivery, and why the artifact worth keeping is a timestamped fetch from each relay, stored where the operator cannot edit it.