Yeah that would be freaking awesome and we could so much cool stuff with our nsecs if we could just schnorr-sign arbitrary data with Alby or Nos2x nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 and nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x
Can we get signatures on arbitrary data in NIP-07? That would be great!
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Discussion
we have that. there is a general signSchnorr() in Alby
Yeeeeesssssss!!! P2PK nuts on the web here we go!
Was there ever been an attempt to standardise this in NIP-07. it would enable so many cross protocol usecases. Opening a PR as we speak
Do you have any protection for web apps asking users to sign event ids? I could see this being misused to get users to sign events without them being able to see what they are signing
Pretty sure albys default behaviour is to pop open and ask the user for confirmation
Getting „Error: hex invalid 2“ when calling this with „test“ in my browser console. Any idea why?
Nvm. String needs to be a hex string. Your documentation seems to be outdated.
yes. you sign a hash.
where is it wrong?
https://guides.getalby.com/developer-guide/v/alby-browser-extension-apis/window.nostr/signschnorr
The code example says
const signature = await window.nostr.signSchnorr("some text here");
But that would throw