Replying to Avatar lemon

I see it in all of its glory!

So on the downloader side for the archive files: is it just constantly seeking updates from uploader relays for published events?

I didn’t notice any payment actions at first, but watching again I see the wallet balance change as the file is chunked and then reassembled

Is this done with a nip60 e-cash integration?

In this example, both wallets started with 120 sats each and ended with 112 sats. Is that because other blossom servers were involved and took a cut at both ends (as opposed to funds just flowing from one user to one server)?
Avatar
Leito 1y ago

We are using X-Cashu. We just put the ecash on the call for upload when the blossom returns a 402-Payment Required code (Blossom returns upload prices).

No NIP 60 is needed in this case because we are connecting directly to the server.

This Blossom Server was configed to charge on Download and Upload.

The "Downloader" did not have the file so it paid for the chunks individually.

The nostr file is just for the front end to know how to rebuild the file.

Reply to this note

Please Login to reply.

Discussion

No replies yet.