because the gods don't want to use more than 2 chars for nips, so they decided to start using hexadecimal instead to keep it short.
The ecash section of the nostr:npub13s5mxgws70rpxsug96jfvglggackjrxs2ehypwg0prjaxsek42sqd9l03e guide is live! Thanks to all the #Cashu and #Fedimint devs who helped out. I got to think through some of the unique nuances of ecash and suggest some design best practices. Check it out and let me know your thoughts: https://bitcoin.design/guide/how-it-works/ecash/introduction/
great! the only thing that I feel should be added is explaining how tokens can be locked to a pubkey ensuring that it can only be spent with the corresponding private key.
yo #sec
where's the water wheel and shack? 😅
are you drawing these yourself? I really like the style and content
demo day at nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5 #sec3
#Bounty Alert:
100K sats for a great Coffee Shop name that is bitcoin/nostr related.
Name must still make sense to non-bitcoiners and non-nostr users. don't go super heavy, a play on words probably makes most sense.
Name must be catchy, clear, easy to say, 2 to 3 syllables max.
Think something clever like nostr:npub1key55ax33gkl50uqemvl4khrtqrhzm7wzpc7fhseutt5ddkcwcrqgxlt3h but since they have the best name ever. We are on the hunt for the next best name.
This is not a programming bounty. there are no criteria to be met here lol, but I will honor the bounty if I pick your name suggestion. Also it will become the name of the Cafe!
#CoffeeChain has been considered, but it is being used as a name for a shitcoin. so probably i'll have to skip, unless you think it doesn't matter.
Cough Fee
that note is in draft mode, you have all those tiny options to choose from (usually you want to click on yolo as it will add pow, sign and post all at once)
I already do have in-memory and indexedDB for all events that come through, but it's only used at the moment to get single missing events to build threads, can't really query it easily yet
ah ok. yeah those can compound rapidly, especially if you run it on multiple relays...
I need a good way to browse the local db so you can easily get data without re-asking for it.
damn, only saw this now.. do you think it was because of bad client behaviour handling requests or because you requested too much data? how much is 40k sats worth of data with silent.link?
