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 treated as trusted if it's signed by the same key as the reference event that is being attested to.
The idea is that you are already trusting the pubkey that signs the reference event - if you didn't, you wouldn't be interested in the reference event (or its OTS data) at all. So if you see a purported OTS proof that's signed by the same key as the reference event, you can by default treat this as trusted without the need to perform a verification against what's recorded on Bitcoin.
In that situation, the only time you need to perform an audit against Bitcoin is when there is some positive reason to suspect that the OTS data you were provided with is incorrect.
#nostrdev #asknostr #OpenTimestamps
inkan
npub16x…56z6l
2026-03-08 12:16:19 UTC
Author Public Key
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6lPublished at
2026-03-08 12:16:19 UTCEvent JSON
{
"id": "3dd92f976439e0bda9161f05881a5ed72256506128159562375d898c96c5e416",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1772972179,
"kind": 1,
"tags": [
[
"t",
"nostrdev"
],
[
"t",
"asknostr"
],
[
"t",
"opentimestamps"
]
],
"content": "Has anyone thought about how to disseminate Opentimestamps OTS proof data attesting to Nostr events across the relay network?\n\nI've been trying to implement this such that OTS data is by default treated as trusted if it's signed by the same key as the reference event that is being attested to.\n\nThe idea is that you are already trusting the pubkey that signs the reference event - if you didn't, you wouldn't be interested in the reference event (or its OTS data) at all. So if you see a purported OTS proof that's signed by the same key as the reference event, you can by default treat this as trusted without the need to perform a verification against what's recorded on Bitcoin.\n\nIn that situation, the only time you need to perform an audit against Bitcoin is when there is some positive reason to suspect that the OTS data you were provided with is incorrect.\n\n#nostrdev #asknostr #OpenTimestamps",
"sig": "071d06dc4d7d19a07fa43c95d54c0af6b4ee779d3938ba1401cb3a2e00f895992cefe17d035b3b3b623882e873249c5a8ca27133e029e81a418473d1d484e043"
}