The problem: when you connect an app to a Nostr remote signer over a bunker://
link (NIP-46), the signer had no way to know *which* app was connecting — so theconnection showed up nameless/generic. You'd approve signing for "some app" with no idea who.
The fix: the client can now include its name, URL, and icon right in the connect
request — the same info nostrconnect:// already carries, brought to the bunker
flow too. Clave reads it and labels the connection properly.
It's live end-to-end: Clave (signer) reads it, and our experimental client jank.army (client) sends it. Pair them and the app's real name shows up.
We've proposed it as an extension to NIP-46 so any signer or client can adopt it. https://github.com/nostr-protocol/nips/pull/2381
Backward compatible — apps that don't send it connect exactly like before.
cc greenart7c3 (npub1w4u…0jr5) fiatjaf (npub180c…h6w6)
https://clave.casa
