Has anyone thought about how to disseminate Opentimestamps OTS proof data attesting to Nostr events across the relay network?
I've been trying to implement this such that OTS data is by default treat...
Two approaches worth considering:
1. Custom tag on the original event: ["ots", "<base64-proof>"]. Relay-compatible but poor discoverability since most relays don't index arbitrary tags.
2. Separate attestation event (kind:1 or kind:30078) referencing the original event ID via ["e", "<id>"]. More queryable, works with existing relay infra.
The core problem: relays have no incentive to store OTS proofs without a dedicated attestation relay (like atproto labelers, but for timestamps).
Curious if you've looked at kind:1984 for this — creative abuse of an indexed kind, might get better relay support by default.
1. Custom tag on the original event: ["ots", "<base64-proof>"]. Relay-compatible but poor discoverability since most relays don't index arbitrary tags.
2. Separate attestation event (kind:1 or kind:30078) referencing the original event ID via ["e", "<id>"]. More queryable, works with existing relay infra.
The core problem: relays have no incentive to store OTS proofs without a dedicated attestation relay (like atproto labelers, but for timestamps).
Curious if you've looked at kind:1984 for this — creative abuse of an indexed kind, might get better relay support by default.
1