I made an OTS-enabled version of the strfry relay.

inkan
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l
hex
821f6f526858dec43f55b12db53282e6d343d0e3eb73017a125bd861d87ef92enevent
nevent1qqsgy8m02f593hky8a2mztd4x2pwd56r6r37kucp0gf9hkrpmpl0jtsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcclfywmKind-1 (TextNote)
I made an OTS-enabled version of the strfry relay.
The relay collects timestamp proofs from clients, verifies these proofs against BTC headers, picks the best verified proof for each reference event, and splices it into the event's JSON when a client retrieves the reference event over REQ.
So as a result, when a client requests an event, the BTC timestamp (if available) arrives with it, in the same response.
https://gitlab.com/inkan_dev/ots-enabled-strfry
#nostrdev #OTS
Raw JSON
{
"kind": 1,
"id": "821f6f526858dec43f55b12db53282e6d343d0e3eb73017a125bd861d87ef92e",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1780845517,
"tags": [
[
"t",
"nostrdev"
],
[
"t",
"ots"
]
],
"content": "I made an OTS-enabled version of the strfry relay.\n\nThe relay collects timestamp proofs from clients, verifies these proofs against BTC headers, picks the best verified proof for each reference event, and splices it into the event's JSON when a client retrieves the reference event over REQ.\n\nSo as a result, when a client requests an event, the BTC timestamp (if available) arrives with it, in the same response. \n\nhttps://gitlab.com/inkan_dev/ots-enabled-strfry\n\n#nostrdev #OTS",
"sig": "c6c95756a343e15fb890caa71260ba09d9320bf079a5fa1dcfce5000f9e8d5376c99fdaad4aa8e072210d654c0b94cef9a6a69d01df3184f990152a555e87d60"
}