Great plug haha. Bought and almost 50% through. Loving it so far.
However I am wondering about statements like “The goal of TDD is to create a test suite that you would trust with your life.”
Is that really possible? I can only think about so many edge cases. Never all of them. If I refactor a module and see all green I might be confident in that system, but what happens if my refactoring causes an edge case to error, that used to just slip through? Won’t it re-introduce the fear of touching the old code?
Working on Cashu Payment Requests aka. “Can I has nutz?”. This will enable typical point-of-sale transactions with Cashu. Early feedback is appreciated 💜
Charging the hyperdrive 🤙💜 
Yes, easy. nprofile can encode relay hints. However I would not build on that, but roll our own spec, that can include an amount, memo, etc
What books on software testing / TDD / writing better automated tests would your recommend? #asknostr
GN Nostr 💜 
nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226
I love that cashu is data agnostic and can be sent via any medium. Although if you send to someone you always have this giant block of text. Is there any mechanism to shrink it down or human readable? Sort of a TinyUrl?
There are attempts to make it smaller, but we are talking „half“ not „tiny“. The token itself contains all information necessary to claim your sats, that’s why it is so big. There is no way (I can think of) to shrink it down without introducing trust
GM, PV and welcome 💜
Listening to nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft's Clean Agile and I wonder if it would be overkill to implement an agile approach in a one-man-show. Might be fun 🤙
Cashu Token can become really big very quickly. An animated QR code makes sure that even devices with lower end hardware will be able to scan them, even if on a small screen (by splitting the data).
Animated QR codes finally made it into the live-version of npub.cash 🤙💜
Not all wallets support the format yet, but most do. I took this opportunity to give the modal some touch ups as well 👀 https://video.nostr.build/c007e85c2cea68ee511123252aac6aa568aae794d1201168658d435f0d11d5d4.mp4
You are right, this is misleading. What I meant is „a signature that can be verified using my public key“.
I’ll make sure that this is updated.
Got it!
Yeah, would be pretty neat to have a npub.cash address directly in Cashu.me… am I right nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg 👀👀
Proof of steak 🥩🔥 This one was worth every single cent and more!
Thanks for everyone who commented on this one day steak journey haha 🙌🏻 
nostr:note1a2vnd306fpet48xt9x8x8cy9l0a8efgz34tdk0m3e6ll8ehuuqysvej2mg
You are not really supposed to „send“ to npub.cash yourself. It acts as Lightning address for you. Like a post box for payments
Here is a video of the process https://video.nostr.build/83c6c949f7c7b74614a06fa03fe7b1c098de0688feab6b14b826ff609736cf9b.mp4
With Cashu the sender generates the code. In npub.cash click on „Cashu“, copy the token, go into your Cashu wallet and paste it there
Make sure to approve the signing requests in nsec.app when you open the app, or give it privileges to sign automatically. Npub.cash is built on nip-98 and every request will require a signature from your nsec.bunker
Are you using nsec bunker / nip-46? Try clearing the cache.
Claiming on Cashu shouldn’t show a qr code. Just text and buttons. Animated QRs coming next week 🤙