pull down to refresh
Do you feel like 'attack prevention' needs to be prioritised in the business going forward
Innocently, people sometimes begrudgingly employ cleaners but they keep back the onset of mould and harmful nasties we would only notice if they weren't there
The same could be a routine job in the digital world going forward....
Head of cyber crime lol, they'll need at least 10BTC per annum and a lexus with really shitty mpg 🤣🤣
Yea for our part we need to add more automation that could find things before others do, we've picked the low hanging fruit but it'll need constant iteration.
The business angle of these projects necessitates we offer premium services for businesses that run them. The unfortunate reality with irreversible bearer-asset money is that any business using it needs to bear some hotwallet risk if they don't want to go down the KYB/middleman path, and few will have the expertise to do so.
Prevention is one part but incident response is another.
Note the footer in our Lightning.Pub README, Lightning software has always been a target, and we've been hit before.
I commiserated with Ben Arc a few years ago at a conference once as LNbits too had been hit with nearly identical exploits.
Pub is only hard to the extent it is because it's a honeypot that's been running in the open for several years now.
Minimal damage in both cases since we treat the node accordingly, as a hot wallet in an adversarial environment. We log extensively and caught both almost as they were happening and patched within hours. The latter in particular would have earned more by asking for a bounty vs. what they stole. The first actually donated back some sats as they had to deposit to do the race and we rugged them mid-exploit.
I also run AI against our production logs to see what probing is happening and to get ideas for other things we can check.
When GLM 5.2 dropped we found a few other edgey things that weren't a risk to the operator, but to ndebits users if a linked app was hostile, and patched those.
We also recently patched something a hostile Boltz operator could have exploited found by GPT 5.6 Sol (swaps have been default-off anyway while we dogfooded, was never shipped to the front-end, and now with Boltz transitionally dead we're waiting to see what happens before we either add Loop or actually ship Boltz Swaps to the front-end)
After the 2024 attack we implemented a Watchdog service that immediately shuts down the Pub if the LND and database delta grows beyond some HTLC flap.
Won't divulge much about the LND environment itself but it's been comfy, so far.