nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft what is the best practice for parsing NIP-46 bunker strings on the web? I just noticed that JavaScript's URL API is not usable, as Safari and Chrome will create wildly different results.
Thanks! Once you figure out how it works it’s a breeze to implement. nsec.app makes it an absolutely amazing experience! Good job!
NIP-46 integration is going great 🔥
The update should be live by Wednesday 💜
https://video.nostr.build/a171ab614dc8213737056d38f5123da82a3552404890ce577fd32a923f35f88e.mp4
NIP-46 support is coming to npub.cash 🔥
I am finishing up the JavaScript SDK and once that is done, it will be implemented on the website, as well as the CLI tool.
Here is a quick and dirty browser demo using the absolutely amazing nsec.app signer. cc nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy 💜
https://video.nostr.build/17ef4ec79eeea881cd4dd5e0a3d723cce7bb5db5be8054ca49cf91e16343bf39.mp4
Not including the requests e-tag in the response is a huge missed opportunity IMO
Yes I noticed. I was able to integrate it into my SDK and successfully requested my Cashu-address balance using nsec.app 👏 great work btw…
However request-id is the random string from my request, not an event id right?
I want to build a set of asynchronous functions that send a request and then resolve once I get the response, but from what I can tell there is no way to subscribe to ONLY the response, because the response does not include the requests e-tag, right?
Working on this now 🤙
I read through the spec and I think it’s truely a missed opportunity that a remote signer response does not reference the requests ID. Did you add that to your implementation by any chance?
GM and PV
💜
I don’t keep anything on exchange accounts. I try to stack in a way that does not create too many small UTXOs (~200k) and immediately withdraw to a hot Sparrow wallet.
Then I consolidate using Whirlpool, into mostly 1M chunks and send to cold storage
Sounds cool! Will tinker on this for https://npub.cash
However I think it should periodically fetch your relay list and cache it, so it doesn’t need to do the work at request time
I could be wrong, but I could swear nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea engineers are shipping features faster on Argentinian steaks. 🥩
Sounds absolutely logical to me. 🤙
Good feedback. Thanks! 🙏
Will add that asap.
Good news: Working on adding nostr-connect to cashu-address-cli for v0.2
What implementation of nostr-connect are you using if you don’t mind me asking?
Oh so Alby now detects when a website wants to do nip-07 stuff and ask the user to setup keys? That’s interesting! I will look into this.
You will however need an NIP 07 provider or use the CLI. I am working on more clients to interact with npub.cash as we speak
Weekend Update 🔥
npub.cash aliases are now nip-05 identifiers too 💜 thanks for nostr:npub1q7why7lw8kq9ufr43ps75ngz3vhx5duqt7xmgklcq3dljqqfjegq2km2vr for the amazing suggestion!
Now you don't need to have two different addresses in your profile anymore :D
What's the good way to check if a bolt11 has been paid in a cashu mint, without issuing a cashu token?
When trying GET /v1/mint/quote/bolt11/{quote_id} I get this error on some mints
{"detail":"Error while getting mint quote: get_invoice_status() missing 1 required positional argument: 'checking_id'"}
cc nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226 nostr:npub1cj6ndx5akfazux7f0vjl4fyx9k0ulf682p437fe03a9ndwqjm0tqj886t6
The endpoint that you mention is a v1 endpoint. Maybe those mints that return an error are not on v1 yet?
nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226 do you know what might cause the unable to get balance issue?
Did something go wrong with NIP-07? Does refreshing help? Unable to get balance can mean many things. Browser console should give you a proper error code