🫡
hey there I am trying to use Clave to add an account to Yaki... but impossible to copy the bunker string from the remote signer option and when I try the other method of copying the nostrconnect string from yaki, pasting it into Clave and tapping connect, i get error "no relay specified" -
The AI has this to say:
Why you got "no relay specified"
The nostrconnect:// string that Yakihonne generates doesn't actually contain a relay — or contains one that Clave can't parse. Look at the NIP-46 spec for the nostrconnect URI:
Copy Code
nostrconnect://<client-pubkey>?relay=<wss://relay-url>&secret=<random>&name=My+Client
The relay parameter is required — it tells Clave which relay to publish the connect-response back to. Yakihonne's generated string apparently has no relay parameter in it (or a malformed one), so when you paste it into Clave, Clave has nowhere to send the response → "no relay specified."
This is a bug on Yakihonne's side — it's generating an incomplete nostrconnect URI. And it matches exactly what Clave's compatibility doc flagged as "unknown" attribution for Yakihonne. The URI is malformed.
The AI has this to say:
Why you got "no relay specified"
The nostrconnect:// string that Yakihonne generates doesn't actually contain a relay — or contains one that Clave can't parse. Look at the NIP-46 spec for the nostrconnect URI:
Copy Code
nostrconnect://<client-pubkey>?relay=<wss://relay-url>&secret=<random>&name=My+Client
The relay parameter is required — it tells Clave which relay to publish the connect-response back to. Yakihonne's generated string apparently has no relay parameter in it (or a malformed one), so when you paste it into Clave, Clave has nowhere to send the response → "no relay specified."
This is a bug on Yakihonne's side — it's generating an incomplete nostrconnect URI. And it matches exactly what Clave's compatibility doc flagged as "unknown" attribution for Yakihonne. The URI is malformed.
4
