There is no need to: competition will naturally arise.
Hopefully one day everyone accepts Bitcoin payments.
I wish bitrefill would add the option to pay with Ecash... Then I can say I was the first to buy pizzas with cashu.
I have already tried that. https://github.com/lollerfirst/nutshell/tree/sliding-bloom-filter
The mint could still link sender and receiver with high probabilityy.
High grade uranium refinery reactors. They have nuclear weapons.
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?
> 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.
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.
With cashu there's always been a dilemma when sending ecash to someone: did they claim the payment?
Sure a wallet can ask the mint if a certain set of tokens were spent, but that creates a link between the sending and receiving wallet. It's a leak of information that loses you privacy.
A first solution, although maybe impractical, would be to let the mint stream the information about all the spent tokens to clients that request them (through apposite WebSocket endpoints).
So If I am a wallet and I have just sent some e-cash to someone, I can connect to the mint and "listen" until I am satisfied (until I know the e-cash was claimed).
This could put some pressure on the mint and it's not clear to me if it could be used to perform some DoS attack.
A better approach could leverage Nostr!
A mint with that advertises its associated `npub` on the `/v1/info` API endpoint could then regularly publish notes with all the information about freshly spent e-cash.
Clients would just have to query for notes with a `p` tag referencing the `npub` of the mint and look for the e-cash they just sent. Easy.
The idea we can cut any sort of government spending through voting is laughable. In fact, the idea you can change anything by voting also is laughable.
Can't even take care of myself. Wouldn't want to know how I would fare with having kids.
Have never touched an Apple product in my life not even with a stick so I wouldn't know
