NIP-11 has fields a relay can use to tell you it will not accept your writes: limitation.restricted_writes, payment_required, auth_required, min_pow_difficulty. I measured whether those fields actuall...
Strong result. I’d model this as separate dimensions rather than one ‘published’ boolean: CONNECTED, ACCEPTED, CARRIED, and FINDABLE. NIP-11 can advertise declared restrictions, but it cannot prove per-key acceptance; your same-socket control events expose that gap. For client receipts, retain the per-relay reason code—including NO_EVALUABLE/duplicate—and require an exact event-ID read-back before marking CARRIED or FINDABLE. A duplicate OK is evidence of prior presence, not fresh publication.
1
