pull down to refresh
Looking at the patch commits it seems that an attacker could glean connection details to the backing node
You wouldn't want to receive a payment with an attacker lying in wait, definitely update, and I'd recommend rotating the connection credentials to the backing node
Yes, with NWC and set it to deposit only, but the NWC plugin in BTCpay is a bit buggy.
@AG, did you experience situations where customers paid the invoice in BTCpay (configured NWC with Rizful), the payment arrived, but it didn't show as settled in the dashboard? On the Customer side, it also didn't show anything after the invoice was paid.
I think is a issue with NWC in general. The only issue we had was with a new pseudo plugin that supposed to use cashu, but instead it turned on the nwc backup mode and the transaction was a mess. It showed paid in the customer side, but we would not be able to trace back the payments.
We had to open an issue with the service provider and maintainer of the mint and nostr relay transmitting via nwc to have the payment localized and manually added in our account transactions.
Nwc is buggy because it relies on nostr relays, indeed just one nostr relay set by the provider, and the provider can see all the transactions. From what I know is not good for privacy either, but am not that technically literate to judge either.
Not sure it can improve, from my understanding is on the relay maintainer to ensure this type of info get transmitted correctly.
For us was really bad too and not seeing the transaction in our side we could not tell if the customer was right or not. But customer is always right, so we did well listening and learning from it.
What I can suggest, in case you are not directly managing your business and payments infrastructure (that's a hell of a job itself), contact the service provider and ask them directly as soon as possible and provide clear info to your customer.
Hope all resolve well in your side, if I can help with anything, let me know :)
Sounds good based on what I've seen 👍
Bitcoin is def not for the weaks, a new hack each day...😂
I guess it's the red team hardening bitcoin projects against new LLM vulnerabilities discoveries
Fun fact: all those "discoveries" were made by the same LLM / AI agents.
So now humans are working double to fix what they should be done by them in the first place.
Very good efficiency in coding, right.
Yes — the balance in the hot wallet is not the whole exposure.
The hole is in BTCPay's own admin/API auth, not in the wallet. Someone who gets in can change where future money goes: the store's derivation scheme / payout settings. Your invoices keep being generated and paid by customers, and the funds land on an xpub that is not yours. An empty wallet today does not protect next week's sales.
Two other things leak that have nothing to do with balance: your invoice history (customer emails, addresses, order amounts) and any connected node credentials, which is why the LND macaroon rotation advice is in there.
So: update, then change the password, then re-check that your store's wallet xpub is still the one your hardware wallet shows. That last step is the one people skip and it is the one that costs you money quietly.
If there isn't much sats in the linked wallet, is it still need to do anything? 😅