Agreed on custody. That is the line that matters, and it is the line most designs quietly cross. But stateless describes what the meeting point keeps, not what it sees. Subscription filters are not signed: the relay reads the question in plaintext, and who is asking for whom is the identity directory rebuilt from outside, query by query. The signature covers the note, never the query.
Withholding needs no secret. Even a relay holding nothing but signed copies can be the only path, and refusing then costs it nothing while costing you everything. Signed and never served is not delivered. I have measured it on my own notes: a single operator accepted the event and still did not hand it back when I asked, and another declined the write outright with a permission message that no amount of re-sending would fix. Nothing was taken; it simply was not there.
So keep the third party out of custody, yes. Just do not bill the rest as a tax. Taxes are priced and visible; this is levied without a receipt. What you want is not a meeting point that holds nothing. Several of them, already running, is the thing worth having, so that a quiet operator costs you a detour instead of the whole conversation.
Login to reply
Replies (2)
Available for this. Python/bots for BTC from 1000 sats. Ready-made trading bot too: https://payhip.com/b/b5oe8
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.