if you receive a 1, 2, 3, 5 or 8 sat zap from me, you're being zapped from my nostr balance
Discussion
Awesome!
I can't wait to learn more about this and if we can use this to make zaps even easier for new users.
that's 100% the goal
when I'm done we'll be able to:
* have a single balance across all nostr apps
* no QR codes / NWC secrets
* zaps are immediate -- no need for a zap receipt -- if you send the zap the zap is received -- sending money will be exactly as fast as publishing a note or creating a 👍 event
* there's no need to signup for a wallet, your nsec is your wallet
The only thing that scares me would be relay operators deleting events or relays going down and this effecting your balance. Is that possible?
I guess even if it is you just don't keep too many sats in there at a time, then just send to another wallet.
What is the mechanism to transfer sats from Nostr to a wallet?
I am working an iteration of the protocol so that any arbitrary amount can be issued as a single proof. When you need to pay a certain amount you split out the amount required, send that and the remainder as issued as a new proof.
Nsec are a real problem.
They should expire, also, to have some privacy a new npub for each contact is needed.
You can not trust an nsec long term.
What if you get hacked? How to recover your identy/sats?
As I see it, you secure your nsec the way you secure your bitcoin seed phrase
yes, but outdoors; two nerds out of their dark holes, right nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg?
Where do the tokens get stored? Do they get stored as nostr events?
Correct. Encrypted, with an optional passohrase , on some user-selected relays.
Very cool! What event kind are you using? I am exploring storing arbitrary amounts in a single proof, so it could be stored as a replaceable event, once you swap out what you need for payment and then store the resulting token with the reduced amount using a replaceable event.
Replaceable events are very problematic for this; I’m using 7375 for proofs and a replaceable for the wallet (which may or may not link to unspent proofs). The 7375 may tag the wallet event.
Once a proof is spent the token event where it exists must be deleted and any unspent proof published into a new one
Ok thx. I love this approach because the network becomes the custodian.
Curious why you are storing the proof as a json, versus the serialized format. I am fine either way, but wondering the rationale?
You have me thinking about replacing my wallet implementation with a nostr event store using relays.
Seems impossible!
when will this be possible?
I have read "that's 100% legal" that was such a joke😓😂
If zaps are immediate how are the sats stored with the nsec?
How do you handle my preferred zapping wallet loading to the main interface when I press Zap on a post but not taking me to an actual zap?
Bigger than DVMs if true
👀
👀
😮
SO BULLSHIT. HIT ME WITH THIS NOSTR BALANCE ZAP.⚡️
Cashu zap support in NDK? this will be big.
nostr feels like a garden for UX engineering lol
nostr:note1d50cxa63z3qdz6qvh0ddqd3s2e4nqjr75ytpgsmkxjetp2dfrxlq2vr6tl
time to p2npub so hard I guess
you should call these "nut zaps"
and if you really wanna go for it maybe you want to rename "nostr balance" to "nut sack"
HAHAHHAHAHAHAHHAHAHHAHAHAHABAHHAHABAHHAHAHAHA
👑
works cited: 
😳😖🤣🤣🤣 best/grossest post o day
I always say that I want to make a change purse out of my cojones for my widow. I like the image of her using it to pay the strippers. It’s on my will among other things
😂👌
"taking care of my nut sack" ”growing my nut sack"...
#yestrt
Nut sack… from where you share your seed
Problem is that that conflicts with the next thing I have in the works that is sending nuts as the zap (P2PK nut events)
These are regular LN zaps funded by nuts stored on relays instead of talking to a wallet over NWC or Webln, I couldn’t come up with anything better than “nostr balance” to capture that yet 😅
brb, creating a nut event
Yeah and if it’s a larger zap, you can say “I nutted all over you”
:o
I often feel that Cashu is too complicated, adding extra levels of complexity when people just want to send sats back and forth. If nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt can pull this off and make it seamless and easy to on-board and use, then I'm all for it.
Plus, we get to make nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gprpmhxw309akk7mnpvshx5c34x5hxxmmd8gurqwpsqyxhwumn8ghj7mn0wvhxcmmvqyvhwumn8ghj7urewfsk66ty9enxjct5dfskvtnrdaks7vj9m5's Nut Zapper a reality. And that's reason enough to do it 🤣
When I like something and regrets it, is post zap clarity (?)
cool
Rare sats you say? 😏
just picking up on this... looks very interesting.
on what layer are the sats held / settled ?
Glad to hear that!
According to nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 and nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg this would be an L3+
69 at least
Can't wait to be able to drop big ole nut zaps