For example, the XPUB is stored only on the BTCPay API server in watch-only mode, which means that an infinite number of Bitcoin addresses can be generated for receiving tips while keeping everything secure.
The question is: if this is for tips (aka small amounts), why have to be onchain (for fuck sake!). BTCpay also support LN invoices, why not use that API?
Geeze guys, stop building payment solutions for onchain. Onchain will be exclusively for opening / closing LN channels. All other payments will be only through LN.
You have been warned.
Well, I completely understand your point of view but I'm currently bullish on-chain.
Also It will not actually accept small amounts , like the amount textfield will give you an error message "Please use Lightning for smaller tips." :)
reply
You will remember my words later....
reply
On-chain is great, but for instant payments, you want to dive into LN.
Mempool is full currently, that doesn't matter for LN.
reply
Yes, LN is for instant payments. But is not only about that.
What people should understand is that:
  • onchain is THE SETTLEMENT, your vault, your central bank, your holding stash that you almost not use it.
  • LN is THE FUCKING PAYMENT NETWORK, your spending pockets, your commercial bank.
You cannot have a functional money without a good payment network. And that is what it is is LN: a fucking payment network.
reply
Hello friends @DarthCoin and @sime , I'm excited to share an update on my Personal Bitcoin Tip Card project 🚀!
Thanks for your helpful feedback. So, I have added Lightning Network (LN) support to my project using LnurlPay and WebLN methods. Now, users can receive LN tips easily by updating their identity.json file with their Bitcoin Lightning Address. The Personal Bitcoin Tip Card will then create LN invoices to accept LN tips with ease.
Here is a small preview:
reply
I tipped you 10 sats via Phoenix wallet though the UI didn't update when I did.
As a tipper, I want to be informed that my tip worked.
reply
Hey, thanks for the tip! I'm sorry to hear that the UI didn't update when you tipped me. Unfortunately, I haven't implemented any functionality that can check the status of the invoice to see if it's paid or not. If you use the WebLN functionality, it will give you a paid success dialog. However, when you tip by scanning the invoice qr code, it will not show you the paid success dialog.
However, I understand your concern as a tipper, and I will definitely look into implementing a feature that can inform you when your tip has been successful. One solution that I have in mind is using the LNBits API (/api/v1/payments/<payment_hash>) endpoint to check the status of the invoice. However, this may require a different setup and may only be used for specific use cases like checking the status of invoices.
Thank you for bringing this to my attention. I will try to implement a solution that can inform you of your tip's status in the future when tipping by scanning the QR code. Any further brainstorming from your side is greatly appreciated.
reply