Can make use of this: cashubtc/nuts#21
The idea is that you can request a /melt but then immediately return. Maybe the payment state change could be communicated using a websocket. Otherwise, we can just keep on doing the pull-based state checking like we're doing it now (plus the new pending state, see PR above).
Can make use of this: cashubtc/nuts#21
The idea is that you can request a
/meltbut then immediately return. Maybe the payment state change could be communicated using a websocket. Otherwise, we can just keep on doing the pull-based state checking like we're doing it now (plus the new pending state, see PR above).