elementsproject / paypercall Goto Github PK

Useful to reduce lightning fees even further, if you know ahead of time that you're going to send lots of API requests.

Might make sense to let the service operator set some discount for bulk orders, too.

Would significantly improve the privacy of API consumers by unlinking the lightning payment from the API invocation.

Allow services to signal that API execution has failed, which should free up the payment token and allow it to be used for another API call.

• If the X-Charge response header is set to yes, consider the request a success and mark the payment token as spent. If the X-Charge header is set to any other value (normally no), consider the request a failure and mark the payment token as usable.

• If the X-Charge response header is not specified,

  • If the --explicit-charge config option is set, consider the request a failure.

  • If the --explicit-charge config option is not set, consider the request a success if the status code is 2xx or 3xx, otherwise consider it a failure.

Freeing up the payment token means removing it from the spent table, which means we should log the execution error to a separate (new) table.

Hello,

This repository is listed on the Awesome Lightning-Network list, which is a collection of useful lightning-network projects. However, it seems that the 'lightning-network' topic is missing from this repository's topics.

Adding the 'lightning-network' topic will help users discover your project more easily and recognize its relevance to the lightning-network ecosystem. To add the topic, please follow these steps:

1. Navigate to the main page of the repository.
2. Click on the gear icon next to "About" on the right side of the page.
3. In the "Topics" section, type 'lightning-network' and press Enter.
4. Click "Save changes."

Thank you for your attention and for contributing to the lightning-network community!