Best way to accept #Bitcoin. No fees, no intermediary. Free, open source & self-hosted Bitcoin payment processor for self-sovereign individuals and businesses.
🚨BTCPay Server 2.4.4 is out!
A security-focused update in response to ongoing attempts to attack the project.
We recommend all server admins update.
Some changes are breaking, so please read the article before updating. Thank you to everyone helping us protect the community and for bearing with us. 💚
@FractalEncrypt Most users won't notice them, but if you use any of this functionality, you will. Those using tap-to-pay in their stores should definitely check the settings.
🚨BTCPay Server 2.4.4 is out!
A security-focused update in response to ongoing attempts to attack the project.
We recommend all server admins update.
Some changes are breaking, so please read the article before updating. Thank you to everyone helping us protect the community and for bearing with us. 💚
I promise I am working on re-enabling outside access to LND and CLN (opt-in) for docker deployments.
Meanwhile, this release is packed with security hardening. Update recommended!
Boring releases will continue for a little while as we adapt our worfklows to AI...
There is a new WHMCS v4.0.0 release die to @BtcpayServer v2.4.4 dropping support for legacy API keys. See here for more details https://t.co/1jo0nf5YPq
We’ve updated Core Lightning (CLN) to v26.06.7 in BTCPay Server’s Docker deployment.
External access to CLN remains disabled out of an abundance of caution. We expect to safely re-enable it within the next week or two.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
Note: ARM32 devices, including some older Raspberry Pis, may not work because ARM32 binaries were not distributed with this CLN release.
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
Flint is now live in the BTCPay plugin store and available to all, with a one-click install! Accept Lightning in seconds, no channels necessary.
https://t.co/Z3Ho0qMt0L
A huge thank you to the @BtcpayServer team for thorough reviews throughout the listing process 🧡
If you're running CLN, the @BtcpayServer team has prepared an update for you.
Kudos to @ndeet & @NicolasDorier for acting quickly to address the reports.
@jurbed Kudos for a great guide on alternatives for CLN to keep accepting Lightning payments during --offline time.
We've updated the default deployment, so opt-in fragment is no longer needed 🫡 https://t.co/hmCC0XawxV
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
BTCPay Server has disabled routes to Core Lightning and Eclair in its default deployment following the CLN vulnerability reports.
If you're running a BTCPay Server instance, update immediately via Server Settings or command line.
The AI-generated CVE wave hitting Lightning implementations is already forcing downstream infrastructure to respond in real time.
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
If you run Core Lightning: when the release is published: upgrade with signed binaries, or start your node with `--offline`.
Details stay under embargo for two weeks. Previous releases, including 26.04, are unsupported.
Full details when the embargo lifts. The 26.09 release is still planned for late September.
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.
Looks like a severe Core Lightning (CLN) issue was discovered.
It sounds like you should consider restarting your CLN node with `--offline` and be on the lookout for the point release coming in the next few days. (Messages from CLN discord via https://t.co/Ep9BEDQuCS).
Following public reports, we have disabled routes to CLN and Eclair in our default deployment.
To update, go to Server Settings → Maintenance → Update, or run btcpay-update(.)sh from the command line after removing the parentheses.