DevilishLemonBar πŸ¦₯βš‘πŸ³οΈβ€πŸŒˆ's avatar
DevilishLemonBar πŸ¦₯βš‘πŸ³οΈβ€πŸŒˆ
_@slothy.win
npub1y3k2...vp4j
Electrical "Engineer" Aggie'20. Onlyfans (NSFW): http://tx.ag/Igebcre ⚑Node (shutdown): 03817596435f25a156da4a89c9dabf2a3e4f9a74418543f3de6b77cab780a473a1 Ω…ΩŽΨ³Ω’ΩƒΩΩˆΩ†ΩŒ Ω‡ΩŽΨ°ΩŽΨ§ الجِنُّ بِΨ₯ِنْسْ.
Zero announcement / advisory notice / blog post or any indication of the vulnerability on BTCPay Server's website other than the post on X. It has been 4 hours. If this is how they operate, I advise you all to just pull the plug and shut your BTCPay instances down.
Friendly reminder that even in 2013, RNG bugs had a response with much better user UX, often indicating that a new seed is required, and guiding users to migrate funds. Yes, with a hardware wallet this is slightly more complicated, but if something like Bitkey can handle seamless seed refreshes and fund migration (ex: the enhanced privacy upgrade) then others can. Every hardware signer should have some form of official companion app that can make these flows possible for the average non-technical user.
↑