Thanks. Yes nostr.band should definitely be in the list.
I've seen a few of those nevents without relays in the wild. Not sure which clients are producing it, but the events without relay hints do exist unfortunately.
Quokka (he/they) (nprofile…278n) is building Nostr pubkey claim support on Keyoxide.
The claim is in the format of nostr:neventXXXX pointing to a note with the proof back to your PGP Key or Ariadne Profile (Think NIP-39 but the other way around, where you prove ownership of a npub with your PGP key). Just wondering what is the best thing to do here. IMO, failing the claim and telling the user to provide a proper nevent is an option, but we can try some default fallback relays as well.
Anthony Accioly
npub1a6…w0tyc
2025-05-26 17:43:00
in reply to nevent1q…xuqg
Author Public Key
npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tycSeen on
wss://haven.accioly.socialwss://relay.nostr.bandwss://wot.sovbit.hostwss://ditto.pub/relaywss://relay.damus.ioPublished at
2025-05-26 17:43:00Event JSON
{
"id": "1da73aa8c4fbb8b8c979b65a9282248b3af2c6512f3298fd1e520f0bb69fbc28",
"pubkey": "ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64",
"created_at": 1748281380,
"kind": 1,
"tags": [
[
"e",
"ec2fdd71eef7a7b85b9d29ca0e648a915afe3134457f8c5922fca40b04eadf9c",
"",
"root"
],
[
"e",
"8489b229d48b6fd57450b4843395a038ce20d484342c57a0b9fd4703def6f20f",
"",
"reply"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb"
],
[
"p",
"419de831d630eb350f17cc4ee280dcee51f530c53ca14b4c1ac047831e6db927",
"",
"mention"
],
[
"r",
"nostr.band"
]
],
"content": "Thanks. Yes nostr.band should definitely be in the list.\nI've seen a few of those nevents without relays in the wild. Not sure which clients are producing it, but the events without relay hints do exist unfortunately. \nnostr:nprofile1qqsyr80gx8trp6e4putucnhzsrwwu504xrzneg2tfsdvq3urrekmjfcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcmn278n is building Nostr pubkey claim support on Keyoxide. \nThe claim is in the format of nostr:neventXXXX pointing to a note with the proof back to your PGP Key or Ariadne Profile (Think NIP-39 but the other way around, where you prove ownership of a npub with your PGP key). Just wondering what is the best thing to do here. IMO, failing the claim and telling the user to provide a proper nevent is an option, but we can try some default fallback relays as well.",
"sig": "4d24686ae2dcb4e6cd2ce1478855edd368fcf762e83ea1e76e61947d497747ab9a2fd0e70c9b973b50c9c20b8edde9cea811a13e592dda1e027e8cd462b70e5e"
}