Oddbean new post about | logout
 by now we're used to logging in to a nostr app and our social graph and data being there

now we'll become used to logging into an app and our money being there too

#nutsack

https://sphinxdateranch.com/media/catalog/product/cache/7a47274eba68bad16b989efe5caaae72/s/p/spicy-mix.png 
 Sounds great, just as long as others keep their hands off my nutsack. 🥜 
 Unless there is consent! 
 But what if i want to protect my nuts in a separate nsack, keep identity away from money 
 You can! 
 And spend/zap from the identity i use? Thats cool 
 YUP! 
 Ecash stored as a NIP44 encrypted event = SUPERPOWER 
 Few 
 Magic things.
nostr:nevent1qqs0ce2f6cyrtsv6pgpjwr7z9emuu7x3kkqg9ph6rgu34dxtmts5kycpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg86np9a0kajstc8u9h846rmy6320wdepdeydfz8w8cv7kh9sqv02gpsgqqqqqqsl0tdct 
 👀 
 i don't accept peanuts for payment, sats only 
 Great one Fren thanks 👍😊 

#BTC #Zap⚡#Nostr #JulianAssangeIsFree 🔥🚀 
 Interested to see how the relays handle this, are they all of a sudden, money transmitters?

 
 Alright alright 🤙🏻 
 I fucking love that this is seriously being called #NutSack. Keep the #Nostr weird! 
 Nut meme the future you wish to see 
 I think I used the ginger emoji instead of the 🥜 lol. 
 Can users view each other's nutsacks?  
 For example, can I look at nostr:nprofile1qqsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uq3vamnwvaz7tmzv4mx7tnwdaehgu339e3k7mf07mjd7k's nutsack to see if his is larger than mine or will the balances be encrypted? 
 Only the girls can see the boy's nutsacks. Unless the guy is gay, so I hear.  
 👀 
 As far as I understand, you would still only be able to see someone's public Cashu zaps. Cashu zaps could be encrypted using nip44 in which case you wouldn't see them. The receivers client would combine the public and private (nip44) balances  
 There a meme here with the classic https://i.nostr.build/0ltBun56xoKJRTSQ.jpg
template  
 So many jokes can be made in the name of technological progress.
nostr:nevent1qqs0ce2f6cyrtsv6pgpjwr7z9emuu7x3kkqg9ph6rgu34dxtmts5kycpzdmhxue69uhk7enxvd5xz6tw9ec82c30qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqpkfn5f7 
 jokes/thanks 4 the endorphins/ gr8 days all! 
 Smooth 
 So a client sets up one or more cashu wallets on relay for the user. Cashu zaps can be received to that wallet, and this all works because cashu nuts work as backed bearer assets themselves and the control key is made the nsec. Ingenious. 

Please correct me where I'm wrong, but remaining steps to a fully integrated system are: 
1. Clients need to implement cashu wallet support (relay wallet) and support for cashu zaps (relay nuts) between said wallet(s).
2. Implement transfer of nuts in and out of the relay wallet.
3. Implement sending of relay nuts to a lightning address, such that receipt of the sats does not require the recipient to have setup a relay wallet.
4. Implement receive of relay nuts from a lightning transaction, such that the sender does not need to be aware of the wallet being on relay.

I have barely touched cashu, so for all I know most of this is already done or is unnecessary. 
 nutsack  is to bitcoin like a neclace is to #gold  ...   flaunt ..  
 And its a good thing  ..  what is the point of gold if there was no jewellery  :-) 
 nut cloud 
 What about fees ? When, not if, bitcoin fees go higher than the unbanked can afford, is this different ? Are these nostr txn fees somehow tied to bitcoin fees ? Because it was shocking to see non custodial LN freeze when  bitcoin  fees went through the roof.  
 🍻 
 Wikifreedia

There are two specs; both under my profile in the Nostr category 
 Why isn't #nutsack part of the spec? Should be written in there somewhere 🤔  
 We've moved beyond nips at this point. Things are moving way faster than that repository can keep up with, and we should embrace it.  We need a method for releasing new specs to be judged and iterated on in a public way. Pull requests are too slow, but even in that case - they should have reached some stability to be submitted for "The Protocol". 
 We've moved beyond nips at this point. Things are moving way faster than that repository can keep up with, and we should embrace it.  We need a method for releasing new specs to be judged and iterated on in a public way. Pull requests are too slow, but even in that case - they should have reached some stability to be submitted for "The Protocol". 
 nostr:nevent1qqs0ce2f6cyrtsv6pgpjwr7z9emuu7x3kkqg9ph6rgu34dxtmts5kycpzemhxue69uhk2er9dchxummnw3ezumrpdejz7q3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqqqqz7kj6vv