-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Handling fees #7
Comments
I am not sure I will have time to address the fee issue. |
there are some new extensions that do split payments, i am not sure how stable they are but there isn't anything for custom fees for groups of users. e.g. members have discounted fees vs public. Perhaps a new extension will need to be written for LNBits. |
At the moment, putting 100 SAT into the account and creating a Laisee over 100 SAT will result in an error. We should encourage at least a 1% "buffer" for fees in the account, as defined by LNBits |
Added 1 sat default fee for now, it appears to work on lnpay.co back end, please test on your intsance. @Liongrass |
Refactor Laiseebot to use split payments extension, should be stable enough now, as of 20 Apr 2023. (I hope). Also see article https://bitkarrot.substack.com/p/lightning-prisms-with-lnbits |
We could create a lnbits user account for @laiseebot
Everytime the bot creates a Laisee, it first sends the appropriate fee to the @laiseebot, as if the laiseebot was another user. This can happen silently in the background.
The text was updated successfully, but these errors were encountered: