Nostr Web Client

A WebSocket stream would quickly get out of hand on the server for a large mint. The Nostr integration is interesting as it effectively outsources the horizontal scaling of the WebSocket stream idea to relays. I can help if you want to collaborate.

x 1y ago 💬 2

We could write a NUT. I assume some we can use some already established event kind (was thinking kind 30078, application-specific data) so as to avoid having to write a NIP as well.

Reply to this note

Please Login to reply.

Discussion

David Caseria 1y ago

I'm a little confused about the intended use case for kind 30078 events. Is it meant for end-user applications? If so, would it be better to have a dedicated event kind for this instead?

What do you think about events for each operation: mint, melt, and swap? It would publicly announce the mint's liabilities and determine when a proof was claimed. I'm unsure if that's ideal or if it's expanding the scope too much. I'm also unsure how best to handle proof of assets and liabilities for a mint, but it may be best to figure out a comprehensive solution.

nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg do you have any thoughts?

x 1y ago 💬 1

> What do you think about events for each operation

In theory it wouldn't benefit the PoL scheme but in practice maybe it could make it more feasible to execute, if that's what you were referring to.

David Caseria 1y ago

Good point. It probably makes more sense to keep this focused on your original idea