Correct. Encrypted, with an optional passohrase , on some user-selected relays.
Discussion
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.
