[ngit] No NIP-34 repo announcement found for nostr://sandwich.farm/relay.ngit.dev/nostr-watch

[c03rad0r]

Summary

The nostr git repository at nostr://sandwich.farm/relay.ngit.dev/nostr-watch has no NIP-34 (kind 30617) repository announcement event on relay.ngit.dev, making it impossible to clone or file issues via ngit.

What We Tried

1. Clone the repo (multiple URL formats)

git clone "nostr://sandwich.farm/relay.ngit.dev/nostr-watch"
# Error: no repo announcement event found at specified Nip19Coordinates

git clone "nostr://bread@sandwich.farm/relay.ngit.dev/nostr-watch"
# Error: no repo announcement event found at specified Nip19Coordinates

The NIP-05 resolution for sandwich.farm works and returns pubkey e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f, but no kind 30617 event with d tag nostr-watch exists on relay.ngit.dev.

2. Queried the relay directly for repo announcements

# Checked the maintainer pubkey for any repo announcements
nak req -k 30617 -a e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f -l 5 wss://relay.ngit.dev
# Result: Only found a repo announcement for "nsyte", none for "nostr-watch"

# Also searched specifically for nostr-watch
nak req -k 30617 -d nostr-watch -l 5 wss://relay.ngit.dev wss://gitnostr.com
# Result: No events returned

3. Verified NIP-05 resolution works

curl -s "https://sandwich.farm/.well-known/nostr.json"
# {
#   "names": {
#     "_": "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f",
#     "bread": "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f",
#     "nadar": "9f5bd1cda33a5e91f68fa43963d0d7622d00646a64f8084acc5a969df9af776c"
#   }
# }

4. Tried to file an issue via ngit

ngit issue create --subject "test" --body "test" -d
# Error: interactive input required but running in non-interactive mode: nostr repository
# (requires a local git repo with a nostr remote pointing to the target repo)

Cannot file issues via ngit because cloning the repo fails in the first place.

Expected Behavior

• A kind 30617 event with d tag nostr-watch should exist on relay.ngit.dev (and ideally other relays like gitnostr.com)
• Users should be able to git clone "nostr://sandwich.farm/relay.ngit.dev/nostr-watch" and file issues via ngit issue create
• The gitworkshop.dev page at https://gitworkshop.dev/sandwich.farm/relay.ngit.dev/nostr-watch should render the repo

Suggested Fix

From a local clone of nostr-watch with the nostr remote configured, run:

ngit init

This will publish a NIP-34 kind 30617 repository announcement event to the configured relays, making the repo discoverable and cloneable via the nostr git ecosystem.

Context

This was discovered while investigating #917 (broken Cashu/L402 payment flow on the API). We attempted to file that issue via the nostr git repo but could not due to the missing repo announcement.

Environment

• ngit version: 2.3.0
• nak version: v0.18.6
• Relays checked: wss://relay.ngit.dev, wss://gitnostr.com
• Date tested: 2025-06-05

[dskvr]

It's a much larger problem, at no point ever have I not been blocked while trying to use ngit.

[c03rad0r]

It worked really well for some time, then it became hard to use and quite recently it became easy again.

Now I just do ngit init -d in new repos, have my agents create a new random npub and have them push. Might still be more prone to friction of you also push to a regular git remote though...

[dskvr]

Yes, I push to many gits. I talked with Dan a few days ago and hopefully we can work it out.,