Yeah, working on a solve for that right now. Cashu tokens (especially if made up of many single small nuts) can become HUGE. A single QR code will not be able to handle that.
Fix: Animated QR code, but those are not broadly supported yet. But we are working on it.
Thank you so much for giving it a spin and leaving feedback 💜
At least try it and let me know what to improve 🤙
There are many different nip-07 providers available. For Firefox and Safari too.
I just unlocked a P2PK Cashu nut in my web browser using nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm and paid a Lightning Invoice with it...
This is nuts... 🤯🥜
That’s not how this works ;) I’ll send them to your Cashu-Address in a minute
I’ll make sure to finish the docs today and let you know 🤙
Recently installed nostr:npub1dx5q2el8nd4eh3eg9t2e25fd7zuqg7zxz6ldkc3uzgh66ss2yc6st288sj don’t know my Cashu-Adress though 😅 nostr:note1wp2e3ymaf93vrugjyfkejm94azlvqmr9w0gth4wvha0d8s8f6r3sqvfsa4
It’s
Check out https://app.cashu-address.com to learn more
I’ll send some Sats to anyone who shares this post… ⚡️
Plot twist: I’ll send them to their Cashu-Address 💜
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
Nvm. String needs to be a hex string. Your documentation seems to be outdated.
Getting „Error: hex invalid 2“ when calling this with „test“ in my browser console. Any idea why?
Doing some housekeeping 💜🥜
V1 is getting close!
https://github.com/lightning-digital-entertainment/cashu-address/pull/6
I see where you are coming from. But BH I think anything that requires nostr related state (in this case a users private key) should be under window.nostr.
It would not make sense for something in window.bitcoin to access state that the user setup as nostr private key and sign with it. These things should be decoupled.
Pretty sure albys default behaviour is to pop open and ask the user for confirmation
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
Would signSchnorr work for your purpose?
https://guides.getalby.com/developer-guide/v/alby-browser-extension-apis/window.nostr/signschnorr
Yes perfect. Did you ever propose to make it part of the spec? It’s difficult to rely on if it is not adopted by most providers
Can we get signatures on arbitrary data in NIP-07? That would be great!
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
You can check out the whole protocol specification as flowchart here: https://link.excalidraw.com/readonly/GEiWWmg1mVjQcjhD0GCJ?darkMode=true
However not every single step is implemented in the demo app yet. This whole idea is just a few weeks old and constantly evolving. I am trying to get a v1 release ready by the end of February
Even better: people can’t stop you. Just zapped nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 some nuts haha