nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv I really like the idea behind the minibits ln address to cashu mint flow, and it made me think about this: is there a way to achieve the same thing, but without being dependent from a specific wallet app (nothing against minibits in particular, I am just reasoning about this from a general point of view). So a ln address service that will lock all the received sats on a user specified cashu mint based on some logic (nostr pubkey, wallet seed, etc...). I might be saying stupid things here as I am not an expert on these topics, but I like the general idea.
Discussion
The flow is as follows:
1. Address is parsed by the wallet and Lnurl well-known link is constructed
2. Lnurl link is requested by sender wallet, retrieving min/max limits and an url to get invoice next
3. Invoice for specific amount is requested by wallet. Server requests quote from the mint that includes an invoice and est fee and passes that to the senderwallet. Server stores related data.
4. Server checks with the mint if an invoice has been paid.
5. If so, server constructs blinded messages for paid amount and asks mint for ecash
6. Server stores retrieved ecash and uses some way (push message+claim api or nostr dm) to send the ecash to the receiving wallet.
7. Wallet receives (swaps ecash for fresh notes with the mint)
So eventually this could be generalized in terms of mints. Because server needs to know how to reach recieving wallet, not sure it can be easily done on the receiving wallet side.