I can't wait to learn more about this and if we can use this to make zaps even easier for new users.
Discussion
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
👀