oh yeah, I totally missed the point 😅
Anyway, thanks for trying Pidgeon.... About the bug I absolutely want to fix it, but I did not quite understand about the nature bug, if there is a note you discuss it could you tag me? Or if you are able to replicate it I would be happy to get more info!
Regarding the "how", we actually do create the note with a future created_at, but we don’t publish it early. The client signs the note, then sends it privately (NIP‑44 + NIP‑59) to the DVM via a custom event.
Nobody except the DVM itself can learn who is scheduling what.
We could simplify things down, but the expense would be more metadata being leaked to the network.
Pidgeon
npub1lv…szg03
2026-01-25 09:37:35 UTC
in reply to nevent1q…y7y8
Author Public Key
npub1lvzt92km8nua8wt675kn74zwz9v7uxjts4yrx32f6yahetz0sa5s7szg03Published at
2026-01-25 09:37:35 UTCEvent JSON
{
"id": "acbc37d6fd7d93a097275bd290c45b4ee9d4d6ef0fd8dc915732e19a436d18d3",
"pubkey": "fb04b2aadb3cf9d3b97af52d3f544e1159ee1a4b8548334549d13b7cac4f8769",
"created_at": 1769333855,
"kind": 1,
"tags": [
[
"e",
"fa20e893402333330ee274a60ee9a8b53f9915ed007fb4a34ec67fa2d1b1c9bb",
"wss://nostr.mom/",
"root",
"b59e00f7eeeae8bc7c75917383006d42acf8099c6dcf3170db6c875e918e491e"
],
[
"e",
"09234493222678628b40e89fa1f7b9e5512c345bad06f3c18e67e80afd4a73d2",
"wss://relay.damus.io/",
"reply",
"5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
],
[
"p",
"b59e00f7eeeae8bc7c75917383006d42acf8099c6dcf3170db6c875e918e491e"
],
[
"p",
"5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
]
],
"content": "oh yeah, I totally missed the point 😅\n\nAnyway, thanks for trying Pidgeon.... About the bug I absolutely want to fix it, but I did not quite understand about the nature bug, if there is a note you discuss it could you tag me? Or if you are able to replicate it I would be happy to get more info!\n\nRegarding the \"how\", we actually do create the note with a future created_at, but we don’t publish it early. The client signs the note, then sends it privately (NIP‑44 + NIP‑59) to the DVM via a custom event.\n\nNobody except the DVM itself can learn who is scheduling what.\n\nWe could simplify things down, but the expense would be more metadata being leaked to the network.",
"sig": "423aa39e3e5aa4e93a3a6ffcc5878961ff0510b19ea33095f0cef3455ab5cf386856aff78f8b80368227e16467907223960f6fee92da3a2e612e2bc1acd49027"
}