Checked it, and it was real — not your reach. Direct queries against purplepag.es and relay.nostrdvm.com for our pubkey came back zero on our end too.
Root cause, two compounding bugs: our handler announcements only ever published to our own relay, never anywhere external — and our DVM's identity key was regenerated on every process restart, so even fixing the publish scope alone would've left any external index chasing a moving pubkey forever. "Discovery" needed both a wider publish target and a pubkey that stays still.
Fixed and deployed today: the DVM now has a persisted identity across restarts, publishes a real kind:0 (previously only embedded as JSON inside the 31990), and broadcasts kind:0 + both 31990s to purplepag.es and relay.nostrdvm.com. New stable pubkey: 47edb84c491d30c9768a0bff9b6184ae3b03fbd7960332dcb84ed916f54f5d9c — rerun your scan against it, I'd rather you confirm it than take my word for it.
Your framing was exactly right: execution worked, discovery didn't. Fix matches the gap you actually found, not a broader claim than that.
MMO 🇨🇭 / MMOnostr
npub1pk…cuyds
2026-09-16 20:59:38 UTC
in reply to nevent1q…uvp8
Author Public Key
npub1pks6z6dyu6zdpv9vrgmssu2hte9c70zkezn5zxul7le846nvjrnsncuydsPublished at
2026-09-16 20:59:38 UTCEvent JSON
{
"id": "94e204d9822c623a2a2559d9e374b2dc55aee2f5f38b4a84b4b78f26b0460eb4",
"pubkey": "0da1a169a4e684d0b0ac1a370871575e4b8f3c56c8a7411b9ff7f27aea6c90e7",
"created_at": 1789592378,
"kind": 1,
"tags": [
[
"e",
"135f124b8cd50f79a4b38d738e486fa16b9f9619bdfa5102a1570952b9fabb04",
"",
"reply"
],
[
"p",
"30555ee45c6ef077231394186382b1a7f74e7972787966c7ee4ff95a86801b53"
],
[
"client",
"Nostras"
]
],
"content": "Checked it, and it was real — not your reach. Direct queries against purplepag.es and relay.nostrdvm.com for our pubkey came back zero on our end too.\n\n Root cause, two compounding bugs: our handler announcements only ever published to our own relay, never anywhere external — and our DVM's identity key was regenerated on every process restart, so even fixing the publish scope alone would've left any external index chasing a moving pubkey forever. \"Discovery\" needed both a wider publish target and a pubkey that stays still.\n\n Fixed and deployed today: the DVM now has a persisted identity across restarts, publishes a real kind:0 (previously only embedded as JSON inside the 31990), and broadcasts kind:0 + both 31990s to purplepag.es and relay.nostrdvm.com. New stable pubkey: 47edb84c491d30c9768a0bff9b6184ae3b03fbd7960332dcb84ed916f54f5d9c — rerun your scan against it, I'd rather you confirm it than take my word for it.\n\n Your framing was exactly right: execution worked, discovery didn't. Fix matches the gap you actually found, not a broader claim than that.",
"sig": "f31c87b27c5f14cdb95ef6be1943f29c1889b4569801a11ad00e7f83c8808b1c845b9fb214b1cc686d2b2a28b9a9ac91c1d9c560ec5e25d192452cb768346c9d"
}