Introducing the first option for accepting donations in akkounts: one-time donations via BTCPay.
Supports both on-chain and Lightning options. For on-chain donations, the donation is shown as pending until confirmed, while Lightning donations are confirmed instantly, of course. There is also an email notification once on-chain donations have been confirmed, so you don't have to remember to follow up on it.
Furthermore, you can choose the amount either in EUR, USD, or sats. When choosing an amount in sats, the exchange rate will be fetched after receiving the payment notification from BTCPay and added to the donation record then. When choosing a fiat amount, the conversion is already done by BTCPay, so we just add the amount of sats we see from the payment notification already.
In order to test the functionality directly against https://btcpay.kosmos.org, please DM me for a testing API key.
(This PR already includes a small refactoring commit that will make it easier to integrate the next option, which is sats directly from one's Kosmos LndHub account, which can then also be done as a monthly subscription that is automatically debited.)
Introducing the first option for accepting donations in akkounts: one-time donations via BTCPay.
Supports both on-chain and Lightning options. For on-chain donations, the donation is shown as pending until confirmed, while Lightning donations are confirmed instantly, of course. There is also an email notification once on-chain donations have been confirmed, so you don't have to remember to follow up on it.
Furthermore, you can choose the amount either in EUR, USD, or sats. When choosing an amount in sats, the exchange rate will be fetched after receiving the payment notification from BTCPay and added to the donation record then. When choosing a fiat amount, the conversion is already done by BTCPay, so we just add the amount of sats we see from the payment notification already.
In order to test the functionality directly against https://btcpay.kosmos.org, please DM me for a testing API key.
(This PR already includes a small refactoring commit that will make it easier to integrate the next option, which is sats directly from one's Kosmos LndHub account, which can then also be done as a monthly subscription that is automatically debited.)
refs #31
Isn't a amount_sats = params[:amount_sats] missing here?
I couldn't see the amount_sats being assigned anywhere other than to nil when a different currency is selected, but it is being used further down in this action.
Isn't a `amount_sats = params[:amount_sats]` missing here?
I couldn't see the `amount_sats` being assigned anywhere other than to `nil` when a different currency is selected, but it is being used further down in this action.
Good catch! Since I did actual donations using sats for the amount, it must have gotten lost for the commit somehow. Added a spec to catch that, since that spec was missing in the first place.
Good catch! Since I did actual donations using sats for the amount, it must have gotten lost for the commit somehow. Added a spec to catch that, since that spec was missing in the first place.
When trying to create a contribution I'm getting an error (see screenshot).
I'm in the Zerotier network and when I GET http://10.1.1.163:23001/api/v1/health from my computer directly, I get a correct response of
{"synchronized":true}
When I do the same from within the web container, the request times out.
When trying to create a contribution I'm getting an error (see screenshot).
I'm in the Zerotier network and when I GET `http://10.1.1.163:23001/api/v1/health` from my computer directly, I get a correct response of
```json
{
"synchronized": true
}
```
When I do the same from within the web container, the request times out.
As discussed during the last call, we'll merge this and test in production, since I am unable to debug macOS Docker issues and connecting to our private network in dev should not be a prerequisite.
As discussed during the last call, we'll merge this and test in production, since I am unable to debug macOS Docker issues and connecting to our private network in dev should not be a prerequisite.
raucao
merged commit 8b897168cc into master2024-03-13 16:31:54 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Introducing the first option for accepting donations in akkounts: one-time donations via BTCPay.
Supports both on-chain and Lightning options. For on-chain donations, the donation is shown as pending until confirmed, while Lightning donations are confirmed instantly, of course. There is also an email notification once on-chain donations have been confirmed, so you don't have to remember to follow up on it.
Furthermore, you can choose the amount either in EUR, USD, or sats. When choosing an amount in sats, the exchange rate will be fetched after receiving the payment notification from BTCPay and added to the donation record then. When choosing a fiat amount, the conversion is already done by BTCPay, so we just add the amount of sats we see from the payment notification already.
In order to test the functionality directly against https://btcpay.kosmos.org, please DM me for a testing API key.
(This PR already includes a small refactoring commit that will make it easier to integrate the next option, which is sats directly from one's Kosmos LndHub account, which can then also be done as a monthly subscription that is automatically debited.)
refs #31
@@ -10,0 +27,4 @@def createif params[:currency] == "sats"fiat_amount = nilfiat_currency = nilIsn't a
amount_sats = params[:amount_sats]missing here?I couldn't see the
amount_satsbeing assigned anywhere other than tonilwhen a different currency is selected, but it is being used further down in this action.Good catch! Since I did actual donations using sats for the amount, it must have gotten lost for the commit somehow. Added a spec to catch that, since that spec was missing in the first place.
@galfert Want to give it your stamp of approval?
When trying to create a contribution I'm getting an error (see screenshot).
I'm in the Zerotier network and when I GET
http://10.1.1.163:23001/api/v1/healthfrom my computer directly, I get a correct response ofWhen I do the same from within the web container, the request times out.
Code looks alright. Wasn't able to test it yet, because of the error I commented above.
As discussed during the last call, we'll merge this and test in production, since I am unable to debug macOS Docker issues and connecting to our private network in dev should not be a prerequisite.